minor clean-up

Author: marionbarker

docs/browser/automatic.md

@@ -81,7 +81,7 @@ This is an optional step. If you are happy with the automatic sync and update, y
 ??? tip "Instructions to Modify the Automatic Actions (Click to Open/Close)"
     You can modify the automation by creating and using some variables.
 
-    To configure the automated build more granularly involves creating up to two environment variables: `SCHEDULED_BUILD` and/or `SCHEDULED_SYNC`. See [How to configure a variable](#how-to-configure-a-variable).
+    To configure the automated build more granularly involves creating up to two variables: `SCHEDULED_BUILD` and/or `SCHEDULED_SYNC`. See [How to configure a variable](#how-to-configure-a-variable).
 
     Note that the weekly and monthly `Build Loop` actions will continue, but the actions are modified if one or more of these variables is set to false. **A successful Action Log will still appear, even if no automatic activity happens**.
 

docs/browser/bb-errors.md

@@ -23,9 +23,9 @@ These are two places to ask for help, but please choose only one. You may get a
 
 ### What Information is Needed for Help
 
-1. Your GitHub address (required):
+1. Your GitHub name used for building (required):
 
-    * You can also provide a link to your repository like the example, but substitute your information
+    * Best to provide a link to your repository, like the example, but substitute your information
     * If you are building an app other than Loop, replace LoopWorkspace with the app repository name
 
     ``` {.text .copy  title="If you use an organization" }
@@ -153,7 +153,7 @@ This section is required when you need to search for a string to diagnose and er
 If there are *Apple* Developer agreements you have not accepted, you may get errors when you try to Build that indicate your *Apple* <code>Secrets</code> are incorrect even if they are not.
 
 * The misleading message tells you that one or more of these: <code>FASTLANE_ISSUER_ID</code>, <code>FASTLANE_KEY_ID</code> or <code>FASTLANE_KEY</code> is not correct
-    * Once `Loop 3.6.0` or newer is available, this should no longer appear unless you have a mistake in one of thsoe
+    * Once `Loop 3.6.0` or newer is available, this should no longer appear unless you have a mistake in one of those
 * Check your *Apple* Developer account for agreements first, before trying to fix those `Secrets`
 * If you previously built successfully - it is almost certainly the agreement
 * It can take 15 minutes to an hour after the agreement is signed before it can be used

docs/browser/build-dev-browser.md

@@ -93,7 +93,7 @@ If you have one branch as default, for example `main`, and choose to build a dif
 
 The [Automatic Update & Build](automatic.md){: target="_blank" } features are applied to the default branch of your repository. Normally this is the `main` branch. If you are a developer or tester who wants the `dev` branch to be built automatically, you must configure it as your default branch. Be aware that for this situation, you will not get automatic updates of released code.
 
-Most people should keep `main` as default and make a considered decision when to launch a manual build of the `dev` branch. At that time, it will automatically update to the latest `dev` commit unless you have modified your environment settings: [Modify Automatic Building](automatic.md#modify-automatic-building){: target="_blank" }.
+Most people should keep `main` as default and make a considered decision when to launch a manual build of the `dev` branch. At that time, it will automatically update to the latest `dev` commit unless you have modified your settings with special `Variables`: [Modify Automatic Building](automatic.md#modify-automatic-building){: target="_blank" }.
 
 ## Change Default `Branch`
 

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 you use your own organization (recommended) or personal account.
+    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/intro-summary.md

@@ -158,7 +158,7 @@ suggest you use your desired password tool to save the password for this account
 <your information here>
 suggest you use your desired password tool to save the password for this account
 
-There are Six Secrets and One Environment Variable:
+There are Six Secrets and One Variable:
  - the list below shows the expected format of each.
 You can replace each prototype with your secret as you gather them,
  - or put your secret below a prototype.
@@ -201,7 +201,7 @@ MATCH_PASSWORD
 <looks like this>
 AnyThingYouWant-sameForEveryRepository
 
-New addition, this environment variable:
+New addition, this Variable:
 
 ENABLE_NUKE_CERTS = true
 

docs/browser/secrets.md

@@ -311,6 +311,7 @@ In the instructions below, use your *GitHub* username instead of `my-name`.
 ???+ tip "GH_PAT comes from personal `my-name` account"
     The *GitHub* personal access token used as one of the 6 <code>Secrets</code> is associated with your personal account (`my-name`); so if you already have one, you just keep using it.
 
+**Your personal *GitHub* account is still needed. The free organization points to your private account as a member. Please do not delete your personal *GitHub* account after creating an organization. If you do that - you will no longer have access to your organization.**
 
 ## Make up a Password