Normalize triple-backtick language identifiers (#3477)

* ```Shell

* main pass

* reverting PowerShell

* revert bash

* missing lang

* shell to console

* to console or bash

* not code

Author: mikehoffms

CONTRIBUTING.md

@@ -38,7 +38,7 @@ To make substantial changes to an existing article, add or change images, or con
 
 2. Click the green **Clone or download** button, copy to your clipboard, then run the following code at your command prompt:
 
-   ```Shell
+   ```console
    git clone {paste_your_repo_clone_link}
    ```
 

microsoft-edge/devtools/console/console-javascript.md

@@ -105,25 +105,25 @@ For example, on Windows:
 
 Edge Stable:
 
-```shell
+```console
 "C:\Users\localAccount\AppData\Local\Microsoft\Edge\Application\msedge.exe" --unsafely-disable-devtools-self-xss-warnings
 ```
 
 Edge Beta:
 
-```shell
+```console
 "C:\Users\localAccount\AppData\Local\Microsoft\Edge Beta\Application\msedge.exe" --unsafely-disable-devtools-self-xss-warnings
 ```
 
 Edge Dev:
 
-```shell
+```console
 "C:\Users\localAccount\AppData\Local\Microsoft\Edge Dev\Application\msedge.exe" --unsafely-disable-devtools-self-xss-warnings
 ```
 
 Edge Canary:
 
-```shell
+```console
 "C:\Users\localAccount\AppData\Local\Microsoft\Edge SxS\Application\msedge.exe" --unsafely-disable-devtools-self-xss-warnings
 ```
 

microsoft-edge/devtools/device-mode/testing-other-browsers.md

@@ -83,7 +83,7 @@ To use the Android emulator:
 
 To install the Chromium Content Shell for Android, keep your emulator running and run the following command:
 
-```shell
+```console
 git clone https://github.com/PaulKinlan/chromium-android-installer.git
 chmod u+x ./chromium-android-installer/*.sh
 ./chromium-android-installer/install-chromeandroid.sh
@@ -101,7 +101,7 @@ Similar to the Chromium Content Shell, you can get an APK to install Firefox ont
 
 To install the file onto an open emulator or connected Android device, run the following command:
 
-```shell
+```console
 adb install <path_to_APK>/fennec-XX.X.XX.android-arm.apk
 ```
 

microsoft-edge/devtools/dom/index.md

@@ -387,6 +387,7 @@ When you use a web browser to request a page, the server returns HTML code like
 
 The browser then parses the HTML and creates a tree of objects based on the HTML like this:
 
+<!-- DOM not at https://learn.microsoft.com/contribute/content/code-in-docs#fenced-code-blocks, renders OK -->
 ```DOM
 html
     head

microsoft-edge/devtools/ie-mode/index.md

@@ -57,7 +57,7 @@ To debug the content of an IE mode tab, use IEChooser to open Internet Explorer
 
 Launch Microsoft Edge with remote debugging turned on from the command-line interface.  Microsoft Visual Studio, Microsoft Visual Studio Code, and other development tools typically run a command to launch Microsoft Edge.  The following command launches Microsoft Edge with the remote debugging port set to `9222`.
 
-```shell
+```console
 start msedge --remote-debugging-port=9222
 ```
 

microsoft-edge/devtools/javascript/publish-source-maps-to-azure.md

@@ -73,7 +73,7 @@ At the final step of your application's build process, for every source map you
 
 Build systems vary from application to application, so there isn't a clear single way to apply this. But here is a sample [Webpack 5 plugin](https://webpack.js.org/), which can be added to your Webpack configuration if you're using it:
 
-```js
+```javascript
 // file: webpack.plugin-symbols.js
 // Copyright (C) Microsoft Corporation. All rights reserved.
 // Licensed under the BSD 3-clause license.
@@ -130,7 +130,7 @@ module.exports = class PrepareSourceMapsForSymbolServerPlugin {
 
 You can then add the plugin to the `plugins` section in your `webpack.config.js` configuration file:
 
-```js
+```javascript
 const PrepareSourceMapsForSymbolServerPlugin = require('./webpack.plugin-symbols.js');
 
 // ...
@@ -181,7 +181,7 @@ When configuring this task, set the `indexableFileFormats` parameter to either `
 
 The Symbol Server team publishes a .NET Core application, `symbol.exe`, which can be downloaded automatically.  To programmatically download `symbol.exe`, use the `GET` method of the `Client` endpoint in the Symbol Service REST API, as described in [Client - Get](/rest/api/azure/devops/symbol/client/get).  Then run the following command to publish your source maps to the Azure Artifacts symbol server:
 
-```cmd
+```console
 symbol publish
         -d {root directory containing your source maps}
         -n {a unique name for this job}

microsoft-edge/devtools/javascript/snippets.md

@@ -172,25 +172,25 @@ For example, on Windows:
 
 Edge Stable:
 
-```shell
+```console
 "C:\Users\localAccount\AppData\Local\Microsoft\Edge\Application\msedge.exe" --unsafely-disable-devtools-self-xss-warnings
 ```
 
 Edge Beta:
 
-```shell
+```console
 "C:\Users\localAccount\AppData\Local\Microsoft\Edge Beta\Application\msedge.exe" --unsafely-disable-devtools-self-xss-warnings
 ```
 
 Edge Dev:
 
-```shell
+```console
 "C:\Users\localAccount\AppData\Local\Microsoft\Edge Dev\Application\msedge.exe" --unsafely-disable-devtools-self-xss-warnings
 ```
 
 Edge Canary:
 
-```shell
+```console
 "C:\Users\localAccount\AppData\Local\Microsoft\Edge SxS\Application\msedge.exe" --unsafely-disable-devtools-self-xss-warnings
 ```
 

microsoft-edge/devtools/protocol/index.md

@@ -21,13 +21,13 @@ To attach a custom tooling client to the DevTools Server in Microsoft Edge:
 
 1.  Launch Microsoft Edge with the remote debugging port.
 
-    ```shell
+    ```console
     msedge.exe --remote-debugging-port=9222
     ```
 
 1.  Optionally, you can start a separate instance of Microsoft Edge using a distinct user profile.
 
-    ```shell
+    ```console
     msedge.exe --user-data-dir=<some directory>
     ```
 

microsoft-edge/devtools/quick-source/quick-source-tool.md

@@ -80,7 +80,7 @@ For example, if not done already, clone the **MicrosoftEdge / Demos** repo to yo
 
 1. Clone the repo to your local drive, entering the URL string that you copied from the GitHub repo.  If you use a command prompt:
 
-   ```Shell
+   ```console
    # example location where the repo directory will be added:
    cd ~/GitHub
    git clone https://github.com/MicrosoftEdge/Demos.git
@@ -107,13 +107,13 @@ Continue with the next section.
 
 1. Create a working branch named "test" and switch to it (to avoid altering the demo's files in the "main" branch):
 
-   ```Shell
+   ```console
    git checkout -b test
    ```
 
    That's equivalent to:
 
-   ```Shell
+   ```console
    git branch test
    git switch test
    ```

microsoft-edge/devtools/remote-debugging/webviews.md

@@ -48,15 +48,20 @@ if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
 
 The setting applies to all of the Android WebViews of the app.
 
-> [!TIP]
-> Android WebView debugging isn't affected by the state of the `debuggable` flag in the manifest of the app.  If you want to turn on Android WebView debugging only when the `debuggable` flag is `true`, test the flag at runtime.
->
-> ```java
-> if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
->     if (0 != (getApplicationInfo().flags & ApplicationInfo.FLAG_DEBUGGABLE))
->    { WebView.setWebContentsDebuggingEnabled(true); }
-> }
-> ```
+
+<!-- ------------------------------ -->
+#### Testing the flag at runtime
+
+Android WebView debugging isn't affected by the state of the `debuggable` flag in the manifest of the app.
+
+If you want to turn on Android WebView debugging only when the `debuggable` flag is `true`, test the flag at runtime:
+
+```java
+if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
+    if (0 != (getApplicationInfo().flags & ApplicationInfo.FLAG_DEBUGGABLE))
+        { WebView.setWebContentsDebuggingEnabled(true); }
+}
+```
 
 
 <!-- ====================================================================== -->