cleanup comment

Author: mikehoffms

microsoft-edge/devtools-guide-chromium/javascript/guides/mark-content-scripts-library-code.md

@@ -23,7 +23,7 @@ ms.date: 05/04/2021
    limitations under the License.  -->
 # Add content scripts to the Ignore List
 
-<!-- todo: define _content script_, like in
+<!-- todo: define _content script_
 * [Using the Content scripts tab for Microsoft Edge extensions](../../sources/index.md#using-the-content-scripts-tab-for-microsoft-edge-extensions) in _Sources tool overview_.
 * [Content scripts](https://developer.chrome.com/docs/extensions/develop/concepts/content-scripts) in Chrome Extensions docs.
 -->

microsoft-edge/devtools-guide-chromium/javascript/overrides.md

@@ -13,14 +13,11 @@ ms.date: 09/25/2023
 
 Sometimes you need to try out some possible fixes for a webpage, but you don't have access to the source files, or changing the page requires a slow and complex build process.  You can debug and fix all kind of problems in DevTools.  But the changes don't persist; after you refresh the local file, all your work is gone.  The Overrides feature in the [Sources](../sources/index.md) tool helps you solve this problem.
 
-You can now take a resource of the current webpage and store it locally.  When you refresh the webpage, the browser doesn't load the resource from the server; instead, the browser replaces the server resource with your local copy of the resource.
-
-<!-- todo: a note from review, maybe incorp:
-The overrides that you make are saved across reloads.
-You're not supposed to use this feature for mapping to your source files.
-When you set up a folder for local overrides the first time, that folder should be empty.
-DevTools will create all of the folders and sub-folders that it needs to store overrides within it.
--->
+You can take a resource of the current webpage and store it locally.  When you refresh the webpage, the browser doesn't load the resource from the server; instead, the browser replaces the server resource with your local copy of the resource.  The overrides that you create are saved across reloads.
+
+The overrides feature is not intended for mapping to your source files.
+
+When you set up a folder for local overrides the first time, that folder should be empty.  DevTools then creates all of the folders and sub-folders that it needs to store overrides within it.
 
 
 <!-- ====================================================================== -->

microsoft-edge/devtools-guide-chromium/sample-code/sample-code.md

@@ -179,7 +179,8 @@ To clone the **MicrosoftEdge / Demos** repo to your local drive:
 
    ```Shell
    # example location where the repo directory will be added:
-   cd c:/users/localAccount/github/
+   cd ~/GitHub
+   cd c:/users/localAccount/GitHub/  # alt format
    git clone https://github.com/MicrosoftEdge/Demos.git
    ```
 
@@ -302,8 +303,7 @@ If you start the localhost server from a specific demo folder, such as `\Demos\d
 Starting the server from within a specific demo directory:
 
 ```
-$ cd "C:\Users\localAccount\GitHub\Demos\demo-to-do"
-$ cd ~/GitHub/Demos/demo-to-do  # alt syntax
+$ cd ~/GitHub/Demos/demo-to-do
 $ npx http-server
 ```
 
@@ -322,8 +322,8 @@ If you start the localhost server from within the entire `\Demos\` folder and th
 Starting the server from within the entire `\Demos\` directory:
 
 ```
-$ cd "C:\Users\localAccount\GitHub\Demos"
-$ cd ~/GitHub/Demos  # alt syntax
+$ cd ~/GitHub/Demos
+$ cd "C:\Users\localAccount\GitHub\Demos"  # alt syntax
 $ npx http-server
 ```