Update based on feedback from Stein

Documentation/UsersGuide/GettingStarted.md

@@ -36,11 +36,11 @@ In the main area of the application, several 3D views can be open at the same ti
 
 #### Editing the views
 
-Most of the settings and features of ResInsight is accesible through the **Project Tree** and the **Property Editor**. Selecting an item in the **Project Tree** activates the corresponding 3D View, and shows the Items properties in the **Property Editor**, available for editing. 
+Most of the settings and features of ResInsight is accessible through the **Project Tree** and the **Property Editor**. Selecting an item in the **Project Tree** activates the corresponding 3D View, and shows the item properties in the **Property Editor** available for editing. 
 
 Toggling a checkbox next to an item in the **Project Tree** will toggle visibility in the 3D view. Toggling a checkbox for a collection of items will affect the visibility for all items in the collection. ![](images/TreeViewToggle.png)
 
-Context menu commands are also available, to do special operations on a selected set of items.
+Context menu commands are also available to do special operations on a selected set of items.
 
 ### Cases and their types
 
@@ -51,7 +51,7 @@ three different Case types:
 This is a Case based on the results of an Eclipse analysis, read from a grid file together with restart data.
 
 ##### Input case ![](images/EclipseInput24x24.png) 
-This Case type is based on a `*.GRDECL` file, or a part of an Eclipse *Input* file. This Case type supports loading single ascii files defining Eclipse Cell Properies, and also to export miodified property sets to ascii files.
+This Case type is based on a `*.GRDECL` file, or a part of an Eclipse *Input* file. This Case type supports loading single ASCII files defining Eclipse Cell Properties, and also to export modified property sets to ASCII files.
 Each of the Eclipse properties is listed as separate entities in the **Project Tree**, and can be renamed and exported.
 
 #####  Statistics case ![](images/Histogram24x24.png)
@@ -59,7 +59,7 @@ This is a Case type that belongs to a *Grid Case Group* and makes statistical ca
 
 #### Grid Case Groups ![](images/GridCaseGroup24x24.png) 
 
-A **Grid Case Group** is a group of **Result Cases** whith identical grids, but generally different active cells, initial values and results. These cases are called *Source Cases*. 
+A **Grid Case Group** is a group of **Result Cases** with identical grids, but generally different active cells, initial values and results. These cases are called *Source Cases*. 
 
 The purpose of a Grid Case group is to make it easy to calculate statistics across the source cases both for static and dynamic Eclipse Properties. 
 
@@ -69,7 +69,7 @@ See [ Multiple realizations and statistics ](CaseGroupsAndStatistics.md) for mor
 
 #### Input data support ###
 
-ResInsight supports the follwing type of Eclipse input data:
+ResInsight supports the following type of Eclipse input data:
 - `*.GRID` and `*.EGRID` files along with their `*.INIT` and restart files `*.XNNN` and `*.UNRST`. 
 - Grid and Property data from  `*.GRDECL` files.
 
@@ -79,9 +79,9 @@ ResInsight supports the follwing type of Eclipse input data:
 1. Select **File->Import->Import Eclipse Case** and select an `*.EGRID` or `*.GRID` Eclipse file for import.
 2. The case is imported, and a view of the case is created
 
-*TIP:* You can select several grid files in one go.
+*TIP:* You can select several grid files in one go by multiple selection of files( Ctrl + left mouse button, Shift + left mouse button). 
 
-##### Eclipse ascii input data
+##### Eclipse ASCII input data
 1. Select **File->Import->Import Input Eclipse Case** and select a `*.GRDECL` file.
 2. The case is imported, and a view of the case is created
 3. Right click the **Input Properties** in the generated **Input Case** and use the context menu to import additional Eclipse Property data files.
@@ -95,7 +95,7 @@ The X and Y grid data can be negated in order to make the Grid model appear corr
 
 ### Model navigation 
 
-ResInsight comes with two 3D navigation modes. The active mode can be selected in the **Preferences** dialog (**Edit->Preferences**).
+ResInsight comes with two 3D navigation modes. The active mode can be selected in the **Preferences** dialog (**Edit -> Preferences**).
 
 Abbreviation | Meaning
 -------------|-------
@@ -131,27 +131,27 @@ LMB single click  | Update status bar and **Result Info**
 ### Project files and Cache directory
 
 ResInsight stores which cases you have imported and all the settings for each view etc. in a project file with the extension `.rsp`.
-This file only contains references to the real data files, and even references to datafiles generated by ResInsight itself.
+This file only contains references to the real data files, and even references to data files generated by ResInsight itself.
 
-Statistics calculations, property sets you generate by using Octave and well paths are saved to a folder in the same directory as you save the project file, and is named \<ProjectFileName\>_cache. So if you need to move your project, make sure you move this folder as well.
+Statistics calculations, property sets you generate by using Octave, and well paths are saved to a folder in the same directory as you save the project file, and is named \<ProjectFileName\>_cache. So if you need to move your project, make sure you move this folder as well.
 
 *TIP:* The `.rsp`-file is an XML file, and can be edited by any text editor.  
 
 ### Export options
 #### Snapshot images 
 ##### Single View ![](images/SnapShot.png) ![](images/SnapShotSave.png)
-Image export of current 3D view can be launched from **File->Export->Snapshot To File**. A snapshot can also be copied to clipboard using **Edit->Copy Snapshot To Clipboard**. 
+Image export of current 3D view can be launched from **File -> Export -> Snapshot To File**. A snapshot can also be copied to clipboard using **Edit->Copy Snapshot To Clipboard**. 
 
 ##### All Views ![](images/SnapShotSaveViews.png)
-If a project contains multiple views, all views can be exported using **File->Export->Snapshot All Views To File**. 
+If a project contains multiple views, all views can be exported using **File -> Export -> Snapshot All Views To File**. 
 
-There is also possible to launch snapsotting of all the views from the command line. See  [ Command Line Arguments]      (CommandLineParameters.md)
+It is also possible to snapshot all views from the command line. See  [ Command Line Arguments]      (CommandLineParameters.md)
 
 
 
 
-#### Export of Eclipse Properties as Ascii data
-Eclipse Properties can be exported to Eclipse Ascii files by activating the context menu for a **Cell Result**. ![](images/ExportProperty.png) 
+#### Export of Eclipse Properties as ASCII data
+Eclipse Properties can be exported to Eclipse ASCII files by activating the context menu for a **Cell Result**. ![](images/ExportProperty.png) 
 
 The command will export the property set currently loaded and shown in the 3D View to a file with the following format:
 

Documentation/UsersGuide/ReservoirViews.md

@@ -12,20 +12,20 @@ The **Cell Result** item defines which Eclipse property the 3D View uses for the
 
 ### Cell Edge Results ![](images/EdgeResult_1.png)
 
-The **Cell Edge Result** visualization mode is one of ResInsights special features. Its main use is to show the MULT(X, Y, Z) properties at the same time. 
-This will show the MULT property values *different from 1.0* along the correct edges og the cells. In effect this highlights the Faults, and makes it easy to verify all the MULT values in one go.
+The **Cell Edge Result** visualization mode is one of ResInsight's special features. Its main use is to show the MULT(X, Y, Z) properties at the same time. 
+This will show the MULT property values *different from 1.0* along the correct edges of the cells. In effect this highlights the faults and makes it easy to verify all the MULT values in one go.
 
 ![](images/CellEdgeExample.png)
 
-ResInsight supports all Properties ending with X, Y, Z or (X-, Y-, Z-) but without the filtering done for the MULT propery.
+ResInsight supports all properties ending with X, Y, Z and X-, Y-, Z-. However, it is only the MULT property that ignores values of 1.0.
 
-When selecting a result variable for cell edge, a second legend shows up in the 3D view. Color legend management is available when selecting the **Legend Definition** item belonging to the **Cell Edge Result** item. 
+When selecting a result variable for cell edge, a second legend shows up in the 3D view showing the variation in values for this second property. Color legend management is available when selecting the **Legend Definition** item belonging to the **Cell Edge Result** item. 
 
 ### Info Box
 
 The **Info Box** controls the visibility of the animation progress, the Case description box, and the results histogram.
 
-The **Results Histogram** shows a histogram of the complete timeseries of the currently loaded **Cell Result** together with:
+The **Results Histogram** shows a histogram of the complete time series of the currently loaded **Cell Result** together with:
 
 - The mean value ( a blue line ) 
 - P10 and P90 ( red lines )
@@ -36,9 +36,9 @@ The **Results Histogram** shows a histogram of the complete timeseries of the cu
 ### Cell Filters
 Cell Filters are used to control visibility of the cells in the 3D view. Three types of filters exists:
 
-- **Range filter**    : 		Define a IJK subset of the model.
-- **Property filter** : 	Define a value range for a property to control cell visibility.
-- **Well cell filter** : 	Display grid cells that has connections to a well. Controlled from the **Simulation Wells** item.
+- **Range filter**     : Define a IJK subset of the model.
+- **Property filter**  : Define a value range for a property to control cell visibility.
+- **Well cell filter** : Display grid cells that has connections to a well. Controlled from the **Simulation Wells** item.
 
 All filters can be turned on or off using the toggle in the **Project Tree** and controlled from their corresponding **Property Editor**.
 
@@ -53,11 +53,11 @@ Below is a snapshot of the **Property Editor** of the **Range Filter** :
 
 ![](images/RangeFilterProperties.png)
 
- - **Filter Type** The filter can either make the specified range visible ( *Include* ), or remove the range from the View ( *Exclude* ).
- - **Grid** This option selects which of the grids the range is addressing.
- - **Apply to Subgrids** This option tells ResInsight to use the visibility of the cells in the current grid to control the visibility of the cells in sub-LGR's. If this option is turned off, Sub LGR-cells is not included in this particular Range Filter.  
+ - **Filter Type** : The filter can either make the specified range visible ( *Include* ), or remove the range from the View ( *Exclude* ).
+ - **Grid** :  This option selects which of the grids the range is addressing.
+ - **Apply to Subgrids** : This option tells ResInsight to use the visibility of the cells in the current grid to control the visibility of the cells in sub-LGR's. If this option is turned off, Sub LGR-cells is not included in this particular Range Filter.  
  
-The **Start** and **Width** labels in front of the sliders features a number in parenthesis.<br>
+The **Start** and **Width** labels in front of the sliders features a number in parenthesis denoting maximum available value.<br>
 The **Start** labels shows the index of the start of the active cells.<br>
 The **Width** labels shows the number of active cells from the start of the active cells.
 
@@ -67,7 +67,7 @@ The **Width** labels shows the number of active cells from the start of the acti
   
 ![](images/PropertyFilterProperties.png)
 
-This filter filters the cells based on a property value range (Min - Max). Cells whithin the range is either shown or hidden depending the **Filter Type**.( *Include* / *Exclude* ). Exclude-filters removes the selected cells from the View even if some other filter includes them.
+This filter filters the cells based on a property value range (Min - Max). Cells in the range are either shown or hidden depending on the **Filter Type** ( *Include* / *Exclude* ). Exclude-filters removes the selected cells from the **View** even if some other filter includes them.
 
 A new property filter can be made by activating the context menu for **Property Filters**. The new property filter is based on the currently viewed cell result by default.
 
@@ -95,7 +95,7 @@ The Property Editor of the **Simulation Wells** item is shown below:
 -  **Use Well Fence** and 
 -  **Well Fence direction** Controls whether to add extensions of the well cells in the I, J or K direction to the set of range filtered cells
 - **Well head** These options control the appearance and position of the well labels and and symbols of the top of the well
-- **Global Well Pipe Visibility** Controls when and whether to show the pipe representationof the wells. The options are:
+- **Global Well Pipe Visibility** Controls if and when to show the pipe representation of the wells. The options are:
    - *All On* will show the pipes from all wells disregarding the individual settings on the well.
    - *All Off* will hide all simulation well pipes. 
 		- *Individual* Will respect the individual settings for each well, and only show the well pipes from the wells with this option set on. See below.
@@ -109,10 +109,10 @@ The Property Editor of the **Simulation Wells** item is shown below:
 ##### Well pipes of Multi Segment Wells
 
 ###### Geometry approximated
-The pipe geometry generated for MSW's are based on the topology of the well (branch/segment structure) and the position of the cells beeing connected. The segement lengths are used as hints to place the branch points at sensible places. Thus the pipe geometry itself is not geometrically correct, but makes the topology of the well esier to see.
+The pipe geometry generated for MSW's are based on the topology of the well (branch/segment structure) and the position of the cells being connected. The segment lengths are used as hints to place the branch points at sensible places. Thus the pipe geometry itself is not geometrically correct, but makes the topology of the well easier to see.
 
 ###### Dummy branches
-Often MSW's are modelled using a long stem without connections and a multitude of small branches; one for each connection. ResInsight offsets the the pipe within the cell to clearly show how the topology of the well is defined.
+Often MSW's are modeled using a long stem without connections and a multitude of small branches; one for each connection. ResInsight offsets the the pipe within the cell to clearly show how the topology of the well is defined.
 
 ![](images/MSWDummyBranchExample.png)
 
@@ -124,12 +124,12 @@ Branch and segment info of a MSW-connected-Cell is shown in the **Result Info**
 
 Each of the wells can have some individual settings. These options works as specializations of the ones set on the global level (**Simulation Wells** See above) but will *only come into play when they are not ignored by the global settings*.
 
-This is paticularly important to notice for the **Show Well Pipe** and **Range Filter** options. They will not have effect if the corresponding global settings in **Simulation Wells** allows them to.
+This is particularly important to notice for the **Show Well Pipe** and **Range Filter** options. They will not have effect if the corresponding global settings in **Simulation Wells** allows them to.
  
 The properties of a single well are shown below.
 
 ![](images/WellProperties.png)
 
-There are only one option that needs further explanation:
+One option needs further explanation:
 
 - **Pipe Radius Scale** This option is a scale that is added to the "global" scale set in the **Simulation Wells** properties.