Fix common spelling mistakes (#4956)

* add codespell

* first fixes

* doc fixes

* fix docstrings and comments

* functional changes

* docstrings again

* and docs again

* rename args

* add ignore

* use pre-commit for filtering instead

* ups

* fix typo in filter

docs/docs/build/allocate.md

@@ -112,7 +112,7 @@ Set this option to *True* to signal that stock items can be used interchangeably
 
 **Substitute Stock**
 
-Set this option to *True* to allow substitute parts (as specifed by the BOM) to be allocated, if the primary parts are not available.
+Set this option to *True* to allow substitute parts (as specified by the BOM) to be allocated, if the primary parts are not available.
 
 ## Allocating Tracked Stock
 

docs/docs/build/bom.md

@@ -58,7 +58,7 @@ When using the InvenTree [template / variant](../part/template.md) feature, it m
 
 If a BOM Line Item is designed as *Inherited*, it will be automatically included in the BOM of any part which is a variant (or sub-variant) of the part for which the BOM Line Item is defined.
 
-This is particulary useful if a template part is defined with the "common" BOM items which exist for all variants of that template.
+This is particularly useful if a template part is defined with the "common" BOM items which exist for all variants of that template.
 
 Consider the example diagram below:
 
@@ -140,7 +140,7 @@ To process with BOM validation, click on the <span class='fas fa-clipboard-check
 
 ## Multi Level BOMs
 
-Multi-level (hierarchical) BOMs are natively supported by InvenTree. A Bill of Materials (BOM) can contain sub-assemblies which themselves have a defined BOM. This can continue for an unlimted number of levels.
+Multi-level (hierarchical) BOMs are natively supported by InvenTree. A Bill of Materials (BOM) can contain sub-assemblies which themselves have a defined BOM. This can continue for an unlimited number of levels.
 
 When viewing a BOM table, sub-assemblies are not loaded by default, but can be loaded "on demand" by pressing the <span class='fas fa-sync-alt'></span> icon associated with the particular subassembly:
 

docs/docs/build/build.md

@@ -83,7 +83,7 @@ Each *Build Order* has an associated *Status* flag, which indicates the state of
 
 When a *Build Order* is created, we then have the ability to *allocate* stock items against that build order. The particular parts we need to allocate against the build are specified by the BOM for the part we are assembling.
 
-- A *Stock Alloction* links a certain quantity of a given *Stock Item* to the build.
+- A *Stock Allocation* links a certain quantity of a given *Stock Item* to the build.
 - At least one stock allocation is required for each line in the BOM
 - Multiple stock allocations can be made against a BOM line if a particular stock item does not have sufficient quantity for the build
 
@@ -198,7 +198,7 @@ To complete a build, click on <span class='fas fa-tools'></span> icon on the bui
 The form will validate the build order is ready to be completed, and will prevent you from continuing if any of the below conditions are present unless you select one of the presented options to override the validation and accept completion of the build anyway.
 
 !!! info "Incomplete Build"
-	If the warning message `Required build quantity has not been completed` is shown, you have build ouputs that have not yet been completed.
+	If the warning message `Required build quantity has not been completed` is shown, you have build outputs that have not yet been completed.
 
 	In the unlikely event that you wish to proceed despite this, you can toggle the `Accept Incomplete` option to true to override the error and allow completion without the required number of build outputs.