CNV-74970: Removing callouts from Support CNV docs modules

modules/virt-configuring-pod-log-verbosity.adoc

@@ -33,12 +33,13 @@ metadata:
 spec:
   logVerbosityConfig:
     kubevirt:
-      virtAPI: 5 <1>
+      virtAPI: 5
       virtController: 4
       virtHandler: 3
       virtLauncher: 2
       virtOperator: 6
 ----
-<1> The log verbosity value must be an integer in the range `1–9`, where a higher number indicates a more detailed log. In this example, the `virtAPI` component logs are exposed if their priority level is `5` or higher.
++
+The log verbosity value must be an integer in the range `1–9`, where a higher number indicates a more detailed log. In this example, the `virtAPI` component logs are exposed if their priority level is `5` or higher.
 
 . Apply your changes by saving and exiting the editor.

modules/virt-enable-guest-log-default-cli.adoc

@@ -31,7 +31,8 @@ metadata:
   name: kubevirt-hyperconverged
 spec:
   virtualMachineOptions:
-    disableSerialConsoleLog: true <1>
+    disableSerialConsoleLog: true
 #...
 ----
-<1> Set the value of `disableSerialConsoleLog` to `false` if you want serial console access to be enabled on VMs by default.
++
+Set the value of `disableSerialConsoleLog` to `false` if you want serial console access to be enabled on VMs by default.

modules/virt-loki-log-queries.adoc

@@ -83,10 +83,11 @@ If the query matches a large number of logs, the query might time out.
 
 |Container|[source,text]
 ----
-{log_type=~".+",kubernetes_container_name=~"<container>\|<container>"} <1>
+{log_type=~".+",kubernetes_container_name=~"<container>\|<container>"}
 \|json\|kubernetes_labels_app_kubernetes_io_part_of="hyperconverged-cluster"
 ----
-<1> Specify one or more containers separated by a pipe (`\|`).
+
+Specify one or more containers separated by a pipe (`\|`).
 
 |`virt-launcher`
 |You must select *application* from the log type list before running this query.
@@ -94,9 +95,10 @@ If the query matches a large number of logs, the query might time out.
 [source,text]
 ----
 {log_type=~".+", kubernetes_container_name="compute"}\|json
-\|!= "custom-ga-command" <1>
+\|!= "custom-ga-command"
 ----
-<1> `\|!= "custom-ga-command"` excludes libvirt logs that contain the string `custom-ga-command`. (https://bugzilla.redhat.com/show_bug.cgi?id=2177684[*BZ#2177684*])
+
+`\|!= "custom-ga-command"` excludes libvirt logs that contain the string `custom-ga-command`. (https://bugzilla.redhat.com/show_bug.cgi?id=2177684[*BZ#2177684*])
 |====
 
 You can filter log lines to include or exclude strings or regular expressions by using line filter expressions.

modules/virt-set-guest-log-single-vm-cli.adoc

@@ -35,10 +35,11 @@ spec:
     spec:
       domain:
         devices:
-          logSerialConsole: true <1>
+          logSerialConsole: true
 #...
 ----
-<1> To enable access to the guest's serial console log, set the `logSerialConsole` value to `true`.
++
+To enable access to the guest's serial console log, set the `logSerialConsole` value to `true`.
 
 . Apply the new configuration to the VM by running the following command:
 +

virt/support/virt-troubleshooting.adoc

@@ -51,7 +51,7 @@ include::modules/virt-viewing-logs-cli.adoc[leveloffset=+2]
 [id="guest-system-logs_{context}"]
 == Guest system logs
 
-Viewing the boot logs of VM guests can help diagnose issues. You can configure access to guests' logs and view them by using either the {product-title} web console or the `oc` CLI.
+Viewing the boot logs of VM guests can help diagnose issues. You can configure access to guests' logs and view them by using either the {product-title} web console or the {oc-first}.
 
 Even if the guest VM has no network, you can access it using its VNC or serial console, as documented in xref:../../virt/managing_vms/virt-accessing-vm-consoles.adoc#virt-accessing-vm-consoles[Connecting to virtual machine consoles]