Update content

umn/source/auditing.rst

@@ -27,7 +27,7 @@ Supported RFS Operations
    +------------------------+---------------+-------------------------------------------------------+
    | deployStack            | stack         | Deploying a stack directly                            |
    +------------------------+---------------+-------------------------------------------------------+
-   | deleteStack            | stack         | Deleting a stack starts                               |
+   | deleteStack            | stack         | Deleting a stack started                              |
    +------------------------+---------------+-------------------------------------------------------+
    | deleteStackEnd         | stack         | Deleting a stack finished                             |
    +------------------------+---------------+-------------------------------------------------------+

umn/source/iam_agency.rst

@@ -25,12 +25,14 @@ RFS uses an agency only in resource operation requests, such as creating a stack
 3. Enter an agency name,
 
    -  the \ **Agency Type**\  is set to \ **Cloud Service**
+
    -  the **Cloud Service** is set to **RFS**.
 
 
-   **Figure 2** Creating an agency
+      .. figure:: /_static/images/en-us_image_0000002202025297.png
+         :alt: **Figure 2** Create an agency
 
-   |image1|
+         **Figure 2** Create an agency
 
 .. caution::
 
@@ -58,7 +60,6 @@ You can determine the permissions to be granted to an agency. OpenTelekom cloud
 
 6. Click **OK**. The agency is created. Now you can use it in \ :ref:`Configure the stack. <en-us_topic_0000001955571466__li459mcpsimp>`
 
-   |image2|\ For more information about IAM Agencies, see: `Cloud Service Agency <https://docs.otc.t-systems.com/identity-access-management/umn/user_guide/agencies/cloud_service_agency.html#iam-06-0004>`__.
+   |image1|\ For more information about IAM Agencies, see: `Cloud Service Agency <https://docs.otc.t-systems.com/identity-access-management/umn/user_guide/agencies/cloud_service_agency.html#iam-06-0004>`__.
 
-.. |image1| image:: /_static/images/en-us_image_0000002156930225.png
+.. |image1| image:: /_static/images/en-us_image_0000001991770693.png
-.. |image2| image:: /_static/images/en-us_image_0000001991770693.png

umn/source/managing_stacks/deleting_a_stack.rst

@@ -66,15 +66,14 @@ If a stack is no longer needed, you can perform the following steps to delete it
 
    b. and confirm the deletion by entering **Delete** in the text box and click **OK**.
 
-   .. _en-us_topic_0000001991890809____d0e1485:
 
-   **Figure 6** Dialog box for deleting a stack
+      .. figure:: /_static/images/en-us_image_0000002166698096.png
+         :alt: **Figure 6** Dialog box for deleting a stack
 
-   |image2|
+         **Figure 6** Dialog box for deleting a stack
 
 .. warning::
 
    Stacks cannot be restored after being deleted. Exercise caution when performing this operation.
 
 .. |image1| image:: /_static/images/en-us_image_0000002158817102.png
-.. |image2| image:: /_static/images/en-us_image_0000002194220965.png

umn/source/managing_templates/deleting_a_template.rst

@@ -47,11 +47,11 @@ If a template is no longer in use, RFS supports deleting it. You can choose to d
 
 #. In the dialog box displayed, click **Yes** as shown in :ref:`Figure Dialog box for deleting a template <en-us_topic_0000002082821521____d0e1006>`. The template(s) and all versions will be deleted.
 
-   .. _en-us_topic_0000002082821521____d0e1006:
 
-   **Figure 5** Dialog box for deleting a template
+   .. figure:: /_static/images/en-us_image_0000002166704124.png
+      :alt: **Figure 5** Dialog box for deleting a template
 
-   |image2|
+      **Figure 5** Dialog box for deleting a template
 
    .. caution::
 
@@ -59,4 +59,3 @@ If a template is no longer in use, RFS supports deleting it. You can choose to d
       -  If you just want to delete a template version, please go to \ :ref:`View the Template Details <en-us_topic_0000002119404102>`\ .
 
 .. |image1| image:: /_static/images/en-us_image_0000002194186605.png
-.. |image2| image:: /_static/images/en-us_image_0000002121759436.png

umn/source/managing_templates/replicating_a_template.rst

@@ -44,7 +44,11 @@ Replicating a Template
 
 #. A dialog box is displayed where you can specify the name, description and version description of the new template.
 
-   |image3|
+
+   .. figure:: /_static/images/en-us_image_0000002166544344.png
+      :alt: **Figure 5** Dialog box for replicating a template
+
+      **Figure 5** Dialog box for replicating a template
 
    .. note::
 
@@ -57,4 +61,3 @@ Replicating a Template
 
 .. |image1| image:: /_static/images/en-us_image_0000002194220969.png
 .. |image2| image:: /_static/images/en-us_image_0000002121776826.png
-.. |image3| image:: /_static/images/en-us_image_0000002157074637.png

umn/source/permission_management/custom_policies.rst

@@ -29,7 +29,7 @@ The following lists examples of custom policies for RFS.
 
    “Deny” permissions should be used together with “Allow” permissions. If “Deny” and “Allow” permissions are both assigned, the “Deny” permissions take precedence over the “Allow” permissions.
 
-   Assume that you want to grant the RF FullAccess permissions to users but do not want them to delete stacks. You can create a custom policy for denying stack deletion, and attach this policy together with the RF FullAccess policy to the users. As an explicit deny in any policy overrides any allows, the users can perform all operations on stacks except deleting them. The following shows an example policy for denying stack deletion.
+   Assume that you want to grant the **RF FullAccess** permissions to users but do not want them to delete stacks. You can create a custom policy for denying stack deletion, and attach this policy together with the **RF FullAccess** policy to the users. As an explicit deny in any policy overrides any allows, the users can perform all operations on stacks except deleting them. The following shows an example policy for denying stack deletion.
 
    .. code-block::