Merge pull request #228728 from seesharprun/cosmos-rename-how-to-model-partition-example

Cosmos DB | Rename `how-to-model-partition-example.md` to `model-partition-example.md`

Author: JamesJBarnett

articles/cosmos-db/.openpublishing.redirection.cosmos-db.json

@@ -65,6 +65,11 @@
       "redirect_url": "/azure/cosmos-db/nosql/samples-java",
       "redirect_document_id": true
     }, 
+    {
+      "source_path_from_root": "/articles/cosmos-db/nosql/how-to-model-partition-example.md",
+      "redirect_url": "/azure/cosmos-db/nosql/model-partition-example",
+      "redirect_document_id": true
+    }, 
     {
       "source_path_from_root": "/articles/cosmos-db/nosql/sql-api-nodejs-samples.md",
       "redirect_url": "/azure/cosmos-db/nosql/samples-nodejs",

articles/cosmos-db/concepts-limits.md

@@ -173,7 +173,7 @@ An Azure Cosmos DB item can represent either a document in a collection, a row i
 
 ¹ Large document sizes up to 16 MB are supported with Azure Cosmos DB for MongoDB only. Read the [feature documentation](../cosmos-db/mongodb/feature-support-42.md#data-types) to learn more.
 
-There are no restrictions on the item payloads (like number of properties and nesting depth), except for the length restrictions on partition key and ID values, and the overall size restriction of 2 MB. You may have to configure indexing policy for containers with large or complex item structures to reduce RU consumption. See [Modeling items in Azure Cosmos DB](how-to-model-partition-example.md) for a real-world example, and patterns to manage large items.
+There are no restrictions on the item payloads (like number of properties and nesting depth), except for the length restrictions on partition key and ID values, and the overall size restriction of 2 MB. You may have to configure indexing policy for containers with large or complex item structures to reduce RU consumption. See [Modeling items in Azure Cosmos DB](nosql/model-partition-example.md) for a real-world example, and patterns to manage large items.
 
 ## Per-request limits
 

articles/cosmos-db/index.yml

@@ -57,7 +57,7 @@ additionalContent:
         - title: Model your data
           links:
           - text: Data modeling and partitioning
-            url: how-to-model-partition-example.md
+            url: nosql/model-partition-example.md
           - text: Azure Cosmos DB service quotas
             url: concepts-limits.md
         - title: Analytics with Azure Synapse Link

articles/cosmos-db/mongodb/pre-migration-steps.md

@@ -166,7 +166,7 @@ The following Azure Cosmos DB configuration choices can't be modified or undone
   * In a similar way, the partitioning capability automatically adds capacity and rebalances the data accordingly. For more information on choosing the right partition key for your data, see [choosing a partition key](../partitioning-overview.md#choose-partitionkey).
 * Follow the guide for [Data modeling in Azure Cosmos DB](../modeling-data.md) to choose a data model.
 * Follow [Optimize provisioned throughput cost in Azure Cosmos DB](../optimize-cost-throughput.md#optimize-by-provisioning-throughput-at-different-levels) to choose between dedicated and shared throughput for each resource that you migrate
-* [How to model and partition data on Azure Cosmos DB using a real-world example](../how-to-model-partition-example.md) is a real-world example of sharding and data modeling to aid you in your decision-making process
+* [How to model and partition data on Azure Cosmos DB using a real-world example](../nosql/model-partition-example.md) is a real-world example of sharding and data modeling to aid you in your decision-making process
 
 ### Cost of ownership
 

articles/cosmos-db/nosql/TOC.yml

@@ -152,7 +152,7 @@
           href: modeling-data.md
         - name: Modeling and partitioning - a real-world example
           displayName: model, partition, example
-          href: how-to-model-partition-example.md
+          href: model-partition-example.md
         - name: Synthetic partition key
           href: synthetic-partition-keys.md
     - name: Partitioning and horizontal scaling

articles/cosmos-db/nosql/change-feed-design-patterns.md

@@ -70,7 +70,7 @@ For example, the change feed helps you perform the following tasks efficiently:
 
 * Implement an application-level data tiering and archival. For example, you can store "hot data" in Azure Cosmos DB and age out "cold data" to other storage systems such as [Azure Blob Storage](../../storage/common/storage-introduction.md).
 
-When you have to [denormalize data across partitions and containers](how-to-model-partition-example.md#v2-introducing-denormalization-to-optimize-read-queries
+When you have to [denormalize data across partitions and containers](model-partition-example.md#v2-introducing-denormalization-to-optimize-read-queries
 ), you can read from your container's change feed as a source for this data replication. Real-time data replication with the change feed can only guarantee eventual consistency. You can [monitor how far the Change Feed Processor lags behind](how-to-use-change-feed-estimator.md) in processing changes in your Azure Cosmos DB container.
 
 ## Event sourcing