Update container-insights-manage-agent.md

Author: ibrar2411

articles/azure-monitor/containers/container-insights-manage-agent.md

@@ -91,15 +91,15 @@ To reenable discovery of the environmental variables, apply the same process you
 ```  
 ## Semantic version update of container insights agent version
 
-Container insights has shifted the image version and naming convention to semver format. SemVer helps developers keep track of every change made to a software during its development phase and ensures that the software versioning is consistent and meaningful. The old version was in format of ciprod<timestamp>-<commitId> and win-ciprod<timestamp>-<commitId>, Semver is started from 3.1.4 and win-3.1.4. 
+Container Insights has shifted the image version and naming convention to [semver format] (https://semver.org/). SemVer helps developers keep track of every change made to a software during its development phase and ensures that the software versioning is consistent and meaningful. The old version was in format of ciprod<timestamp>-<commitId> and win-ciprod<timestamp>-<commitId>, our first image versions using the Semver format are 3.1.4 for Linux and win-3.1.4 for Windows. 
 
 Semver is a universal software versioning schema which is defined in the format MAJOR.MINOR.PATCH, which follows the following constraints: 
 
 1. Increment the MAJOR version when you make incompatible API changes. 
 2. Increment the MINOR version when you add functionality in a backwards compatible manner. 
 3. Increment the PATCH version when you make backwards compatible bug fixes.
 
-With the rise of Kubernetes and the OSS ecosystem, container insights migrate to use semver image following the K8s recommended standard wherein with each minor version introduced, all breaking changes were required to be publicly documented with each new Kubernetes release.   
+With the rise of Kubernetes and the OSS ecosystem, Container Insights migrate to use semver image following the K8s recommended standard wherein with each minor version introduced, all breaking changes were required to be publicly documented with each new Kubernetes release.   
 
 ## Next steps