Merge pull request #50852 from ShaunaDiaz/BZ1982550_f

BZ1982550_f fixing footnote numbering for Customer Portal

Author: stevsmit

modules/configuring-ovs-log-level-permanently.adoc

@@ -25,7 +25,7 @@ apiVersion: machineconfiguration.openshift.io/v1
 kind: MachineConfig
 metadata:
   labels:
-    machineconfiguration.openshift.io/role: master  <.>
+    machineconfiguration.openshift.io/role: master  <1>
   name: 99-change-ovs-loglevel
 spec:
   config:
@@ -36,13 +36,13 @@ spec:
       - dropins:
         - contents: |
             [Service]
-              ExecStartPost=-/usr/bin/ovs-appctl vlog/set syslog:dbg  <.>
+              ExecStartPost=-/usr/bin/ovs-appctl vlog/set syslog:dbg  <2>
               ExecReload=-/usr/bin/ovs-appctl vlog/set syslog:dbg
           name: 20-ovs-vswitchd-restart.conf
         name: ovs-vswitchd.service
 ----
-<.> After you perform this procedure to configure control plane nodes, repeat the procedure and set the role to `worker` to configure worker nodes.
-<.> Set the `syslog:<log_level>` value. Log levels are `off`, `emer`, `err`, `warn`, `info`, or `dbg`. Setting the value to `off` filters out all log messages.
+<1> After you perform this procedure to configure control plane nodes, repeat the procedure and set the role to `worker` to configure worker nodes.
+<2> Set the `syslog:<log_level>` value. Log levels are `off`, `emer`, `err`, `warn`, `info`, or `dbg`. Setting the value to `off` filters out all log messages.
 
 . Apply the machine config:
 +

modules/developer-cli-odo-ref-build-images.adoc

@@ -12,12 +12,12 @@ components:
 - image:
     imageName: quay.io/myusername/myimage
     dockerfile:
-      uri: ./Dockerfile <.>
-      buildContext: ${PROJECTS_ROOT} <.>
+      uri: ./Dockerfile <1>
+      buildContext: ${PROJECTS_ROOT} <2>
   name: component-built-from-dockerfile
 ----
-<.> The `uri` field indicates the relative path of the Dockerfile to use, relative to the directory containing the `devfile.yaml`. The devfile specification indicates that `uri` could also be an HTTP URL, but this case is not supported by odo yet.
-<.> The `buildContext` indicates the directory used as build context. The default value is `+${PROJECTS_ROOT}+`.
+<1> The `uri` field indicates the relative path of the Dockerfile to use, relative to the directory containing the `devfile.yaml`. The devfile specification indicates that `uri` could also be an HTTP URL, but this case is not supported by odo yet.
+<2> The `buildContext` indicates the directory used as build context. The default value is `+${PROJECTS_ROOT}+`.
 
 For each image component, odo executes either `podman` or `docker` (the first one found, in this order), to build the image with the specified Dockerfile, build context, and arguments.
 

modules/developer-cli-odo-ref-catalog.adoc

@@ -49,9 +49,9 @@ $ odo catalog describe component nodejs
 .Example output
 [source,terminal]
 ----
-* Registry: DefaultDevfileRegistry <.>
+* Registry: DefaultDevfileRegistry <1>
 
-Starter Projects: <.>
+Starter Projects: <2>
 ---
 name: nodejs-starter
 attributes: {}
@@ -68,8 +68,8 @@ projectsource:
   zip: null
   custom: null
 ----
-<.> _Registry_ is the registry from which the devfile is retrieved.
-<.> _Starter projects_ are sample projects in the same language and framework of the devfile, that can help you start a new project.
+<1> _Registry_ is the registry from which the devfile is retrieved.
+<2> _Starter projects_ are sample projects in the same language and framework of the devfile, that can help you start a new project.
 
 
 See `odo create` for more information on creating a project from a starter project.

modules/migration-mtc-cr-manifests.adoc

@@ -132,20 +132,20 @@ metadata:
   labels:
     migplan: <migplan>
 spec:
-  analyzeImageCount: true <.>
-  analyzeK8SResources: true <.>
-  analyzePVCapacity: true <.>
-  listImages: false <.>
-  listImagesLimit: 50 <.>
+  analyzeImageCount: true <1>
+  analyzeK8SResources: true <2>
+  analyzePVCapacity: true <3>
+  listImages: false <4>
+  listImagesLimit: 50 <5>
   migPlanRef:
     name: <migplan>
     namespace: openshift-migration
 ----
-<.> Optional: Returns the number of images.
-<.> Optional: Returns the number, kind, and API version of the Kubernetes resources.
-<.> Optional: Returns the PV capacity.
-<.> Returns a list of image names. The default is `false` so that the output is not excessively long.
-<.> Optional: Specify the maximum number of image names to return if `listImages` is `true`.
+<1> Optional: Returns the number of images.
+<2> Optional: Returns the number, kind, and API version of the Kubernetes resources.
+<3> Optional: Returns the PV capacity.
+<4> Returns a list of image names. The default is `false` so that the output is not excessively long.
+<5> Optional: Specify the maximum number of image names to return if `listImages` is `true`.
 
 [id="migcluster_{context}"]
 == MigCluster

modules/nw-egress-router-pod-ovn.adoc

@@ -31,13 +31,13 @@ kind: Pod
 metadata:
   name: egress-router-pod
   annotations:
-    k8s.v1.cni.cncf.io/networks: egress-router-redirect  <.>
+    k8s.v1.cni.cncf.io/networks: egress-router-redirect  <1>
 spec:
   containers:
     - name: egress-router-pod
       image: {egress-pod-image-name}
 ----
-<.> The specified network must match the name of the network attachment definition. You can specify a namespace, interface name, or both, by replacing the values in the following pattern: `<namespace>/<network>@<interface>`. By default, Multus adds a secondary network interface to the pod with a name such as `net1`, `net2`, and so on.
+<1> The specified network must match the name of the network attachment definition. You can specify a namespace, interface name, or both, by replacing the values in the following pattern: `<namespace>/<network>@<interface>`. By default, Multus adds a secondary network interface to the pod with a name such as `net1`, `net2`, and so on.
 
 // Clear temporary attributes
 :!router-type: