openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OCPBUGS#31297: Fixed typos

Browse Source
This commit is contained in:
srir
2024-07-29 16:02:58 +05:30
committed by openshift-cherrypick-robot
parent ea7c34a2c4
commit dd25193887
5 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
modules/cnf-checking-numa-aware-scheduler-logs.adoc
View File

@@ -79,7 +79,7 @@ numaresourcesscheduler.nodetopology.openshift.io/numaresourcesscheduler created
. Check that the NUMA-aware scheduler was successfully deployed:
.. Run the following command to check that the CRD is created succesfully:
.. Run the following command to check that the CRD is created successfully:
+
[source,terminal]
----

2
modules/cnf-reporting-more-exact-reource-availability.adoc
View File

@@ -76,7 +76,7 @@ numaresourcesscheduler.nodetopology.openshift.io/numaresourcesscheduler created
. Check that the NUMA-aware scheduler was successfully deployed:
.. Run the following command to check that the CRD is created succesfully:
.. Run the following command to check that the CRD is created successfully:
+
[source,terminal]
----

4
modules/cnf-troubleshooting-numa-aware-workloads.adoc
View File

@@ -45,7 +45,7 @@ $ oc get numaresourcesschedulers.nodetopology.openshift.io numaresourcesschedule
topo-aware-scheduler
----
. Verify that NUMA-aware scheduable nodes have the `noderesourcetopologies` CR applied to them. Run the following command:
. Verify that NUMA-aware schedulable nodes have the `noderesourcetopologies` CR applied to them. Run the following command:
+
[source,terminal]
----
@@ -65,7 +65,7 @@ compute-1.example.com 17h
The number of nodes should equal the number of worker nodes that are configured by the machine config pool (`mcp`) worker definition.
====
. Verify the NUMA zone granularity for all scheduable nodes by running the following command:
. Verify the NUMA zone granularity for all schedulable nodes by running the following command:
+
[source,terminal]
----

2
modules/nodes-vsphere-machine-set-concept-static-ip.adoc
View File

@@ -38,4 +38,4 @@ spec:
status: {}
----
The machine controller updates the machine with a status of `IPAddressClaimed` to indicate that a static IP address has succesfully bound to the `IPAddressClaim` resource. The machine controller applies the same status to a machine with multiple `IPAddressClaim` resources that each contain a bound static IP address.The machine controller then creates a virtual machine and applies static IP addresses to any nodes listed in the `providerSpec` of a machine's configuration.
The machine controller updates the machine with a status of `IPAddressClaimed` to indicate that a static IP address has successfully bound to the `IPAddressClaim` resource. The machine controller applies the same status to a machine with multiple `IPAddressClaim` resources that each contain a bound static IP address.The machine controller then creates a virtual machine and applies static IP addresses to any nodes listed in the `providerSpec` of a machine's configuration.

2
rest_api/console_apis/consolequickstart-console-openshift-io-v1.adoc
View File

@@ -285,7 +285,7 @@ Required::
| `success`
| `string`
| success describes the succesfully passed task.
| success describes the successfully passed task.
|===