Reformat the rst documents

Main changes:
Set the textwidth to 100, exceptions: tables and http links may be
longer than the limits
Cut off the table width as shorten as possible

JIRA: PHAROS-227

Change-Id: I07861e675d76ab5063f388d3be7d0b51c8bad38b
Signed-off-by: 10013968 <zhang.jun3g@zte.com.cn>

1 files changed, 18 insertions, 10 deletions

diff --git a/docs/specification/remoteaccess.rst b/docs/specification/remoteaccess.rst
index 185eaa89..4b8160ba 100644
--- a/docs/specification/remoteaccess.rst
+++ b/docs/specification/remoteaccess.rst
@@ -9,11 +9,12 @@ Remote Management
 Remote access is required for …
 
   * Developers to access deploy/test environments (credentials to be issued per POD / user)
-  * Connection of each environment to Jenkins master hosted by Linux Foundation for automated deployment and test
+  * Connection of each environment to Jenkins master hosted by Linux Foundation for automated
+    deployment and test
 
-OpenVPN is generally used for remote however community hosted labs may vary due to company security rules. For POD
-access rules / restrictions refer to individual lab documentation as each company may have different access rules
-and acceptable usage policies.
+OpenVPN is generally used for remote however community hosted labs may vary due to company security
+rules. For POD access rules / restrictions refer to individual lab documentation as each company may
+have different access rules and acceptable usage policies.
 
 Basic requirements:
 
@@ -31,15 +32,19 @@ Lights-out management network requirements:
   * Access to server is through a lights-out-management tool and/or a serial console
   * Refer to applicable light-out mangement information from server manufacturer, such as ...
 
-    * Intel lights-out `RMM <http://www.intel.com/content/www/us/en/server-management/intel-remote-management-module.html>`_
+    * Intel lights-out
+      `RMM <http://www.intel.com/content/www/us/en/server-management/intel-remote-management-module.html>`_
     * HP lights-out `ILO <http://www8.hp.com/us/en/products/servers/ilo/index.html>`_
     * CISCO lights-out `UCS <https://developer.cisco.com/site/ucs-dev-center/index.gsp>`_
 
 Linux Foundation Lab is a UCS-M hardware environment with controlled access *as needed*
 
-    * `Access rules and procedure <https://wiki.opnfv.org/display/pharos/Lflab+Hosting>`_ are maintained on the Wiki
-    * `A list of people <https://wiki.opnfv.org/display/pharos/Lf+Support>`_ with access is maintained on the Wiki
-    * Send access requests to infra-steering@lists.opnfv.org with the following information ...
+    * `Access rules and procedure <https://wiki.opnfv.org/display/pharos/Lflab+Hosting>`_ are
+      maintained on the Wiki
+    * `A list of people <https://wiki.opnfv.org/display/pharos/Lf+Support>`_ with access is
+      maintained on the Wiki
+    * Send access requests to infra-steering@lists.opnfv.org with the
+      following information ...
 
       * Name:
       * Company:
@@ -50,6 +55,9 @@ Linux Foundation Lab is a UCS-M hardware environment with controlled access *as
       * What specific POD/machines will be accessed:
       * What support is needed from LF admins and LF community support team:
 
-    * Once access is approved please follow instructions for setting up VPN access
+    * Once access is approved please follow instructions for setting up VPN access ...
+      https://wiki.opnfv.org/get_started/lflab_hosting
     * The people who require VPN access must have a valid PGP key bearing a valid signature from LF
-    * When issuing OpenVPN credentials, LF will be sending TLS certificates and 2-factor authentication tokens, encrypted to each recipient's PGP key
+    * When issuing OpenVPN credentials, LF will be sending TLS certificates and 2-factor
+      authentication tokens, encrypted to each recipient's PGP key
+