Fix broken links

Author: leeyi45

docs/src/modules/2-bundle/5-documentation/1-cadet/1-cadet.md

@@ -27,7 +27,7 @@ Since modules are already written in Typescript, there is no need to use type-aw
 All type annotations should be written in directly Typescript
 so as not to confuse Typedoc and ensure that the Typescript compiler is able to ensure type safety.
 
-If you do need to the type of an export to be documented differently from its type in Typescript source code, you can use a [type map](../7-type_map).
+If you do need to the type of an export to be documented differently from its type in Typescript source code, you can use a [type map](../../7-type_map).
 :::
 
 Let us look at more examples from the `curve` module.

docs/src/modules/2-bundle/5-documentation/2-dev.md

@@ -31,7 +31,7 @@ the entire documentation server to read it).
 
 If you have more complex documentation needs, you can follow the instructions in the next section.
 
-### 2. As a collection of Markdown files located [here](../../../lib/dev):
+### 2. As a collection of Markdown files located [here](../../../lib/dev/index):
 
 Within the `dev` folder, each markdown file/folder structure represents a separate bundle.
 

docs/src/modules/2-bundle/5-documentation/index.md

@@ -4,5 +4,5 @@ title: Bundle Documentation
 
 Contents of this section
 
-- [Cadet Documentation](./1-cadet)
+- [Cadet Documentation](./1-cadet/1-cadet)
 - [Developer Documentation](./2-dev)

docs/src/modules/2-bundle/7-type_map.md

@@ -11,7 +11,7 @@ Regardless of the situation, type maps are a way for bundle authors to control t
 > Currently `js-slang` only performs any kind of type checking for modules when the typed Source variant is used.
 > This means that type maps are only used by the typed Source Variant.
 >
-> This also means that documentation (mentioned [here](./5-documentation/5-documentation)) will not reflect the types specified by the type map
+> This also means that documentation (mentioned [here](./5-documentation/1-cadet/1-cadet)) will not reflect the types specified by the type map
 
 Type Maps are opt-in. If the bundle does not provide a type map, then no type checking is performed on its exports, similar to
 how `skipLibCheck: true` is used in Typescript.
@@ -101,7 +101,7 @@ export const translate = RuneFunctions.translate;
 > Notice that when re-exporting, the documentation is attached to the constant declaration and not the declaration in the class. This is so that
 > the documentation is properly applied to the exported function.
 >
-> Also notice that the `@function` tag has been applied. More information about why this is necessary can be found [here](./5-documentation/5-documentation#use-of-function)
+> Also notice that the `@function` tag has been applied. More information about why this is necessary can be found [here](./5-documentation/1-cadet/1-cadet#use-of-function)
 >
 > A quick way to check if you have written your documentation correctly is to see if IntelliSense in VSCode is able to display it to you.