Fix some typos in the posture checks doc

src/pages/how-to/manage-posture-checks.mdx

@@ -1,7 +1,7 @@
 # Manage access with posture checks
 
 NetBird enables administrators to manage network access by creating access policies that dictate
-which peer groups can interact with other peers in your network.
+which peer groups can interact with others in the network.
 Posture checks extend these policies, augmenting their capabilities by allowing administrators to
 enforce access restrictions based on specified criteria. By integrating posture checks seamlessly
 into policy-based ACLs, NetBird evaluates various attributes to determine the eligibility of peers to
@@ -9,9 +9,15 @@ connect to the network.
 
 ## Concepts
 
+There is a number of posture checks that you can choose to enforce access restrictions based on specific criteria.
+
+<p>
+    <img src="/docs-static/img/how-to-guides/supported-posture-checks-list.png" alt="high-level-dia" className="imagewrapper"/>
+</p>
+
 ### NetBird client version check
 
-The NetBird client version check verifies the version of NetBird installed on the device attempting to connect to the
+he NetBird client version check verifies the version of the NetBird software installed on the device attempting to connect to the
 network. This check ensures that only devices running a specified version of NetBird can gain access,
 thus preventing outdated or incompatible clients from compromising network security.
 
@@ -25,13 +31,12 @@ secure operating systems can access network resources.
     This check requires NetBird version [0.26.0](https://github.com/netbirdio/netbird/releases) or newer.
 </Note>
 
-The check evaluates the actual `OS version` for Android, macOS, and iOS, while for Linux and Windows, it assesses
-the `kernel version`.
+The check evaluates the actual `OS version` for Android, macOS, and iOS, while for Linux and Windows, it assesses the `kernel version`.
 
 Below are some examples of OS versions for each operating system:
 
 * Android 14 Upside Down Cake: `14`, `14.3`
-* macIS 13	Ventura: `13`, `13.6.4`
+* macOS 13	Ventura: `13`, `13.6.4`
 * macOS 14 Sonoma: `14`, `14.3.1`
 * iOS 16 / iPadOS 16: `16`, `16.7.5`
 * Linux kernel: `6`, `6.7.5`
@@ -45,15 +50,15 @@ The geolocation check examines the connecting device's geographical location bas
 This check allows administrators to enforce access restrictions based on geographic regions,
 offering country-wide and city-level granularity.
 
-## Managing Posture Checks
+## Managing posture checks
 
-Posture Checks are dynamic, and you can create a policy with multiple posture checks. A single posture
+Posture checks are dynamic, and you can create a policy with multiple posture checks. A single posture
 check can also be reused across different policies. When managing posture checks, you can update them as
 per your requirements.
 
-However, deleting a posture check is only possible if it's not currently used in any policy. If a posture
-check is in use, you need to unassigned it from the respective policy before you can delete it.
-This precaution ensures the continuity and integrity of your security setup.
+Deleting a posture check is only possible if it's not currently used in any policy. If a posture check is in use,
+you need to unassign it from the respective policy before you can delete it. This precaution ensures the continuity
+and integrity of your security setup.
 
 Here are some steps to help you create and manage your posture checks effectively:
 
@@ -61,7 +66,7 @@ In the example below, we are creating a posture check that will only allow clien
 higher to connect and access network resources.
 
 ### Creating posture checks
-Access the `Access Control` tab, the `Posture Checks` section and click `Create Posture Check`.
+Access the `Access Control` tab, then the `Posture Checks` section, and click `Create Posture Check`.
 
 <p>
     <img src="/docs-static/img/how-to-guides/add-posture-check.png" alt="high-level-dia" className="imagewrapper"/>