More typos.

builder/azure/arm/config.go

@@ -384,7 +384,7 @@ type Config struct {
 	// Same as [`azure_tags`](#azure_tags) but defined as a singular repeatable block
 	// containing a `name` and a `value` field. In HCL2 mode the
 	// [`dynamic_block`](/packer/docs/templates/hcl_templates/expressions#dynamic-blocks)
-	// will allow you to create those programatically.
+	// will allow you to create those programmatically.
 	AzureTag config.NameValues `mapstructure:"azure_tag" required:"false"`
 	// Resource group under which the final artifact will be stored.
 	ResourceGroupName string `mapstructure:"resource_group_name"`

builder/azure/common/client/config.go

@@ -33,7 +33,7 @@ var NullModelSDKErr = fmt.Errorf("Unexpected SDK response, please open an issue
 // one of the following: `client_secret`, `client_jwt`, `client_cert_path` --
 // Packer will use the specified Azure Active Directory (AAD) Service Principal
 // (SP).
-// If none ofthese options are specified, Packer will attempt to use the Managed Identity
+// If none of these options are specified, Packer will attempt to use the Managed Identity
 // and subscription of the VM that Packer is running on.  This will only work if
 // Packer is running on an Azure VM with either a System Assigned Managed
 // Identity or User Assigned Managed Identity.

docs-partials/builder/azure/common/client/Config.mdx

@@ -5,7 +5,7 @@ Config allows for various ways to authenticate Azure clients.  When
 one of the following: `client_secret`, `client_jwt`, `client_cert_path` --
 Packer will use the specified Azure Active Directory (AAD) Service Principal
 (SP).
-If none ofthese options are specified, Packer will attempt to use the Managed Identity
+If none of these options are specified, Packer will attempt to use the Managed Identity
 and subscription of the VM that Packer is running on.  This will only work if
 Packer is running on an Azure VM with either a System Assigned Managed
 Identity or User Assigned Managed Identity.