Address RST formattting issues (extra spaces etc)

JIRA: COPPER-1
Fix more pesky "errors"

Change-Id: I65e722f8969a58e32cde1e4651dfc62fd45c18a7
Signed-off-by: blsaws <bryan.sullivan@att.com>

1 files changed, 7 insertions, 7 deletions

diff --git a/docs/design/introduction.rst b/docs/design/introduction.rst
index 7f16248..f82d47e 100644
--- a/docs/design/introduction.rst
+++ b/docs/design/introduction.rst
@@ -5,7 +5,7 @@ Introduction
  This work is licensed under a Creative Commons Attribution 3.0 Unported License.
 
  http://creativecommons.org/licenses/by/3.0/legalcode
- 
+
 .. NOTE::
    This is the working documentation for the Copper project.
 
@@ -19,10 +19,10 @@ As focused on by Copper, configuration policy helps ensure that the NFV service
   * what I want
   * what I don't want
 
-Using road-based transportation as an analogy, some examples of this are shown below. 
+Using road-based transportation as an analogy, some examples of this are shown below.
 
 .. list-table:: Configuration Intent Example
-   :widths: 10 45 45 
+   :widths: 10 45 45
    :header-rows: 1
 
    * - Who I Am
@@ -54,11 +54,11 @@ According to their role, service providers may apply more specific configuration
      - clustering, auto-scaling, anti-affinity, live migration
    * - disaster recovery
      - geo-diverse anti-affinity
-   * - high compute/storage performance 
+   * - high compute/storage performance
      - clustering, affinity
-   * - high network performance 
+   * - high network performance
      - data plane acceleration
-   * - resource reclamation 
+   * - resource reclamation
      - low-usage monitoring
 
 Although such intent to capability translation is conceptually useful, it is unclear how it can address the variety of aspects that may affect the choice of an applicable configuration capability. For that reason, the Copper project will initially focus on more specific configuration requirements as fulfilled by specific configuration capabilities, and how those requirements and capabilities are expressed in VNF and service design and packaging, or as generic poicies for the NFVI.
@@ -69,4 +69,4 @@ OPNFV Brahmaputra will be the initial OPNFV release for Copper, with the goals:
   * Add the OpenStack Congress service to OPNFV, through at least one installer project
   * If possible, add Congress support to the OPNFV CI/CD pipeline for all Genesis project installers (Apex, Fuel, JOID, Compass)
   * Integrate Congress tests into Functest and develop additional use case tests for post-OPNFV-install
-  * Extend with other OpenStack components for testing, as time permits
\ No newline at end of file
+  * Extend with other OpenStack components for testing, as time permits