Revert "Merge branch 'nextjs-12' of https://github.com/JiaeK/rescript-lang.org into nextjs-12"

This reverts commit 5334930, reversing
changes made to 25d4a35.

Author: JiaeK

CONTRIBUTING.md

@@ -30,17 +30,17 @@ If you need inspiration on what to work on, you can check out issues tagged with
 
 We really appreciate all input from users, community members and potential contributors. Please make sure to consider the other person's opinion and don't assume any common knowledge.
 
-**Most importantly: Keep it professional and be nice to each other**
+**Most importantly: Keep it professional and be nice to eachother**
 
-There might be situations where others don't understand a proposed feature or have different opinions on certain writing styles. That's fine, discussions are always welcome! Communicate in clear actionables, make your plans clear and always stick to the original topic.
+There might be situations where others don't understand a proposed feature or have different opinions on certain writing styles. That's fine, discussions are always welcome! Communicate in clear actionables, make your plans clear and always to stick to the original topic.
 
 If other contributors disagree with certain proposals and don't change their mind after longer discussions, please don't get discouraged when an issue gets closed / postponed. Everyone tries their best to make the platform better, and to look at it in another perspective: Closed issues are also a highly valuable resource for others to understand technical decisions later on.
 
 ### Communicate your Time Commitment
 
 Open Source development can be a challenge to coordinate, so please make sure to block enough time to work on your tasks and show commitment when taking on some work. Let other contributors know if your time schedule changes significantly, and also let others know if you can't finish a task.
 
-We value your voluntary work, and of course it's fine to step back from a ticket for any reason (we can also help you if you are getting stuck). Please talk to us in any case, otherwise we might re-assign the ticket to other contributors.
+We value your voluntary work, and of course it's fine to step back from a ticket for any reasons (we can also help you if you are getting stuck). Please talk to us in any case, otherwise we might re-assign the ticket to other contributors.
 
 ### Communication Channels
 
@@ -66,7 +66,7 @@ Always check if there are any designs for certain UI components and think about
 ### Technical Writing (Documentation)
 
 - Think and write in a JS friendly mindset when explaining concepts / showing examples.
-- No `foo` examples if somewhat possible. Try to establish practical context in your showcase examples.
+- No `foo` examples if somewhat possible. Try to establish practical context in your show case examples.
 - No references to `OCaml`. ReScript is its own language, and we don't rely on external resources of our host language.
 - If possible, no references to `Reason` examples / external resources. Our goal is to migrate everything to ReScript syntax.
 

data/sidebar_react_latest.json

@@ -2,7 +2,7 @@
   "Overview": [
     "introduction",
     "installation",
-    "migrate-react"
+    "migrate-from-v3"
   ],
   "Main Concepts": [
     "elements-and-jsx",

data/sidebar_react_v0100.json

@@ -2,7 +2,7 @@
   "Overview": [
     "introduction",
     "installation",
-    "migrate-react"
+    "migrate-from-reason-react"
   ],
   "Main Concepts": [
     "elements-and-jsx",

pages/docs/manual/latest/let-binding.mdx

@@ -35,7 +35,7 @@ let message = {
   let part2 = "world"
   part1 ++ " " ++ part2
 }
-// `part1` and `part2` are not accessible here!
+// `part1` and `part2` not accessible here!
 ```
 ```js
 var message = "hello world";
@@ -72,7 +72,7 @@ Let bindings are "immutable", aka "cannot change". This helps our type system de
 
 ## Binding Shadowing
 
-The above restriction might sound impractical at first. How would you change a value then? Usually, 2 ways:
+The above restriction might sound unpractical at first. How would you change a value then? Usually, 2 ways:
 
 The first is to realize that many times, what you want isn't to mutate a variable's value. For example, this JavaScript pattern:
 
@@ -181,5 +181,5 @@ Still, `%%private` is useful in the following scenarios:
 
 - **Code generators.** Some code generators want to hide some values but it is sometimes very hard or time consuming for code generators to synthesize the types for public fields.
 
-- **Quick prototyping.** During prototyping, we still want to hide some values, but the interface file is not stable yet, `%%private` provides you such convenience.
+- **Quick prototyping.** During prototyping, we still want to hide some values, but the interface file is not stable yet, `%%private` provide you such convenience.
 

pages/docs/manual/latest/migrate-from-bucklescript-reason.mdx

@@ -26,7 +26,7 @@ Enjoy the improved experience!
 
 ### Upgrade Individual Folders
 
-This is useful for per-directory conversions:
+This is useful for per-directory convertions:
 
 ```console
 # *.rei, *.ml, *.mli,....
@@ -56,7 +56,7 @@ npx rescript convert -all
 - First class module: from `(module S: Student)` to `module(S: Student)`.
 - No custom infix operator for now (including `mod`).
 - Object access: from `settings##visible #= true` to `settings["visible"] = true`. Rejoice!
-- Object: from `Js.t({"age": int})` to just `{"age": int}`. The `Js.t` part is now unneeded.
+- Object: from `Js.t({"age": int})` to just `{"age": int}`. The `Js.t` part is now uneeded.
 - Attribute: from `[@myAttribute "hello"]` to `@myAttribute("hello")`. From `[%re bla]` to `%re(bla)`.
 - Removed dereference syntax `result^`. Just use `result.contents`.
 - `fun` pattern matching syntax removed.

pages/docs/manual/latest/primitive-types.mdx

@@ -156,7 +156,7 @@ ReScript's `true/false` compiles into a JavaScript `true/false`.
 
 32-bits, truncated when necessary. We provide the usual operations on them: `+`, `-`, `*`, `/`, etc. See [Js.Int](api/js/int) for helper functions.
 
-**Be careful when you bind to JavaScript numbers!** Since ReScript integers have a much smaller range than JavaScript numbers, data might get lost when dealing with large numbers. In those cases, it’s much safer to bind the numbers as **floats**. Be extra mindful of this when binding to JavaScript Dates and their epoch time.
+**Be careful when you bind to JavaScript numbers!** Since ReScript integers have a much smaller range than JavaScript numbers, data might get lost when dealing with large numbers. In those cases it’s much safer to bind the numbers as **float**. Be extra mindful of this when binding to JavaScript Dates and their epoch time.
 
 To improve readability, you may place underscores in the middle of numeric literals such as `1_000_000`. Note that underscores can be placed anywhere within a number, not just every three digits.
 

pages/docs/manual/latest/tuple.mdx

@@ -6,7 +6,7 @@ canonical: "/docs/manual/latest/tuple"
 
 # Tuple
 
-Tuples are a ReScript-specific data structure that doesn't exist in JavaScript. They are:
+Tuples are a ReScript-specific data structure that don't exist in JavaScript. They are:
 
 - immutable
 - ordered

pages/docs/manual/latest/type.mdx

@@ -9,7 +9,7 @@ canonical: "/docs/manual/latest/type"
 Types are the highlight of ReScript! They are:
 - **Strong**. A type can't change into another type. In JavaScript, your variable's type might change when the code runs (aka at runtime). E.g. a `number` variable might change into a `string` sometimes. This is an anti-feature; it makes the code much harder to understand when reading or debugging.
 - **Static**. ReScript types are erased after compilation and don't exist at runtime. Never worry about your types dragging down performance. You don't need type info during runtime; we report all the information (especially all the type errors) during compile time. Catch the bugs earlier!
-- **Sound**. This is our biggest differentiator versus many other typed languages that compile to JavaScript. Our type system is guaranteed to **never** be wrong. Most type systems make a guess at the type of a value and show you a type in your editor that's sometimes incorrect. We don't do that. We believe that a type system that is sometimes incorrect can end up dangerous due to expectation mismatches.
+- **Sound**. This is our biggest differentiator versus many other typed languages that compile to JavaScript. Our type system is guaranteed to **never** be wrong. Most type systems make a guess at the type of a value and show you a type in your editor that's sometime incorrect. We don't do that. We believe that a type system that is sometime incorrect can end up being dangerous due to expectation mismatches.
 - **Fast**. Many developers underestimate how much of their project's build time goes into type checking. Our type checker is one of the fastest around.
 - **Inferred**. You don't have to write down the types! ReScript can deduce them from their values. Yes, it might seem magical that we can deduce all of your program's types, without incorrectness, without your manual annotation, and do so quickly. Welcome to ReScript =).
 

pages/docs/react/latest/installation.mdx

@@ -28,7 +28,7 @@ Then add the following setting to your existing `bsconfig.json`:
 
 > The [new jsx transform](https://ko.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html) of ReactJS is available with `mode: "automatic"`.
 
-**Note** JSX v4 is newly introduced with the idomatic record-based representation of component. If your dependecies are not compatible with v4 yet, then you can use v3 in the same project. Check out the details in [Migrate from v3](/docs/react/latest/migrate-react)
+**Note** JSX v4 is newly introduced with the idomatic record-based representation of component. If your dependecies are not compatible with v4 yet, then you can use v3 in the same project. Check out the details in [Migrate from v3](/docs/react/latest/migrate-from-v3)
 
 To test your setup, create a new `.res` file in your source directory and add the following code:
 

pages/docs/react/latest/migrate-react.mdx renamed to pages/docs/react/latest/migrate-from-v3.mdx

@@ -1,7 +1,7 @@
 ---
 title: Migrate from JSX v3
 description: "Migrate from JSX v3"
-canonical: "/docs/react/latest/migrate-react"
+canonical: "/docs/react/latest/migrate-from-v3"
 ---
 
 # Migrate from JSX v3
@@ -211,32 +211,3 @@ let make = () => {
   </div>
 }
 ```
-
-### Mangling the prop name
-
-The prop name was mangled automatically in v3, such as `_open` becomes `open` in the generated js code. This is no longer the case in v4 because the internal representation is changed to the record instead object. If you need to mangle the prop name, you can use the `@as` annotation.
-
-Rewrite this:
-
-```res
-module Comp = {
-  @react.component
-  let make = (~_open, ~_type) =>
-    <Modal _open _type>
-      <Description />
-    </Modal>
-}
-```
-
-To this:
-
-```res
-module Comp = {
-  @react.component
-  let make =
-    (@as("open") ~_open, @as("type") ~_type) =>
-      <Modal _open _type>
-        <Description />
-      </Modal>
-}
-```

pages/docs/react/v0.10.0/migrate-react.mdx renamed to pages/docs/react/v0.10.0/migrate-from-reason-react.mdx

@@ -1,7 +1,7 @@
 ---
 title: Migrate from ReasonReact
 description: "Migrate from ReasonReact"
-canonical: "/docs/react/latest/migrate-react"
+canonical: "/docs/react/latest/migrate-from-reason-react"
 ---
 
 # Migrate from ReasonReact