update language and put in some admonitions, fix links

Author: marionbarker

docs/browser/automatic.md

@@ -9,21 +9,23 @@ The instructions provided for building with a browser include settings to automa
 
     What does that mean?
 
-    * **inactive** means no commits within the last 60 days
+    * **inactive** means stable code (no new commit within the last 60 days)
     * **disables actions** means the Build Action shows up as disabled
 
 ### What Manual Action is Required?
 
 For any repository that is stable, like the *Loop* app, you may need to take manual action to keep automatic builds flowing every month.
 
 * Put a calendar reminder to check every month on the 2nd day of the month (or later)
-    * Check that *TestFlight* has a new build of the *Loop* app
+    * Check that *TestFlight* has a new build of the *Loop* (or other) app
     * If not, go to your repository to see if the build action is disabled
 * If necessary, enable the build action at your repository as shown in the graphic below and then launch a manual build
 
 ![fix a disabled build state](img/build-disabled-fix.png )
 
-This keeps the most recent version of your app available in *TestFlight* for you to install when you are ready.
+This keeps the most recent version of your app available in *TestFlight* for you to install when you are ready. This should be required no more frequently than every 60 days, however, best to make it a monthly habit to check.
+
+> Builds in *TestFlight* are good for 90 days before they [expire](../operation/features/notifications.md#loop-app-expiration-notification){: target="_blank" }.
 
 ## What is Automatic
 
@@ -33,9 +35,10 @@ These events are automatically scheduled:
     * If found, your fork is automatically updated and a new build created and uploaded to *TestFlight*
 * Once a month: Build the app and upload the fresh build to *TestFlight*
 
-> These automatic actions happen on schedule, but if your build action is disabled, no build actually happens, no warning email is sent and a green checkmark (✅) appears beside a very short build action in which the actual build was skipped.
->
-> * Refer to [What Manual Action is Required?](#what-manual-action-is-required)
+!!! important "You Get No Warning if Repository Build Action is Disabled"
+    These automatic actions happen on schedule, but if your build action is disabled, no build actually happens, no warning email is sent and a green checkmark (✅) appears beside a very short build action in which the actual build was skipped.
+
+    * Refer to [What Manual Action is Required?](#what-manual-action-is-required)
 
 If you do not want this automatic schedule, you can modify it.
 
@@ -63,9 +66,10 @@ In that case, you should check your favorite information site to find out what t
 
 On the first day of every month, you will see a successful `build action`. The purpose of this build is to provide a recent version of the app in *TestFlight* so you are never in a situation where you have no app on your phone.
 
-> This automatic monthly build happens on schedule, but if your build action is disabled, no build actually happens, no warning email is sent and a green checkmark (✅) appears beside a very short build action in which the actual build was skipped.
->
-> * Refer to [What Manual Action is Required?](#what-manual-action-is-required)
+!!! important "You Get No Warning if Repository Build Action is Disabled"
+    If your build action is disabled, no build actually happens, no warning email is sent and a green checkmark (✅) appears beside a very short build action in which the actual build was skipped.
+
+    * Refer to [What Manual Action is Required?](#what-manual-action-is-required)
 
 You start getting [Notifications](../operation/features/notifications.md#loop-app-expiration-notification){: target="_blank" } when there are fewer than 20 days until expiration. When you see the warning, install the newest build from your *TestFlight* app. You do not want to get the dreaded "Loop Beta is not available" message on your phone. (The warnings get very agressive when close to expiration.)
 

docs/browser/bb-overview.md

@@ -122,7 +122,7 @@ These considerations were prepared when most people were using a Mac computer to
 * Automatic Updates are loaded into *TestFlight*
     * With version 3.4 and newer, builds are automatically prepared at least once a month
     * You choose when to install the new app from TestFlight onto your phone
-    * WARNING: starting May 2025, [Manual Action for Automatic Build](automatic.md#manual-action-for-automatic-build){: target="_blank" } may be required - be sure to check monthly to see if you need to start a build manually
+    * **WARNING:** starting May 2025, [Manual Action for Automatic Build](automatic.md#manual-action-for-automatic-build){: target="_blank" } may be required - be sure to check monthly to see if you need to start a build manually
 * Manual Updates are easy
     * Starting an update takes a few minutes of your time; it can be done from your phone; the rest is automatic and is done in about an hour
 * After the *GitHub* Build starts, your app is ready to install on your *iPhone* in about an hour

docs/browser/bb-update.md

@@ -168,7 +168,7 @@ Refer to graphic below as you follow the steps to build the *Loop* app. The numb
 * (1) Click on the `Actions` tab
 * (2) Select the `4. Build Loop` workflow on the left
     * If using a mobile browser, be sure to use landscape mode to more closely match how *GitHub* looks on a computer.
-* If you notice your build action is disabled, you must do (3)
+* If you notice your build action is disabled, you must (3) click on `Enable workflow`
 * (4) Look on the right and click `Run workflow` to  see the dropdown
 * (5) Click on the green `Run workflow` button in the dropdown
 * Wait ~25 min for the build to complete successfully

docs/browser/other-apps.md

@@ -390,7 +390,7 @@ Refer to the graphic below for the first four steps:
 
 1. Wait a few minutes to make sure there is not an early failure
     * If you see the red `X` (:octicons-x-circle-fill-16:{: .failed }):
-        * Use the Browser Build Errors page to resolve the error, substituting , then repeat the Action
+        * Use the Browser Build Errors page (which uses LoopWorkspace repository) to resolve the error, substituting the repository name for the app you are building, then repeat the Action
         * [Quick Reference for Browser Build Errors](bb-errors.md#quick-reference-for-browser-build-errors){: target="_blank" }
 1. If the process appears to be happening without an error, go do something else for a while. The build should take less than half an hour (these tend to build faster than the *Loop* app.
     * When you see the green check (:octicons-check-circle-fill-16:{: .passed }) continue

docs/browser/phone-install.md

@@ -66,9 +66,12 @@ The instructions on the [Configure to Use Browser](intro-summary.md){: target="_
     * This is only for the `default` branch, typically `main`
 * Build the app at least once a month and upload it to *TestFlight*
 
-> These automatic actions happen on schedule, but starting May 2025, you may find your build action disabled by *GitHub*. (Might happen every 60 days.) In that case, no build actually happens, no warning email is sent and a green checkmark (✅) appears beside a very short build action in which the actual build was skipped.
->
-> * Refer to [What Manual Action is Required?](automatic.md#what-manual-action-is-required){: target="_blank" }
+!!! important "You Get No Warning if Repository Build Action is Disabled"
+    Alert - this issue is new as of May 2025. Your build action might be disabled by *GitHub*, which means you need to enable it manually.
+
+    If your build action is disabled, no build actually happens, no warning email is sent and a green checkmark (✅) appears beside a very short build action in which the actual build was skipped.
+
+    * Refer to [Manual Action for Automatic Build](automatic.md#manual-action-for-automatic-build){: target="_blank" }
 
 Unless you make the recommended one-time change to [Disable Automatic Install from *TestFlight*](#disable-automatic-install-from-testflight), the default setting for each app found in *TestFlight* is to: