summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDario Nieuwenhuis <dirbaio@dirbaio.net>2022-01-16 12:06:04 +0100
committerGitHub <noreply@github.com>2022-01-16 12:06:04 +0100
commit06816cdc34dd9d90d8d47c0e4a5bd7914efa8eac (patch)
tree39d8f529763b15f4bbe7485952a364e9437b3991
parentad1f542aacc35f1c7d8d0ae046f9c3edabe420c1 (diff)
parent08b65ffd6c97f268546086d33401adaca80338ed (diff)
downloadnrf-softdevice-06816cdc34dd9d90d8d47c0e4a5bd7914efa8eac.zip
Merge pull request #94 from danbev/typos_readme
Fix typos in README.md
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index 9defc17..626ce80 100644
--- a/README.md
+++ b/README.md
@@ -85,7 +85,7 @@ To run an example, simply use `cargo run` from the `examples` folder:
The first thing to do is find out how much flash the SoftDevice you've chosen uses. Look in the release notes, or google for your SoftDevice version and "memory map". For an s132 v7.3 its listed as 0x26000, or in human readable numbers 152K (0x26000 in hex is 155648 in decimal / 1024 bytes = 152K)
-Set the memory.x to move your applications flash start to after the SoftDevice size and subtract it from the total avialable size:
+Set the memory.x to move your applications flash start to after the SoftDevice size and subtract it from the total available size:
```bash
MEMORY
@@ -140,7 +140,7 @@ pub fn embassy_config() -> embassy_nrf::config::Config {
## Troubleshooting
-If your SoftDevice is hardfaulting on enable and you think you have everything right, mak sure to go back and do a full chip erase or recover, and reflash the SoftDevice again. A few bytes of empty space after the SoftDevice are required to be 0xFF, but might not be if the softdevice was flashed over an existing binary.
+If your SoftDevice is hardfaulting on enable and you think you have everything right, make sure to go back and do a full chip erase or recover, and reflash the SoftDevice again. A few bytes of empty space after the SoftDevice are required to be 0xFF, but might not be if the softdevice was flashed over an existing binary.
If the following linking error occurs
```