Fix examples, add more links

Author: ryyppy

pages/docs/react/latest/styling.mdx

@@ -19,22 +19,25 @@ If they work in JS then they almost certainly work in ReScript. In the next few
 
 This is the most basic form of styling, coming straight from the 90ies. You can apply a `style` attribute to any DOM element with our `ReactDOM.Style.make` API:
 
-```rescript
-<div style=(
-  ReactDOM.Style.make(~color="#444444", ~fontSize="68px", ())
-)/>
+```res
+<div style={ReactDOM.Style.make(~color="#444444", ~fontSize="68px", ())} />
 ```
 
-It's a labeled (therefore typed) function call that maps to the familiar style object `{color: '#444444', fontSize: '68px'}`. For every CSS attribute in the CSS specfication, there is a camelCased label in our `make` function.
+It's a [labeled](/docs/manual/latest/function#labeled-arguments) (therefore typed) function call that maps to the familiar style object `{color: '#444444', fontSize: '68px'}`. For every CSS attribute in the CSS specfication, there is a camelCased label in our `make` function.
 
 **Note** that `make` returns an opaque `ReactDOM.Style.t` type that you can't read into. We also expose a `ReactDOM.Style.combine` that takes in two `style`s and combine them.
 
 ### Escape Hatch: `unsafeAddProp`
 
 The above `Style.make` API will safely type check every style field! However, we might have missed some more esoteric fields. If that's the case, the type system will tell you that the field you're trying to add doesn't exist. To remediate this, we're exposing a `ReactDOM.Style.unsafeAddProp` to dangerously add a field to a style:
 
-```reason
-let myStyle = ReactDOM.Style.make(~color="#444444", ~fontSize="68px", ());
+```res
+let style =
+  ReactDOM.Style.make(
+    ~color="red",
+    ~padding="10px",
+    (),
+  )->ReactDOM.Style.unsafeAddProp("-webkit-animation-name", "moveit")
 ```
 
 ## Global CSS
@@ -74,7 +77,7 @@ We now need to create a module binding that imports our styles as a JS object:
 let app = <div className={styles["root"]} />
 ```
 
-**Note:** `{..}` is an open JS object type, which means the type checker will not type check correct classname usage. If you want to enforce compiler errors, replace `{..}` with a concrete JS object type, such as `{"root": string}`.
+**Note:** `{..}` is an open [JS object type](/docs/manual/latest/object#type-declaration), which means the type checker will not type check correct classname usage. If you want to enforce compiler errors, replace `{..}` with a concrete JS object type, such as `{"root": string}`.
 
 
 ## CSS Utility Libraries