Relative links + nits

Author: chenglou

pages/docs/manual/latest/build-performance.mdx

@@ -63,7 +63,7 @@ In short, thanks to our bsc compiler and bsb build system's architecture, we're
 
 ## Speed Up Incremental Build
 
-ReScript uses the concept of interface files (`.resi`) (or, equivalently, [module signatures](/docs/manual/latest/module#signatures)). Exposing only what you need naturally speeds up incremental builds. E.g. if you change a `.res` file whose corresponding `.resi` file doesn't expose the changed part, then you've reduced the amount of dependent files you have to rebuild.
+ReScript uses the concept of interface files (`.resi`) (or, equivalently, [module signatures](module.md#signatures)). Exposing only what you need naturally speeds up incremental builds. E.g. if you change a `.res` file whose corresponding `.resi` file doesn't expose the changed part, then you've reduced the amount of dependent files you have to rebuild.
 
 <!-- TODO: validate this -->
 

pages/docs/manual/latest/interop-cheatsheet.mdx

@@ -69,11 +69,11 @@ Handling a value that can be `undefined` and `null`, by ditching the `option` ty
 <CodeTab labels={["ReScript", "JS Output"]}>
 
 ```res
-let jsNull = Js.Nullable.null;
-let jsUndefined = Js.Nullable.undefined;
-let result1: Js.Nullable.t<string> = Js.Nullable.return("hello");
-let result2: Js.Nullable.t<int> = Js.Nullable.fromOption(Some(10));
-let result3: option<int> = Js.Nullable.toOption(Js.Nullable.return(10));
+let jsNull = Js.Nullable.null
+let jsUndefined = Js.Nullable.undefined
+let result1: Js.Nullable.t<string> = Js.Nullable.return("hello")
+let result2: Js.Nullable.t<int> = Js.Nullable.fromOption(Some(10))
+let result3: option<int> = Js.Nullable.toOption(Js.Nullable.return(10))
 ```
 ```js
 var Caml_option = require("./stdlib/caml_option.js");

pages/docs/manual/latest/lazy-values.mdx

@@ -109,7 +109,7 @@ var lazyDoesFileExist = {
 
 </CodeTab>
 
-Whenever we want to wrap a function `unit => 'a`, we use `Lazy.from_fun`, otherwise we use the `lazy([expr])` keyword to wrap an expression or a function with 1 or more arguments.
+Whenever we want to wrap a function `unit => 'a`, we use `Lazy.from_fun`, otherwise we use the `lazy(expr)` keyword to wrap an expression or a function with 1 or more arguments.
 
 ## Force a lazy computation
 

pages/docs/manual/latest/variant.mdx

@@ -157,7 +157,7 @@ If you come from an untyped language, you might be tempted to try `type myType =
 
 ### Interop with JavaScript
 
-_This section assumes knowledge about our [FFI](/docs/reason-compiler/latest/interop-overview). Skip this if you haven't felt the itch to use variants for wrapping JS functions yet_.
+_This section assumes knowledge about our JavaScript interop. Skip this if you haven't felt the itch to use variants for wrapping JS functions yet_.
 
 Quite a few JS libraries use functions that can accept many types of arguments. In these cases, it's very tempting to model them as variants. For example, suppose there's a `myLibrary.draw` JS function that takes in either a `number` or a `string`. You might be tempted to bind it like so: