Merge pull request #36929 from v-thepet/links3-20

BULK Fix broken links

Author: prmerger-automator[bot]

azure-sql/database/disaster-recovery-guidance.md

@@ -127,7 +127,7 @@ Create the logins that must be present in the `master` database on the new prima
 
 ### Setup telemetry alerts
 
-You need to make sure your existing alert rule settings are updated to map to the new primary database and the different server. For more information about database alert rules, see [Receive Alert Notifications](/azure/azure-monitor/alerts/alerts-overview) and [Track Service Health](/azure/service-health/service-notifications).
+You need to make sure your existing alert rule settings are updated to map to the new primary database and the different server. For more information about database alert rules, see [Receive Alert Notifications](/azure/azure-monitor/alerts/alerts-overview) and [Service Health notifications](/azure/service-health/service-health-notifications-properties).
 
 ### Enable auditing
 

docs/tools/visual-studio-code-extensions/mssql/mssql-data-api-builder.md

@@ -200,7 +200,7 @@ For more information on REST endpoints, see [Data API builder REST API](/azure/d
 
 ### GraphQL
 
-Select **Nitro** to open the [Nitro](https://github.com/nicedoc/nitro) GraphQL playground, where you can write and test GraphQL queries and mutations interactively.
+Select **Nitro** to open the [Nitro](https://chillicream.com/docs/nitro) GraphQL playground, where you can write and test GraphQL queries and mutations interactively.
 
 For more information on GraphQL endpoints, see [Data API builder GraphQL API](/azure/data-api-builder/concept/api/graphql).