fix according to vale

docs/src/main/asciidoc/auto-configure-azure-sdk-clients.adoc

@@ -33,7 +33,7 @@ There are two ways to use Spring Cloud Azure starters. One is using Azure SDKs w
 </dependency>
 ----
 
-Or including the Spring Cloud Azure Starter directly without adding Azure SDK dependencies. For example with Cosmos DB:
+Or including the Spring Cloud Azure starter directly without adding Azure SDK dependencies. For example with Cosmos DB:
 
 [source,xml]
 ----

docs/src/main/asciidoc/resource-handling.adoc

@@ -140,7 +140,7 @@ Resource storageFileResource = resourceLoader.getResource("azure-file://[your-fi
 ----
 
 ===== Get resources by searching pattern
-You can use implementation class of `ResourcePatternResolver` to search resources. Using `AzureStorageBlobProtocolResolver` to search `blob` resources, and `AzureStorageFileProtocolResolver` to search `file` resources.
+You can use implementation class of `ResourcePatternResolver` to search resources. Use `AzureStorageBlobProtocolResolver` to search `blob` resources, and `AzureStorageFileProtocolResolver` to search `file` resources.
 
 - Pattern search, the **searchPattern** should start with `azure-blob://` or `azure-file://`. Such as `azure-blob://+++**+++/+++**+++`, it means list all blobs in all containers; `azure-blob://demo-container/**`, it means list all blobs in the demo-container container, including any sub-folders.
 - Location search, the **searchLocation** should start with `azure-blob://` or `azure-file://`, the remaining file path should exist, otherwise an exception will be thrown.

docs/src/main/asciidoc/spring-cloud-stream-support.adoc

@@ -1022,7 +1022,7 @@ See the <<si-sb-headers, Service Bus message headers>> for the basic message hea
 NOTE: When setting the partiton key, the priority of message header is higher than Spring Cloud Stream property. So `spring.cloud.stream.bindings.<binding-name>.producer.partition-key-expression` will take effect only when none of the headers of `ServiceBusMessageHeaders#SESSION_ID`, `ServiceBusMessageHeaders#PARTITION_KEY`, `AzureHeaders#PARTITION_KEY` is configured.
 
 ===== Multi Binder Support
-Connection to mutiple Service Bus namespaces is also supported by using multi binders.This sample takes connection string as example. Credentials of service principals and managed identities are also supported, users can set related properties in each binder's environment settings.
+Connection to mutiple Service Bus namespaces is also supported by using multi binders. This sample takes connection string as example. Credentials of service principals and managed identities are also supported, users can set related properties in each binder's environment settings.
 
 Step 1. To use multiple binders of ServiceBus, we need to configure below properties in application.yml
 [source,yaml]

docs/src/main/asciidoc/spring-jms-support.adoc

@@ -122,7 +122,7 @@ spring:
       pricing-tier: ${PRICING_TIER}
 ----
 
-NOTE: The default enabled `ConnectionFactory` is the `CachingConnectionFactory` which adds Session caching as well MessageProducer caching. If you want to activate the connection pooling featured one of JmsPoolConnectionFactory, the property of `spring.jms.servicebus.pool.enabled` should be specified `true`. The other pooling configuration options(`spring.jms.servicebus.pool.` prefix) can be found in the above
+NOTE: The default enabled `ConnectionFactory` is the `CachingConnectionFactory` which adds Session caching as well MessageProducer caching. If you want to activate the connection pooling featured one of JmsPoolConnectionFactory, the property of `spring.jms.servicebus.pool.enabled` should be specified `true`. You can find other pooling configuration options (properties with prefix `spring.jms.servicebus.pool.`) from the above
 <<jms-servicebus-pool-configuration, Configuration>> section.
 
 === Samples