address review comments

Author: Rohit-0505

docs/contribute/contributing.md

@@ -64,32 +64,32 @@ process. We use [the standard DCO text of the Linux Foundation](https://develope
 
 * Fork and clone the repository to your local machine.
 
-    ```shell
-    git clone [email protected]:ironcore-dev/ironcore-dev.github.io.git
-    cd docs
-    ```
+```shell
+git clone [email protected]:ironcore-dev/ironcore-dev.github.io.git
+cd docs
+```
 
 * Create a branch from the `main` using 'git checkout' command. 
 !!! note 
     If needed, rebase to the current `main` branch before submitting your pull request. If it doesn't merge properly
     with `main` you may be asked to rebase your changes.
 
-    ```shell
-    git checkout -b my_feature
-    # rebase if necessary
-    git fetch upstream main
-    git rebase upstream/main
-    ```
+```shell
+git checkout -b my_feature
+# rebase if necessary
+git fetch upstream main
+git rebase upstream/main
+```
 
 * Commits should be as small as possible, while ensuring that each commit is correct independently 
 
 * Commit your changes to your feature branch and push it to your fork.
 
-    ```shell
-    git add .
-    git commit -m "Something meaningful"
-    git push origin my_feature
-    ```
+```shell
+git add .
+git commit -m "Something meaningful"
+git push origin my_feature
+```
 
 !!! note
     Alternatively you can amend your commit before pushing if you forgot something by using `git commit --amend`
@@ -111,5 +111,4 @@ for a review in the pull request or a comment.
 We use GitHub issues to track bugs and enhancement requests. Please provide as much context as possible when you open an issue. The information you provide must be comprehensive enough to understand, reproduce the behavior and find related reports of that issue for the assignee. 
 Therefore, contributors may use but aren't restricted to the issue template provided by the IronCore maintainers.
 
-
 Thank you for helping improve our documentation!

docs/iaas/usage-guides/ipam.md

@@ -1,4 +1,5 @@
 # IPAM Resources
+
 This guide explains how to use IronCore's integrated IP address management (IPAM) resources to define and manage IP prefixes and allocations.
 
 ## Prefix

docs/iaas/usage-guides/networking.md

@@ -1,6 +1,6 @@
 # Networking Resources
 
-This guide describes the core networking resources in IronCore, such as `Networks`, `NetworkInterfaces`, `VirtualIPs`, `NAT gateways`, `LoadBalancers`, and `NetworkPolicies`. It explains how to define, configure, and manage these resources for the infrastructure.
+This guide describes the core networking resources in IronCore, such as `Networks`, `NetworkInterfaces`, `VirtualIPs`, `NAT gateways`, `LoadBalancers`, and `NetworkPolicies`.
 
 ## Network
 
@@ -26,11 +26,9 @@ spec:
 ### Key Fields:
 
 - `peerings` (`list`): Are the list of network peerings with this `Network` (optional).
-
-
 ### More about IronCore Network:
 
-- **Network creation**: [ironcore-net](https://github.com/ironcore-dev/ironcore-net) is the network plugin for IronCore that realizes the `Network` resource, When an IronCore `Network` is created, a corresponding `core.apinet.ironcore.dev/Network` is created in the ironcore-net(apinet) cluster.
+- **Network creation**: [ironcore-net](https://github.com/ironcore-dev/ironcore-net) is the network plugin for IronCore that realizes the `Network` resource. When an IronCore `Network` is created, a corresponding `core.apinet.ironcore.dev/Network` is created in the ironcore-net(apinet) cluster.
 Once created and with an allocated ID, the IronCore `Network` will be patched with the corresponding providerID of the apinet Network and set to state: `Available`. 
 The format of a network providerID is as follows:
 `ironcore-net://<namespace>/<name>/<id>/<uid>`
@@ -61,7 +59,6 @@ status:
   - name: peering1
     state: Ready
   state: Available
-
 ```
 
 For detailed e2e example on network peering
@@ -73,7 +70,6 @@ A `NetworkInterface` resource in IronCore represents a connection point between
 network. It encapsulates the configuration and life cycle management of the virtual network interface, ensuring 
 seamless connectivity for `Machines`.
 
-
 ### Example NetworkInterface Resource
 
 An example of how to define a `NetworkInterface` resource in IronCore:
@@ -179,7 +175,6 @@ spec:
 - `portsPerNetworkInterface` (`int32`): This Specifies the number of ports allocated per network interface and controls how many simultaneous connections can be handled per interface. If empty, 2048 (DefaultPortsPerNetworkInterface) is the default.
 - `networkRef` (`string`): It represents which network this `NATGateway` serves.
 
-
 After reconciling all `NATGateways`, the status gets updated with the corresponding values for `ips` as shown below.
 
 ```yaml