Use consistent spelling for Ironic

Author: furkatgofurov7

docs/architecture.md

@@ -40,7 +40,7 @@ with Ironic to make changes on the Bare Metal Server.
 During the initial introspection and state changes, the above logic works in the
  opposite direction as well. Information gathered during introspection or any
  state changes on the Bare Metal Server, results in BMO learning about the
- change(s) via ironic and a chain of events starts. Once BMO learns about the
+ change(s) via Ironic and a chain of events starts. Once BMO learns about the
  changes, it makes the required
 changes on the BMH.
 

docs/deployment_workflow.md

@@ -18,7 +18,7 @@ The cluster should either :
   the userData and would set the providerIDs based on the BareMetalHost UID.
 * Be deployed with the ProviderID set to be the BareMetalHostUUID
 * be deployed with each node with the label "metal3.io/uuid" set to the
-  BareMetalHost UID that is provided by ironic to cloud-init through the
+  BareMetalHost UID that is provided by Ironic to cloud-init through the
   metadata `ds.meta_data.uuid`. This can be achieved by setting the following in
   the KubeadmConfig :
 

docs/dev-setup.md

@@ -53,7 +53,7 @@ This requires the following environment variables to be exported :
 * `IRONIC_URL`
 
 Those need to be set up accordingly with the
-[local ironic setup](https://github.com/metal3-io/baremetal-operator/blob/master/docs/dev-setup.md#running-a-local-instance-of-ironic)
+[local Ironic setup](https://github.com/metal3-io/baremetal-operator/blob/master/docs/dev-setup.md#running-a-local-instance-of-ironic)
 
 The tilt-settings file can be customized. Tilt will also consider everything
 under `tilt.d` directory.
@@ -70,7 +70,7 @@ latest code of CAPM3.
 Tilt can be used in Metal3-dev-env, as long as the
 03_launch_mgmt_cluster.sh script is **NOT** run. In that case Ironic needs to
 be deployed locally first, following the
-[local ironic setup](https://github.com/metal3-io/baremetal-operator/blob/master/docs/dev-setup.md#running-a-local-instance-of-ironic)
+[local Ironic setup](https://github.com/metal3-io/baremetal-operator/blob/master/docs/dev-setup.md#running-a-local-instance-of-ironic)
 
 By default, the Cluster API components deployed by Tilt have experimental
 features turned off. If you would like to enable these features, add
@@ -153,7 +153,7 @@ This requires the following environment variables to be exported :
 * `IRONIC_URL`
 
 Those need to be set up accordingly with the
-[local ironic setup](https://github.com/metal3-io/baremetal-operator/blob/master/docs/dev-setup.md#running-a-local-instance-of-ironic)
+[local Ironic setup](https://github.com/metal3-io/baremetal-operator/blob/master/docs/dev-setup.md#running-a-local-instance-of-ironic)
 
 The cluster-api management components that are deployed are configured at the
 `/config` folder of each repository respectively. Making changes to those files
@@ -247,7 +247,7 @@ below.  Please note, the precedence of variables is as follows:
    `worker-templates.flavors[0].WORKER_MACHINE_COUNT`
 1. vars defined at 'metadata' level-- spans workers i.e.
    `metadata.WORKER_MACHINE_COUNT`
-1. programmatically defined default vars i.e. everything except ironic
+1. programmatically defined default vars i.e. everything except Ironic
    related URL variables "DEPLOY_KERNEL_URL", "DEPLOY_RAMDISK_URL",
    "IRONIC_INSPECTOR_URL" and "IRONIC_URL"
 

docs/getting-started.md

@@ -129,7 +129,7 @@ unset. If unset, then `IRONIC_USERNAME` and `IRONIC_PASSWORD` must be set.
 
 ##### IRONIC_INSPECTOR_USERNAME
 
-Username for Ironic inspector basic auth. Optional, but either this variable or
+Username for Ironic Inspector basic auth. Optional, but either this variable or
 `IRONIC_INSPECTOR_NO_BASIC_AUTH` must be set.
 
 ```sh
@@ -138,7 +138,7 @@ Username for Ironic inspector basic auth. Optional, but either this variable or
 
 ##### IRONIC_INSPECTOR_PASSWORD
 
-Password for Ironic inspector basic auth. Optional, but either this variable or
+Password for Ironic Inspector basic auth. Optional, but either this variable or
 `IRONIC_INSPECTOR_NO_BASIC_AUTH` must be set.
 
 ```sh
@@ -147,7 +147,7 @@ Password for Ironic inspector basic auth. Optional, but either this variable or
 
 ##### IRONIC_INSPECTOR_NO_BASIC_AUTH
 
-Disables basic authentication for Ironic inspector API. Any value provided in
+Disables basic authentication for Ironic Inspector API. Any value provided in
 this variable disables authentication. To enable authentication, leave this
 variable unset. If unset, then `IRONIC_INSPECTOR_USERNAME` and
 `IRONIC_INSPECTOR_PASSWORD` must be set.
@@ -347,10 +347,10 @@ WORKERS_KUBEADM_EXTRA_CONFIG="
 
 Before running the `move` command of Clusterctl, elements such as Ironic if
 applicable, need to be moved to the target cluster. It is recommended to
-scale down the ironic pod in the origin cluster before deploying it on the
+scale down the Ironic pod in the origin cluster before deploying it on the
 target cluster to prevent issues with a duplicated DHCP server.
 
-Both for pivoting or updating ironic, it is critical that the cluster is in
+Both for pivoting or updating Ironic, it is critical that the cluster is in
 a stable situation. No operations on BareMetal hosts shall be on-going,
 otherwise they might fail. Similarly, in order to prevent conflict during
 the pivoting of the DHCP server, we recommend to have no BareMetalHosts
@@ -360,7 +360,7 @@ of the IP address of a running host that would not be supported by Ironic.
 
 In the case of a self-hosted cluster, special care must be paid to Ironic.
 Since Ironic runs on the target cluster, updating the target cluster means
-that ironic will need to be moved between nodes of the cluster. This results
+that Ironic will need to be moved between nodes of the cluster. This results
 in similar issues as pivoting. The following points should be ensured to run
 a target cluster upgrade: