Fix typos

Author: fhammerschmidt

_blogposts/2023-06-05-first-class-dynamic-import-support.mdx

@@ -91,7 +91,7 @@ module LazyTitle = {
 let titleJsx = <LazyTitle text="Hello!" />
 ```
 
-That's all the code we need! The new `<LazyTitle />` component behaves exactly the same as the wrapped `<Title />` component, but will be lazy loaded via React's built in lazy mechanism.
+That's all the code we need! The new `<LazyTitle />` component behaves exactly the same as the wrapped `<Title />` component, but will be lazy loaded via React's built-in lazy mechanism.
 
 Needless to say, all the code examples you've seen so far are fully type-safe.
 
@@ -132,7 +132,6 @@ Feel free to try out our new dynamic import feature with the latest beta release
 
 Please note that this release is only intended for experiments and feedback purposes.
 
-
 ## Conclusion
 
 The most important take away of the new dynamic imports functionality in ReScript is that you'll never need to care about _where_ what you're importing is located on the file system - the compiler already does it for you.

pages/docs/manual/latest/equality-comparison.mdx

@@ -122,4 +122,4 @@ For small objects it can be 2x times faster than alternative deep compare functi
 
 For larger objects instead of using `==` you could manually use a faster alternative such as [fast-deep-compare](https://www.npmjs.com/package/fast-deep-equal), or write a custom comparator function.
 
-[This repo](https://github.com/jderochervlk/rescript-perf) has benchmarks comparing results of different libraries compared to ReScript's built in equality function.
+[This repo](https://github.com/jderochervlk/rescript-perf) has benchmarks comparing results of different libraries compared to ReScript's built-in equality function.

pages/docs/manual/latest/promise.mdx

@@ -24,7 +24,7 @@ type user = {name: string}
 let fetchUser: string => promise<user>
 ```
 
-To work with promise values (instead of using `async` / `await`) you may want to use the built in `Promise` module. 
+To work with promise values (instead of using `async` / `await`) you may want to use the built-in `Promise` module. 
 
 ## Promise
 

pages/docs/manual/latest/variant.mdx

@@ -365,7 +365,7 @@ Here's a list of all possible things you can unbox:
 - `string`: `String(string)`
 - `float`: `Float(float)`. Note you can only have one of `float` or `int` because JavaScript only has `number` (not actually `int` and `float` like in ReScript) so we can't disambiguate between `float` and `int` at runtime.
 - `int`: `Int(int)`. See note above on `float`.
-- `bigint`: `BigInt(int)`. **Since 11.1** This is a distinct type from JavaScripts `number` type so you can use it beside either `float` or `int`.
+- `bigint`: `BigInt(int)`. **Since 11.1** This is a distinct type from JavaScript's `number` type so you can use it beside either `float` or `int`.
 - `bool`: `Boolean(bool)`
 - `array<'value>`: `List(array<string>)`
 - `('a, 'b, 'c)`: `Tuple((string, int, bool))`. Any size of tuples works, but you can have only one case of array or tuple in a variant. 

pages/docs/manual/v10.0.0/promise.mdx

@@ -24,7 +24,7 @@ type user = {name: string}
 let fetchUser: string => promise<user>
 ```
 
-To work with promise values (instead of using `async` / `await`) you may want to use the built in `Js.Promise2` module. 
+To work with promise values (instead of using `async` / `await`) you may want to use the built-in `Js.Promise2` module. 
 
 ## Js.Promise2
 

pages/docs/react/latest/lazy-components.mdx

@@ -39,6 +39,6 @@ module LazyTitle = {
 let titleJsx = <LazyTitle text="Hello!" />
 ```
 
-That's all the code we need! The new `<LazyTitle />` component behaves exactly the same as the wrapped `<Title />` component, but will be lazy loaded via React's built in lazy mechanism.
+That's all the code we need! The new `<LazyTitle />` component behaves exactly the same as the wrapped `<Title />` component, but will be lazy loaded via React's built-in lazy mechanism.
 
 > You can read more about `Js.import` and dynamic import in ReScript in [this part of the documentation](/docs/manual/latest/import-from-export-to-js#dynamic-import).

pages/docs/react/latest/migrate-react.mdx

@@ -34,7 +34,6 @@ or, to keep using the legacy `React.createElement` API like with JSX v3:
 }
 ```
 
-
 ### File-level config
 
 The top-level attribute `@@jsxConfig` is used to update the `jsx` config for the rest of the file (or until the next config update). Only the values mentioned are updated, the others are left unchanged.
@@ -73,7 +72,7 @@ JSX v3 is still available with the latest version of compiler and rescript-react
 }
 ```
 
-To build certain dependencies in v3 compatibility mode, whatever the version used in the root project, use `"v3-dependencies"`. The listed dependencies will be built in v3 mode, and in addition `-open ReactV3` is added to the compiler options.
+To build certain dependencies in v3 compatibility mode, whatever the version used in the root project, use `"v3-dependencies"`. The listed dependencies will be built-in v3 mode, and in addition `-open ReactV3` is added to the compiler options.
 
 ## Migration of v3 components
 
@@ -230,7 +229,6 @@ module Comp = {
 }
 ```
 
-
 ### Bindings to JS components with optional props
 
 Previously, you could wrap optional props with an explicit `option` when writing bindings to JS components. This approach functioned only due to an implementation detail of the ppx in JSX 3; it's not how to correctly write bindings to a function with optional arguments.

pages/docs/react/v0.11.0/migrate-react.mdx

@@ -84,7 +84,7 @@ JSX v3 is still available with the latest version of compiler and rescript-react
 }
 ```
 
-To build certain dependencies in V3 compatibility mode, whatever the version used in the root project, use `"v3-dependencies"`. The listed dependencies will be built in V3 mode, and in addition `-open ReactV3` is added to the compiler options.
+To build certain dependencies in V3 compatibility mode, whatever the version used in the root project, use `"v3-dependencies"`. The listed dependencies will be built-in V3 mode, and in addition `-open ReactV3` is added to the compiler options.
 
 ## Migration of V3 components
 
@@ -241,7 +241,6 @@ module Comp = {
 }
 ```
 
-
 ### Bindings to JS components with optional props
 
 Previously, you could wrap optional props with an explicit `option` when writing bindings to JS components. This approach functioned only due to an implementation detail of the ppx in JSX 3; it's not how to correctly write bindings to a function with optional arguments.

pages/docs/reason-compiler/latest/build-advanced.mdx

@@ -9,24 +9,24 @@ You might use some pre-processor to generate boilerplate code during development
 - System-dependent, which should be delayed until running on user machines.
 - System-independent: lex, yacc, m4, re2c, etc, which can be executed any time.
 
-BS has built in support for [conditional compilation](conditional-compilation.md), which satisfies the first point. This section is about the second point.
+BS has built-in support for [conditional compilation](conditional-compilation.md), which satisfies the first point. This section is about the second point.
 
 An example, where bsb uses [ocamlyacc](http://caml.inria.fr/pub/docs/manual-ocaml-4.00/manual026.html):
 
 ```json
 {
-  "generators" : [
+  "generators": [
     {
-      "name" : "ocamlyacc",
+      "name": "ocamlyacc",
       "command": "ocamlyacc $in"
     }
   ],
-  "sources" : {
-    "dir" : "src",
-    "generators" : [
+  "sources": {
+    "dir": "src",
+    "generators": [
       {
-        "name" : "ocamlyacc",
-        "edge" : ["test.ml", "test.mli", ":", "test.mly"]
+        "name": "ocamlyacc",
+        "edge": ["test.ml", "test.mli", ":", "test.mly"]
       }
     ]
   }
@@ -41,7 +41,7 @@ When developing a project, `bsb` will track the dependencies between `test.ml` a
 
 ```json
 {
-  "cut-generators" : true
+  "cut-generators": true
 }
 ```
 

pages/docs/reason-compiler/latest/compiler-architecture-principles.mdx

@@ -9,7 +9,7 @@ Source Language
   v
 Surface Syntax Tree
   |
-  | (built in Syntax tree transformation)
+  | (built-in Syntax tree transformation)
   v
 Surface Syntax Tree
   |