The changes in this commit primarily focus on fixing Markdown links, minor grammatical errors, and some stylistic improvements in the documentation for a virtual machine (MVM) assembly language.

* **Markdown Links Corrected:** Numerous Markdown links throughout the documentation have been updated to use the `.md` extension.  This ensures that links resolve correctly when rendered using a Markdown processor.  Affected files include `_Sidebar.md`, `Home.md`, `Getting-Started.md`, `Assembly-Intro.md`, `Registers.md`, `Memory-Model.md`, `Standard-Library.md`, `System-Calls.md`, `Virtual-Devices.md`, `Instruction-Set.md`, and `Future-Plans.md`.

* **Grammatical Fixes:** Minor grammatical errors have been corrected, such as changing "are stored" to "is stored" in `System-Call-Implementation.md`.  The term "Maths" has been changed to the British English spelling "Maths" in `Standard-Library.md`.  American English spelling "Personalized" has been changed to British English spelling "Personalised" in `Future-Plans.md`. Use of analyze vs analyse (American vs British english)

* **Stylistic Changes:** Some stylistic changes have been made to improve readability.  For example, extraneous backticks have been removed from code examples in `Instruction-Set.md`.  Unnecessary trailing spaces and a trailing ``` in `System-Call-Implementation.md` have been removed.  Blank lines and indentation have been adjusted in `Memory-Model.md`.  Comments markers have been changed from `;` to `//` in `Instruction-Set.md`.

* **Content Changes:**  A small content change was made to the return value description in `System-Call-Implementation.md` to reflect stack management by the VM's runtime. Word repetition removed. Redundant explanations in `Instruction-Set.md` removed. Removed `INR` and `DEALLOC` instructions.  Removed some IDE-specific configuration changes in `.idea/misc.xml` and `.idea/inspectionProfiles/Project_Default.xml`.

In summary, these changes enhance the documentation's clarity, consistency, and correctness, making it more accessible and useful for users learning about the MVM assembly language. They do not introduce new functionality or alter the behavior of the MVM itself.

Author: ChippyPlus

.idea/inspectionProfiles/Project_Default.xml

@@ -49,11 +49,11 @@ PRINTR R1      // Print the value in R4 (15)
 
 For detailed information, refer to:
 
-* [Instruction Set](Instruction-Set): Detailed explanation of each instruction.
-* [Registers](Registers): Information on the different register types.
-* [Memory Model](Memory-Model): How memory is organised and accessed.
-* [System Calls](System-Calls): How to interact with the OS kernel.
-* [Standard Library](Standard-Library): Overview of available functions.
+* [Instruction Set](Instruction-Set.md): Detailed explanation of each instruction.
+* [Registers](Registers.md): Information on the different register types.
+* [Memory Model](Memory-Model.md): How memory is organised and accessed.
+* [System Calls](System-Calls.md): How to interact with the OS kernel.
+* [Standard Library](Standard-Library.md): Overview of available functions.
 
 This introduction provides a foundation for understanding the MVM assembly language. You can start writing programs
 after

.idea/misc.xml

@@ -3,14 +3,14 @@
 ## I. Language and Runtime Enhancements
 
 1. **Customizable Syntax:** Allow users to define their own syntax for MVM assembly language, enabling domain-specific
-   languages or personalized coding styles.
+   languages or personalised coding styles.
 2. **Built-in Data Structures:** Implement built-in support for more complex data structures like hash maps, trees, and
    graphs, accessible through standard library functions or new instructions.
 3. **Type Inference:** Add type inference to your higher-level language (if you create one), reducing the need for
    explicit type declarations.
-4. **Automatic Memory Management:**  Explore garbage collection algorithms (mark-and-sweep, reference counting) to
+4. **Automatic Memory Management:** Explore garbage collection algorithms (mark-and-sweep, reference counting) to
    automate memory management and prevent memory leaks.
-5. **Reflection API:** Allow programs running in the VM to inspect and manipulate their own structure and behavior (
+5. **Reflection API:** Allow programs running on the VM to inspect and manipulate their own structure and behaviour (
    e.g., access register values, inspect the call stack).
 6. **Dynamic Linking:** Enable dynamic linking of libraries or modules, allowing programs to load and use external code
    at runtime.
@@ -40,8 +40,8 @@
 
 ## IV. Debugging and Development Tools
 
-17. **Time-Travel Debugging:** Implement a debugger that allows stepping backward through program execution to analyze
-	program behavior.
+17. **Time-Travel Debugging:** Implement a debugger that allows stepping backward through program execution to analyse
+	program behaviour.
 18. **Code Coverage Analysis:** Add tools to measure code coverage during testing.
 19. **Performance Profiler:** Develop tools to profile CPU usage, memory access patterns, and other performance metrics.
 20. **Bytecode Disassembler:** Create a tool to disassemble MVM bytecode back into assembly language for easier
@@ -63,6 +63,6 @@
 	execution environment (interesting for simulations or genetic algorithms).
 27. **MVM as a Service:** Create a web service that allows users to upload and run MVM programs remotely.
 
-This document details planned enhancements for the MVM. This is a high-level view, and the prioritization and specifics
+This document details planned enhancements for the MVM. This is a high-level view, and the prioritisation and specifics
 are subject to change.
 

docs/Assembly-Intro.md

@@ -86,6 +86,7 @@ call println             // Prints the string located in F1 to stdout
 To run this program, use one of the above commands, replacing `<path_to_assembly_file.kar>` with `myprogram.kar`. The
 output will be printed to the console.
 
-Now you can start writing and executing your own assembly programs. Refer to the [Instruction Table](Instruction-Table)
+Now you can start writing and executing your own assembly programs. Refer to
+the [Instruction Table](Instruction-Table.md)
 for a list of instructions and their syntax.
 

docs/Future-Plans.md

@@ -32,7 +32,7 @@ rewrite focuses on simulating a time-sharing operating system kernel within the
 ## Getting Started
 
 For detailed instructions on setting up and running the virtual machine, please refer to
-the [Installation and Setup](Getting-Started) guide.
+the [Installation and Setup](Getting-Started.md) guide.
 
 ## Explore the Documentation