doc: Moved more sections from README into new locations.

Author: Paebbels

doc/Installation.rst

@@ -3,25 +3,27 @@
 Installation/Updates
 ####################
 
-.. image:: https://img.shields.io/badge/OSVVM-OsvvmLibraries-EDB74E.svg?longCache=true&logo=GitHub&labelColor=333333
+.. image:: https://img.shields.io/badge/OSVVM-OSVVM--Scripts-EDB74E.svg?longCache=true&logo=GitHub&labelColor=333333
    :alt: Sourcecode on GitHub
    :height: 22
-   :target: https://github.com/OSVVM/OsvvmLibraries
+   :target: https://github.com/OSVVM/OSVVM-Scripts
 .. image:: https://img.shields.io/github/v/tag/OSVVM/OsvvmLibraries
    :target: https://github.com/OSVVM/OsvvmLibraries/releases/latest
    :alt: GitHub Release
 
-OSVVM is hosted and developed on https://github.com/OSVVM. It's components are split into multiple Git repositories,
-which be used individually or as a group. The all-in-one repository is called
+OSVVM is hosted and developed at https://github.com/OSVVM. It's components are split into multiple Git repositories,
+which can be used individually or as a group. The all-in-one repository is called
 `OsvvmLibraries <https://github.com/OSVVM/OsvvmLibraries>`__.
 
+See :ref:`INSTALL/Download` for downloadable archives.
 
-OSVVM is available as either a git repository OSVVM Libraries or a zip file from osvvm.org Downloads Page.
+
+.. _INSTALL/Clone:
 
 Clone OsvvmLibraries
 ********************
 
-OsvvmLibraries summarizes all OSVVM repositories into a single parent repository, which has OSVVM's components
+OsvvmLibraries aggregates all OSVVM repositories into a single parent repository, which has OSVVM's components
 registered as Git submodules. |br|
 When cloning ensure to append the ``–recursive`` flag.
 
@@ -34,6 +36,8 @@ When cloning ensure to append the ``–recursive`` flag.
    Git Documentation: `git clone <https://git-scm.com/docs/git-clone>`__
 
 
+.. _INSTALL/Submodule:
+
 Register OsvvmLibraries as Git Submodule
 ****************************************
 
@@ -51,13 +55,18 @@ OSVVM as a submodule into that project. The following commands assume, OSVVM get
    Git Documentation: `git submodule add <https://git-scm.com/docs/git-submodule>`__
 
 
+.. _INSTALL/IndividualSubmodules:
+
 Register Individual VCs as Git Submodule
 ****************************************
 
 .. todo::
 
    describe individual submodule workflow
 
+
+.. _INSTALL/Updating:
+
 Updating OSVVM or OSVVM Components
 **********************************
 
@@ -66,6 +75,8 @@ Updating OSVVM or OSVVM Components
    describe update process using Git
 
 
+.. _INSTALL/Download:
+
 Download OSVVM Libraries
 ************************
 
@@ -85,6 +96,14 @@ OsvvmLibraries is also offered as an archive at https://github.com/OSVVM/OsvvmLi
    OSVVM added a CI job for packaging all sources (incl. submodules) into a single archive.
 
 
+.. todo::
+
+   OSVVM is available as either a git repository OSVVM Libraries or a zip file from osvvm.org Downloads Page.
+
+   `Downlaods from osvvm.org <https://osvvm.org/downloads>`__
+
+.. _INSTALL/BusinessContinuity:
+
 Business Continuity Planning
 ****************************
 
@@ -95,4 +114,3 @@ Business Continuity Planning
    1. fork on GitHub
    2. mirror to local Git server (e.g. GitLab)
    3. clone to local machine
-

doc/QuickStartGuide.rst

@@ -3,6 +3,10 @@
 Quick Start Guide
 #################
 
+.. important::
+
+   If you haven't installed OsvvmLibraries yet, please get OSVVM using one of the described methods in :ref:`INSTALL`
+
 Create a Simulation directory
 *****************************
 
@@ -15,6 +19,13 @@ The following assumes you have created a directory named :file:`sim` in the :fil
 Alternately, you can run simulations out of the Scripts, but cleanup is a mess as a simulator tends to create numerous
 temporaries.
 
+.. todo::
+
+   Is :file:`sim_vendor-name` still valid?
+
+   What about :file:`temp`?
+
+
 Start the Script environment in the Simulator
 *********************************************
 
@@ -132,3 +143,13 @@ API. The script API is created using Tcl procedures.
 
       If you were to open :file:`testbench_MultipleMemory.pro`, you would find that ``RunTest`` is used instead as it is
       an abbreviation for the ``analyze``, ``TestName`` and ``simulate`` when the names are the same.
+
+
+Regression.tcl
+**************
+
+.. todo::
+
+   Show how a regression.tcl could look like assuming OSVVM is a git submodule.
+
+