diff --git a/docs/concepts/04-transforms.md b/docs/concepts/04-transforms.md
index e41cc5dd2..8cc0941a0 100644
--- a/docs/concepts/04-transforms.md
+++ b/docs/concepts/04-transforms.md
@@ -4,7 +4,7 @@ Slate's data structure is immutable, so you can't modify or delete nodes directl
 
 Slate's transform functions are designed to be very flexible, to make it possible to represent all kinds of changes you might need to make to your editor. However, that flexibility can be hard to understand at first.
 
-> 🤖 Check out the [Transforms](../api/transforms.md) reference for a full list of Slate's transforms.
+> 🤖 Check out the [Transforms](/api/transforms.md) reference for a full list of Slate's transforms.
 
 ## Selection Transforms
 
@@ -29,7 +29,7 @@ Transforms.move(editor, {
 })
 ```
 
-[Selection Transforms API Reference](api/transforms#selection-transforms)
+[Selection Transforms API Reference](/api/transforms#selection-transforms)
 
 ## Text Transforms
 
@@ -52,6 +52,8 @@ Transforms.delete(editor, {
 })
 ```
 
+[Text Transforms API Reference](/api/transforms#text-transforms)
+
 ## Node Transforms
 
 Node transforms act on the individual element and text nodes that make up the editor's value. For example you could insert a new text node at a specific path:
@@ -77,6 +79,8 @@ Transforms.moveNodes(editor, {
 })
 ```
 
+[Node Transforms API Reference](https://docs.slatejs.org/api/transforms#node-transforms)
+
 ## The `at` Option
 
 Many transforms act on a specific location in the document. By default, they will use the user's current selection. But this can be overridden with the `at` option.