Merge pull request #224560 from baanders/1-20-edits

ADT: Small edits

Author: JamesJBarnett

articles/digital-twins/media/quickstart-azure-digital-twins-explorer/delete-instance.png

@@ -36,6 +36,7 @@ To manage the throttling, here are some recommendations for working with limits.
 * Use retry logic. The [Azure Digital Twins SDKs](concepts-apis-sdks.md) implement retry logic for failed requests, so if you're working with a provided SDK, this functionality is already built-in. Otherwise, consider implementing retry logic in your own application. The service sends back a `Retry-After` header in the failure response, which you can use to determine how long to wait before retrying.
 * Use thresholds and notifications to warn about approaching limits. Some of the service limits for Azure Digital Twins have corresponding [metrics](../azure-monitor/essentials/data-platform-metrics.md) that can be used to track usage in these areas. To configure thresholds and set up an alert on any metric when a threshold is approached, see the instructions in [Create a new alert rule](../azure-monitor/alerts/alerts-create-new-alert-rule.md?tabs=metric). To set up notifications for other limits where metrics aren't provided, consider implementing this logic in your own application code.
 * Deploy at scale across multiple instances. Avoid having a single point of failure. Instead of one large graph for your entire deployment, consider sectioning out subsets of twins logically (like by region or tenant) across multiple instances. 
+* For modeling recommendations to help you operate within the functional limits, see [Modeling tools and best practices](concepts-models.md#modeling-tools-and-best-practices).
 
 >[!NOTE]
 >Azure Digital Twins will automatically scale resources to meet the rate limits described in this article. You may experience throttling before these limits are reached due to internal scaling to adapt to the incoming load. Internal scaling can take anywhere from 5 to 30 minutes, during which time your application may encounter 429 errors.

articles/digital-twins/reference-service-limits.md

@@ -11,9 +11,6 @@ ms.author: baanders
 
 The following table lists the functional limits of Azure Digital Twins. 
 
-> [!TIP]
-> For modeling recommendations to operate within these functional limits, see [Modeling tools and best practices](../articles/digital-twins/concepts-models.md#modeling-tools-and-best-practices).
-
 | Area | Capability | Default limit | Adjustable? |
 | --- | --- | --- | --- |
 | Azure resource | Number of Azure Digital Twins instances in a region, per subscription | 10 | Yes |