diff --git a/docs/mocks.md b/docs/mocks.md
index 6ca97acf7c..de4f418ca8 100644
--- a/docs/mocks.md
+++ b/docs/mocks.md
@@ -2,9 +2,9 @@
 
 There are 3 ways to mock data to develop on Pioneer
 
-- Storybook mocks
-- Local node mocks
-- GraphQL (query-node) mocks (**deprecated**)
+- [Storybook mocks](#storybook-mocks))
+- [Local node mocks](#node-mock)
+- [GraphQL (query-node) mocks (**deprecated**)](#query-node-mocks)
 
 ## Storybook mocks
 
@@ -104,7 +104,7 @@ To show help:
 yarn node-mocks --help
 ```
 
-#### Chain spec
+#### Chain spec (**deprecated**)
 
 Another way to influence the on-chain state for testing purpose, is to provide a customize `chain-spec.json` file when running a Joystream node:
 
diff --git a/docs/tests.md b/docs/tests.md
index e5dadedad3..265d910c3d 100644
--- a/docs/tests.md
+++ b/docs/tests.md
@@ -28,7 +28,8 @@ The Pioneer Storybook has 3 type of stories:
 
 One of the main advantage of having tests done in the stories is that the same mocks are used to both write the stories (and often to also create the page itself) and to write the tests. It also makes it easier to debug the tests by providing a visual feed back of everything it does.
 
-For more information the mocks see
+> [!IMPORTANT]
+> Read how to mock data in the pages stories and tests [here](mocks.md#storybook-mocks)
 
 ## Integration tests
 
diff --git a/packages/ui/README.md b/packages/ui/README.md
index 4f396b8447..b0b8ef1d8f 100644
--- a/packages/ui/README.md
+++ b/packages/ui/README.md
@@ -11,8 +11,8 @@
    - [Build tools](#build-tools)
 - [Directory structure](#directory-structure)
 - [Concepts](#concepts)
-  - [Modals](#authentication)
-      - [Modals with steps](#modals-with steps)
+  - [Modals](#modals)
+      - [Modals with steps](#modals-with-steps)
       - [Transactions](#transactions)
    - [Query Node](#query-node)
        - [Adding queries](#adding-queries)