Standardize note formatting in docs (#29516)

Author: sreallymatt

website/docs/d/active_directory_domain_service.html.markdown

@@ -10,7 +10,7 @@ description: |-
 
 Gets information about an Active Directory Domain Service.
 
--> **Supported Modes:** At present this data source only supports **User Forest** mode and _not_ **Resource Forest** mode. [Read more](https://docs.microsoft.com/azure/active-directory-domain-services/concepts-resource-forest) about the different operation modes for this service.
+-> **Note:** At present this data source only supports **User Forest** mode and _not_ **Resource Forest** mode. [Read more](https://docs.microsoft.com/azure/active-directory-domain-services/concepts-resource-forest) about the different operation modes for this service.
 
 ## Example Usage
 

website/docs/d/automation_variables.html.markdown

@@ -61,7 +61,7 @@ A `variable` block exports the following attributes:
 
 - `value` - The value of the Automation Variable.
 
-~> **NOTE:** There is no `value` property returned for `encrypted` or `null` variable types.
+~> **Note:** There is no `value` property returned for `encrypted` or `null` variable types.
 
 ## Timeouts
 

website/docs/d/batch_pool.html.markdown

@@ -187,11 +187,11 @@ A `certificate` block exports the following:
 
 * `store_location` - The location of the certificate store on the compute node into which the certificate is installed, either `CurrentUser` or `LocalMachine`.
 
--> **NOTE:** This property is applicable only for pools configured with Windows nodes (that is, created with cloudServiceConfiguration, or with virtualMachineConfiguration using a Windows image reference). For Linux compute nodes, the certificates are stored in a directory inside the task working directory and an environment variable `AZ_BATCH_CERTIFICATES_DIR` is supplied to the task to query for this location. For certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., `/home/{user-name}/certs`) and certificates are placed in that directory.
+-> **Note:** This property is applicable only for pools configured with Windows nodes (that is, created with cloudServiceConfiguration, or with virtualMachineConfiguration using a Windows image reference). For Linux compute nodes, the certificates are stored in a directory inside the task working directory and an environment variable `AZ_BATCH_CERTIFICATES_DIR` is supplied to the task to query for this location. For certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., `/home/{user-name}/certs`) and certificates are placed in that directory.
 
 * `store_name` - The name of the certificate store on the compute node into which the certificate is installed.
 
--> **NOTE:** This property is applicable only for pools configured with Windows nodes (that is, created with cloudServiceConfiguration, or with virtualMachineConfiguration using a Windows image reference).
+-> **Note:** This property is applicable only for pools configured with Windows nodes (that is, created with cloudServiceConfiguration, or with virtualMachineConfiguration using a Windows image reference).
 
 * `visibility` - Which user accounts on the compute node have access to the private data of the certificate.
 

website/docs/d/blueprint_definition.html.markdown

@@ -10,7 +10,7 @@ description: |-
 
 Use this data source to access information about an existing Azure Blueprint Definition
 
-~> **NOTE:** Azure Blueprints are in Preview and potentially subject to breaking change without notice.
+~> **Note:** Azure Blueprints are in Preview and potentially subject to breaking change without notice.
 
 ## Example Usage
 

website/docs/d/blueprint_published_version.html.markdown

@@ -10,7 +10,7 @@ description: |-
 
 Use this data source to access information about an existing Blueprint Published Version
 
-~> **NOTE:** Azure Blueprints are in Preview and potentially subject to breaking change without notice.
+~> **Note:** Azure Blueprints are in Preview and potentially subject to breaking change without notice.
 
 ## Example Usage
 

website/docs/d/cognitive_account.html.markdown

@@ -53,7 +53,7 @@ The following attributes are exported:
 
 * `secondary_access_key` - The secondary access key of the Cognitive Services Account
 
--> **NOTE:** The `primary_access_key` and `secondary_access_key` properties are only available when `local_auth_enabled` is `true`.
+-> **Note:** The `primary_access_key` and `secondary_access_key` properties are only available when `local_auth_enabled` is `true`.
 
 * `tags` - A mapping of tags to assigned to the resource.
 

website/docs/d/container_app_environment.html.markdown

@@ -36,35 +36,35 @@ In addition to the Arguments listed above - the following Attributes are exporte
 
 * `infrastructure_subnet_id` - The ID of the Subnet in use by the Container Apps Control Plane.
 
-~> **NOTE:** This will only be populated for Environments that have `internal_load_balancer_enabled` set to true.
+~> **Note:** This will only be populated for Environments that have `internal_load_balancer_enabled` set to true.
 
 * `custom_domain_verification_id` - The ID of the Custom Domain Verification for this Container App Environment.
 
 * `default_domain` - The default publicly resolvable name of this Container App Environment. This is generated at creation time to be globally unique.
 
 * `docker_bridge_cidr` - The network addressing in which the Container Apps in this Container App Environment will reside in CIDR notation.
 
-~> **NOTE:** This will only be populated for Environments that have `internal_load_balancer_enabled` set to true.
+~> **Note:** This will only be populated for Environments that have `internal_load_balancer_enabled` set to true.
 
 * `internal_load_balancer_enabled` - Does the Container App Environment operate in Internal Load Balancing Mode?
 
 * `location` - The Azure Location where this Container App Environment exists.
 
 * `log_analytics_workspace_name` - The name of the Log Analytics Workspace this Container Apps Managed Environment is linked to.
 
-~> **NOTE:** This will only be populated for Environments that have `logs_destination` set to `log-analytics` and the Log Analytics Workspace is in the same subscription as the Environment.
+~> **Note:** This will only be populated for Environments that have `logs_destination` set to `log-analytics` and the Log Analytics Workspace is in the same subscription as the Environment.
 
 * `platform_reserved_cidr` - The IP range, in CIDR notation, that is reserved for environment infrastructure IP addresses.
 
-~> **NOTE:** This will only be populated for Environments that have `internal_load_balancer_enabled` set to true.
+~> **Note:** This will only be populated for Environments that have `internal_load_balancer_enabled` set to true.
 
 * `platform_reserved_dns_ip_address` - The IP address from the IP range defined by `platform_reserved_cidr` that is reserved for the internal DNS server.
 
-~> **NOTE:** This will only be populated for Environments that have `internal_load_balancer_enabled` set to true.
+~> **Note:** This will only be populated for Environments that have `internal_load_balancer_enabled` set to true.
 
 * `static_ip_address` - The Static IP address of the Environment.
 
-~> **NOTE:** If `internal_load_balancer_enabled` is true, this will be a Private IP in the subnet, otherwise this will be allocated a Public IPv4 address.
+~> **Note:** If `internal_load_balancer_enabled` is true, this will be a Private IP in the subnet, otherwise this will be allocated a Public IPv4 address.
 
 * `tags` - A mapping of tags assigned to the resource.
 

website/docs/d/cosmosdb_account.html.markdown

@@ -47,7 +47,7 @@ The following attributes are exported:
 
 * `key_vault_key_id` - The Key Vault key URI for CMK encryption.
 
-~> **NOTE:** The CosmosDB service always uses the latest version of the specified key.
+~> **Note:** The CosmosDB service always uses the latest version of the specified key.
 
 * `ip_range_filter` - The current IP Filter for this CosmosDB account
 

website/docs/d/disk_encryption_set.html.markdown

@@ -45,7 +45,7 @@ The following attributes are exported:
 
 * `managed_hsm_key_id` - Key ID of a key in a managed HSM.
 
-~> Note: Only one of `key_vault_key_url` and `managed_hsm_key_id` will be set, depending on where the encryption key is stored.
+~> **Note:** Only one of `key_vault_key_url` and `managed_hsm_key_id` will be set, depending on where the encryption key is stored.
 
 * `identity` - An `identity` block as defined below.
 

website/docs/d/function_app.html.markdown

@@ -56,7 +56,7 @@ The following attributes are exported:
 
 * `os_type` - A string indicating the Operating System type for this function app.
 
-~> **NOTE:** This value will be `linux` for Linux Derivatives, or an empty string for Windows.
+~> **Note:** This value will be `linux` for Linux Derivatives, or an empty string for Windows.
 
 * `outbound_ip_addresses` - A comma separated list of outbound IP addresses.