Update LoopDocs for release 3.6.0

Release/3.6.0

Author: marionbarker

docs/browser/automatic.md

@@ -17,11 +17,12 @@ Regardless of your choice, please [Disable Automatic Installation from *TestFlig
 You still need to **take these actions** to ensure a recent build of the *Loop* app is available in *TestFlight* for you to install on your phone when you choose:
 
 * Keep your *Apple Developer* account up to date with agreements signed
-* [Renew Certificate](bb-update.md#renew-certificate){: target="_blank" } once a year
+* Check your *GitHub* action if you ever get an email saying an automatic action failed
+* Look at your *TestFlight* app on the second of every month to make sure a new build is available for you to install when you are ready
 
 ### Successful Weekly Action
 
-Normally, you will see a successful `build action` once a week. This happens at 08:00 UTC every Wednesday.
+Normally, you will see a successful `build action` once a week. This happens every Wednesday.
 
 If there are no updates to the `main` branch, your actions show a very short, successful `build action` as shown in the graphic below. It only takes about a minute because the logic says - no update then skip the build. 
 
@@ -33,7 +34,7 @@ In that case, you should check your favorite information site to find out what t
 
 ### Successful Monthly Action
 
-On the first day of every month at 06:00 UTC, 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.
+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.
 
 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.)
 
@@ -67,9 +68,7 @@ The `alive` branch you need is created automatically when you run the `Build Loo
 
 ## Automatic Certificates
 
-Coming soon with `Loop 3.6.0`. 
-
-Already here with `LoopCaregiver`, `LoopFollow` and some other Open-Source apps.
+Automatic renewal of certificates is included in `Loop 3.6.0`.
 
 ### Requirements
 
@@ -86,11 +85,11 @@ You must have the `ENABLE_NUKE_CERTS` variable set to `true` for your *GitHub* o
     * You need a new `Distribution` Certificate at *Apple*
     * You need to create new signing credentials for `Match-Secrets`
 
-    For the `Loop` app, up through version 3.4.4, you must to do this [Renew Certificate](bb-update.md#renew-certificate){: target="_blank" } process manually. Once version 3.6.0 is released, it will be automatic.
+    For the `Loop` app, up through version 3.4.4, you had to do this [Renew Certificate](bb-update.md#renew-certificate){: target="_blank" } process manually. Now that version 3.6.0 is released, it is automatic.
 
 ### Automatic Certificate Renewal
 
-Some Open-Source apps, in particular `Trio`, `LoopCaregiver` and `LoopFollow` already have this capability. It will be available in with the next release of the *Loop* app (3.6.0).
+Some Open-Source apps, in particular `Trio`, `LoopCaregiver`, `LoopFollow` and `Loop` have automatic certificate renewal.
 
 * If your signing credentials for the app being built are invalid and `ENABLE_NUKE_CERTS` is `true`, then signing credentials will be cleared from your `Match-Secrets` repository, a new `Distribution` certificate will be created at *Apple* and signing credentials for the current app will be generated and stored in `Match-Secrets`.
 
@@ -106,13 +105,13 @@ The times are shifted to make sure only one Open-Source app performs a `nuke` ac
 
 | Open-Source App | AutoCerts? | Wed<br>UTC | 1st of Month<br>UTC |
 |:--|:-:|:-:|:-:|
-| <span translate="no">Loop</span> | `dev` only | 09:00 | 07:00 |
+| <span translate="no">Loop</span> | &#x2705; | 09:00 | 07:00 |
 | <span translate="no">LoopCaregiver</span> | &#x2705; | 13:00 | 11:00 |
 | <span translate="no">LoopFollow</span> | &#x2705; | 12:00 | 10:00 |
 | <span translate="no">LoopFollow_Second</span> | &#x2705; | 12:20 | 10:20 |
 | <span translate="no">LoopFollow_Third</span> | &#x2705; | 12:40 | 10:40 |
 | <span translate="no">Trio</span> | &#x2705; | 08:00 | 06:00 |
-| <span translate="no">xDrip4iOS</span> | n | 16:00 | 14:00 |
+| <span translate="no">xDrip4iOS</span> | &#x274C; | 16:00 | 14:00 |
 
 
 ## Modify Automatic Building

docs/browser/bb-errors.md

@@ -3,7 +3,7 @@
 !!! important "Get Help, Not Frustrated"
     For first-time builders, there are a lot of one-time steps that all have to be correct and many screens look similar.
 
-    If you are updating your build or renewing certificates, the process can be confusing and some error messages can be misleading.
+    If you are updating your build, the process can be confusing and some error messages can be misleading.
 
     If you are having trouble, don't hesitate to ask for help.
 
@@ -61,7 +61,6 @@ Mentors can go to your public&nbsp;_<span translate="no">GitHub repository</span
 
     **Solution**:
 
-    * For `Loop`: wait for 3.6.0 release (coming soon), all other apps are updated
     * Manually sync your fork of the repository: [Update `Fork`](bb-update.md#update-fork){: target="_blank" }
     * Manually start your build: [Build](bb-update.md#build-the-app){: target="_blank" }
 
@@ -78,7 +77,7 @@ If you get an error when building with a browser, you can use this page to figur
 !!! important "Certificate is missing"
     If you get this build error message: `No code signing identity found and can not create a new one because you enabled`, you do not have certificates needed to run the build.
 
-    * See [Renew Certificates](bb-update.md#renew-certificate){: target="_blank" }
+    * With `Loop 3.6.0` and newer, this should not happen. Make sure you [Add Variable](prepare-fork.md#add-variable){: target="_blank" } to automatically renew certificates.
 
 These are some of the most common errors to date.
 
@@ -137,13 +136,11 @@ This is an example of a message that is not terribly descriptive - which is why
 
 ### Missing Certificates
 
-> Coming soon: when Loop 3.6.0 (or newer) is available, certificates will be automatically renewed if your developer account is up to date, all agreements are signed and you completed the new [Add Variable](prepare-fork.md#add-variable){: target="_blank" } step.
-
-> After Loop 3.6.0 is released, the first attempt to build will update the files required for automatic certificate creation. The second attempt to build will use the new files. So if the first attempt with Loop 3.6.0 fails, try again.
+> With `Loop 3.6.0` or newer, certificates are automatically renewed if your developer account is up to date, all agreements are signed and you completed the new [Add Variable](prepare-fork.md#add-variable){: target="_blank" } step.
 
 If your certificates have expired, you will see this error when you try to build. It does not have a clear annotation. The error string starts with: `No code signing identity found and can not create a new one because you enabled`.
 
-* See [Renew Certificates](bb-update.md#renew-certificate){: target="_blank" }
+> The first automatic build when Loop 3.6.0 is released will update the files required for automatic certificate creation. The next automatic build will use the new files. So if the first attempt with Loop 3.6.0 fails, try again.
 
 ![graphic showing missing distribution certificate](img/missing-distribution-certificate.png){width="800"}
 {align="center"}
@@ -441,9 +438,7 @@ Copy the words on the line below and paste them into the search function for you
 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 these *Actions* again:
-        * `Create Certificates`
-        * `Build Loop`
+    * 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`.
@@ -475,9 +470,8 @@ For example, you might see:
 
 Return to [First-Time: Identifiers for the `Loop` app](prepare-app.md#identifiers-for-the-loop-app) and make sure you followed all the steps.
 
-You must create certificates again before you can build *Loop*:
+You can build *Loop*:
 
-* Action: `Create Certificates`
 * Action: `Build Loop`
 
 ### `Error: A new one cannot be created because you enabled`
@@ -701,4 +695,4 @@ The `Identifier` that is associated with the `Loop` identifier cannot be deleted
 
 If coming here because you enter the wrong `TEAMID` in `Secrets` - return to [Rerun Steps with Correct TEAMID](#rerun-steps-with-correct-teamid) when you've deleted as many identifiers as you can.
 
-After you delete identifiers, you must add them back before you can build a given app. Configure them and create certificates before you can build again.
+After you delete identifiers, you must add them back before you can build a given app. Configure them and build again.

docs/browser/bb-overview.md

@@ -50,7 +50,6 @@ The steps on these pages must be completed for you to build an app using a brows
 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" }
 
 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.
@@ -101,9 +100,7 @@ There is also a helpful video for this process. Once again, this was prepared fo
 
 * [How to Update and Rebuild DIY Loop with a Web Browser](https://www.youtube.com/watch?v=0ipTsiqbbrQ){: target="_blank" }
 
-After 3.6.0 is released, certificates will be automatically renewed. In the meantime, they must be renewed manually using these instructions:
-
-* [Renew Certificates](bb-update.md#renew-certificate){: target="_blank" }
+> With `Loop 3.6.0`, certificates are automatically created and renewed. You no longer need to renew certificates as a separate step.
 
 ## Other Topics