Merge pull request #102669 from catslovedata/patch-2

Fixed some typos and applied minor formatting changes

Author: jborsecnik

articles/cosmos-db/attachments.md

@@ -18,29 +18,29 @@ Azure Cosmos DB attachments are special items that contain references to an asso
 
 Azure Cosmos DB supports two types of attachments:
 
-* **Unmanaged Attachments** are a wrapper around an URI reference to a blob that is stored in an external service (for example, Azure Storage, OneDrive, etc.). This approach is similar to storing a URI property in a standard Azure Cosmos DB item.
+* **Unmanaged Attachments** are a wrapper around a URI reference to a blob that is stored in an external service (for example, Azure Storage, OneDrive, etc.). This approach is similar to storing a URI property in a standard Azure Cosmos DB item.
 * **Managed Attachments** are blobs managed and stored internally by Azure Cosmos DB and exposed via a system-generated mediaLink.
 
 
 > [!NOTE]
-> Attachment is a legacy feature. Their support is scoped to offer continued functionality if you are already using this feature.
+> Attachments are a legacy feature. Their support is scoped to offer continued functionality if you are already using this feature.
 > 
-> Instead of using attachments, we recommend you to use Azure Blob Storage as a purpose-built blob storage service to store blob data . You can continue to store metadata related to blobs, along with reference URI links, in Azure Cosmos DB as item properties. Storing this data in Azure Cosmos DB provides the ability to query metadata and links to blobs stored in Azure Blob Storage.
+> Instead of using attachments, we recommend you to use Azure Blob Storage as a purpose-built blob storage service to store blob data. You can continue to store metadata related to blobs, along with reference URI links, in Azure Cosmos DB as item properties. Storing this data in Azure Cosmos DB provides the ability to query metadata and links to blobs stored in Azure Blob Storage.
 > 
 > Microsoft is committed to provide a minimum 36-month notice prior to fully deprecating attachments – which will be announced at a further date.
 
 ## Known limitations
 
 Azure Cosmos DB’s managed attachments are distinct from its support for standard items – for which it offers unlimited scalability, global distribution, and integration with other Azure services.
 
-- Attachments aren't supported in all versions of the Azure Cosmos DB’s SDKs.
+- Attachments aren't supported in all versions of the Azure Cosmos DB SDKs.
 - Managed attachments are limited to 2 GB of storage per database account.
 - Managed attachments aren't compatible with Azure Cosmos DB’s global distribution, and they aren't replicated across regions.
 
 > [!NOTE]
-> Azure Cosmso DB for MongoDB version 3.2 utilizes managed attachments for GridFS and are subject to the same limitations.
+> Azure Cosmos DB for MongoDB version 3.2 utilizes managed attachments for GridFS and these are subject to the same limitations.
 >
-> We recommend developers using the MongoDB GridFS feature set to upgrade to Azure Cosmso DB for MongoDB version 3.6 or higher, which is decoupled from attachments and provides a better experience. Alternatively, developers using the MongoDB GridFS feature set should also consider using Azure Blob Storage - which is purpose-built for storing blob content and offers expanded functionality at lower cost compared to GridFS.
+> We recommend developers using the MongoDB GridFS feature set to upgrade to Azure Cosmos DB for MongoDB version 3.6 or higher, which is decoupled from attachments and provides a better experience. Alternatively, developers using the MongoDB GridFS feature set should also consider using Azure Blob Storage - which is purpose-built for storing blob content and offers expanded functionality at lower cost compared to GridFS.
 
 ## Migrating Attachments to Azure Blob Storage
 
@@ -51,7 +51,7 @@ We recommend migrating Azure Cosmos DB attachments to Azure Blob Storage by foll
 3. If applicable, add URI references to the blobs contained in Azure Blob Storage as string properties within your Azure Cosmos DB dataset.
 4. Refactor your application code to read and write blobs from the new Azure Blob Storage container.
 
-The following dotnet code sample shows how to copy attachments from Azure Cosmos DB to Azure Blob storage as part of a migration flow by using Azure Cosmos DB's .NET SDK v2 and Azure Blob Storage .NET SDK v12. Make sure to replace the `<placeholder values>` for the source Azure Cosmos DB account and target Azure Blob storage container.
+The following code sample shows how to copy attachments from Azure Cosmos DB to Azure Blob storage as part of a migration flow by using Azure Cosmos DB's .NET SDK v2 and Azure Blob Storage .NET SDK v12. Make sure to replace the `<placeholder values>` for the source Azure Cosmos DB account and target Azure Blob storage container.
 
 ```csharp
 
@@ -163,6 +163,6 @@ namespace attachments
 ## Next steps
 
 - Get started with [Azure Blob storage](../storage/blobs/storage-quickstart-blobs-dotnet.md)
-- Get references for using attachments via [Azure Cosmos DB’s .NET SDK v2](/dotnet/api/microsoft.azure.documents.attachment)
-- Get references for using attachments via [Azure Cosmos DB’s Java SDK v2](/java/api/com.microsoft.azure.documentdb.attachment)
-- Get references for using attachments via [Azure Cosmos DB’s REST API](/rest/api/cosmos-db/attachments)
+- Get references for using attachments via [Azure Cosmos DB's .NET SDK v2](/dotnet/api/microsoft.azure.documents.attachment)
+- Get references for using attachments via [Azure Cosmos DB's Java SDK v2](/java/api/com.microsoft.azure.documentdb.attachment)
+- Get references for using attachments via [Azure Cosmos DB's REST API](/rest/api/cosmos-db/attachments)