Fixing pretty much every existing internal link.

Sometimes, it pays to RTFD

docs/part/part.md

@@ -25,7 +25,7 @@ The category part list provides an overview of each part:
 
 The list of parts underneath a given category can be filtered by multiple user-configurable filters, which is especially useful when a large number of parts exist under a certain category.
 
-Clicking on the part name links to the [*Part Detail*](../views) view.
+Clicking on the part name links to the [*Part Detail*](./views.md) view.
 
 ## Part Options
 
@@ -37,25 +37,25 @@ A *Virtual* part is one which does not physically exist but should still be trac
 
 ### Template
 
-A *Template* part is one which can have *variants* which exist underneath it. [Read further information about template parts here](../template).
+A *Template* part is one which can have *variants* which exist underneath it. [Read further information about template parts here](./template.md).
 
 ### Assembly
 
-If a part is designated as an *Assembly* it can be created (or built) from other component parts. As an example, a circuit board assembly is made using multiple electronic components, which are tracked in the system. An *Assembly* Part has a Bill of Materials (BOM) which lists all the required sub-components. [Read further information about BOM management here](../../build/bom).
+If a part is designated as an *Assembly* it can be created (or built) from other component parts. As an example, a circuit board assembly is made using multiple electronic components, which are tracked in the system. An *Assembly* Part has a Bill of Materials (BOM) which lists all the required sub-components. [Read further information about BOM management here](../build/bom.md).
 
 ### Component
 
-If a part is designated as a *Component* it can be used as a sub-component of an *Assembly*. [Read further information about BOM management here](../../build/bom)
+If a part is designated as a *Component* it can be used as a sub-component of an *Assembly*. [Read further information about BOM management here](../build/bom.md)
 
 ### Trackable
 
 Trackable parts can be assigned batch numbers or serial numbers which uniquely identify a particular stock item. Trackable parts also provide other features (and restrictions) in the InvenTree ecosystem.
 
-[Read further information about trackable parts here](../trackable).
+[Read further information about trackable parts here](./trackable.md).
 
 ### Purchaseable
 
-If a part is designated as *Purchaseable* it can be purchased from external suppliers. Setting this flag allows parts to be added to [purchase orders](../../buy/po).
+If a part is designated as *Purchaseable* it can be purchased from external suppliers. Setting this flag allows parts to be added to [purchase orders](../companies/po.md).
 
 ### Salable
 

docs/part/test.md

@@ -39,4 +39,4 @@ If this flag is set, then a corresponding test result against a stock item must
 
 ### Test Results
 
-Individual stock item objects can have test results associated with them which correspond to test templates. Refer to the [stock test result](../../stock/test) documentation for further information.
+Individual stock item objects can have test results associated with them which correspond to test templates. Refer to the [stock test result](../stock/test.md) documentation for further information.

docs/part/trackable.md

@@ -8,7 +8,7 @@ Denoting a part as *Trackble* changes the way that [stock items](../../stock/sto
 
 For many parts in an InvenTree database, simply tracking current stock levels (and locations) is sufficient. However, some parts require more extensive tracking than simple stock level knowledge.
 
-Any stock item associated with a trackable part *must* have either a batch number or a serial number. This includes stock created manually or via an internal process (such as a [Purchase Order](../../buy/po) or a [Build Order](/../../build/build)).
+Any stock item associated with a trackable part *must* have either a batch number or a serial number. This includes stock created manually or via an internal process (such as a [Purchase Order](../companies/po.md) or a [Build Order](../build/build.md)).
 
 
 ## Assign Serial Numbers

docs/part/views.md

@@ -32,13 +32,13 @@ A Part is defined in the system by the following parameters:
 
 ## Parameters
 
-Parts can have multiple defined [parameters](../parameter).
+Parts can have multiple defined [parameters](./parameter.md).
 
 ## Variants
 
 If a part is a *Template Part* then the *Variants* tab will be visible.
 
-[Read about Part templates](../template)
+[Read about Part templates](./template.md)
 
 ## Stock
 
@@ -70,7 +70,7 @@ The *Allocated* tab displays how many units of this part have been allocated to
 
 ## BOM
 
-The *BOM* tab displays the [Bill of Materials](../../build/bom) - a list of sub-components used to build an assembly. Each row in the BOM specifies a quantity of another Part which is required to build the assembly. This tab is only visible if the Part is an *assembly* (meaning it can be build from other parts).
+The *BOM* tab displays the [Bill of Materials](../build/bom.md) - a list of sub-components used to build an assembly. Each row in the BOM specifies a quantity of another Part which is required to build the assembly. This tab is only visible if the Part is an *assembly* (meaning it can be build from other parts).
 
 ## Build Orders
 
@@ -102,7 +102,7 @@ The *Sales Orders* tab shows a list of the sales orders for this part. It provid
 
 ## Tests
 
-If a part is marked as *trackable*, the user can define tests which must be performed on any stock items which are instances of this part. [Read more about testing](../test).
+If a part is marked as *trackable*, the user can define tests which must be performed on any stock items which are instances of this part. [Read more about testing](./test.md).
 
 ## Attachments