Merge branch 'master' into skade-patch-2

beginner-workshop/src/SUMMARY.md

@@ -14,5 +14,5 @@
 - [Radio Out](./radio-out.md)
 - [Radio In ](./radio-in.md)
 - [Radio Puzzle](./radio-puzzle.md)
-- [Starting a Project from Scatch](./from-scatch.md)
-- [References and Ressources](./references-ressources.md)
+- [Starting a Project from Scratch](./from-scatch.md)
+- [References and Resources](./references-ressources.md)

beginner-workshop/src/from-scratch.md

@@ -1,4 +1,4 @@
-# Starting a Project from Scatch
+# Starting a Project from Scratch
 
 So far we have been using a pre-made Cargo project to work with the nRF52840 DK. In this section we'll see how to create a new embedded project for any microcontroller.
 

beginner-workshop/src/references-resources.md

@@ -1,4 +1,4 @@
-# References and Ressources
+# References and Resources
 
 - [nRF52840 Product Specification 1.1](https://infocenter.nordicsemi.com/pdf/nRF52840_PS_v1.1.pdf)
 - The [Embedded Rust Book][embedded rust] is a great learning resource, especially the Concurrency chapter.

beginner-workshop/src/running-from-vsc.md

@@ -1,4 +1,4 @@
-# Runnging the Program from VS Code
+# Running the Program from VS Code
 
 Both `cargo-embed` and `cargo-flash` are tools based on the `probe-rs` library. This library exposes an API to communicate with the J-Link and perform all the operations exposed by the JTAG protocol. For this workshop we have developed a small Cargo runner that uses the `probe-rs` library to streamline the process of running a program and printing logs, like `cargo-embed`, while also having better integration into VS code.
 
@@ -26,4 +26,4 @@ stack backtrace:
 
 `cargo run` will compile the application and then invoke the `dk-run` tool with its argument set to the path of the output ELF file.
 
-Unlike `cargo-embed`, `dk-run` will terminate when the program reaches a breakpoint (`asm::bkpt`) that halts the device. Before exiting `dk-run` will print a stack backtrace of the program starting from the breakpoint. This can be used to write small test programs that are meant to perform some work and then terminate.
+Unlike `cargo-embed`, `dk-run` will terminate when the program reaches a breakpoint (`asm::bkpt`) that halts the device. Before exiting `dk-run` will print a stack backtrace of the program starting from the breakpoint. This can be used to write small test programs that are meant to perform some work and then terminate.

beginner-workshop/src/viewing-logs.md

@@ -16,4 +16,4 @@ This command will bring up a Text User Interface (TUI). You should see "Hello, w
 chip = "nRF52840_xxAA"
 ```
 
-Logging is implemented using the Real Time Transfer (RTT) protocol. Under this protocol the target device writes log messages to a ring buffer stored in RAM; the PC communicates with the J-Link to read out log messages from this ring buffer. This logging approach is non-blocking in the sense that the target device does not have to wait for physical IO (USB comm, serial interface, etc.) to complete while logging messages since they are written to memory. It is possible, however, for the target device to overrun the ring buffer; this causes old log messages to be overwritten.
+Logging is implemented using the Real Time Transfer (RTT) protocol. Under this protocol the target device writes log messages to a ring buffer stored in RAM; the PC communicates with the J-Link to read out log messages from this ring buffer. This logging approach is non-blocking in the sense that the target device does not have to wait for physical IO (USB comm, serial interface, etc.) to complete while logging messages since they are written to memory. It is possible, however, for the target device to run out of space in its logging ring buffer; this causes old log messages to be overwritten.