summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorTim Gates <tim.gates@iress.com>2021-09-14 04:02:53 +1000
committerGitHub <noreply@github.com>2021-09-13 20:02:53 +0200
commit84a93b54410681ce1aaae80ba7a7e6d3300dcfa1 (patch)
tree6d4e438a2c2012b94dbb5b9f03635f513b7f25ee /doc
parentc9aeef94ea824ad7304ca3f0bd76a476f4744ff4 (diff)
docs: Fix a few typos (#606)
* docs: Fix a few typos There are small typos in: - doc/versioning.md - src/components/ble/NimbleController.cpp - src/libs/mynewt-nimble/CODING_STANDARDS.md - src/libs/mynewt-nimble/docs/btshell/btshell_GAP.rst - src/systemtask/SystemTask.cpp Fixes: - Should read `milliseconds` rather than `miliseconds`. - Should read `unnecessary` rather than `uncesseray`. - Should read `target` rather than `tharget`. - Should read `project` rather than `projct`. - Should read `preferred` rather than `prefered`. - Should read `functioning` rather than `functionning`. - Should read `forever` rather than `forver`. - Should read `existing` rather than `exisiting`.
Diffstat (limited to 'doc')
-rw-r--r--doc/versioning.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/versioning.md b/doc/versioning.md
index b08af714..48e05043 100644
--- a/doc/versioning.md
+++ b/doc/versioning.md
@@ -3,4 +3,4 @@ The versioning of this project is based on [Semantic versionning](https://semver
- The **patch** is incremented when we fix a bug on a **released** version (most of the time using a **hotfix** branch).
- The **minor** is incremented when we release a new version with new features. It corresponds to a merge of **develop** into **master**.
- - The **major** should be incremented when a breaking change is made to the application. We still have to define what is a breaking change in the context of this project. For now, I suggest that it stays **0** until we have a fully functionning firmware suited for the final user. \ No newline at end of file
+ - The **major** should be incremented when a breaking change is made to the application. We still have to define what is a breaking change in the context of this project. For now, I suggest that it stays **0** until we have a fully functioning firmware suited for the final user. \ No newline at end of file