BlenderBIM: typo fixes

src/blenderbim/docs/devs/running_tests.rst

@@ -7,8 +7,8 @@ The BlenderBIM Add-on has three layers of tests for each of its three technology
 layers:
 
 1. **Core tests**: abstract domain logic unit tests agnostic of Blender
-2. **Tool tests**: low-level concrete unit tests dependant on Blender
-3. **BIM tests**: high-level integration UI and smoke tests dependant on Blender
+2. **Tool tests**: low-level concrete unit tests dependent on Blender
+3. **BIM tests**: high-level integration UI and smoke tests dependent on Blender
 
 These tests use ``pytest`` as the test framework and runner, so install it:
 

src/blenderbim/docs/devs/undo_system.rst

@@ -2,7 +2,7 @@ Undo system
 ===========
 
 Supporting undo and redo is quite a complex problem because the Blender undo
-system only keeps track of changes occuring in the Blender system. However,
+system only keeps track of changes occurring in the Blender system. However,
 changes actually occur in two other locations that Blender doesn't know about:
 the IFC dataset, and the BlenderBIM Add-on system that synchronises Blender and
 the IFC dataset.

src/blenderbim/docs/devs/ux_guidelines.rst

@@ -23,7 +23,7 @@ BIM will by definition contain a (big) number of submodules or subschemas. Grant
 
   - Tools to create, modify or delete items are in the dedicated Toolbar (The left one)   in the 3D viewport
   
-  - Some Misc tools and informations are displayed in the N panel of the 3D viewport .   They're shortcuts to things that are already present elsewhere in the UI, but are   handy to have when modifying objects or geometry in the Viewport.
+  - Some Misc tools and information are displayed in the N panel of the 3D viewport .   They're shortcuts to things that are already present elsewhere in the UI, but are   handy to have when modifying objects or geometry in the Viewport.
   
   - Adding specific Import / Export IFC operators (arguably a bit misleading since   BlenderBim does more than import / export in these operations)
 
@@ -87,7 +87,7 @@ Icons
 
 **Use** : To disable the edition state of a particular item.
 
-**Expected result** : A part of the interface showing the item attributes is either shrinked down or hidden. The button is usually replaced by a button to delete this item.
+**Expected result** : A part of the interface showing the item attributes is either shrunk down or hidden. The button is usually replaced by a button to delete this item.
 
 * .. image:: https://user-images.githubusercontent.com/25156105/137271575-dcae9e56-3c64-4d8b-89b0-6cf103b999f2.png
 
@@ -139,7 +139,7 @@ Icons
 
 **Use** : to import a particular file from the user's computer's directory to the current context
 
-**Expected result** : A new file browser window should open, with sufficient information provided to the user to know which file type should be loaded in (eg adding a file extension, adding information in the filebrowser UI). When the file is loaded, the interface should expand to show the attributes or informations or new context-sensitive operations provided by the imported file.
+**Expected result** : A new file browser window should open, with sufficient information provided to the user to know which file type should be loaded in (eg adding a file extension, adding information in the filebrowser UI). When the file is loaded, the interface should expand to show the attributes or information or new context-sensitive operations provided by the imported file.
 
 **Proposal** : Currently there are some instances where I don't know if the elements are supposed to require an external file, eg 
  

src/blenderbim/docs/devs/writing_docs.rst

@@ -2,7 +2,7 @@ Writing docs
 ============
 
 The following colours and annotation styles should be used for annotating
-images. All stroke widths are 3px with a corner radius of 3px.  Horizonal
+images. All stroke widths are 3px with a corner radius of 3px.  Horizontal
 underlines are 5px with a corner radius of 2px. The dark green is **39b54a** and
 the light green is **d9e021**.
 

src/blenderbim/docs/users/georeferencing.rst

@@ -63,7 +63,7 @@ Northings, and Orthogonal Height in the **IFC Georeferencing** panel.
 
 When **Local engineering coordinates** are used, typically the architect will
 nominate a local origin and model geometry will be drawn orthogonally (i.e.
-along the X and Y axis). This local origin often correlates with a site bounary,
+along the X and Y axis). This local origin often correlates with a site boundary,
 surveyed point, or grid intersection. This means that the model's coordinates
 are typically smaller numbers and correlate to surface distance measurements,
 not Eastings and Northings, and the model's +Y axis will point to **Project
@@ -205,7 +205,7 @@ True north
 
 When **Local engineering coordinates** are used, the model's +Y axis points to
 **Project North** for the convenience of drafting. When **Map Coordinates** are
-used, the model's +Y axis points to **Grid North** for the neccessity of
+used, the model's +Y axis points to **Grid North** for the necessity of
 surveying.
 
 **Project North** and **Grid North** is different to **True North**. The angle