Merge pull request #32961 from sup95/patch-1

Fix typo

Author: American-Dipper

articles/cosmos-db/how-to-model-partition-example.md

@@ -474,7 +474,7 @@ So to optimize this last request, we introduce a third container to our design,
 
 This container is partitioned by `type`, which will always be `post` in our items. Doing that ensures that all the items in this container will sit in the same partition.
 
-To achieve the denormalization, we just have to hook on the change feed pipeline we have previously introduced to dispatch the posts to that new container. One important thing to bare in mind is that we need to make sure that we only store the 100 most recent posts; otherwise, the content of the container may grow beyond the maximum size of a partition. This is done by calling a [post-trigger](stored-procedures-triggers-udfs.md#triggers) every time a document is added in the container:
+To achieve the denormalization, we just have to hook on the change feed pipeline we have previously introduced to dispatch the posts to that new container. One important thing to bear in mind is that we need to make sure that we only store the 100 most recent posts; otherwise, the content of the container may grow beyond the maximum size of a partition. This is done by calling a [post-trigger](stored-procedures-triggers-udfs.md#triggers) every time a document is added in the container:
 
 ![Denormalizing posts into the feed container](./media/how-to-model-partition-example/denormalization-3.png)
 
@@ -570,4 +570,4 @@ After this introduction to practical data modeling and partitioning, you may wan
 
 - [Work with databases, containers, and items](databases-containers-items.md)
 - [Partitioning in Azure Cosmos DB](partitioning-overview.md)
-- [Change feed in Azure Cosmos DB](change-feed.md)
+- [Change feed in Azure Cosmos DB](change-feed.md)