fix more links and add errors on invalid links

Author: jderochervlk

markdown-pages/blog/enhanced-ergonomics-for-record-types.mdx

@@ -141,7 +141,7 @@ let name = nameFromB(a :> b)
 
 Notice how `a` now has more fields than `b`, but we can still coerce `a` to `b` because `b` has a subset of the fields of `a`.
 
-In combination with [optional record fields](../docs/manual/record.mdx#optional-record-fields), one may coerce a mandatory field of an `option` type to an optional field:
+In combination with [ReScript objects are like ](../docs/manual/record.mdx#optional-record-fields), one may coerce a mandatory field of an `option` type to an optional field:
 
 ```rescript
 type a = {

markdown-pages/docs/manual/array-and-list.mdx

@@ -192,7 +192,7 @@ var anotherList = {
 
 #### Access
 
-`switch` (described in the [pattern matching section](pattern-matching-destructuring.mdx)) is usually used to access list items:
+`switch` (described in the [pattern matching section](./pattern-matching-destructuring.mdx)) is usually used to access list items:
 
 <CodeTab labels={["ReScript", "JS Output"]}>
 

markdown-pages/docs/manual/bind-to-js-function.mdx

@@ -29,7 +29,7 @@ We also expose a few special features, described below.
 
 ## Labeled Arguments
 
-ReScript has [function](function.mdx) signature. These work on an `external` too! You'd use them to _fix_ a JS function's unclear usage. Assuming we're modeling this:
+ReScript has [function](./function.mdx) signature. These work on an `external` too! You'd use them to _fix_ a JS function's unclear usage. Assuming we're modeling this:
 
 ```js
 // MyGame.js
@@ -109,7 +109,7 @@ In a `send`, the object is always the first argument. Actual arguments of the me
 
 ### Chaining
 
-Ever used `foo().bar().baz()` chaining ("fluent api") in JS OOP? We can model that in ReScript too, through the [pipe operator](pipe.mdx).
+Ever used `foo().bar().baz()` chaining ("fluent api") in JS OOP? We can model that in ReScript too, through the [pipe operator](./pipe.mdx).
 
 ### Nested function call
 
@@ -164,7 +164,7 @@ var v = Path.join("a", "b");
 
 </CodeTab>
 
-`module` will be explained in [Import from/Export to JS](import-from-export-to-js.mdx).
+`module` will be explained in [Import from/Export to JS](./import-from-export-to-js.mdx).
 
 ## Modeling Polymorphic Function
 

markdown-pages/docs/manual/bind-to-js-object.mdx

@@ -15,7 +15,7 @@ JavaScript objects are a combination of several use-cases:
 - As a class.
 - As a module to import/export.
 
-ReScript cleanly separates the binding methods for JS object based on these 4 use-cases. This page documents the first three. Binding to JS module objects is described in the [Import from/Export to JS](import-from-export-to-js.mdx) section.
+ReScript cleanly separates the binding methods for JS object based on these 4 use-cases. This page documents the first three. Binding to JS module objects is described in the [Import from/Export to JS](./import-from-export-to-js.mdx) section.
 
 {/* TODO: mention scope here too? */}
 
@@ -47,7 +47,7 @@ var johnName = MySchool.john.name;
 
 </CodeTab>
 
-External is documented [here](external.mdx). `@module` is documented [here](import-from-export-to-js.mdx).
+External is documented [here](./external.mdx). `@module` is documented [here](./import-from-export-to-js.mdx).
 
 If you want or need to use different field names on the ReScript and the JavaScript side, you can use the `@as` decorator:
 
@@ -92,7 +92,7 @@ var value = [7, "baz"];
 
 ### Bind Using ReScript Object
 
-Alternatively, you can use [ReScript object](object.mdx) to model a JS object too:
+Alternatively, you can use [ReScript object](./object.mdx) to model a JS object too:
 
 <CodeTab labels={["ReScript", "JS Output"]}>
 

markdown-pages/docs/manual/editor-plugins.mdx

@@ -153,7 +153,7 @@ Below is a list of all the scenarios where using dots trigger completion in addi
 
 #### Objects
 
-When writing a `.` on something that's a [structural object](object.mdx), you'll get completions for those object properties. Example:
+When writing a `.` on something that's a [structural object](./object.mdx), you'll get completions for those object properties. Example:
 
 ```res
 let obj = {

markdown-pages/docs/manual/embed-raw-javascript.mdx

@@ -113,4 +113,4 @@ Embedding raw JS snippets isn't the best way to experience ReScript, though it's
 
 At the end, we get a fully safe, converted ReScript file whose JS output is clean enough that we can confidently assert that no new bug has been introduced during the conversion process.
 
-We have a small guide on this iteration [here](converting-from-js.mdx). Feel free to peruse it later.
+We have a small guide on this iteration [here](./converting-from-js.mdx). Feel free to peruse it later.

markdown-pages/docs/manual/exception.mdx

@@ -8,12 +8,12 @@ order: 19
 
 # Exception
 
-Exceptions are just a special kind of variant, thrown in **exceptional** cases (don't abuse them!). Consider using the [`option`](null-undefined-option.mdx) or [`result`](/docs/manual/api/stdlib/result) type for recoverable errors.
+Exceptions are just a special kind of variant, thrown in **exceptional** cases (don't abuse them!). Consider using the [`option`](./null-undefined-option.mdx) or [`result`](/docs/manual/api/stdlib/result) type for recoverable errors.
 
 You can create your own exceptions like you'd make a variant (exceptions need to be capitalized too).
 
 <CodeTab labels={["ReScript", "JS Output"]}>
-
+  
 ```res example
 exception InputClosed(string)
 // later on

markdown-pages/docs/manual/external.mdx

@@ -28,11 +28,11 @@ order: 3
 
 </CodeTab>
 
-There are several kinds of `external`s, differentiated and/or augmented through the [attribute](attribute.mdx) they carry. This page deals with the general, shared mechanism behind most `external`s. The different `external`s are documented in their respective pages later. A few notable ones:
+There are several kinds of `external`s, differentiated and/or augmented through the [attribute](./attribute.mdx) they carry. This page deals with the general, shared mechanism behind most `external`s. The different `external`s are documented in their respective pages later. A few notable ones:
 
-- `@val`, `@scope`: [bind to global JS values](bind-to-global-js-values.mdx).
-- `@module`: [bind to JS imported/exported values](import-from-export-to-js.mdx).
-- `@send`: [bind to JS methods](bind-to-js-function.mdx).
+- `@val`, `@scope`: [bind to global JS values](./bind-to-global-js-values.mdx).
+- `@module`: [bind to JS imported/exported values](./import-from-export-to-js.mdx).
+- `@send`: [bind to JS methods](./bind-to-js-function.mdx).
 
 You can also use our [Syntax Lookup](../../syntax-lookup/) tool to find them.
 

markdown-pages/docs/manual/function.mdx

@@ -251,7 +251,7 @@ function drawCircle(color, radius) {
 
 </CodeTab>
 
-The first line is the function's signature, we would define it like that in an interface file (see [Signatures](module.mdx#signatures)). The function's signature describes the types that the **outside world** interacts with, hence the type `int` for `radius` because it indeed expects an `int` when called.
+The first line is the function's signature, we would define it like that in an interface file (see [Signatures](./module.mdx#signatures)). The function's signature describes the types that the **outside world** interacts with, hence the type `int` for `radius` because it indeed expects an `int` when called.
 
 In the second line, we annotate the arguments to help us remember the types of the arguments when we use them **inside** the function's body, here indeed `radius` will be an `option<int>` inside the function.
 

markdown-pages/docs/manual/import-export.mdx

@@ -34,8 +34,8 @@ A ReScript project's file names need to be unique.
 
 By default, every file's type declaration, binding and module is exported, aka publicly usable by another file. **This also means those values, once compiled into JS, are immediately usable by your JS code**.
 
-To only export a few selected things, use a `.resi` [interface file](module.mdx#signatures).
+To only export a few selected things, use a `.resi` [interface file](./module.mdx#signatures).
 
 ## Work with JavaScript Import & Export
 
-To see how to import JS modules and export stuff for JS consumption, see the JavaScript Interop section's [Import from/Export to JS](import-from-export-to-js.mdx).
+To see how to import JS modules and export stuff for JS consumption, see the JavaScript Interop section's [Import from/Export to JS](./import-from-export-to-js.mdx).