Apply suggestions from Walter

content/guides/apertis_release_process.md

@@ -230,7 +230,7 @@ In a typical Apertis Release, we have multiple repository components
 * Backports repository components like: `apertis:v2023:backports:development`, `apertis:v2023:backports:target`
 
 
-For packages landing into an Apertis Stable Release, it would land through either of `backports`, `updates`, or `seucrity` repository components.
+For packages landing into an Apertis Stable Release, it would land through either of `security`, `updates`, or `backports` repository components.
 Packages accumulate into either of the repositories and eventually get folded into the main respective repository, just like the stable release procedure followed in the Debian project.
 
 The above structure allows Apertis users to have immediate access to updates through either of the repository channels, provided those repositories are enabled in their apt configuration.
@@ -250,7 +250,7 @@ bv2023.0ab<B_CNT> in v2023-backports
 
 In the above example, the revisioning is carefully ordered to ensure that when Stable Update packages finally land into the main repository, they have the proper revision.
 
-Consider the above with an example of package `foo` and version `1.0-1`. Under Apertis, its typcial reflection would be something like: `foo-1.0-1+apertis0bv2023.0db1_amd64.deb` which would be the initial version in the main repository. Over the course, we may push a new security update reflecting as `foo-1.0-3+apertis0bv2023.0cb1_amd64.deb` which would live for a defined time until the next Stable Point Release in the security repository, like `apertis:v2023:security:development`. Eventually, as part of the Stable Point Release, the package will be folded into the main repository, at which point, its reflection in the main repository will become: `foo-1.0-3+apertis0bv2023.0db1_amd64.deb`.
+Consider the above with an example of package `foo` and version `1.0-1`. Under Apertis, its typical reflection would be something like: `foo-1.0-1+apertis0bv2023.0db1_amd64.deb` which would be the initial version in the main repository. Over the course, we may push a new security update reflecting as `foo-1.0-3+apertis0bv2023.0cb1_amd64.deb` which would live for a defined time until the next Stable Point Release in the security repository, like `apertis:v2023:security:development`. Eventually, as part of the Stable Point Release, the package will be folded into the main repository, at which point, its reflection in the main repository will become: `foo-1.0-3+apertis0bv2023.0db1_amd64.deb`.
 
 Over its lifecycle in the Apertis v2023 release so far, package `foo` has had 3 versions: `1.0-1+apertis0bv2023.0db1`, `1.0-3+apertis0bv2023.0cb1` and `1.0-3+apertis0bv2023.0db1`
 
@@ -271,7 +271,7 @@ $ dpkg --compare-versions 1.0-3+apertis0bv2023.0cb2 lt 1.0-3+apertis0bv2023.0db1
 Latter version is greater
 ```
 
-The above repository versioning scheme is reliable across the entire lifespan of an Apertis Stable Release. No further tweakings to project config are required.
+The above repository versioning scheme is reliable across the entire lifespan of an Apertis Stable Release. No further tweaks to project config are required.
 
 # Appendix