Fix typos

Author: ebariaux

Sources/EmbeddedSwift/Documentation.docc/CompilerDetails/ABI.md

@@ -30,7 +30,7 @@ The layout of Embedded Swift's class metadata is *different* from full Swift:
 - The **destructor pointer** is stored at **offset 1**. This function is invoked by Swift's deallocator when the class instance is destroyed.
 - The **ivar destroyer** is stored at **offset 2**. This function is invoked to destroy instance members when creation of the object is cancelled (e.g. in a failable initializer).
 - Lastly, the **vtable** is stored at **offset 3**: For each Swift class in the class's inheritance hierarchy, in order starting
-  from the root class and working down to the most derived class, the function pointers to the implementation of every method of the class in declaration order in stored.
+  from the root class and working down to the most derived class, the function pointers to the implementation of every method of the class in declaration order is stored.
 
 ### Witness Tables ABI
 

Sources/EmbeddedSwift/Documentation.docc/GettingStarted/Introduction.md

@@ -22,7 +22,7 @@ It's also a good mental model to think of the Swift compiler in Embedded Swift m
 This results in properties that are a great fit for embedded software development:
 
 - **Small binaries** that can be as tiny as a few hundred bytes for "Hello World"-like programs (fully self-contained).
-- **No hidden runtime costs** – Embedded Swift's runtime library does not manage any data structures behind your back, is itself less than a kilobyte in size, and it eligible to be removed if unused.
+- **No hidden runtime costs** – Embedded Swift's runtime library does not manage any data structures behind your back, is itself less than a kilobyte in size, and is eligible to be removed if unused.
 - **No hidden allocations** which would cause unpredictable performance cliffs.
 - **Full C/C++ interoperability** to directly interact with existing C libraries and hardware-specific code, making it easy to integrate with vendor SDKs.
 - **Modern language features** like optionals, generics, and strong type safety are all available in Embedded Swift.

Sources/EmbeddedSwift/Documentation.docc/GuidedExamples/PicoGuide.md

@@ -49,7 +49,7 @@ bin/                                               libexec/
 ## Building a "blinky" embedded app
 
 The standard "Hello, World" in embedded development is a program that repeatedly blinks an LED. Let's build one. The following setup can be also found in [swift-embedded-examples](https://github.com/apple/swift-embedded-examples/blob/main/pico-blink-sdk/README.md), but we're going to show below that all you need is just three files.
-Let's create a new empty directory and prepare a simple structure for a CMake-based project that can be used on top the Pico SDK:
+Let's create a new empty directory and prepare a simple structure for a CMake-based project that can be used on top of the Pico SDK:
 
 ```
 embedded-swift-tutorial