diff --git a/documentation/guides/getting-started.md b/documentation/guides/getting-started.md
index 5b3f0fd2e..ac4f6cc30 100644
--- a/documentation/guides/getting-started.md
+++ b/documentation/guides/getting-started.md
@@ -22,7 +22,7 @@ Or for a TypeScript starter:
 
 ## Learn Solid
 
-Solid is all about small composable pieces that serve as building blocks for our applications. These pieces are mostly functions and in so Solid has many shallow-top level APIs. Fortunately to start you won't need to know about most of them.
+Solid is all about small composable pieces that serve as building blocks for our applications. These pieces are mostly functions with many shallow-top level APIs. Fortunately to start you won't need to know about most of them.
 
 The two main types of blocks you have at your disposal are Components and Reactive Primitves.
 
@@ -38,7 +38,7 @@ function MyComponent(props) {
 
 Components are lightweight as they are not stateful themselves and have no instances but instead serve as factory functions for our DOM elements and reactive primitives.
 
-Solid's fine-grained reactivity is built on 3 simple primitives, Signals, Memos, and Effects. They form an auto-tracking synchronization engine that ensures your view stays up to date. Reactive computations take the form of simple function-wrapped expressions that executes synchronously.
+Solid's fine-grained reactivity is built on 3 simple primitives, Signals, Memos, and Effects. They form an auto-tracking synchronization engine that ensures your view stays up to date. Reactive computations take the form of simple function-wrapped expressions that execute synchronously.
 
 ```js
 const [first, setFirst] = createSignal("JSON");
@@ -61,7 +61,7 @@ Declarative data is the practice of tying the description of data’s behavior t
 
 ### 2. Vanishing Components
 
-It's hard enough to structure your components without taking updates into consideration. Solid updates completely independent of the components. Component functions are called once and then cease to exist. Components exists to organize your code and not much else.
+It's hard enough to structure your components without taking updates into consideration. Solid updates are completely independent of the components. Component functions are called once and then cease to exist. Components exists to organize your code and not much else.
 
 ### 3. Read/Write segregation