reword

JnHs · JnHs · commit 676771285a4b · 2024-06-26T09:16:10.000-07:00
diff --git a/articles/azure-arc/kubernetes/extensions-release.md b/articles/azure-arc/kubernetes/extensions-release.md
@@ -127,7 +127,7 @@ The most recent version of the Flux v2 extension and the two previous versions (
 >
 > The [HelmChart](https://fluxcd.io/flux/components/source/helmcharts/) kind will be promoted from `v1beta2` to `v1` (GA). The `v1` API is backwards compatible with `v1beta2`, with the exception of the `.spec.valuesFile` field, which will be replaced by `.spec.valuesFiles`.
 >
-> We recommend updating your deployments before July 22, 2024, to stop using the fields that will be removed, and migrate to the new fields. This will help avoid problems due to breaking changes when the new version is released. The new fields are already available in the current version of the APIs.
+> To avoid issues due to breaking changes, we recommend updating your deployments by July 22, 2024, so that they stop using the fields that will be removed and use the replacement fields instead. These new fields are already available in the current version of the APIs.
 
 > [!NOTE]
 > When a new version of the `microsoft.flux` extension is released, it may take several days for the new version to become available in all regions.

Original file line number	Diff line number	Diff line change
`@@ -127,7 +127,7 @@ The most recent version of the Flux v2 extension and the two previous versions (`
`127`	`127`	`>`
`128`	`128`	> The [HelmChart](https://fluxcd.io/flux/components/source/helmcharts/) kind will be promoted from `v1beta2` to `v1` (GA). The `v1` API is backwards compatible with `v1beta2`, with the exception of the `.spec.valuesFile` field, which will be replaced by `.spec.valuesFiles`.
`129`	`129`	`>`
`130`		`-> We recommend updating your deployments before July 22, 2024, to stop using the fields that will be removed, and migrate to the new fields. This will help avoid problems due to breaking changes when the new version is released. The new fields are already available in the current version of the APIs.`
	`130`	`+> To avoid issues due to breaking changes, we recommend updating your deployments by July 22, 2024, so that they stop using the fields that will be removed and use the replacement fields instead. These new fields are already available in the current version of the APIs.`
`131`	`131`
`132`	`132`	`> [!NOTE]`
`133`	`133`	> When a new version of the `microsoft.flux` extension is released, it may take several days for the new version to become available in all regions.