Last adaptions for introduction / getting-started

Author: ryyppy

pages/docs/gentype/latest/getting-started.mdx

@@ -16,7 +16,7 @@
 
 `bs-platform` 8.0.0 or higher: use `genType` 3.26.0 or higher.
 
-For earlier versions, check the [genType repository README](https://github.com/reason-association/genType).
+For earlier versions, check the [genType README requirements section](https://github.com/reason-association/genType#requirements).
 
 </Warn>
 

pages/docs/gentype/latest/introduction.mdx

@@ -1,22 +1,28 @@
 # GenType
 
-`genType` lets you export ReScript values and types to use in JavaScript, and import JavaScript values and types into ReScript, idiomatically. Converter functions between the two representations are generated based on the type of the value. The converters can be generated in vanilla JavaScript, or in [TypeScript](https://www.typescriptlang.org/) / [Flow](https://flow.org/en/) for a type-safe idiomatic interface.
+`genType` is a code generation tool that lets you export ReScript values and types to use in JavaScript, and import JavaScript values and types into ReScript.
+
+Converter functions between the two representations are generated based on the type of the value. The converters can be generated in vanilla JavaScript, or in [TypeScript](https://www.typescriptlang.org/) / [Flow](https://flow.org/en/) for a type-safe idiomatic interface.
 In particular, conversion of [ReasonReact](https://reasonml.github.io/reason-react/) components both ways is supported, with automatic generation of the wrappers.
 
 Here's an article describing how to use `genType` as part of a migration strategy where a tree of components is gradually converted to ReScript bottom-up (old article containing Reason / BuckleScript): [Adopting Reason: strategies, dual sources of truth, and why genType is a big deal](https://medium.com/p/c514265b466d).
 
-The implementation of @genType performs a type-directed transformation of ReScript programs after [bucklescript](https://github.com/BuckleScript/bucklescript) compilation. The transformed programs operate on data types idiomatic to JS. For example, a ReScript function operating on a ReScript variant `type t  = | A(int) | B(string)` (which is represented as custom blocks at runtime) is exported to a JS function operating on the corresponding JS object of type `{ tag: "A"; value: number }
+The implementation of genType performs a type-directed transformation of ReScript programs after ReScript source code compilation. The transformed programs operate on data types idiomatic to JS.
+
+For example, a ReScript function operating on a ReScript variant `type t  = | A(int) | B(string)` (which is represented as custom blocks at runtime) is exported to a JS function operating on the corresponding JS object of type `{ tag: "A"; value: number }
   | { tag: "B"; value: string }`.
 
-The output of `genType` can be configured by using one of 3 back-ends: `untyped` to generate wrappers in vanilla JS, `typescript` to generate [TypeScript](https://www.typescriptlang.org/), and `flow` to generate JS with [Flow](https://flow.org/en/) type annotations.
+The output of genType can be configured by using one of 3 back-ends: `untyped` to generate wrappers in vanilla JS, `typescript` to generate [TypeScript](https://www.typescriptlang.org/), and `flow` to generate JS with [Flow](https://flow.org/en/) type annotations.
 
-## A More Concrete Example
+## A Quick Example
 
 Let's assume we are working on a TypeScript (TS) codebase and we want to integrate a single ReasonReact component.
 
-Firstly we want to be able to import the ReasonReact component like any other React component, secondly we also want to preserve all the ReScript types in the TS type system (and convert incompatible values if necessary). **That's exactly what `genType` was made for!**
+We want to be able to import the ReasonReact component like any other React component in our existing TS code, but we also want to preserve all the ReScript types in the TS type system (and convert incompatible values if necessary).
+
+**That's exactly what genType was made for!**
 
-First we'll set up a ReasonReact component just like this (we will assume that `genType` and `bs-platform` is already configured correctly):
+First we'll set up a ReasonReact component:
 
 ```res
 /* src/MyComp.res */
@@ -68,9 +74,11 @@ export const make: React.ComponentType<{ readonly color: color; readonly name: s
 };
 ```
 
-Note how `genType` automatically maps the `color` variant to TS via a string union type `color = "Red" | "Blue"`.  We can seamlessly use ReScript specific data structures within TS without doing any manual transformations!
+genType automatically maps the `color` variant to TS via a string union type `color = "Red" | "Blue"`, and also provides all the converters to convert between the ReScript & TS representation as well.
 
-Now, within our TypeScript application, we can now import and use the React component in following manner:
+Therefore way we can seamlessly use ReScript specific data structures within TS without writing the converter code by hand!
+
+Within our TypeScript application, we can now import and use the React component in the following manner:
 
 ```ts
 // src/App.ts
@@ -84,8 +92,10 @@ const App = () => {
 };
 ```
 
-We are only scratching the surface on what `genType` can actually do. For more information, head to the [Getting Started](getting-started) section, or find relevant topics from the sidebar !
+That's it for our quick example.
+
+For detailed information, head to the [Getting Started](getting-started) or [Usage](usage) section.
 
 ## Development
 
-For contributions, issues or questions, please refer to the [`genType` Github repository](https://github.com/reason-association/genType) or our [forum](https://forum.rescript-lang.org).
+For contributions, issues or questions, please refer to the [Github repository](https://github.com/reason-association/genType) or our [ReScript forum](https://forum.rescript-lang.org).