Updates docs for scenarios/issues

Changes include:
 - Updated scenarios table with final support info for Colorado 1.0
 - Updated known issues for more scenarios
 - Minor RST syntax fixes

Change-Id: Ied751a726a7c9cc062793c78fbac9c6e44e4a882
Signed-off-by: Tim Rozet <trozet@redhat.com>

2 files changed, 22 insertions, 22 deletions

diff --git a/docs/installationprocedure/architecture.rst b/docs/installationprocedure/architecture.rst
index f1861d0a..c2b38d00 100644
--- a/docs/installationprocedure/architecture.rst
+++ b/docs/installationprocedure/architecture.rst
@@ -105,31 +105,32 @@ the installer as a (-d) deploy setting.  Read further in the Apex documentation
 to learn more about invoking the deploy command.  Below is quick reference
 matrix for OPNFV scenarios supported in Apex.  Please refer to the respective
 OPNFV Docs documentation for each scenario in order to see a full scenario
-description.  The following scenarios correspond to a supported <Scenario>.yaml
-deploy settings file:
+description.  Also, please refer to release-notes for information about known
+issues per scenario.  The following scenarios correspond to a supported
+<Scenario>.yaml deploy settings file:
 
 +-------------------------+------------+-----------------+
-| **Scenario**            | **Owner**  | **Known Issues**|
+| **Scenario**            | **Owner**  | **Supported**   |
 +-------------------------+------------+-----------------+
-| os-nosdn-nofeature-ha   | Apex       |                 |
+| os-nosdn-nofeature-ha   | Apex       | Yes             |
 +-------------------------+------------+-----------------+
-| os-nosdn-nofeature-noha | Apex       |                 |
+| os-nosdn-nofeature-noha | Apex       | Yes             |
 +-------------------------+------------+-----------------+
-| os-nosdn-ovs-noha       | OVS for NFV|                 |
+| os-nosdn-ovs-noha       | OVS for NFV| Yes             |
 +-------------------------+------------+-----------------+
-| os-nosdn-fdio-noha      | FDS        |                 |
+| os-nosdn-fdio-noha      | FDS        | Yes             |
 +-------------------------+------------+-----------------+
-| os-odl_l2-nofeature-ha  | Apex       |                 |
+| os-odl_l2-nofeature-ha  | Apex       | Yes             |
 +-------------------------+------------+-----------------+
-| os-odl_l3-nofeature-ha  | Apex       | APEX-112        |
+| os-odl_l3-nofeature-ha  | Apex       | Yes             |
 +-------------------------+------------+-----------------+
-| os-odl_l2-sfc-noha      | SFC        |                 |
+| os-odl_l2-sfc-noha      | SFC        | Yes             |
 +-------------------------+------------+-----------------+
-| os-odl_l2-bgpvpn-noha   | SDNVPN     |                 |
+| os-odl_l2-bgpvpn-ha     | SDNVPN     | No              |
 +-------------------------+------------+-----------------+
-| os-odl_l2-fdio-noha     | FDS        |                 |
+| os-odl_l2-fdio-noha     | FDS        | Yes             |
 +-------------------------+------------+-----------------+
-| os-onos-nofeature-ha    | ONOSFW     |                 |
+| os-onos-nofeature-ha    | ONOSFW     | Yes             |
 +-------------------------+------------+-----------------+
-| os-onos-sfc-ha          | ONOSFW     |                 |
+| os-onos-sfc-ha          | ONOSFW     | Yes             |
 +-------------------------+------------+-----------------+
diff --git a/docs/installationprocedure/requirements.rst b/docs/installationprocedure/requirements.rst
index d54d584b..1b3fe87d 100644
--- a/docs/installationprocedure/requirements.rst
+++ b/docs/installationprocedure/requirements.rst
@@ -46,14 +46,13 @@ Network requirements include:
        deployment. The External network is where public internet access would
        reside if available.
 
-\* *These networks can be combined with each other or all combined on the
-    Control Plane network.*
-\* *Non-External networks will be consolidated to the Control Plane network
-    if not specifically configured.*
-\*\* *Internal API network, by default, is collapsed with provisioning in IPv4
-     deployments, this is not possible with the current lack of PXE boot
-     support and therefore the API network is required to be its own
-     network in an IPv6 deployment.*
+\*These networks can be combined with each other or all combined on the
+Control Plane network.
+
+\*\*Internal API network, by default, is collapsed with provisioning in IPv4
+deployments, this is not possible with the current lack of PXE boot
+support and therefore the API network is required to be its own
+network in an IPv6 deployment.
 
 Bare Metal Node Requirements
 ----------------------------