Merge pull request #294532 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/governance/resource-graph/changes/get-resource-changes.md

@@ -64,6 +64,8 @@ When a resource is created, updated, or deleted, a new change resource (`Microso
 ```
 
 [See the full reference guide for change resource properties.](/rest/api/resources/changes)
+> [!NOTE]
+> Snapshots are not currently supported for deleted resources.
 
 ## Run a query
 

articles/iot-edge/how-to-connect-downstream-device.md

@@ -86,7 +86,7 @@ You can use a service like [Azure Key Vault](/azure/key-vault/) or a function li
 
 Once the root CA certificate is on the downstream device, make sure the applications that are connecting to the gateway can access the certificate.
 
-Installing the root CA certificate in the operating system's certificate store generally allows most applications to use the root CA certificate. There are some exceptions, like NodeJS applications that don't use the OS certificate store but rather use the Node runtime's internal certificate store. If you can't install the certificate at the operating system level, skip ahead to [Use certificates with Azure IoT SDKs](#use-certificates-with-azure-iot-sdks).
+Installing the root CA certificate in the operating system's certificate store generally allows most applications to use the root CA certificate. There are some exceptions, like Node.js applications that don't use the OS certificate store but rather use the Node runtime's internal certificate store. If you can't install the certificate at the operating system level, skip ahead to [Use certificates with Azure IoT SDKs](#use-certificates-with-azure-iot-sdks).
 
 Install the root CA certificate on either Ubuntu or Windows.
 
@@ -144,7 +144,7 @@ Now you're ready to use certificates with a sample in the language of your choic
 
 # [NodeJS](#tab/nodejs)
 
-This section provides a sample application to connect an Azure IoT NodeJS device client to an IoT Edge gateway. For NodeJS applications, you must install the root CA certificate at the application level as shown here. NodeJS applications don't use the system's certificate store.
+This section provides a sample application to connect an Azure IoT Node.js device client to an IoT Edge gateway. For Node.js applications, you must install the root CA certificate at the application level as shown here. Node.js applications don't use the system's certificate store.
 
 1. Get the sample for **edge_downstream_device.js** from the [Azure IoT device SDK for Node.js samples repo](https://github.com/Azure/azure-iot-sdk-node/tree/main/device/samples).
 1. Make sure that you have all the prerequisites to run the sample by reviewing the **readme.md** file.

articles/reliability/reliability-defender-devops.md

@@ -59,7 +59,7 @@ To request recovery of a connector created in a downed region:
    resources
     | extend connectorType = tostring(parse_json(properties["environmentName"]))
     | where type == "microsoft.security/securityconnectors"
-    | where connectorType in ("AzureDevOps", "Github", "GitLab")
+    | where connectorType in ("AzureDevOps", "GitHub", "GitLab")
     | project connectorResourceId = id, region = location
 
 1. Once the DevOps resources have been released from the old connector and appear for the new connector, [reconfigure the pull request annotations](/azure/defender-for-cloud/enable-pull-request-annotations) as needed.

articles/spring-apps/basic-standard/concept-app-customer-responsibilities.md

@@ -57,7 +57,7 @@ When you deploy your polyglot applications to the Enterprise plan, assign specif
 | .NET   | [.NET and .NET core support policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) |
 | Python | [Status of Python versions](https://devguide.python.org/versions/)                                    |
 | Go     | [Go release history](https://go.dev/doc/devel/release)                                                |
-| NodeJS | [Nodejs releases](https://nodejs.org/en/about/previous-releases/)                                     |
+| Node.js | [Nodejs releases](https://nodejs.org/en/about/previous-releases/)                                     |
 | PHP    | [PHP supported versions](https://www.php.net/supported-versions.php)                                  |
 
 ### Stack image support

articles/spring-apps/enterprise/how-to-enterprise-configure-apm-integration-and-ca-certificates.md

@@ -45,7 +45,7 @@ Azure Spring Apps supports CA certificates for all language family buildpacks, b
 | .NET              |                     | ✔        |             | ✔         |            |
 | Go                |                     |           |             | ✔        |            |
 | Python            |                     |           |             |           |            |
-| NodeJS            |                     | ✔        | ✔           | ✔        | ✔          |
+| Node.js            |                     | ✔        | ✔           | ✔        | ✔          |
 | Web servers       |                     |           |             | ✔        |            |
 | Java Native Image |                     |           |             |           |            |
 | PHP               |                     | ✔         | ✔          | ✔         |            |

articles/spring-apps/enterprise/whats-new.md

@@ -33,7 +33,7 @@ The following updates are now available:
     - App Accelerator: upgraded to 1.8.1.
     - Build service:
       - Go buildpack: added support for Go 1.22, deprecated Go 1.20, changed default version from Go 1.20 to Go 1.21.
-      - NodeJS buildpack: changed default version from Node.js 19 to Node.js 20.
+      - Node.js buildpack: changed default version from Node.js 19 to Node.js 20.
       - Java Native Image buildpack: deprecated Java 20, added Java 21.
       - PHP buildpack: added PHP 8.3
   - Regular upgrade to keep Azure Kubernetes Service up-to-date: upgraded to 1.29.7.

articles/storage/common/storage-explorer-network.md

@@ -87,7 +87,7 @@ To set credentials, you must go to the Proxy Settings dialog (**Edit** > **Confi
 
 ### Use system proxy
 
-When this option is selected, Storage Explorer will use your OS proxy settings. More specifically, it will result in network calls being made using the Chromium networking stack. The Chromium networking stack is much more robust than the NodeJS networking stack normally used by Storage Explorer. Here's a snippet from [Chromium's documentation](https://www.chromium.org/developers/design-documents/network-settings) on what all it can do:
+When this option is selected, Storage Explorer will use your OS proxy settings. More specifically, it will result in network calls being made using the Chromium networking stack. The Chromium networking stack is much more robust than the Node.js networking stack normally used by Storage Explorer. Here's a snippet from [Chromium's documentation](https://www.chromium.org/developers/design-documents/network-settings) on what all it can do:
 
 > The Chromium network stack uses the system network settings so that users and administrators can control the network settings of all applications easily. The network settings include:
 > - proxy settings
@@ -127,7 +127,7 @@ Currently, AzCopy only supports proxy servers that use **basic authentication**.
 
 ## SSL certificates
 
-By default, Storage Explorer uses the NodeJS networking stack. NodeJS ships with a predefined list of trusted SSL certificates. Some networking technologies, such as proxy servers or anti-virus software, inject their own SSL certificates into network traffic. These certificates are often not present in NodeJS' certificate list. NodeJS won't trust responses that contain such a certificate. When NodeJS doesn't trust a response, then Storage Explorer will receive an error.
+By default, Storage Explorer uses the Node.js networking stack. Node.js ships with a predefined list of trusted SSL certificates. Some networking technologies, such as proxy servers or anti-virus software, inject their own SSL certificates into network traffic. These certificates are often not present in NodeJS' certificate list. Node.js won't trust responses that contain such a certificate. When Node.js doesn't trust a response, then Storage Explorer will receive an error.
 
 You have multiple options for resolving such errors:
 - Use [**system proxy**](#use-system-proxy) as your proxy source.