Merge pull request #901 from marionbarker/working-docs

Update directions and graphics

Author: marionbarker

docs/browser/bb-errors.md

@@ -492,7 +492,7 @@ Once you have created an app in the *App Store* that is not based on your `TEAMI
     * Tap on `Remove App`
     * New dialog window appears, select `Remove`
 
-At this point, get your correct `TEAMID`, fix your Secrets file to have the correct `TEAMID` and then return to [First-Time: Configure Secrets](prepare-fork.md#configure-secrets). This time you will be updating `TEAMID` in the repository secret list.
+At this point, get your correct `TEAMID`, fix your Secrets file to have the correct `TEAMID` and then return to [First-Time: Configure Secrets](prepare-fork.md#configure-secrets). This time you will be updating `TEAMID` in the secret list.
 
 ## Repeat `Build Loop` Errors
 

docs/browser/bb-overview.md

@@ -40,18 +40,18 @@ In addition to the pages linked below in [Configure to use Browser](#configure-t
 
 ### Configure to use Browser
 
-The steps on these pages must be completed (in order) for you to build an app using a browser:
+The steps on these pages must be completed for you to build an app using a browser:
 
 1. [Introduction and Summary](intro-summary.md){: target="_blank" }
 1. [Collect Secrets](secrets.md){: target="_blank" }
     * Some from *Apple*
     * Some from *GitHub*
 1. [Prepare Fork](prepare-fork.md){: target="_blank" }
-1. [Identifiers](identifiers.md){: target="_blank" }
+1. [Prepare Identifiers](identifiers.md){: target="_blank" }
 1. [Prepare App](prepare-app.md){: target="_blank" }
+1. [Prepare *TestFlight* Group](tf-users.md){: target="_blank" }
 1. [Create Certificates](certs.md){: target="_blank" }
 1. [Build the *Loop* App](build-yml.md){: target="_blank" }
-1. [*TestFlight* Users](tf-users.md){: target="_blank" }
 
 The pages of instructions listed above give detailed steps on how to build the *Loop* app. If you are building a different app, you can follow the detailed instructions but will need to know the Fork, App Name, Identifiers and in some cases App Group for the App you intend to build. Once you build one app, subsequent apps are much easier to build.
 

docs/browser/bb-update.md

@@ -443,6 +443,8 @@ If your `Personal Access Token` has expired or has an expiration date, you can r
 !!! tip "Update new GH_PAT to <code>Secrets</code>"
     After you get your new token, immediately add it to your <code>Secrets</code> for any app you build with this method. You don't have to rebuild the app, but it's a good idea to at least run `Action 1. Validate Secrets` for each repository to make sure you did not make a mistake.
 
+    This might be a good time to [Switch to a GitHub Organization](prepare-fork.md#switch-to-a-github-organization){: target="_blank" }.
+
 You can regenerate your *GitHub* `Personal Access Token` at any time by clicking on the link below. (it will open in a new browser tab.)
 
 * [Link to access your *GitHub* Personal Access Token](https://github.com/settings/tokens){: target="_blank" }
@@ -478,17 +480,17 @@ The next step is to update GH_PAT in your <code>Secrets</code>. (If you build ot
 
 ### Update <code>Secrets</code>
 
-This example is for updating GH_PAT in the <code>Secrets</code> for your `repository`, but the same method can be applied when changing any of the <code>Secrets</code>.
+This example is for updating GH_PAT in the <code>Secrets</code> for your `repository`, but the same method can be applied when changing any of the <code>Secrets</code>. It uses a personal account, instead of an organization. So it shows changing the `Secret` for a specific repository and would need to be repeated for every repository you use. This might be a good time to [Switch to a GitHub Organization](prepare-fork.md#switch-to-a-github-organization){: target="_blank" }.
 
 Open the `repository` for which you will update <code>Secrets</code>. On the far right is a Settings selection. If you don't see Settings (if last item on row is Insights), then you are **not** on your `fork` or you need to sign in to your *GitHub* account. You should see `username/LoopWorkspace` with `forked` from `LoopKit/LoopWorkspace` underneath.
 
 Refer to the GIF for help. There are 3 frames.
 
-![screen showing repository secrets list](img/update-secret-gh-pat.gif){width="500"}
+![screen showing secrets list](img/update-secret-gh-pat.gif){width="500"}
 {align="center"}
 
 1. Tap on Settings, then scroll down until you see `Secrets and variables` on the left side and click on the drop down indicator to display `Actions`.
-1. Keep scrolling on the same screen, past the `Action secrets / New repository secret` row, until you see the list of your current <code>Secrets</code>. 
+1. Keep scrolling on the same screen, past the `Action secrets / New secret` row, until you see the list of your current <code>Secrets</code>.
 1. Click on the GH_PAT, tap on the pencil and enter the new token in the form. Click on Update Secret to complete the action.
 
 Scroll all the way to the top of the screen and tap on your LoopWorkspace link. Then follow the [How to Update or Rebuild](#how-to-update-or-rebuild) instructions to start a new build.

docs/browser/build-yml.md

@@ -10,11 +10,6 @@
         * one says *TestFlight* is ready (typically half-hour after the build succeeds)
         * Ignore the one that says you need to fix "issues" in your app. You are not selling the app in the app store; so no action is required. The app you built is for personal use for you or a family member.
     1. Your app should eventually appear on [App Store Connect](https://appstoreconnect.apple.com/apps){: target="_blank" }.
-    1. For each phone/person you would like to support:
-        * Add them in [Users and Access](https://appstoreconnect.apple.com/access/users){: target="_blank" } on App Store Connect.
-        * Add them to your *TestFlight* Internal Testing group.
-
-    [<span class="loop-bigger">:material-skip-forward:</span>](tf-users.md#testflight-users-overview) To skip the detailed instructions, click on [*TestFlight* Users Overview](tf-users.md#testflight-users-overview).
 
 Refer to the graphic below for the first four steps:
 
@@ -63,14 +58,16 @@ Did you get a red X? Head over to the [Errors with Browser](bb-errors.md){: targ
 
 ## Next Steps
 
-If this is your first build, you need to configure your TestFlight Users
-
-* [TestFlight Users](tf-users.md)
+It may take up to an hour for your new build to appear in TestFlight.
 
-If this is a repeat build, wait up to an hour for your new build to appear in TestFlight. Then from the phone where you want to install the *Loop* app, use TestFlight on that phone to install the app.
+From the phone where you want to install the *Loop* app, use TestFlight on that phone to install the app.
 
 * [Install on Phone](phone-install.md)
 
+If is you skipped the step about creating a *TestFlight* Group or want to add another person to your group:
+
+* [TestFlight Group](tf-users.md)
+
 ## Caregivers
 
 If you are a Caregiver who helps manage a loved-ones diabetes, you may use other open-source apps that can be built the same way: