minor changes and reordering

Author: marionbarker

docs/browser/bb-errors.md

@@ -112,7 +112,7 @@ Do not hesitate to [ask a mentor for help](#where-to-get-help-with-browser-build
 
 ### New Builder: Create Certificates Error
 
-New builders are now told they can skip the separate `Create Certificates` step if they choose.  It is run when you `Build Loop`.
+New builders should skip the separate `Create Certificates` step.  It is run when you `Build Loop`.
 
 !!! tip "Successful Certificate, Failed Build"
     The create certificate step simply creates certificates based on how you configured your Identifiers. You can have a successful certificate step but still fail with the build if you made a mistake when you configured the Identifiers.
@@ -176,7 +176,7 @@ These should be a thing of the past - but you must do this step [Add Variable](p
 
 ### Rebuild: Build Error
 
-After you update to `Loop 3.6.0`, the Create Certificates Action is incorporated into the Build Action. So for rebuilders, if you completed the manual sync and added the new variable, you should not get an error when building.
+The Create Certificates Action is incorporated into the Build Action. So for rebuilders, if you completed the manual sync and added the new variable, you should not get an error when building.
 
 > Caveat - your Apple Developer account must be in good standing with a valid credit card attached and all agreements signed.
 
@@ -358,6 +358,8 @@ and
 
 Review [Find the Error](#find-the-error) for instructions on how to use the error strings.
 
+* If you want to do a general search for an error, enter `::error` in the search box or just `error` and look at the first item
+
 List of certificate errors on this page:
 
 * [Error: No profile for team](#error-no-profile-for-team)
@@ -433,7 +435,7 @@ Follow the [Configure to Use Browser: Create Loop App in App Store Connect](prep
 
 You can go straight to [`Build Loop`](build-yml.md#build-the-loop-app){: target="_blank" } which will `Create Certificates` for you. However, you may be more comfortable making sure you got your mistakes fixed. You can run [`Create Certifcates`](certs.md#create-certificates){: target="_blank" } as a stand-alone process. It should only take a few minutes.
 
-After that succeeds, proceed to [`Build Loop`](build-yml.md#build-the-loop-app){: target="_blank" } and keep going.
+* After your stand alone run of Create Certificates succeeds, proceed to [`Build Loop`](build-yml.md#build-the-loop-app){: target="_blank" } and keep going.
 
 ### Error: Error cloning certificates
 
@@ -525,35 +527,11 @@ For each section below, copy the phrase into the search function of the log. If
 
 List of build errors in this section:
 
-* [`Error: Could not find an app on App Store Connect`](#error-could-not-find-an-app-on-app-store-connect)
 * [`Error: Provisioning Profile`](#error-provisioning-profile)
+* [`Error: Could not find an app on App Store Connect`](#error-could-not-find-an-app-on-app-store-connect)
 * [`Error: A new one cannot be created because you enabled`](#error-a-new-one-cannot-be-created-because-you-enabled)
 
 
-### `Error: Could not find an app on App Store Connect`
-
-Copy the words on the line below and paste them into the search function for your action log.
-
-> ``` { .text .copy }
-> Could not find an app on App Store Connect
-> ```
-
-If that phrase is found, then:
-
-* Make sure you completed the [Create Loop App in App Store Connect](prepare-app.md#create-loop-app-in-app-store-connect) Step
-    * Once you've resolved that step, run `Build Loop` action again
-
-
-* This can also be caused if you correctly created the *Loop* App but entered an incorrect value for the `TEAMID`.
-    * If you have the incorrect `TEAMID`, check this link: [Certificates, Identifiers & Profiles](https://developer.apple.com/account/resources/identifiers/list) for entries with the incorrect `TEAMID` embedded
-    * For example, if your `TEAMID` is `0123456789`, but you entered `000123`, you may see both of these in your identifiers list
-        * `com.0123456789.loopkit.Loop`
-        * `com.000123.loopkit.Loop`
-    * Delete the "bogus" identifier version, fix your `TEAMID` and rerun all three steps:
-        * `Add Identifier`
-        * `Create Certificates`
-        * `Build Loop`
-
 ### `Error: Provisioning Profile`
 
 Copy the words on the line below and paste them into the search function for your action log.
@@ -565,8 +543,13 @@ Copy the words on the line below and paste them into the search function for you
 If that phrase is found one, or more times, it means you missed a step when configuring the Loop identifier or missed associating your *Loop* App Group with one or more identifiers.
 
 !!! tip "`App Group` Mistake"
-
-The most common reason for a new builder to see this is that did not spell the `App Group` properly.  In the directions, please copy and paste the protype and then insert your TEAMID. Do not type what you think you see. It is too easy to mess this one up and it will affect every Identifier. (See link to the `App Group` fix below.)
+    The most common reasons for a new builder to see this
+    
+    1. They spelled the `App Group` correctly but missed one or more Identifiers that needed the `App Group` configure - see [`Add App Group to Identifier`](prepare-app.md#add-app-group-to-identifiers){: target="_blank" }
+    1. They did not spell the `App Group` properly
+        *  In the [directions](prepare-app.md#create-app-group){: target="_blank" }, please copy and paste the protype and then insert your TEAMID
+        * Do not type what you think you see 
+        * It is too easy to mess this one up and it will affect every Identifier. Read this whole section and follow the appropriate links
 
 For example, you might see:
 
@@ -577,14 +560,38 @@ For example, you might see:
 
 If some, but not all, of those errors are seen when building the *Loop* app, then you spelled the `App Group` correctly, but failed to associate all the Identifiers with that App Group.
 
-* Link to the entire section: [First-Time: Identifiers for the `Loop` app](prepare-app.md#identifiers-for-the-loop-app)
-* Link to the `App Group` fix
-* Link to the `Identifier` fix
+* Link to the entire section: [First-Time: Identifiers for the `Loop` app](prepare-app.md#identifiers-for-the-loop-app){: target="_blank" }
+    * Link to [Create `App Group`](prepare-app.md#create-app-group){: target="_blank" }
+    * Link to [``Add App Group to Identifier`](prepare-app.md#add-app-group-to-identifiers){: target="_blank" }
 
 You can build *Loop*:
 
 * Action: `Build Loop`
 
+### `Error: Could not find an app on App Store Connect`
+
+Copy the words on the line below and paste them into the search function for your action log.
+
+> ``` { .text .copy }
+> Could not find an app on App Store Connect
+> ```
+
+If that phrase is found, then:
+
+* Make sure you completed the [Create Loop App in App Store Connect](prepare-app.md#create-loop-app-in-app-store-connect) Step
+    * Once you've resolved that step, run `Build Loop` action again
+
+
+* This can also be caused if you correctly created the *Loop* App but entered an incorrect value for the `TEAMID`.
+    * If you have the incorrect `TEAMID`, check this link: [Certificates, Identifiers & Profiles](https://developer.apple.com/account/resources/identifiers/list) for entries with the incorrect `TEAMID` embedded
+    * For example, if your `TEAMID` is `0123456789`, but you entered `000123`, you may see both of these in your identifiers list
+        * `com.0123456789.loopkit.Loop`
+        * `com.000123.loopkit.Loop`
+    * Delete the "bogus" identifier version, fix your `TEAMID` and rerun all three steps:
+        * `Add Identifier`
+        * `Create Certificates`
+        * `Build Loop`
+
 ### `Error: A new one cannot be created because you enabled`
 
 Copy the words on the line below and paste them into the search function for your action log.
@@ -636,7 +643,7 @@ Use the [Examine Annotation](#examine-annotation) instructions to find your erro
 
 ### `ERROR: Asset validation failed`
 
-This error indicates your fork needs to be updated. As of 24 April 2025, you are required to use Xcode 16 to build the app. This is provided with `Loop 3.6.0` and newer versions.
+This error indicates your fork needs to be updated.
 
 There are serveral phrases you can check for. All of them have the same solution.
 
@@ -705,8 +712,8 @@ The graphic below shows the steps to make sure your `fork` is up to date and to
     previous_build_number + 1
     ```
 
-2. Tap on the `Find` button and the `Replace` button to make 2 changes to the file
-3. After modifying the two lines, click on the `Commit changes` button at upper right
+2. Tap on the `Find` button and the `Replace` button to change the file
+3. Click on the `Commit changes` button at upper right
 
 ![Graphic shows steps to edit fastfile](img/tf-build-number-error-03.svg){width="750"}
 {align="center"}
@@ -800,14 +807,17 @@ You will get an email informing you the certificate was revoked.
 
 Run the Build action and a new Distribution Certificate will be created along with the profiles and build credentials needed.
 
+* This is true for Loop, LoopCaregiver, LoopFollow and Trio if you have the ENABLE_NUKE_CERTS variable set to true
+
 !!! question "But my Build Action Failed Again"
     - [x] Make sure you deleted all the Distribution Certificates as directed above.
 
     - [x] Make sure you have the [`ENABLE_NUKE_CERTS` variable](prepare-fork.md#add-variable){: target="_blank" } set to true
+        - [x] Make sure you configured `ENABLE_NUKE_CERTS` as a variable
+        - [x] Make sure you spelled `ENABLE_NUKE_CERTS` correctly
+        - [x] Make sure you entered the value of `true` in little letters
 
-    - [ ] Then follow the link to delete your [Match Secrets repository](#delete-match-secrets) and run the [`Build Loop`](build-yml.md#build-the-loop-app){: target="_blank" } again.
-
-* This is true for Loop, LoopCaregiver, LoopFollow and Trio if you have the ENABLE_NUKE_CERTS variable set to true
+    - [ ] Then follow the link to delete your [Match Secrets repository](#delete-match-secrets); after that step, then run `Build Loop` again.
 
 !!! question "But what about *TestFlight* builds?"
     Previous builds using this method that are already in *TestFlight* are not affected by deleting the `Distribution Certificate`.

docs/browser/bb-overview.md

@@ -146,16 +146,16 @@ For advanced users who want cutting-edge features before official release:
 | **Device Required** | Any device with browser | Mac with recent macOS |
 | **Xcode Required** | No (GitHub provides) | Yes (must update regularly) |
 | **Initial Setup Time** | 2-4 hours over several days | 1-2 hours (if Mac is ready) |
-| **Monthly Updates** | Automatic to TestFlight<br>[Manual Actions](automatic.md#manual-action-for-automatic-build){: target="_blank"}| Manual via Xcode |
-| **Build Time** | ~1 hour (in cloud) | ~30 minutes (local) |
+| **Monthly Updates** | Automatic or<br>Five minutes with [Manual Actions](automatic.md#manual-action-for-automatic-build){: target="_blank"}<br>Build uploaded to TestFlight| Manual via Xcode |
+| **Build Time** | ~30 minutes (in cloud) | ~30 minutes (local) |
 | **App Expiration** | 90 days (TestFlight) | 1 year |
 | **Customization** | Supported | Supported |
 
 **Build Frequently** Please check monthly to see if there is a newer version of the *Loop* app.
 
 * Sometimes there is a new feature
 * Sometimes there is a required update to support the latest phone iOS
-* Even though a *Mac* lets you go a year between builds, that is **not** advisable
+* Even though a *Mac* lets you go a year between builds, you should build at least once a quarter
 
 Both methods produce the identical Loop app. Choose based on your available hardware and preferences.
 

docs/build/phone.md

@@ -22,13 +22,7 @@
 
 The *Loop* app requires an *Apple* device and uses the *Apple Health* app to store and retrieve your blood glucose and insulin data and to store your carbohydrate records. Older iPads do not support *Apple Health* which used to be required, and is still strongly recommended, for the *Loop* app. It may be possible to run Loop with newer iPads and newer *iOS*, but this has not been tested.
 
-You need a minimum version of the mobile operating software, called the *iOS*, to be installed on your iPhone.
-
-* As of v3.8.x, you must use iPhone devices with *iOS* 16.1 or newer
-* The next release will require *iOS* 17 or newer
-    * All phones that support *iOS* 17, also support 18 and 26
-
-* The developers maintain support for the current and one-level earlier *iOS*
+You need a minimum version of the mobile operating software, called the *iOS*, to be installed on your iPhone. It is **strongly advised your phone hardware support and be updated to the most recent iOS**. This is for security and feature compatibility for *Loop* and companion apps.
 
 !!! Danger "Update Older Phones!"
     Some CGM vendors are limiting which iOS versions, and therefore which phones, are supported by their apps.

docs/version/development.md

@@ -27,8 +27,8 @@ This section summarizes differences found in the`dev` branch compared to `main`.
 
 | <div style="width:140px"> branch | version # | <div style="width:140px">last updated | comments |
 |:--|:--|:--|:--|
-| main | 3.10.0 | TBD Jan 2026 | release|
-| dev | 3.11.0 | TBD Jan 2026 | same as main, except version number |
+| main | 3.10.0 | 10 Jan 2026 | release|
+| dev | 3.11.0 | 10 Jan 2026 | same as main, except version number |
 | [feat/pod-keep-alive](#feature-branch-pod-keep-alive-feature)<br>- SHA `52106b8` | 3.9.5 | 07 Jan 2026| - uses the OmniBLE pod-keep-alive branch to support users of iPhone 16 phones with InPlay BLE (-Atlas) DASH pods<br>  - SHA for OmniBLE is `61e3ef9`<br>**Please read [Feature Branch: Pod Keep Alive Feature](#feature-branch-pod-keep-alive-feature)** |
 | [feat/dev-dana-medtrum](#feature-branch-medtrum-and-dana-support) <br>- SHA `ca0463d` | 3.9.5 | 08 Jan 2026 | - adds experimental support for Dana and Medtrum pumps<br>- this branch is ready for expert testers to evaluate and report back<br>  - SHA for DanaKit is `bad8fad`<br>  - SHA for MedtrumKit is ` 0905638` |
 
@@ -322,9 +322,10 @@ Know how to generate an `Issue Report` and `Export a Critical Event Log` when yo
 * An `Issue Report` is a log file generated by the *Loop* app that has a lot of information the developers can parse to figure out what *Loop* was doing when you were having a problem. Some items go back 84 hours (pump and cgm messages), others are limited to a few hours (decision arrays) and some items are overall status (build version number and phone model / iOS).
 * A `Critical Event Log` contains a zip of 7 individual zips. Each zip is for one day and contains the complete set of data used for Loop decision making. The event log goes back 7 full days.
 
-To issue these reports
-* `Loop Settings` and then scroll almost to the bottom and select `Issue Report` and share
-* `Loop Settings` and then scroll almost to the bottom and select `Export a Critical Event Log` and share
+To issue these reports:
+
+* `Loop Settings` and then scroll almost to the bottom and select `Issue Report` and thenm share
+* `Loop Settings` and then scroll almost to the bottom and select `Export a Critical Event Log` and then share
 
 ### Create a Debug Report
 

docs/version/releases.md

@@ -37,7 +37,7 @@ Release information is found on the [*GitHub*&nbsp;_<span translate="no">LoopKit
 
 ## Loop v3.10.0
 
-[*Loop* v3.10.0](https://github.com/LoopKit/LoopWorkspace/releases/tag/v3.10.0) was released on TBD January 2027.
+[*Loop* v3.10.0](https://github.com/LoopKit/LoopWorkspace/releases/tag/v3.10.0) was released on 10 January 2027.
 
 #### Customization Update for v3.10.0
 

mkdocs.yml

@@ -54,7 +54,7 @@ markdown_extensions:
     - attr_list
     - def_list
     - pymdownx.arithmatex:
-        generic: true
+         generic: true
     - pymdownx.details
     - pymdownx.emoji:
         emoji_index: !!python/name:material.extensions.emoji.twemoji