Removed passthroughs

Author: vikram-redhat

admin_guide/pruning_resources.adoc

@@ -486,17 +486,17 @@ day (depending on the number of images being created).
 
 To hard prune orphaned blobs from the registry:
 
-. +++<b>Log in:</b>+++ Log in using xref:../cli_reference/get_started_cli.adoc#basic-setup-and-login[the CLI] as a user with an
+. *Log in*: Log in using xref:../cli_reference/get_started_cli.adoc#basic-setup-and-login[the CLI] as a user with an
 xref:../architecture/additional_concepts/authentication.adoc#oauth[access token].
 
-. +++<b>Run a basic image prune:</b>+++ Basic image pruning removes additional
+. *Run a basic image prune*: Basic image pruning removes additional
 images that are no longer needed. The hard prune does not remove images on its
 own. It only removes blobs stored in the registry storage. Therefore, you should
 run this just before the hard prune.
 +
 See Pruning Images for steps.
 
-. +++<b>Switch the registry to read-only mode:</b>+++ If the registry is not
+. *Switch the registry to read-only mode*: If the registry is not
 running in read-only mode, any pushes happening at the same time as the prune
 will either:
 +
@@ -529,7 +529,7 @@ $ oc rollout -n default \
     latest dc/docker-registry
 ----
 
-. +++<b>Add the system:image-pruner role:</b>+++ The service account used to run
+. *Add the system:image-pruner role*: The service account used to run
 the registry instances requires additional permissions in order to list some
 resources.
 
@@ -549,7 +549,7 @@ $ oc adm policy add-cluster-role-to-user \
     ${service_account}
 ----
 
-. +++<b>(Optional) Run the pruner in dry-run mode:</b>+++ To see how many blobs
+. *(Optional) Run the pruner in dry-run mode*: To see how many blobs
 would be removed, run the hard pruner in dry-run mode. No changes are actually
 made:
 +
@@ -589,7 +589,7 @@ Would free up 2.835 GiB of disk space
 Use -prune=delete to actually delete the data
 ----
 
-. +++<b>Run the hard prune:</b>+++ Execute the following command inside one
+. *Run the hard prune*: Execute the following command inside one
 running instance of *docker-registry* pod to run the hard prune:
 +
 ----
@@ -607,7 +607,7 @@ Deleted 13374 blobs
 Freed up 2.835 GiB of disk space
 ----
 
-. +++<b>Switch the registry back to read-write mode:</b>+++ After the prune is
+. *Switch the registry back to read-write mode*: After the prune is
 finished, the registry can be switched back to read-write mode by executing:
 +
 ----