Avoid e.g. in favor of ex phrasing

dagardner-nv · dagardner-nv · commit 790779b999bc · 2024-10-23T16:09:52.000-07:00
diff --git a/docs/source/getting_started.md b/docs/source/getting_started.md
@@ -53,7 +53,7 @@ More advanced users, or those who are interested in using the latest pre-release
 
 > **Note about Morpheus versions:**
 >
-> Morpheus uses Calendar Versioning ([CalVer](https://calver.org/)). For each Morpheus release there will be an image tagged in the form of `YY.MM-runtime`. This tag will always refer to the latest point release for that version. In addition, there will also be at least one point release version tagged in the form of `vYY.MM.00-runtime`. This will be the initial point release for that version (e.g., `v24.10.00-runtime`). In the event of a major bug, we may release additional point releases (e.g., `v24.10.01-runtime`, `v24.10.02-runtime` etc...), and the `YY.MM-runtime` tag will be updated to reference that point release.
+> Morpheus uses Calendar Versioning ([CalVer](https://calver.org/)). For each Morpheus release there will be an image tagged in the form of `YY.MM-runtime`. This tag will always refer to the latest point release for that version. In addition, there will also be at least one point release version tagged in the form of `vYY.MM.00-runtime`. This will be the initial point release for that version (ex., `v24.10.00-runtime`). In the event of a major bug, we may release additional point releases (ex., `v24.10.01-runtime`, `v24.10.02-runtime` etc...), and the `YY.MM-runtime` tag will be updated to reference that point release.
 >
 > Users who want to ensure they are running with the latest bug fixes should use a release image tag (`YY.MM-runtime`). Users who need to deploy a specific version into production should use a point release image tag (`vYY.MM.00-runtime`).
 

Original file line number	Diff line number	Diff line change
`@@ -53,7 +53,7 @@ More advanced users, or those who are interested in using the latest pre-release`
`53`	`53`
`54`	`54`	`> Note about Morpheus versions:`
`55`	`55`	`>`
`56`		-> Morpheus uses Calendar Versioning ([CalVer](https://calver.org/)). For each Morpheus release there will be an image tagged in the form of `YY.MM-runtime`. This tag will always refer to the latest point release for that version. In addition, there will also be at least one point release version tagged in the form of `vYY.MM.00-runtime`. This will be the initial point release for that version (e.g., `v24.10.00-runtime`). In the event of a major bug, we may release additional point releases (e.g., `v24.10.01-runtime`, `v24.10.02-runtime` etc...), and the `YY.MM-runtime` tag will be updated to reference that point release.
	`56`	+> Morpheus uses Calendar Versioning ([CalVer](https://calver.org/)). For each Morpheus release there will be an image tagged in the form of `YY.MM-runtime`. This tag will always refer to the latest point release for that version. In addition, there will also be at least one point release version tagged in the form of `vYY.MM.00-runtime`. This will be the initial point release for that version (ex., `v24.10.00-runtime`). In the event of a major bug, we may release additional point releases (ex., `v24.10.01-runtime`, `v24.10.02-runtime` etc...), and the `YY.MM-runtime` tag will be updated to reference that point release.
`57`	`57`	`>`
`58`	`58`	> Users who want to ensure they are running with the latest bug fixes should use a release image tag (`YY.MM-runtime`). Users who need to deploy a specific version into production should use a point release image tag (`vYY.MM.00-runtime`).
`59`	`59`