Removing mention of pinned templates

kof-f · web-flow · commit 994f1afef717 · 2024-05-10T15:42:18.000-04:00
diff --git a/articles/virtual-machines/image-builder-api-update-release-notes.md b/articles/virtual-machines/image-builder-api-update-release-notes.md
@@ -71,7 +71,7 @@ In the [Azure VM Image Builder networking options](./linux/image-builder-network
 >
 > Pinning to an older Azure Image Builder API version can provide compatibility with your existing templates, but it's not recommended due to the following factors:
 >
-> - Deprecation Risk: Older API versions may eventually be deprecated. When this happens, your pinned templates could become unsupported, leading to potential issues.
+> - Deprecation Risk: Older API versions may eventually be deprecated.
 >
 > - Missing Features: By pinning to an older API version, you miss out on the latest features and improvements introduced in newer versions. These enhancements often improve performance, security, and functionality.
 

Original file line number	Diff line number	Diff line change
`@@ -71,7 +71,7 @@ In the [Azure VM Image Builder networking options](./linux/image-builder-network`
`71`	`71`	`>`
`72`	`72`	`> Pinning to an older Azure Image Builder API version can provide compatibility with your existing templates, but it's not recommended due to the following factors:`
`73`	`73`	`>`
`74`		`-> - Deprecation Risk: Older API versions may eventually be deprecated. When this happens, your pinned templates could become unsupported, leading to potential issues.`
	`74`	`+> - Deprecation Risk: Older API versions may eventually be deprecated.`
`75`	`75`	`>`
`76`	`76`	`> - Missing Features: By pinning to an older API version, you miss out on the latest features and improvements introduced in newer versions. These enhancements often improve performance, security, and functionality.`
`77`	`77`