diff --git a/source/openstack_use_cases.rst b/source/openstack_use_cases.rst
index 65825356..132d3294 100644
--- a/source/openstack_use_cases.rst
+++ b/source/openstack_use_cases.rst
@@ -1,36 +1,32 @@
-OpenStack* use cases with Clear Linux* OS for Intel® Architecture
-###################################################################
-
-The installation and configuration of a Cloud Management Platform
-depends on use cases and associated architectural choices.
-
-OpenStack supports the following use cases:
-
--  *General purpose* -- A cloud built with common components that should
-   address about 80 percent of common use cases.
-
--  *Compute-focused* -- A cloud designed to address compute-intensive
-   workloads such as high performance computing (HPC).
-
--  *Storage-focused* -- A cloud focused on storage intensive workloads
-   such as data analytics with parallel file systems.
-
--  *Network-focused* -- A cloud depending on high performance and
-   reliable networking, such as a Content Delivery Network (CDN).
-
-Clear Linux OS for Intel Architecture is designed with all of these use
-cases in mind, but the initial target is to enable only those services
-required for Cloud. As such, the Minimum Viable Product (MVP) is
-defined as giving the capability for Clear Linux OS for Intel Architecture to boot an instance
-(Virtual Machine) through OpenStack Services. In order to achieve this,
-it's necessary to enable only those OpenStack services and dependent
-components involved during that interaction. The following diagram
-presents an example architecture of MVP:
-
-.. image:: images\openstack_example_architecture.jpg
-    :align: center
-    :alt: sample OpenStack* architecture
-
-*Note:* Optional Services (Cinder) and OpenStack Dashboard (Horizon) are
-not part of the OpenStack MVP.
-
+OpenStack* use cases with Clear Linux* OS for Intel® Architecture
+###################################################################
+
+The installation and configuration of a Cloud Management Platform
+depends on use cases and associated architectural choices.
+
+OpenStack supports the following use cases:
+
+-  *General purpose* -- A cloud built with common components that should
+   address about 80 percent of common use cases.
+
+-  *Compute-focused* -- A cloud designed to address compute-intensive
+   workloads such as high performance computing (HPC).
+
+-  *Storage-focused* -- A cloud focused on storage intensive workloads
+   such as data analytics with parallel file systems.
+
+-  *Network-focused* -- A cloud depending on high performance and
+   reliable networking, such as a Content Delivery Network (CDN).
+
+Clear Linux OS for Intel Architecture is designed with all of these use
+cases in mind, but the initial target is to enable only those services
+required for Cloud. As such, the Minimum Viable Product (MVP) is
+defined as giving the capability for Clear Linux OS for Intel Architecture to boot an instance
+(Virtual Machine) through OpenStack Services. In order to achieve this,
+it's necessary to enable only those OpenStack services and dependent
+components involved during that interaction. The following diagram
+presents an example architecture of MVP:
+
+.. image:: images\openstack_example_architecture.jpg
+    :align: center
+    :alt: sample OpenStack* architecture
\ No newline at end of file