Fix spelling errors found by codespell

Author: magnesj

content/3d-main-window/3DViews.md

@@ -76,7 +76,7 @@ The <b>Info Box</b> settings can be activated by clicking on the Info Text in th
 
 ![](/images/3d-main-window/ViewTreeGrids.png)
 
-The **Grids** {{< image-in-text src="images/3d-main-window/draw_style_meshlines_24x24.png" >}} node contains child nodes for **Main Grid**, **LGRs** and **Temporary LGRs** where each grid's visibilty can be controlled. The **LGRs** node contains all LGRs loaded from file, while **Temporary LGRs** contains all temporary LGRs (see [Completions LGR]({{% relref "completionslgr" %}})).
+The **Grids** {{< image-in-text src="images/3d-main-window/draw_style_meshlines_24x24.png" >}} node contains child nodes for **Main Grid**, **LGRs** and **Temporary LGRs** where each grid's visibility can be controlled. The **LGRs** node contains all LGRs loaded from file, while **Temporary LGRs** contains all temporary LGRs (see [Completions LGR]({{% relref "completionslgr" %}})).
 Toggling **Grids** off will hide all grids cell geometry. This option is used to display geometry for faults and intersections. This feature is also available as a toolbutton called *Hide grid cells*.
 
 ### Intersections 

content/3d-main-window/AllanDiagrams.md

@@ -10,7 +10,7 @@ weight = 91
 
 ## Separate Fault Result
 
-The **Allan Diagram** is dispayed by selecting the **Separate Fault Result** in the project tree. 
+The **Allan Diagram** is displayed by selecting the **Separate Fault Result** in the project tree. 
 ![](/images/3d-main-window/AllanDiagramPropertyEditor.png)
 
 See [Faults ]({{% relref "faults/#separate-fault-result" %}}) for more details.

content/3d-main-window/Annotations.md

@@ -17,7 +17,7 @@ ResInsight supports displaying a few types of annotations in 3D views and Contou
 ## Global scope vs local scope annotations
 Global annotations may be displayed in all views and are located in the **Annotations** project tree node right below **Grid Models** (Global annotations sub tree). Local annotations are associated with a specific view and are located in the **Annotations** project tree node below the view node (Local annotations sub tree). All annotation types except text annotations are global only. Text annotation may be either global or local.
 
-All global annotations also have a representation in the local **Annotation** tree node in order to toggle visibilty per view. Those annotations are located in tree nodes starting with **Global**.
+All global annotations also have a representation in the local **Annotation** tree node in order to toggle visibility per view. Those annotations are located in tree nodes starting with **Global**.
 
 ![](/images/3d-main-window/LocalAnnotationsTree.png)<br/>
 Local annotations sub tree
@@ -35,7 +35,7 @@ There are two ways of creating a new text annotation.
 
 - **Anchor Point** - The interesting point in the view
 - **Label Point** - The point where the text label is placed
-- **Text** - The text to display. Multiline supprted. The first line will be the name of the annotation in the project tree
+- **Text** - The text to display. Multiline supported. The first line will be the name of the annotation in the project tree
 - **Text appearance** - Set font size, font color, background color and anchor line color
 
 When a text annotation tree node is selected, target markers in each end of the anchor line are displayed. The targets can be clicked and dragged. Clicking the blue part lets the user drag the target vertically (along Z axis). Clicking the magenta part lets the user drag the target in the XY plane.
@@ -59,7 +59,7 @@ To create a user defined polyline annotation, right click **Annotations** or **U
 - **Start Picking Points / Stop Picking Points** - Button to start / stop picking mode
 - **Line Appearance** - Set line color and thickness
 
-When a user defined polyline annotation tree node is selected, the polyline target markers become visible. Those can be dragged around as decribed above.
+When a user defined polyline annotation tree node is selected, the polyline target markers become visible. Those can be dragged around as described above.
 
 ## Polyline Imported From File
 To import a polyline annotation from file, right click **Annotations** or **Polylines From File** tree node in the global annotations sub tree. Then select the file to import and click OK. Imported polyline annotations are not editable.
@@ -91,6 +91,6 @@ Define each point as three double per line (**X Y Depth**). Comment lines are su
 
 
 ## Annotations visibility
-Local annotations visibility is controlled by the check boxes in the local annotations sub tree only. Global annotations visibility, on the other hand, is controlled by the check boxes in both the global and local annotations sub trees. So in order to display a global annotation in a specific view, both the annotation tree note itself and its representation in the local sub tree must have visibilty enabled.
+Local annotations visibility is controlled by the check boxes in the local annotations sub tree only. Global annotations visibility, on the other hand, is controlled by the check boxes in both the global and local annotations sub trees. So in order to display a global annotation in a specific view, both the annotation tree note itself and its representation in the local sub tree must have visibility enabled.
 
 

content/3d-main-window/ColorLegends.md

@@ -47,7 +47,7 @@ Activating this particular *Custom Color Legend* is performed by specifying it a
 
 ## Integer Cell Results
 
-When displaying interger cell results, the default color mapping will be set to a category color mapping. This color legend is used when displaying **Formation Names**. If an integer result is loaded, a custom color legend with names can be used.
+When displaying integer cell results, the default color mapping will be set to a category color mapping. This color legend is used when displaying **Formation Names**. If an integer result is loaded, a custom color legend with names can be used.
 
 Example workflow
 - Select an integer cell result, i.e. FIPNUM

content/3d-main-window/ComparisonView.md

@@ -42,7 +42,7 @@ Properties of an individual view included in a Comparison View are controlled by
 [Cell Filters]({{% relref "filters" %}}),
 and [Intersections]({{% relref "intersections" %}}).
 
-Setting up [Linked Views]({{% relref "linkedviews" %}}) may also be relevant, e.g. to syncronize [cell results]({{% relref "cellresults" %}})
+Setting up [Linked Views]({{% relref "linkedviews" %}}) may also be relevant, e.g. to synchronize [cell results]({{% relref "cellresults" %}})
 and [cell filters]({{% relref "filters" %}}).
 
 {{% notice note %}}

content/3d-main-window/Filters.md

@@ -48,7 +48,7 @@ The available cell filters are:
 
 - **Slice Filter**: Defining a filter to include or exclude a slice of cells in either I-, J-, or K-direction.
 
-The following exemplifies the use of a **Polygon Filter** and target points. Target points are defined and manipulated in 3D view as decribed in [Polygons]({{% relref "polygons" %}}). Vertically, the filter can be set to use the XY target positions or IJK-index of targeted cells. The actual filtering can be specified to whole cells inside polygon, cell center inside polygon, or any cell corner inside polygon.
+The following exemplifies the use of a **Polygon Filter** and target points. Target points are defined and manipulated in 3D view as described in [Polygons]({{% relref "polygons" %}}). Vertically, the filter can be set to use the XY target positions or IJK-index of targeted cells. The actual filtering can be specified to whole cells inside polygon, cell center inside polygon, or any cell corner inside polygon.
 
 ![](/images/3d-main-window/CellFilter_Polygon.png)
 

content/3d-main-window/FlowVectorResult.md

@@ -54,7 +54,7 @@ The Property Editor controls the following settings:
 
 ## Cell Result View
 ResInsight may visualize intercell flows, flow rates, and transmissibilities as *Cell Results* optionally divided by face area, c.f. check-box *Divide By Area* below.
-For instance, the option enables comparison of horisontal and vertical flow velocities as alternative to flow rates as the latter is typically influenced by significant differences in cell face areas.
+For instance, the option enables comparison of horizontal and vertical flow velocities as alternative to flow rates as the latter is typically influenced by significant differences in cell face areas.
 
 ![](/images/3d-main-window/FlowRateCellResultAndLegend.png)
 

content/3d-main-window/Intersections.md

@@ -37,7 +37,7 @@ The property panel of a well path based intersection is shown below:
  ![](/images/3d-main-window/IntersectionWellPath.png)
 
 - **Name** -- Automatically created based on the item specifying the intersection. The user can edit the name, but it will be updated if you change well or well path.
-- **Intersecting Geometry** -- Options to control the curve used for the cross section dependant on the type of intersection.
+- **Intersecting Geometry** -- Options to control the curve used for the cross section dependent on the type of intersection.
 - **Depth Filter** -- Controls the depth/z-range for visible geometry. Can be controlled from the **Intersections** folder object.
 - **K Range Filter** -- Controls the visible K slices. Can be controlled from the **Intersections** folder object.
 

content/3d-main-window/ResultColorLegend.md

@@ -27,7 +27,7 @@ As shown above, the Legend configuration for cell results allows the following s
   - **Current Timestep** -- use of current (single) time step to find min and max values  
   - **User Defined Range** -- user specified range from minimum to maximum numerical value
 
-Furthermore, the legend may display semi-transparent with a sorrounding box by selecting the **Show Box around Legends** option of the 
+Furthermore, the legend may display semi-transparent with a surrounding box by selecting the **Show Box around Legends** option of the 
 [Preferences dialog]({{% relref "preferences" %}}).
 
 ![Legend Background](/images/3d-main-window/legend_background.png) ![Show Box around legends](/images/3d-main-window/legend_with_background.png)

content/3d-main-window/SeismicSections.md

@@ -19,7 +19,7 @@ The following types of Seismic Sections are available:
 - **Inline Section**: A seismic line within a 3D survey *parallel* to the direction in which the data were acquired.
 - **Xline Section**: A seismic line within a 3D survey *perpendicular* to the direction in which the data were acquired.
 - **Depth Slice**: Horizontal slice through the volume data of a 3D survey at a specific depth.
-- **Polyline Section**: Seismic section following a *user defined polyline* ontop a grid model for displaying volume data of a 3D survey, c.f. [Polyline Intersection]({{% relref "intersections" %}}#polyline-intersection) for specification of polyline.
+- **Polyline Section**: Seismic section following a *user defined polyline* on top a grid model for displaying volume data of a 3D survey, c.f. [Polyline Intersection]({{% relref "intersections" %}}#polyline-intersection) for specification of polyline.
 - **Well Path Section**: Seismic section following a *specific well path* through the volume data of a 3D survey.