Fix typos, grammars and improve wording of the docs

docs/source/int_introduction.rst

@@ -7,20 +7,20 @@ Introduction
 novelWriter is a simple, multi-document plain text editor using a modified markdown syntax to apply
 simple formatting to the text. It is designed for writing novels, and allows for the component
 documents to be ordered freely to create the desired structure of the novel. More details about how
-projects are structured is covered on the :ref:`a_struct` page.
+projects are structured is covered in :ref:`a_struct`.
 
 In addition, the project can contain notes on the various plot elements, characters, locations,
 etc, that make up the story. These notes are organised in a set of category-specific top-level
 folders (root folders), and each entry can be tagged and cross-referenced from within the novel
 documents and notes. These tags make it possible to inter-link documents, and generate an overview
 of the entire novel project and how the various documents and plot elements are interconnected.
-This is covered on the :ref:`a_proj` and :ref:`a_notes` pages.
+This is covered in :ref:`a_proj` and :ref:`a_notes`.
 
 These additional features are not standard in markdown, but are available through special meta
 keywords described in :ref:`a_struct_tags`. Syntax highlighting is provided to make it easier to
 verify that the markdown tags are used correctly.
 
-An overview of the supported markdown syntax is covered on the :ref:`a_ui` page.
+An overview of the supported markdown syntax is covered in :ref:`a_ui`.
 
 
 .. _a_intro_design:
@@ -36,7 +36,7 @@ at the same time provide a complete set of features needed for writing a novel.
    links, tables, and other complex structures and objects often needed for such documents.
    Formatting is limited to headers, and bold, italicised and strikethrough text.
 
-The main window does not have a toolbar like most other applications do. This reduces clutter, and
+The main window does not have a toolbar like many other applications do. This reduces clutter, and
 since the documents are formatted with markdown tags, is more or less redundant. However, all
 formatting features supported are available through convenient keyboard shortcuts. They are also
 available in the main menu. A full list of shortcuts can be found in the :ref:`a_ui_shortcuts`
@@ -51,9 +51,10 @@ menu. A number of syntax highlighting themes are also available in :guilabel:`Pr
 of icon themes in colour and greyscale are also offered. The icons are based on the Typicons_ icon
 set designed by Stephen Hutchings.
 
-The main window is split in two, or optionally three, panels. The left-most contains the project
-tree and all the documents in your project. The second panel is the document editor, and the
-optional third panel is a document viewer which can view any document in your project.
+The main window is split in two, or optionally three, panels. The left-most panel contains the
+project tree and all the documents in your project. The second panel is the document editor, and
+the optional third panel is a document viewer which can view any document in your project
+independently of the document editor.
 
 A second tab is also available on the main window. This is the :guilabel:`Outline` tab where the
 entire novel structure can be displayed, with all the tags and references listed. Depending on how
@@ -69,7 +70,7 @@ itself as it appears in the text of the documents.
 Project Layout
 ==============
 
-You are free to structure your project documents as you wish in subfolders, and split the text
+You are free to organise your project documents as you wish into subfolders, and split the text
 between documents in whatever way suits you. All that matters to novelWriter is the linear order
 the documents appear at in the project tree (top to bottom). The chapters, scenes and sections of
 the novel are determined by the headings within those documents.
@@ -83,7 +84,7 @@ The four heading levels (**H1** to **H4**) are treated as follows:
 
 This header level structure is only taken into account for novel documents. For the project notes,
 the header levels have no structural meaning, and the user is free to do whatever they want. See
-the :ref:`a_struct` and :ref:`a_notes` pages for more details.
+:ref:`a_struct` and :ref:`a_notes` for more details.
 
 
 .. _a_intro_export:
@@ -106,8 +107,7 @@ Python dictionary with a couple of lines of code.
 
 A number of filter options can be applied to the produced document, allowing you to export a draft
 manuscript, a reference document of notes, an outline based on chapter and scene titles with a
-synopsis each, and so on. See the :ref:`a_export` page for more details on export features and
-formats.
+synopsis each, and so on. See :ref:`a_export` for more details on export features and formats.
 
 
 .. _a_intro_screenshots: