Updates after peer review

Author: shreyasiddhartha

modules/ossm-about-operator-update-process.adoc

@@ -6,6 +6,6 @@
 [id="ossm-about-operator-update-process_{context}"]
 = About Operator update process
 
-The {SMProduct} Operator will upgrade automatically to the latest available version based on the selected channel when the *approval strategy* field is set to `Automatic` (default). If the *approval strategy* field is set to `Manual`, OLM will generate an update request, which a cluster administrator must approve to update the Operator to the latest version.
+The {SMProduct} Operator will upgrade automatically to the latest available version based on the selected channel when the *approval strategy* field is set to `Automatic` (default). If the *approval strategy* field is set to `Manual`, {olm-first} will generate an update request, which a cluster administrator must approve to update the Operator to the latest version.
 
 The Operator update process does not automatically update the {istio} control plane unless the `{istio}` resource version is set to an alias (for example, `vX.Y-latest`) and the `updateStrategy` is set to `InPlace`. This triggers a control plane update when a new version is available in the Operator. By default, the Operator will not update the {istio} control plane unless the `{istio}` resource is updated with a new version.

modules/ossm-understanding-operator-updates-and-channels.adoc

@@ -6,7 +6,7 @@
 [id="ossm-understanding-operator-updates-and-channels_{context}"]
 = Understanding Operator updates and channels
 
-The {olm-first} manages Operators and their associated services using channels to organise and distribute updates. Channels are a way to group related updates together.
+The {olm-first} manages Operators and their associated services by using channels to organize and distribute updates. Channels are a way to group related updates.
 
 To ensure that your {SMProduct} stays current with the latest security patches, bug fixes, and software updates, keep the {SMProduct} Operator up to date. The upgrade process depends on the configured channel and approval strategy.
 

modules/ossm-understanding-versioning.adoc

@@ -8,7 +8,7 @@
 
 {product-title} follows Semantic Versioning for all product releases. Semantic Versioning uses a three-part version number in the format `X.Y.Z` to communicate the nature of changes in each release.
 
-X (Major version):: indicates significant updates that may include breaking changes, such as architectural shifts, API changes, or schema modifications.
+X (Major version):: indicates significant updates that might include breaking changes, such as architectural shifts, API changes, or schema modifications.
 
 Y (Minor version):: introduces new features and enhancements while maintaining backward compatibility.