Fix more links

fhammerschmidt · fhammerschmidt · commit 0d24d05d81cb · 2024-01-12T14:56:30.000+01:00
diff --git a/pages/docs/manual/v10.0.0/build-configuration.mdx b/pages/docs/manual/v10.0.0/build-configuration.mdx
@@ -34,6 +34,7 @@ Your source files need to be specified explicitly (we don't want to accidentally
   "sources": ["src", "examples"]
 }
 ```
+
 ```json
 {
   "sources": {
@@ -59,22 +60,22 @@ You can mark your directories as dev-only (for e.g. tests). These won't be built
 
 ```json
 {
-  "sources" : {
-    "dir" : "test",
-    "type" : "dev"
+  "sources": {
+    "dir": "test",
+    "type": "dev"
   }
 }
 ```
 
-You can also explicitly allow which modules can be seen from outside. This feature is especially useful for library authors who want to have a single entry point for their users.   
+You can also explicitly allow which modules can be seen from outside. This feature is especially useful for library authors who want to have a single entry point for their users.  
 Here, the file `src/MyMainModule.res` is exposed to outside consumers, while all other files are private.
 
 ```json
 {
   "sources": {
     "dir": "src",
     "public": ["MyMainModule"]
-  },
+  }
 }
 ```
 
@@ -102,7 +103,7 @@ More details can be found on our [external stdlib](./build-external-stdlib) page
 
 ```json
 {
-  "reason": {"react-jsx": 3},
+  "reason": { "react-jsx": 3 },
   "refmt": 3
 }
 ```
@@ -161,7 +162,7 @@ Generating JS files with the `.bs.js` suffix means that, on the JS side, you can
 - It's immediately clear that we're dealing with a generated JS file here.
 - It avoids clashes with a potential `theFile.js` file in the same folder.
 - It avoids the need of using a build system loader for ReScript files. This + in-source build means integrating a ReScript project into your pure JS codebase **basically doesn't touch anything in your build pipeline at all**.
-- [genType](/docs/manual/latest/gentype-introduction) requires `bs.js` for compiled JS artifacts. If you are using `genType`, you need to use `bs.js` for now.
+- [genType](/docs/manual/latest/typescript-integration) requires `bs.js` for compiled JS artifacts. If you are using `genType`, you need to use `bs.js` for now.
 
 ## warnings
 
diff --git a/pages/docs/manual/v9.0.0/build-configuration.mdx b/pages/docs/manual/v9.0.0/build-configuration.mdx
@@ -42,6 +42,7 @@ Your source files need to be specified explicitly (we don't want to accidentally
   "sources": ["src", "examples"]
 }
 ```
+
 ```json
 {
   "sources": {
@@ -67,9 +68,9 @@ You can mark your directories as dev-only (for e.g. tests). These won't be built
 
 ```json
 {
-  "sources" : {
-    "dir" : "test",
-    "type" : "dev"
+  "sources": {
+    "dir": "test",
+    "type": "dev"
   }
 }
 ```
@@ -98,7 +99,7 @@ More details can be found on our [external stdlib](./build-external-stdlib) page
 
 ```json
 {
-  "reason": {"react-jsx": 3},
+  "reason": { "react-jsx": 3 },
   "refmt": 3
 }
 ```
@@ -157,7 +158,7 @@ Generating JS files with the `.bs.js` suffix means that, on the JS side, you can
 - It's immediately clear that we're dealing with a generated JS file here.
 - It avoids clashes with a potential `theFile.js` file in the same folder.
 - It avoids the need of using a build system loader for ReScript files. This + in-source build means integrating a ReScript project into your pure JS codebase **basically doesn't touch anything in your build pipeline at all**.
-- [genType](/docs/manual/latest/gentype-introduction) requires `bs.js` for compiled JS artifacts. If you are using `genType`, you need to use `bs.js` for now.
+- [genType](/docs/manual/latest/typescript-integration) requires `bs.js` for compiled JS artifacts. If you are using `genType`, you need to use `bs.js` for now.
 
 ## warnings
 
diff --git a/pages/docs/react/latest/introduction.mdx b/pages/docs/react/latest/introduction.mdx
@@ -18,7 +18,7 @@ All our documented examples can be compiled in our [ReScript Playground](/try) a
 - Comes with all essential React APIs for building production ready apps (`useState`, `useReducer`, `useEffect`, `useRef`,...)
 - No component class API (all ReScript & React codebases are built on function components & hooks)
 - Strong level of type safety and type inference for component props and state values
-- [GenType](/docs/manual/latest/gentype-introduction) support for importing / exporting React components in TypeScript codebases
+- [GenType](/docs/manual/latest/typescript-integration) support for importing / exporting React components in TypeScript codebases
 
 > **This documentation assumes basic knowledge about ReactJS.**
 >
diff --git a/pages/docs/react/v0.10.0/introduction.mdx b/pages/docs/react/v0.10.0/introduction.mdx
@@ -18,7 +18,7 @@ All our documented examples can be compiled in our [ReScript Playground](/try) a
 - Comes with all essential React APIs for building production ready apps (`useState`, `useReducer`, `useEffect`, `useRef`,...)
 - No component class API (all ReScript & React codebases are built on functional components & hooks)
 - Strong level of type safety and type inference for component props and state values
-- [GenType](/docs/manual/latest/gentype-introduction) support for importing / exporting React components in Flow and TypeScript codebases
+- [GenType](/docs/manual/latest/typescript-integration) support for importing / exporting React components in Flow and TypeScript codebases
 
 > **This documentation assumes basic knowledge about ReactJS.**
 >
diff --git a/pages/docs/react/v0.11.0/introduction.mdx b/pages/docs/react/v0.11.0/introduction.mdx
@@ -18,7 +18,7 @@ All our documented examples can be compiled in our [ReScript Playground](/try) a
 - Comes with all essential React APIs for building production ready apps (`useState`, `useReducer`, `useEffect`, `useRef`,...)
 - No component class API (all ReScript & React codebases are built on function components & hooks)
 - Strong level of type safety and type inference for component props and state values
-- [GenType](/docs/manual/latest/gentype-introduction) support for importing / exporting React components in TypeScript codebases
+- [GenType](/docs/manual/latest/typescript-integration) support for importing / exporting React components in TypeScript codebases
 
 > **This documentation assumes basic knowledge about ReactJS.**
 >

Original file line number	Diff line number	Diff line change
`@@ -34,6 +34,7 @@ Your source files need to be specified explicitly (we don't want to accidentally`
`34`	`34`	`"sources": ["src", "examples"]`
`35`	`35`	`}`
`36`	`36`	```
	`37`	`+`
`37`	`38`	```json
`38`	`39`	`{`
`39`	`40`	`"sources": {`
`@@ -59,22 +60,22 @@ You can mark your directories as dev-only (for e.g. tests). These won't be built`
`59`	`60`
`60`	`61`	```json
`61`	`62`	`{`
`62`		`- "sources" : {`
`63`		`- "dir" : "test",`
`64`		`- "type" : "dev"`
	`63`	`+ "sources": {`
	`64`	`+ "dir": "test",`
	`65`	`+ "type": "dev"`
`65`	`66`	`}`
`66`	`67`	`}`
`67`	`68`	```
`68`	`69`
`69`		`-You can also explicitly allow which modules can be seen from outside. This feature is especially useful for library authors who want to have a single entry point for their users.`
	`70`	`+You can also explicitly allow which modules can be seen from outside. This feature is especially useful for library authors who want to have a single entry point for their users.`
`70`	`71`	Here, the file `src/MyMainModule.res` is exposed to outside consumers, while all other files are private.
`71`	`72`
`72`	`73`	```json
`73`	`74`	`{`
`74`	`75`	`"sources": {`
`75`	`76`	`"dir": "src",`
`76`	`77`	`"public": ["MyMainModule"]`
`77`		`- },`
	`78`	`+ }`
`78`	`79`	`}`
`79`	`80`	```
`80`	`81`
`@@ -102,7 +103,7 @@ More details can be found on our [external stdlib](./build-external-stdlib) page`
`102`	`103`
`103`	`104`	```json
`104`	`105`	`{`
`105`		`- "reason": {"react-jsx": 3},`
	`106`	`+ "reason": { "react-jsx": 3 },`
`106`	`107`	`"refmt": 3`
`107`	`108`	`}`
`108`	`109`	```
@@ -161,7 +162,7 @@ Generating JS files with the `.bs.js` suffix means that, on the JS side, you can
`161`	`162`	`- It's immediately clear that we're dealing with a generated JS file here.`
`162`	`163`	- It avoids clashes with a potential `theFile.js` file in the same folder.
`163`	`164`	`- It avoids the need of using a build system loader for ReScript files. This + in-source build means integrating a ReScript project into your pure JS codebase basically doesn't touch anything in your build pipeline at all.`
`164`		-- [genType](/docs/manual/latest/gentype-introduction) requires `bs.js` for compiled JS artifacts. If you are using `genType`, you need to use `bs.js` for now.
	`165`	+- [genType](/docs/manual/latest/typescript-integration) requires `bs.js` for compiled JS artifacts. If you are using `genType`, you need to use `bs.js` for now.
`165`	`166`
`166`	`167`	`## warnings`
`167`	`168`
Original file line number	Diff line number	Diff line change
`@@ -42,6 +42,7 @@ Your source files need to be specified explicitly (we don't want to accidentally`
`42`	`42`	`"sources": ["src", "examples"]`
`43`	`43`	`}`
`44`	`44`	```
	`45`	`+`
`45`	`46`	```json
`46`	`47`	`{`
`47`	`48`	`"sources": {`
`@@ -67,9 +68,9 @@ You can mark your directories as dev-only (for e.g. tests). These won't be built`
`67`	`68`
`68`	`69`	```json
`69`	`70`	`{`
`70`		`- "sources" : {`
`71`		`- "dir" : "test",`
`72`		`- "type" : "dev"`
	`71`	`+ "sources": {`
	`72`	`+ "dir": "test",`
	`73`	`+ "type": "dev"`
`73`	`74`	`}`
`74`	`75`	`}`
`75`	`76`	```
`@@ -98,7 +99,7 @@ More details can be found on our [external stdlib](./build-external-stdlib) page`
`98`	`99`
`99`	`100`	```json
`100`	`101`	`{`
`101`		`- "reason": {"react-jsx": 3},`
	`102`	`+ "reason": { "react-jsx": 3 },`
`102`	`103`	`"refmt": 3`
`103`	`104`	`}`
`104`	`105`	```
@@ -157,7 +158,7 @@ Generating JS files with the `.bs.js` suffix means that, on the JS side, you can
`157`	`158`	`- It's immediately clear that we're dealing with a generated JS file here.`
`158`	`159`	- It avoids clashes with a potential `theFile.js` file in the same folder.
`159`	`160`	`- It avoids the need of using a build system loader for ReScript files. This + in-source build means integrating a ReScript project into your pure JS codebase basically doesn't touch anything in your build pipeline at all.`
`160`		-- [genType](/docs/manual/latest/gentype-introduction) requires `bs.js` for compiled JS artifacts. If you are using `genType`, you need to use `bs.js` for now.
	`161`	+- [genType](/docs/manual/latest/typescript-integration) requires `bs.js` for compiled JS artifacts. If you are using `genType`, you need to use `bs.js` for now.
`161`	`162`
`162`	`163`	`## warnings`
`163`	`164`
Original file line number	Diff line number	Diff line change
`@@ -18,7 +18,7 @@ All our documented examples can be compiled in our [ReScript Playground](/try) a`
`18`	`18`	- Comes with all essential React APIs for building production ready apps (`useState`, `useReducer`, `useEffect`, `useRef`,...)
`19`	`19`	`- No component class API (all ReScript & React codebases are built on function components & hooks)`
`20`	`20`	`- Strong level of type safety and type inference for component props and state values`
`21`		`-- [GenType](/docs/manual/latest/gentype-introduction) support for importing / exporting React components in TypeScript codebases`
	`21`	`+- [GenType](/docs/manual/latest/typescript-integration) support for importing / exporting React components in TypeScript codebases`
`22`	`22`
`23`	`23`	`> This documentation assumes basic knowledge about ReactJS.`
`24`	`24`	`>`