Replace baremetal with bare metal to maintain consistency

Author: Rohit-0505

docs/baremetal/architecture/discovery.md

@@ -1,6 +1,6 @@
 # Server Discovery and First Boot
 
-This document describes the discovery and first boot process for bare metal servers in IronCore's baremetal automation.
+This document describes the discovery and first boot process for bare metal servers in IronCore's bare metal automation.
 The goal here is to provide a clear understanding of how bare metal servers are discovered and prepared for provisioning.
 
 ## Server Discovery 

docs/baremetal/architecture/provisioning.md

@@ -1,6 +1,6 @@
 # Server Provisioning
 
-This section describes how the provisioning of bare metal servers is handled in IronCore's baremetal automation. 
+This section describes how the provisioning of bare metal servers is handled in IronCore's bare metal automation. 
 In the [discovery section](/baremetal/architecture/discovery) we discussed how servers are discovered and first time
 booted and how they are transitioned into an `Available` state. Now we will focus on the provisioning process, and 
 one can use such a `Server` resource to provision a custom operating system and automate the software installation on

docs/baremetal/index.md

@@ -1,6 +1,6 @@
 # Baremetal Automation
 
-The baremetal automation in IronCore is designed to provide a comprehensive solution for managing physical servers
+The bare metal automation in IronCore is designed to provide a comprehensive solution for managing physical servers
 in a Kubernetes-native way. It leverages the power of Kubernetes Custom Resource Definitions (CRDs) to automate:
 
 - **Discovery**: Automatically detect and register bare metal servers.
@@ -11,7 +11,7 @@ in a Kubernetes-native way. It leverages the power of Kubernetes Custom Resource
 
 ## Core Components
 
-The core components of the baremetal automation in IronCore include:
+The core components of the bare metal automation in IronCore include:
 - [**Metal Operator**](https://github.com/ironcore-dev/metal-operator): The central component that manages the lifecycle of bare metal servers.
 - [**Boot Operator**](https://github.com/ironcore-dev/boot-operator): iPXE and HTTP boot server that provides boot images and Ignition configurations.
 - [**FeDHCP**](https://github.com/ironcore-dev/fedhcp): A DHCP server that provides in-band and out-of-band network configuration to bare metal servers.
@@ -22,7 +22,7 @@ Usage guides and concepts for the `metal-operator` API types can be found in the
 
 ## Prerequisites
 
-The current implementation of the baremetal automation in IronCore requires the following prerequisites:
+The current implementation of the bare metal automation in IronCore requires the following prerequisites:
 
 - In-band and out-of-band network connectivity to the bare metal servers.
 - A management server in the out-of-band network that can communicate with the bare metal servers.

docs/iaas/architecture/networking.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-IronCore's virtual networking architecture provides an end-to-end virtual networking solution for provisioned `Machine`s running in data centers, regardless they are baremetal machines or virtual machines. It is designed to enable robust, flexible and performing networking control plane and data plane.
+IronCore's virtual networking architecture provides an end-to-end virtual networking solution for provisioned `Machine`s running in data centers, regardless they are bare metal machines or virtual machines. It is designed to enable robust, flexible and performing networking control plane and data plane.
 
 - **Robust**: IronCore's virtual networking control plane is mainly implemented using Kubernetes controller model. Thus, it is able to survive component's failure and recover the running states by retrieving the desired networking configuration.
 - **Flexible**: Thanks to the modular and layered architecture design, IronCore's virtual networking solution allows developers to implement and interchange components from the most top-level data center management system built upon defined IronCore APIs, to lowest-level packet processing engines depending on the used hardware.