fix language, typos, remove figure no longer in use

Author: marionbarker

docs/browser/bb-overview.md

@@ -130,6 +130,6 @@ These considerations were prepared when most people were using a Mac computer to
 * After the *GitHub* Build starts, your app is ready to install on your *iPhone* in about an hour
 * The app is delivered to your phone via *TestFlight*
     * The app is considered "Beta" by  *Apple* and expires after 90 days
-    * <span translate="no">Loop 3.4</span>&nbsp; and later versions provide automatic build as the default
+    * <span translate="no">Loop 3.4</span>&nbsp; and newer versions provide automatic build as the default
 * Customization methods are documented at [Customize with Browser](custom-browser.md){: target="_blank" }
 

docs/browser/edit-browser.md

@@ -10,7 +10,7 @@
 !!! warning "Modules vs Submodule"
     This page has instructions to set up your own <code>fork</code> for the Modules, otherwise known as submodules, associated with&nbsp;<span translate="no">LoopWorkspace</span>&nbsp;that are needed for a selected customization.
 
-    Each Module has its own *GitHub* <code>repository</code>;and you will be working with your <code>fork</code> of that Module at https://github.com/my-name-org/Module, where username is your username.
+    Each Module has its own *GitHub* <code>repository</code>;and you will be working with your <code>fork</code> of that Module at https://github.com/my-name-org/Module, where you use your own organization (recommended) or personal account.
 
     If you are an experienced builder who set the Submodule changes up in your personal *GitHub* account, you can leave those forks where they are, i.e., https://github.com/my-name/Module. You do not build from Submodules, so no `Secrets` are required.
 

docs/browser/img/gh-fork-loopworkspace.svg

@@ -210,14 +210,16 @@ With release of Loop 3.6.0:
 
 ## Repository Names for my Fork:
 
-https://github.com/my-github-username-or-org-name/LoopWorkspace
+If you use an organization (recommended)
+https://github.com/my-name-org/LoopWorkspace
+
+or (if you don't use an organzation): 
+https://github.com/my-name/LoopWorkspace
 
 
 Add additional apps here if you decide to build any
 ```
 
-
-
 ## New Terms with <code>*GitHub* Browser Build</code>
 
 The <code>*GitHub* Browser Build</code> may use new and unfamiliar **terms**.

docs/browser/intro-summary.md

@@ -25,7 +25,7 @@
 
 1. Refer the the GIF below:
     * If you created a free organization (strongly recommended), you will see the display shown in the GIF below where you will choose your organization as the owner
-        * If you did not set up a free organization, your username will be automatically filled in as the owner (`Owner`)
+        * If you did not set up a free organization, `my-name` will be automatically filled in as the owner (`Owner`)
     * If you already have a fork, you should not proceed, see [Already Have a LoopWorkspace](#already-have-loopworkspace)
     * The repository name is already filled in
         * Do not rename the repository to something else
@@ -48,9 +48,9 @@ After creating the &nbsp;<span class="notranslate">fork</span>, your screen shou
 
 Carefully compare your screen to the graphic below paying attention to the highlighted sections.
 
-* Note that your username or username-org is now showing
+* Note that your URL is `https://github.com/my-name-org/LoopWorkspace` or `https://github.com/my-name/LoopWorkspace` where `my-name` is the name you chose:
     * Many graphics for LoopDocs are created using a free *GitHub* organization called `loopdocs-tester`
-* The comment under your username indicates where the &nbsp;<span class="notranslate">fork</span>&nbsp; came from (that is a clickable link)
+* The comment on the second row indicates where the &nbsp;<span class="notranslate">fork</span>&nbsp; came from (that is a clickable link)
 * The branch that is selected :octicons-git-branch-16: is `main`
 * The message says "`This branch is up to date with LoopKit/LoopWorkspace:main`"
 
@@ -247,7 +247,7 @@ If your copy (`fork`) is **not** from `LoopKit`, follow the [Delete and Start Fr
 
 If your copy (`fork`) is from `LoopKit`:
 
-* Open your <code>LoopWorkspace</code> repository (`https://github.com/username/LoopWorkspace`) where you use your *GitHub* `username` in the URL
+* Open your <code>LoopWorkspace</code> repository (`https://github.com/my-name-org/LoopWorkspace`) where you use your version of `my-name` in the URL
 * Review the graphic in the [Configure: Successful Fork](#successful-fork) section
     * Make sure all the items highlighted by red rectangles are correct with the possible exception of your fork being up to date
 * If you see a message that your *fork* is not up to date - tap on the `Sync fork` button and follow the instructions