gnelson/ocp-docs-suggestions-1k-pr huggingface dataset:
Original: * Previously, a bug in Bare Metal Operator (BMO) led to JSON parsing errors because of a missing Redfish system ID in Baseboard Management Controller (BMC) URLs. This issue caused users to receive errors when the system ID was left out of the URLs. With this release, BMO handles URLs without a Redfish system ID as addresses without a system ID. This fix improves the software's handling of missing a Redfish system ID in BMC URLs. (link:https://issues.redhat.com/browse/OCPBUGS-56431[OCPBUGS-56431])
Revised: * Previously, a bug in the Bare Metal Operator (BMO) caused JSON parsing errors because of a missing Redfish system ID in Baseboard Management Controller (BMC) URLs. This issue caused users to receive errors when the system ID was left out of the URLs. With this release, BMO handles URLs without a Redfish system ID as addresses without a system ID. This fix improves software handling of missing a Redfish system ID in BMC URLs. (link:https://issues.redhat.com/browse/OCPBUGS-56431[OCPBUGS-56431])
Original: * Previously, during Ironic Python Agent (IPA) deployments, the absence of NetworkManager logs in RAM disk logs hinders effective debugging, impacting network issue resolution. With this release, NetworkManager logs are included in RAM disk logs for IPA debugging. This results in enhanced IPA logs that provide comprehensive NetworkManager data for improved debugging. (link:https://issues.redhat.com/browse/OCPBUGS-56097[OCPBUGS-56097])
Revised: * Previously, during Ironic Python Agent (IPA) deployments, the absence of NetworkManager logs in RAM disk logs hinders effective debugging, impacting network issue resolution. With this release, NetworkManager logs are included in RAM disk logs for IPA debugging. This results in enhanced IPA logs that provide comprehensive `NetworkManager` data for improved debugging. (link:https://issues.redhat.com/browse/OCPBUGS-56097[OCPBUGS-56097])
Original: * Previously, the code did not support Docker image mirroring with a tag and digest. This resulted in failed Helm repository mirroring that caused image duplication and inconsistencies in deployment. With this release, a fix addresses Docker references in Helm repository mirroring that allows tag and digest,  and improves successful image mirroring. (link:https://issues.redhat.com/browse/OCPBUGS-56043[OCPBUGS-56043])
Revised: * Previously, Helm did not support Docker image mirroring with a tag and digest. This resulted in failed Helm repository mirroring that caused image duplication and inconsistencies in deployment. With this release, a fix addresses Docker references in Helm repository mirroring that allows tag and digest, and improves successful image mirroring. (link:https://issues.redhat.com/browse/OCPBUGS-56043[OCPBUGS-56043])
Original: * Previously, a bug in the Bare Metal Operator (BMO) caused JSON parsing errors because of a missing Redfish system ID in Baseboard Management Controller (BMC) URLs. This issue caused users to receive errors when the system ID was left out of the URLs. With this release, BMO handles URLs without a Redfish system ID as addresses without a system ID. This fix improves software handling of missing a Redfish system ID in BMC URLs. (link:https://issues.redhat.com/browse/OCPBUGS-56431[OCPBUGS-56431])
Revised: * Previously, a bug in the Bare Metal Operator (BMO) caused JSON parsing errors because of a missing Redfish system ID in Baseboard Management Controller (BMC) URLs. This issue caused users to receive errors when the system ID was left out of the URLs. With this release, the BMO handles URLs without a Redfish system ID as addresses without a system ID. This fix improves software handling of missing a Redfish system ID in BMC URLs. (link:https://issues.redhat.com/browse/OCPBUGS-56431[OCPBUGS-56431])
Original: * Previously, during Ironic Python Agent (IPA) deployments, the absence of NetworkManager logs in RAM disk logs hinders effective debugging, impacting network issue resolution. With this release, NetworkManager logs are included in RAM disk logs for IPA debugging. This results in enhanced IPA logs that provide comprehensive `NetworkManager` data for improved debugging. (link:https://issues.redhat.com/browse/OCPBUGS-56097[OCPBUGS-56097])
Revised: * Previously, during Ironic Python Agent (IPA) deployments, the absence of NetworkManager logs in RAM disk logs hindered effective debugging, impacting network issue resolution. With this release, NetworkManager logs are included in RAM disk logs for IPA debugging. This results in enhanced IPA logs that provide comprehensive `NetworkManager` data for improved debugging. (link:https://issues.redhat.com/browse/OCPBUGS-56097[OCPBUGS-56097])
Original: * Previously, intermittent resource leaks in the `MachineOSConfig` (MOSC) to `MachineOSBuild` (MOSB) connection due to missing owner references during job creation result in potential resource exhaustion, affecting pod updates. With this release, the owner references are added in the job creation to ensure the consistent removal of MOSB resources when MOSC is deleted, preventing resource leaks. (link:https://issues.redhat.com/browse/OCPBUGS-52189[OCPBUGS-52189])
Revised: * Previously, intermittent resource leaks in the `MachineOSConfig` (MOSC) to `MachineOSBuild` (MOSB) connection due to missing owner references during job creation resulted in potential resource exhaustion, affecting pod updates. With this release, the owner references are added in the job creation to ensure the consistent removal of MOSB resources when MOSC is deleted, preventing resource leaks. (link:https://issues.redhat.com/browse/OCPBUGS-52189[OCPBUGS-52189])
Original: . In the *Administrator* perspective of the web console, navigate to the {rh-app-icon} menu -> *OpenShift GitOps* -> *Cluster Argo CD*. The login page of the Argo CD Web UI is displayed in a new window.
Revised: . In the *Administrator* perspective of the web console, go to the {rh-app-icon} menu -> *OpenShift GitOps* -> *Cluster Argo CD*. The login page of the Argo CD Web UI is displayed in a new window.
Original: . In the *Administrator* perspective of the web console, navigate to the {rh-app-icon} menu -> *OpenShift GitOps* -> *Cluster Argo CD*. The login page of the Argo CD Web UI is displayed in a new window.
Revised: . In the *Administrator* perspective of the web console, go to the {rh-app-icon} menu and click *OpenShift GitOps* -> *Cluster Argo CD*. The login page of the Argo CD Web UI is displayed in a new window.
Original: The `enableRolloutsUI` field restarts the Argo CD server deployment pod, so it takes a few seconds for the Argo Rollouts extension to enable in the Argo CD Web UI.
Revised: The `enableRolloutsUI` field restarts the Argo CD server deployment pod. Therefore, it takes a few seconds for the Argo Rollouts extension to enable in the Argo CD Web UI.
Original: // Module included in the following assemblies:
//
// * scalability_and_performance/telco_ran_du_ref_design_specs/telco-ran-du-rds.adoc

:_mod-docs-content-type: REFERENCE
[id="machine-configuration-crs_{context}"]
= Machine configuration reference CRs

.Machine configuration CRs
[cols="4*", options="header", format=csv]
|====
Component,Reference CR,Description,Optional
Container runtime (crun),`enable-crun-master.yaml`,Configures the container runtime (crun) for control plane nodes.,No
Container runtime (crun),`enable-crun-worker.yaml`,Configures the container runtime (crun) for worker nodes.,No
CRI-O wipe disable,`99-crio-disable-wipe-master.yaml`,Disables automatic CRI-O cache wipe following a reboot for on control plane nodes.,No
CRI-O wipe disable,`99-crio-disable-wipe-worker.yaml`,Disables automatic CRI-O cache wipe following a reboot for on worker nodes.,No
Kdump enable,`06-kdump-master.yaml`,Configures kdump crash reporting on master nodes.,No
Kdump enable,`06-kdump-worker.yaml`,Configures kdump crash reporting on worker nodes.,No
Kubelet configuration and container mount hiding,`01-container-mount-ns-and-kubelet-conf-master.yaml`,Configures a mount namespace for sharing container-specific mounts between kubelet and CRI-O on control plane nodes.,No
Kubelet configuration and container mount hiding,`01-container-mount-ns-and-kubelet-conf-worker.yaml`,Configures a mount namespace for sharing container-specific mounts between kubelet and CRI-O on worker nodes.,No
One-shot time sync,`99-sync-time-once-master.yaml`,Synchronizes time once on master nodes.,No
One-shot time sync,`99-sync-time-once-worker.yaml`,Synchronizes time once on worker nodes.,No
SCTP,`03-sctp-machine-config-master.yaml`,Loads the SCTP kernel module on master nodes.,Yes
SCTP,`03-sctp-machine-config-worker.yaml`,Loads the SCTP kernel module on worker nodes.,Yes
Set RCU normal,`08-set-rcu-normal-master.yaml`,Disables rcu_expedited by setting rcu_normal after the control plane node has booted.,No
Set RCU normal,`08-set-rcu-normal-worker.yaml`,Disables rcu_expedited by setting rcu_normal after the worker node has booted.,No
SRIOV-related kernel arguments,`07-sriov-related-kernel-args-master.yaml`,Enables SR-IOV support on master nodes.,No
|====
Revised: SRIOV-related kernel arguments,`07-sriov-related-kernel-args-master.yaml`,Enables SR-IOV support on control plane nodes.,No
Original: // Module included in the following assemblies:
//
// * scalability_and_performance/telco_ran_du_ref_design_specs/telco-ran-du-rds.adoc

:_mod-docs-content-type: REFERENCE
[id="machine-configuration-crs_{context}"]
= Machine configuration reference CRs

.Machine configuration CRs
[cols="4*", options="header", format=csv]
|====
Component,Reference CR,Description,Optional
Container runtime (crun),`enable-crun-master.yaml`,Configures the container runtime (crun) for control plane nodes.,No
Container runtime (crun),`enable-crun-worker.yaml`,Configures the container runtime (crun) for worker nodes.,No
CRI-O wipe disable,`99-crio-disable-wipe-master.yaml`,Disables automatic CRI-O cache wipe following a reboot for on control plane nodes.,No
CRI-O wipe disable,`99-crio-disable-wipe-worker.yaml`,Disables automatic CRI-O cache wipe following a reboot for on worker nodes.,No
Kdump enable,`06-kdump-master.yaml`,Configures kdump crash reporting on master nodes.,No
Kdump enable,`06-kdump-worker.yaml`,Configures kdump crash reporting on worker nodes.,No
Kubelet configuration and container mount hiding,`01-container-mount-ns-and-kubelet-conf-master.yaml`,Configures a mount namespace for sharing container-specific mounts between kubelet and CRI-O on control plane nodes.,No
Kubelet configuration and container mount hiding,`01-container-mount-ns-and-kubelet-conf-worker.yaml`,Configures a mount namespace for sharing container-specific mounts between kubelet and CRI-O on worker nodes.,No
One-shot time sync,`99-sync-time-once-master.yaml`,Synchronizes time once on master nodes.,No
One-shot time sync,`99-sync-time-once-worker.yaml`,Synchronizes time once on worker nodes.,No
SCTP,`03-sctp-machine-config-master.yaml`,Loads the SCTP kernel module on master nodes.,Yes
SCTP,`03-sctp-machine-config-worker.yaml`,Loads the SCTP kernel module on worker nodes.,Yes
Set RCU normal,`08-set-rcu-normal-master.yaml`,Disables rcu_expedited by setting rcu_normal after the control plane node has booted.,No
Set RCU normal,`08-set-rcu-normal-worker.yaml`,Disables rcu_expedited by setting rcu_normal after the worker node has booted.,No
SRIOV-related kernel arguments,`07-sriov-related-kernel-args-master.yaml`,Enables SR-IOV support on master nodes.,No
|====
Revised: One-shot time sync,`99-sync-time-once-master.yaml`,Synchronizes time once on control plane nodes.,No
Original: // Module included in the following assemblies:
//
// * scalability_and_performance/telco_ran_du_ref_design_specs/telco-ran-du-rds.adoc

:_mod-docs-content-type: REFERENCE
[id="machine-configuration-crs_{context}"]
= Machine configuration reference CRs

.Machine configuration CRs
[cols="4*", options="header", format=csv]
|====
Component,Reference CR,Description,Optional
Container runtime (crun),`enable-crun-master.yaml`,Configures the container runtime (crun) for control plane nodes.,No
Container runtime (crun),`enable-crun-worker.yaml`,Configures the container runtime (crun) for worker nodes.,No
CRI-O wipe disable,`99-crio-disable-wipe-master.yaml`,Disables automatic CRI-O cache wipe following a reboot for on control plane nodes.,No
CRI-O wipe disable,`99-crio-disable-wipe-worker.yaml`,Disables automatic CRI-O cache wipe following a reboot for on worker nodes.,No
Kdump enable,`06-kdump-master.yaml`,Configures kdump crash reporting on master nodes.,No
Kdump enable,`06-kdump-worker.yaml`,Configures kdump crash reporting on worker nodes.,No
Kubelet configuration and container mount hiding,`01-container-mount-ns-and-kubelet-conf-master.yaml`,Configures a mount namespace for sharing container-specific mounts between kubelet and CRI-O on control plane nodes.,No
Kubelet configuration and container mount hiding,`01-container-mount-ns-and-kubelet-conf-worker.yaml`,Configures a mount namespace for sharing container-specific mounts between kubelet and CRI-O on worker nodes.,No
One-shot time sync,`99-sync-time-once-master.yaml`,Synchronizes time once on master nodes.,No
One-shot time sync,`99-sync-time-once-worker.yaml`,Synchronizes time once on worker nodes.,No
SCTP,`03-sctp-machine-config-master.yaml`,Loads the SCTP kernel module on master nodes.,Yes
SCTP,`03-sctp-machine-config-worker.yaml`,Loads the SCTP kernel module on worker nodes.,Yes
Set RCU normal,`08-set-rcu-normal-master.yaml`,Disables rcu_expedited by setting rcu_normal after the control plane node has booted.,No
Set RCU normal,`08-set-rcu-normal-worker.yaml`,Disables rcu_expedited by setting rcu_normal after the worker node has booted.,No
SRIOV-related kernel arguments,`07-sriov-related-kernel-args-master.yaml`,Enables SR-IOV support on master nodes.,No
|====
Revised: Kdump enable,`06-kdump-master.yaml`,Configures kdump crash reporting on control plane nodes.,No
Original: // Module included in the following assemblies:
//
// * scalability_and_performance/telco_ran_du_ref_design_specs/telco-ran-du-rds.adoc

:_mod-docs-content-type: REFERENCE
[id="machine-configuration-crs_{context}"]
= Machine configuration reference CRs

.Machine configuration CRs
[cols="4*", options="header", format=csv]
|====
Component,Reference CR,Description,Optional
Container runtime (crun),`enable-crun-master.yaml`,Configures the container runtime (crun) for control plane nodes.,No
Container runtime (crun),`enable-crun-worker.yaml`,Configures the container runtime (crun) for worker nodes.,No
CRI-O wipe disable,`99-crio-disable-wipe-master.yaml`,Disables automatic CRI-O cache wipe following a reboot for on control plane nodes.,No
CRI-O wipe disable,`99-crio-disable-wipe-worker.yaml`,Disables automatic CRI-O cache wipe following a reboot for on worker nodes.,No
Kdump enable,`06-kdump-master.yaml`,Configures kdump crash reporting on master nodes.,No
Kdump enable,`06-kdump-worker.yaml`,Configures kdump crash reporting on worker nodes.,No
Kubelet configuration and container mount hiding,`01-container-mount-ns-and-kubelet-conf-master.yaml`,Configures a mount namespace for sharing container-specific mounts between kubelet and CRI-O on control plane nodes.,No
Kubelet configuration and container mount hiding,`01-container-mount-ns-and-kubelet-conf-worker.yaml`,Configures a mount namespace for sharing container-specific mounts between kubelet and CRI-O on worker nodes.,No
One-shot time sync,`99-sync-time-once-master.yaml`,Synchronizes time once on master nodes.,No
One-shot time sync,`99-sync-time-once-worker.yaml`,Synchronizes time once on worker nodes.,No
SCTP,`03-sctp-machine-config-master.yaml`,Loads the SCTP kernel module on master nodes.,Yes
SCTP,`03-sctp-machine-config-worker.yaml`,Loads the SCTP kernel module on worker nodes.,Yes
Set RCU normal,`08-set-rcu-normal-master.yaml`,Disables rcu_expedited by setting rcu_normal after the control plane node has booted.,No
Set RCU normal,`08-set-rcu-normal-worker.yaml`,Disables rcu_expedited by setting rcu_normal after the worker node has booted.,No
SRIOV-related kernel arguments,`07-sriov-related-kernel-args-master.yaml`,Enables SR-IOV support on master nodes.,No
|====
Revised: SCTP,`03-sctp-machine-config-master.yaml`,Loads the SCTP kernel module on control plane nodes.,Yes
Original: . Application logs are not collected by the platform log collector
. Use a maximum of 5 {rh-rhacm} configuration policies with a compliant evaluation interval of not less than 10 minutes.
Revised: . Use a maximum of 10 {rh-rhacm} configuration policies, comprising 5 Red{nbsp}Hat provided policies and up to 5 custom configuration policies with a compliant evaluation interval of not less than 10 minutes.
Original: include::https://raw.githubusercontent.com/openshift-kni/commatrix/release-4.18/docs/stable/unique/bm.csv[]
== Additional network flows for {sno} on bare metal
In addition to the base network flows, the following matrix describes the ingress flows to {product-title} services that are specific to {sno} on bare metal.
Revised: In addition to the base network flows, the following matrix describes the ingress flows to {product-title} services that are specific to {sno} configured with `platform: None`.
Original: If you created the key pair on a {op-system-base-full} system, before you can use the public key on a Windows system, make sure the public key is saved using ASCII encoding. For example, the following PowerShell command copies a public key, encoding it for the ASCII character set:
Revised: If you created the key pair on a {op-system-base-full} system, before you can use the public key on a Windows system, make sure the public key is saved by using ASCII encoding. For example, the following PowerShell command copies a public key, encoding it for the ASCII character set:
Original: * You have created a private/public key pair, which is used to configure key-based authentication in the OpenSSH server. The private key must also be configured in the Windows Machine Config Operator (WMCO) namespace. This is required to allow the WMCO to communicate with the Windows VM. See the "Configuring a secret for the Windows Machine Config Operator" section for more details.
Revised: * You have created a private/public key pair, which is used to configure key-based authentication in the OpenSSH server. The private key must be configured in the Windows Machine Config Operator (WMCO) namespace so that the WMCO can communicate with the Windows VM.
Original: * In a fully managed deployment, everything is automated by Red Hat in collaboration with CSP. You can request an OpenShift instance through the CSP web console, and the cluster is automatically created and fully managed by Red Hat. You do not have to worry about node failures or errors in the environment. Red Hat is fully responsible for maintaining the uptime of the cluster. The fully managed services are available on AWS and Azure. For AWS, the OpenShift service is called ROSA (Red Hat OpenShift Service on AWS). For Azure, the service is called Azure Red Hat OpenShift.
Revised: * In a fully managed deployment, everything is automated by Red Hat in collaboration with CSP. You can request an OpenShift instance through the CSP web console, and the cluster is automatically created and fully managed by Red Hat. You do not have to worry about node failures or errors in the environment. Red Hat is fully responsible for maintaining the uptime of the cluster. The fully managed services are available on {aws-short}, {azure-short}, and {gcp-short}. For {aws-short}, the OpenShift service is called ROSA (Red Hat OpenShift Service on AWS). For Azure, the service is called Azure Red Hat OpenShift. For {gcp-short}, the service is called OpenShift Dedicated on {gcp-short}.
Original: ./openshift-install 4.18.0
release image registry.ci.openshift.org/origin/release:4.18ocp-release@sha256:0da6316466d60a3a4535d5fed3589feb0391989982fba59d47d4c729912d6363
Revised: release image registry.ci.openshift.org/origin/release:{product-version}ocp-release@sha256:0da6316466d60a3a4535d5fed3589feb0391989982fba59d47d4c729912d6363
Original: authentication 4.18.0-0    True       False          False      6m18s
baremetal      4.18.0-0    True       False          False      2m42s
network        4.18.0-0    True       True           False      5m58s  Progressing: …
Revised: authentication {product-version}.0-0    True       False          False      6m18s
baremetal      {product-version}.0-0    True       False          False      2m42s
network        {product-version}.0-0    True       True           False      5m58s  Progressing: …
Original: * Previously, a bug fix altered the availability set configuration by changing the fault domain count to use the maximum available value instead of being fixed at 2. This inadvertently caused scaling issues for MachineSets created prior to the bug fix, as the controller attempted to modify immutable availability sets. With this release, availability sets are no longer modified after creation, allowing affected MachineSets to scale properly. (link:https://issues.redhat.com/browse/OCPBUGS-56657[OCPBUGS-56657]). 
Revised: * Previously, a bug fix altered the availability set configuration by changing the fault domain count to use the maximum available value instead of being fixed at 2. This inadvertently caused scaling issues for `MachineSets` created prior to the bug fix, as the controller attempted to modify immutable availability sets. With this release, availability sets are no longer modified after creation, allowing affected `MachineSets` to scale properly. (link:https://issues.redhat.com/browse/OCPBUGS-56657[OCPBUGS-56657]).
Original: * Previously, a bug fix altered the availability set configuration by changing the fault domain count to use the maximum available value instead of being fixed at 2. This inadvertently caused scaling issues for MachineSets created prior to the bug fix, as the controller attempted to modify immutable availability sets. With this release, availability sets are no longer modified after creation, allowing affected MachineSets to scale properly. (link:https://issues.redhat.com/browse/OCPBUGS-56657[OCPBUGS-56657]). 
Revised: * Previously, a bug fix altered the availability set configuration by changing the fault domain count to use the maximum available value instead of being fixed at 2. This inadvertently caused scaling issues for MachineSets created prior to the bug fix, as the controller attempted to modify immutable availability sets. With this release, availability sets are no longer modified after creation, allowing affected MachineSets to scale properly. (link:https://issues.redhat.com/browse/OCPBUGS-56657[OCPBUGS-56657])
Original: * Previously, the build controller looked for secrets that were linked for general use, not specifically for the image pull. With this release, when searching for default image pull secrets, the builds use ImagePullSecrets that are linked to the service account. (link:https://issues.redhat.com/browse/OCPBUGS-54344[OCPBUGS-54344])
Revised: * Previously, the build controller looked for secrets that were linked for general use, not specifically for the image pull. With this release, when searching for default image pull secrets, the builds use `ImagePullSecrets` that are linked to the service account. (link:https://issues.redhat.com/browse/OCPBUGS-54344[OCPBUGS-54344])
Original: Before you perform an image signature verification, you must first create a signature integration in {rh-rhacs-first}.
Revised: _something about why I want to perform an image signature verification_

> Before you perform an image signature verification, you must first create a signature integration in {rh-rhacs-first}.
This is a prerequisite. Instead, a brief description of why and how we are doing the image signature verification should be here. See https://redhat-documentation.github.io/modular-docs/#con-creating-procedure-modules_writing-mod-docs for details.