doc: minor rewordings

Author: maxmoehl

docs/iaas/architecture/networking.md

@@ -6,7 +6,7 @@ IronCore's virtual networking architecture provides an end-to-end virtual networ
 
 - **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.
-- **Performing**: The data plane of IronCore's virtual networking solution is built with the state-of-the-art packet processing framework, [DPDK](https://www.dpdk.org), and currently utilizes the hardware offloading features of [Nvidia's Mellanox SmartNic serials](https://www.nvidia.com/en-us/networking/ethernet-adapters/) to speedup packet processing. With the DPDK's run-to-completion model, IronCore's networking data plane can achieve high performance even in the environment where hardware offloading capability is limited or disabled. 
+- **Performing**: The data plane of IronCore's virtual networking solution is built with the packet processing framework [DPDK](https://www.dpdk.org), and currently utilizes the hardware offloading features of [Nvidia's Mellanox SmartNic serials](https://www.nvidia.com/en-us/networking/ethernet-adapters/) to speedup packet processing. With the DPDK's run-to-completion model, IronCore's networking data plane can achieve high performance even in the environment where hardware offloading capability is limited or disabled.
 
 IronCore's virtual networking architecture is illustrated with the following figure. It consists of several components that work together to ensure network out and inbound connectivity and isolation for `Machine` instances.
 

docs/iaas/architecture/providers/brokers.md

@@ -8,7 +8,7 @@ Below is an example of how a `machinepoollet` and `machinebroker` will translate
 
 ![Brokers](/brokers.png)
 
-Brokers are useful in scenarios where I want to run IronCore not in a single cluster but rather have a federated
+Brokers are useful in scenarios where IronCore should not run in a single cluster but rather have a federated
 environment. For example, in a federated environment, every hypervisor node in a compute cluster would announce it's 
 `MachinePool` inside the compute cluster. A `MachinePoollet`/`MachineBroker` in this compute cluster could now announce 
 a logical `MachinePool` "one level up" as a logical compute pool in e.g. an availability zone cluster. The broker concept