Fix typo: programatically -> programmatically

changeworld · changeworld · commit 5e85a69a6b87 · 2025-05-27T11:24:33.000+09:00
diff --git a/articles/azure-cache-for-redis/cache-how-to-scale.md b/articles/azure-cache-for-redis/cache-how-to-scale.md
@@ -137,7 +137,7 @@ az redis update --cluster-name myCache --resource-group myGroup --set "sku.name"
 For more information on scaling with Azure CLI, see [Change settings of an existing Azure Cache for Redis](cache-manage-cli.md#scale).
 
 > [!NOTE]
-> When you scale a cache up or down programatically (e.g. using PowerShell or Azure CLI), any `maxmemory-reserved` or `maxfragmentationmemory-reserved` are ignored as part of the update request. Only your scaling change is honored. You can update these memory settings after the scaling operation has completed.
+> When you scale a cache up or down programmatically (e.g. using PowerShell or Azure CLI), any `maxmemory-reserved` or `maxfragmentationmemory-reserved` are ignored as part of the update request. Only your scaling change is honored. You can update these memory settings after the scaling operation has completed.
 >
 
 ### [Scale out and in - Premium only](#tab/scale-out-and-in---premium-only)

Original file line number	Diff line number	Diff line change
`@@ -137,7 +137,7 @@ az redis update --cluster-name myCache --resource-group myGroup --set "sku.name"`
`137`	`137`	`For more information on scaling with Azure CLI, see [Change settings of an existing Azure Cache for Redis](cache-manage-cli.md#scale).`
`138`	`138`
`139`	`139`	`> [!NOTE]`
`140`		-> When you scale a cache up or down programatically (e.g. using PowerShell or Azure CLI), any `maxmemory-reserved` or `maxfragmentationmemory-reserved` are ignored as part of the update request. Only your scaling change is honored. You can update these memory settings after the scaling operation has completed.
	`140`	+> When you scale a cache up or down programmatically (e.g. using PowerShell or Azure CLI), any `maxmemory-reserved` or `maxfragmentationmemory-reserved` are ignored as part of the update request. Only your scaling change is honored. You can update these memory settings after the scaling operation has completed.
`141`	`141`	`>`
`142`	`142`
`143`	`143`	`### [Scale out and in - Premium only](#tab/scale-out-and-in---premium-only)`