CODE RUB: Wording changes

Author: cjdutoit

2. Services/2. Services.md

@@ -247,7 +247,7 @@ File versioning governs how changes to models and services are managed and commu
 
 #### 2.0.3.0 Model Versioning
 
-When a model’s structure or behaviour is changed (including adding, removing, or modifying properties), a new version of the model must be created.
+When a model’s structure is changed (including adding, removing, or modifying properties), a new version of the model must be created.
 The version number must be incremented, and both the model file and its path must reflect the new version. This preserves backward compatibility and allows consumers to upgrade at their discretion.
 
 New model versions must be created alongside the previous version and organised in a versioned subfolder.
@@ -367,7 +367,8 @@ The new V2 model service only exposes the latest behavior under the implied V0 n
 The parameter name in the method signature does not include the model version, 
 as it is already reflected in the service file name and path.
 
-**TIP:** Use XML documentation comments to clearly indicate the versioning details of each method, including which model version it corresponds to and any behavior changes. This provides clarity for developers consuming the service and helps maintain a clear history of changes over time.
+TIP: Use XML documentation comments to indicate versioning details only at exposure layers where consumers do not have access to the source code. This ensures external consumers understand which model version is used and any behaviour changes, while avoiding unnecessary comments within internal or non-exposed layers where the code itself is already visible.
+
 **Example:**
 ```csharp
 internal interface IEventAddressV3Service