Skip to content

Commit 91ddc66

Browse files
authored
Merge pull request #235 from MFAshby/doc_correction
Small correction to git URL in documentation files
2 parents 405c85c + bca7ba4 commit 91ddc66

6 files changed

Lines changed: 11 additions & 11 deletions

File tree

.github/workflows/main.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# GitHub Actions Workflow to build FreeRTOS Firmware for PineTime Smart Watch
22
# See https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud
3-
# Based on https://github.com/JF002/Pinetime/blob/master/doc/buildAndProgram.md
4-
# and https://github.com/JF002/Pinetime/blob/master/bootloader/README.md
3+
# Based on https://github.com/JF002/InfiniTime/blob/master/doc/buildAndProgram.md
4+
# and https://github.com/JF002/InfiniTime/blob/master/bootloader/README.md
55

66
# Name of this Workflow
77
name: Build PineTime Firmware

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
# PineTime
33

4-
![Build PineTime Firmware](https://github.com/JF002/Pinetime/workflows/Build%20PineTime%20Firmware/badge.svg?branch=master)
4+
![Build PineTime Firmware](https://github.com/JF002/InfiniTime/workflows/Build%20PineTime%20Firmware/badge.svg?branch=master)
55

66
> The PineTime is a free and open source smartwatch capable of running custom-built open operating systems. Some of the notable features include a heart rate monitor, a week-long battery as well as a capacitive touch IPS display that is legible in direct sunlight. It is a fully community driven side-project, which means that it will ultimately be up to the developers and end-users to determine when they deem the PineTime ready to ship.
77

doc/buildAndProgram.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@ To build this project, you'll need:
88
## Build steps
99
### Clone the repo
1010
```
11-
git clone https://github.com/JF002/Pinetime.git
12-
cd Pinetime
11+
git clone https://github.com/JF002/InfiniTime.git
12+
cd InfiniTime
1313
git submodule update --init
1414
mkdir build
1515
cd build

doc/contribute.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# How to contribute?
22
## Report bugs
3-
You use your Pinetime and find a bug in the firmware? [Create an issue on Github](https://github.com/JF002/Pinetime/issues) explaining the bug, how to reproduce it, the version of the firmware you use...
3+
You use your Pinetime and find a bug in the firmware? [Create an issue on Github](https://github.com/JF002/InfiniTime/issues) explaining the bug, how to reproduce it, the version of the firmware you use...
44
## Write and improve documentation
55
Documentation might be incomplete, or not clear enough, and it is always possible to improve it with better wording, pictures, photo, video,...
66

@@ -41,4 +41,4 @@ The most important rule to follow is to try to keep the code as easy to read and
4141
- **Include guard** : `#pragma once` (no `#ifdef __MODULE__ / #define __MODULE__ / #endif`)
4242
- **Includes** :
4343
- files from the project : `#include "relative/path/to/the/file.h"`
44-
- external files and std : `#include <file.h>`
44+
- external files and std : `#include <file.h>`

doc/filesInReleaseNotes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
# Using the releases
2-
For each new *stable* version of Pinetime, a [release note](https://github.com/JF002/Pinetime/releases) is created. It contains a description of the main changes in the release and some files you can use to flash the firmware in your Pinetime.
2+
For each new *stable* version of Pinetime, a [release note](https://github.com/JF002/InfiniTime/releases) is created. It contains a description of the main changes in the release and some files you can use to flash the firmware in your Pinetime.
33

44
This page describes the files from the release notes and how to use them.
55

6-
**NOTE :** the files included in different could be different. This page describes the release note of [version 0.7.1](https://github.com/JF002/Pinetime/releases/tag/0.7.1), which is the version that'll probably be pre-programmed at the factory for the next batch of Pinetime devkits.
6+
**NOTE :** the files included in different could be different. This page describes the release note of [version 0.7.1](https://github.com/JF002/InfiniTime/releases/tag/0.7.1), which is the version that'll probably be pre-programmed at the factory for the next batch of Pinetime devkits.
77

88
## Files included in the release note
99

doc/gettingStarted/gettingStarted.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ If you just want to flash or upgrade InfiniTime on your PineTime, this page is f
88
- [How to flash InfiniTime using the SWD interface](#how-to-flash-infinitime-using-the-swd-interface)
99

1010
## InfiniTime releases and versions
11-
All releases of InfiniTime are available on the [release page of the GitHub repo](https://github.com/JF002/Pinetime/releases).
11+
All releases of InfiniTime are available on the [release page of the GitHub repo](https://github.com/JF002/InfiniTime/releases).
1212

1313
Versions that are tagged as **RELEASE CANDIDATE** are pre-release versions, that are available for testing before actually releasing a new stable version. If you want to help us debug the project and provide stable versions to other user, you can use them. If you want stable and tested version, you should not flash these release candidate version.
1414

@@ -98,4 +98,4 @@ Launch NRFConnect, tap the sandwish button on the top left and select *Configure
9898

9999
Tap *Add service* and select the server configuration *Current Time service*. Tap OK and connect to your PineTime, it should automcatically sync the time once the connection is established!
100100

101-
![NRFConnect CTS 1](nrfconnectcts1.jpg)
101+
![NRFConnect CTS 1](nrfconnectcts1.jpg)

0 commit comments

Comments
 (0)