4.3 - Vague images removed from the workflow description. (#3436)

Author: 0rnela

modules/common-workflows/assets/images/clm_add_sources.png

@@ -7,7 +7,7 @@ It is also useful if you need to apply updates during a limited maintenance wind
 
 
 
-== Use case
+== Use Case
 
 Content lifecycle management allows you to select software channels as sources, adjust them as required for your environment, and thoroughly test them before installing onto your production clients.
 You can use CLM to manage your software channels from development, through testing, and rolling the changes out to your clients.
@@ -31,54 +31,50 @@ Before you start, you should already have:
 
 
 
-== Step-by-step workflow instructions
+== Step-by-step Workflow Instructions
 
-.Procedure: Create a new CLM project
+.Procedure: Create a new CLM Project
 [role=peocedure]
-. In the {productname} {webui}, navigate to menu:Content Lifecycle[Projects], and click btn:[Create Project].
-  Type a name, label, and description for your project, and click btn:[Create].
+. In the {productname} {webui}, navigate to menu:Content Lifecycle[Projects] section, and click btn:[Create Project].
 +
-image::clm_new_project.png[scaledwidth=80%]
+Type a name, label, and description for your project, and click btn:[Create].
 . In the [guimenu]``Sources`` section, click btn:[Attach/Detach Sources].
-  Select the source type, and select a base channel for your project.
-  The available child channels for the selected base channel are displayed, including information on whether the channel is mandatory or recommended.
-  Check the child channels you require, and click btn:[Save] to return to the project page.
 +
-image::clm_add_sources.png[scaledwidth=80%]
+Select the source type, and select a base channel for your project.
++
+The available child channels for the selected base channel are displayed, including information on whether the channel is mandatory or recommended.
+Check the child channels you require, and click btn:[Save] to return to the project page.
 . Leave the [guimenu]``Filters`` section blank for now, we will not be using them in this example.
   You can add filters later on if you need to.
-. In the [guimenu]``Environment Lifecycle`` section, create three environments: ``production``, ``testing``, and ``development``.
-  Click btn:[Add Environment] and complete the name and label for each.
-  For the ``production`` environment, leave the [guimenu]``Insert before`` field blank.
-  For the ``testing`` environment, in the [guimenu]``Insert before`` field, select ``production``.
-  For the ``development`` environment, in the [guimenu]``Insert before field, select ``testing``.
+. In the [guimenu]``Environment Lifecycle`` section, create three environments: ``production``, ``testing``, and ``development``. Click btn:[Add Environment] and complete the name and label for each.
 +
-image::clm_environments.png[scaledwidth=80%]
-. Click btn:[Build] to build version 1 of your project:
+For the ``production`` environment, leave the [guimenu]``Insert before`` field blank.
 +
-image::clm_build_1.png[scaledwidth=80%]
+For the ``testing`` environment, in the [guimenu]``Insert before`` field, select ``production``.
++
+For the ``development`` environment, in the [guimenu]``Insert before`` field, select ``testing``.
+. Click btn:[Build] to build version 1 of your project:
 
-.Procedure: Assign clients
+
+.Procedure: Assign Clients
 [role=procedure]
 . Navigate to menu:Systems[System List], select the client to assign, and go to the menu:Software[Software Channels] tab.
 . In the [guimenu]``Base Channel`` section, select the CLM project and environment you want to assign the client to.
-  For example, if you want this client to receive updates from your CLM only when packages are in the ``production`` environment, assign the base channel ``<CLM_Project_Name>-production-<Channel_Name>``.
-  Alternatively, you could use this client as a way to test if your CLM packages are working as expected before you promote them to ``development``, so you assign the base channel ``<CLM_Project_Name>-testing-<Channel_Name>``.
 +
-image::clm_assign.png[scaledwidth=80%]
+For example, if you want this client to receive updates from your CLM only when packages are in the ``production`` environment, assign the base channel ``<CLM_Project_Name>-production-<Channel_Name>``.
++
+Alternatively, you could use this client as a way to test if your CLM packages are working as expected before you promote them to ``development``, so you assign the base channel ``<CLM_Project_Name>-testing-<Channel_Name>``.
 . Click btn:[Next] to assign the client.
 
 .Procedure: Promote Environments
 [role=procedure]
   . In the {productname} {webui}, navigate to menu:Content Lifecycle[Projects], and select the project you want to work with.
   . In the [guimenu]``Environment Lifecycle`` section, locate the environment to promote to its successor, and click btn:[Promote].
     You can monitor build progress in the [guimenu]``Environment Lifecycle`` section.
-+
-image::clm_promote.png[scaledwidth=80%]
 
 
 
-== Related topics
+== Related Topics
 
 * For more information about CLM, including information about how to use filters, see xref:administration:content-lifecycle.adoc[].
 * For CLM examples, see xref:administration:content-lifecycle-examples.adoc[].