diff --git a/pages/operations/sahara/7600-security-groups.rst b/pages/operations/sahara/7600-security-groups.rst
index 282d9acbd..bbc8b17de 100644
--- a/pages/operations/sahara/7600-security-groups.rst
+++ b/pages/operations/sahara/7600-security-groups.rst
@@ -1,19 +1,16 @@
 
-
 .. _sahara-security-groups:
 
 Sahara Security Groups
 ----------------------
 
-Sahara used auto-security groups for opening required ports for each plugins.
+Sahara uses auto-security groups for opening required ports for each plugin.
 
+To learn about the open ports for each plugin, please refer to the official
+documentation:
 
-If you want know open ports for each plugin, see official documentation of plugin:
-
-    Hortonworks Hadoop:
-        Version 2.2: `<http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.2.4/bk_HDP_Reference_Guide/content/reference_chap2.html>`_.
-        Version 2.0: `<http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.0.6.0/bk_reference/content/reference_chap2.html>`_.
-
-    Spark: `<https://spark.apache.org/docs/1.2.0/security.html>`_.
-
-    Cloudera: `<http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cdh_ig_ports_cdh5.html>`_.
\ No newline at end of file
+* Hortonworks Hadoop
+  `Version 2.0 <http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.0.6.0/bk_reference/content/reference_chap2.html>`_
+  and `Version 2.2 <http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.2.4/bk_HDP_Reference_Guide/content/reference_chap2.html>`_
+* `Spark <https://spark.apache.org/docs/1.2.0/security.html>`_
+* `Cloudera <http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cdh_ig_ports_cdh5.html>`_
diff --git a/pages/operations/sahara/7700-prepare-to-test.rst b/pages/operations/sahara/7700-prepare-to-test.rst
index ffd2144d4..0538a927e 100644
--- a/pages/operations/sahara/7700-prepare-to-test.rst
+++ b/pages/operations/sahara/7700-prepare-to-test.rst
@@ -4,46 +4,44 @@
 Preparing Sahara for Testing
 ----------------------------
 
-The Platform Tests that are run as part of the Health Tests
-that test Sahara if it is configured in the Environment.
-Before runing the test,
-you must manually perform the actions listed below.
+You can run Platform Tests to verify whether Sahara is functioning correctly.
+To run the tests, Sahara must be deployed and configured.
 
-Note that the tests are run in the tenant
-that you specified in the 'OpenStack Settings' tab
-during OpenStack installation,
-so that is where you need to perform these actions.
-By default, the `admin` tenant is used for the tests.
+You run the tests in the tenant you specified in the `OpenStack Settings` tab
+during the OpenStack installation. By default, the `admin` tenant is used for
+the tests.
 
-You must have at least 4096 MB of available RAM
-in the tenant you are using for the Sahara Platform Tests
-or some tests may fail.
+You must have at least 4096 MB of available RAM in the tenant you are using
+for Sahara Platform Tests otherwise some tests may fail.
 
-#. Get an image with Hadoop for Sahara and register it with Sahara.
+To prepare Sahara for testing, you should get an image and register it
+with Sahara image registry:
 
-   * Download the following image:
+#. Download the `image with Hadoop for Sahara
+   <http://sahara-files.mirantis.com/mos61/sahara-juno-vanilla-2.4.1-ubuntu-14.04.qcow2>`_
 
-     http://sahara-files.mirantis.com/mos61/sahara-juno-vanilla-2.4.1-ubuntu-14.04.qcow2
+#. Register it with Sahara:
 
-   * Then upload the image into OpenStack Image Service (Glance) into
-     the 'admin' tenant and name it 'sahara'.
+   a. Upload the image into Glance into the `admin` tenant. Name it `sahara`.
 
-   * In OpenStack Dashboard (Horizon) access 'Data Processing' panel under the
-     Project menu.
+   b. In Horizon, access the `Data Processing` panel under the `Project` menu.
 
-   * Switch to 'admin' tenant if you are not in it already.
+   c. Switch to the `admin` tenant.
 
-   * Go to the ‘Image Registry’ menu. Here, push the ‘Register Image’ button.
-     The Image registration window will open up.
+   d. Go to the `Image Registry` menu.
 
-   * Select the image you’ve just uploaded.
+   e. Click the `Register Image` button. The `Image registration` dialog
+      appears.
 
-   * Set username to ‘ubuntu’
+   f. Select the image you have just uploaded.
 
-   * For tags, pick ‘vanilla’ plugin and ‘2.4.1’ version and press
-     the ‘Add plugin tags’ button.
+   g. Set username to ``ubuntu``.
 
-   * Finally push the ‘Done’ button
+   h. Select the tags: ``plugin=vanilla`` and ``version=2.4.1``.
 
-After the steps above are done, Sahara is ready to be tested.
+   i. Click ``Add plugin tags``.
+
+   j. Click ``Done``.
+
+Now you can test Sahara.
 
diff --git a/pages/operations/sahara/7760-sahara-images.rst b/pages/operations/sahara/7760-sahara-images.rst
index 88c8a23d1..7908a0662 100644
--- a/pages/operations/sahara/7760-sahara-images.rst
+++ b/pages/operations/sahara/7760-sahara-images.rst
@@ -28,13 +28,13 @@ The default username for these images depends on the distribution:
 | CentOS 6.6       | cloud-user|
 +------------------+-----------+
 
-You can find MD5 checksum of an image by adding .md5 suffix to the image url,
-for example,
-`<http://sahara-files.mirantis.com/mos61/sahara-juno-vanilla-2.4.1-ubuntu-14.04.qcow2.md5>`_.
+You can find MD5 checksum of an image by adding the ``.md5`` suffix
+to the image url, for example
+http://sahara-files.mirantis.com/mos61/sahara-juno-vanilla-2.4.1-ubuntu-14.04.qcow2.md5.
 
-For check an .iso file with an MD5 hash, run the following command:
+To check an ``.iso`` file with an MD5 hash, run:
 
-.. sourcecode:: console
+.. code-block:: console
 
     $ md5sum -c sahara-juno-vanilla-2.4.1-ubuntu-14.04.qcow2.md5
-..
+    ..