Merge pull request #22 from loopandlearn/release_4.4

Update for changes with LoopFollow v4.4

Author: marionbarker

docs/build/build-options.md

@@ -3,60 +3,11 @@
 *LoopFollow* can be built using either the Browser Build or the Mac-Xcode Build method.  A paid Apple Developer account is required to use the Browser Build method.  Regardless of how you build, you can customize your *LoopFollow* app’s name.
 
 * Browser Build: 
-    * If you have never built, see [LoopFollow Browser Build](lf-browser-build.md)
-    * If you are a repeat builder, then you need a one-time update [Browser Build Update for *LoopFollow* v4.0](#browser-build-update-for-loopfollow-v40)
+    * If you have never built, see [*LoopFollow* Browser Build](lf-browser-build.md)
+    * If you are updating from v3.x or older, you need follow the one-time steps to [Update from *LoopFollow* v3.x](lf-browser-build.md#update-from-loopfollow-v3x){: target="_blank" }
 * Mac-Xcode: [Build *LoopFollow* Script for Mac-Xcode](#build-loopfollow-script-for-mac-xcode)
 
-### Browser Build Update for *LoopFollow* v4.0
-
-!!! important "New Capability with LoopFollow v4.0"
-    A new capability was added to LoopFollow regarding remote commands which **requires a one-time update** to your LoopFollow **Identifier**. Browser Build will fail until you take these steps.
-
-It doesn't matter whether the person you follow uses *Loop* or *Trio*. You have to update the Identifiers or the Browser Build will fail.
-
-This requires you to follow these steps:
-
-#### Sync Your *LoopFollow* fork
-
-* Go to your *LoopFollow* fork and click on the Sync button
-* If your browser build already failed, it already did the sync for you
-
-> ![sync the fork](img/github-build-check-fork-status.svg){width="700"}
-
-#### Add Push Notifications Capability to LoopFollow Identifiers
-
-You must manually enable the Push Notifications capabilty to the *LoopFollow* Identifier. Follow the directions below to open the Identifier and then keep scrolling down until you see Push Notifications. Make sure that check box is enabled, as shown in the graphic below. If you do not do this, the Build will fail.
-
-The example graphic below has numbered steps that match these directions:
-
-Click to open the [Certificates, Identifiers & Profiles: Identifiers List](https://developer.apple.com/account/resources/identifiers/list) page. 
-
-1. Locate the LoopFollow Identifer and click on it to open the `Edit your App ID Configuration` screen
-    * The name in the **`NAME`** column may be different if you previously built with a Mac using Xcode, in that case it will start with XC
-2. Looking at the `Capabilities` column, scroll down to the `Push Notifications` row
-3. If the check box is not checked, you must check it
-4. Scroll back to the top and hit Save if you modified that value or All Identifiers if you made no changes
-
-If you made a change and hit Save, you then need to Tap `Continue` and Tap `Save` to complete the process.
-
-> ![graphic showing selection of the push notifications](img/add-push-notifications.svg){width="600"}
-
-Repeat this step if you use LoopFollow_Second or LoopFollow_Third.
-
-#### Run `Build LoopFollow`
-
-1. Click on the Actions tab of your *LoopFollow* repository
-2. On the left side, click on `4. Build LoopFollow`
-3. On the right side, click Run Workflow to show a dropdown menu
-4. Tap the green button that says Run workflow.
-
-> ![add identifiers](img/action-04-build.svg){width="700"}
-
-**Once this completes, be sure to update from TestFlight to get the updated version of *LoopFollow* on your phone.**
-
-Repeat the build and install from TestFlight steps if you use LoopFollow_Second or LoopFollow_Third.
-
-### Build LoopFollow Script for Mac-Xcode
+### Build *LoopFollow* Script for Mac-Xcode
 
 Carefully read the information in the terminal before making any choices.
 
@@ -86,30 +37,40 @@ You are prompted to enter a custom name if you want or you can continue using th
 
 To test a specific feature that is only found in the dev branch, choose option 4. This is not typical, and only builds to the app associated with Looper #1
 
-### Run LoopFollow on Mac using TestFlight
+- - -
+
+## Run *LoopFollow* on Mac
+
+You can run *LoopFollow* on your Mac if you choose.
+
+* [Run *LoopFollow* on Mac using TestFlight](#run-loopfollow-on-mac-using-testflight)
+* [Run *LoopFollow* on Mac with Mac-Xcode Build](#run-loopfollow-on-mac-with-mac-xcode-build)
+
+
+### Run *LoopFollow* on Mac using TestFlight
 
-If you used the Browser Build method, follow these instructions to run LoopFollow on your Mac computer using TestFlight. (You can also use an iPad.)
+If you used the Browser Build method, follow these instructions to run *LoopFollow* on your Mac computer using TestFlight. (You can also use an iPad.)
 
 * You need to install the TestFlight app on your computer
 * The TestFlight app on the Mac shows the same set of builds and uses the same installation procedure as shown in LoopDocs for installing apps on a phone from TestFlight
 * Install on computer from TestFlight
 * You need to enter the data source and configuration values into the app on your computer
 
-From Mac system settings/notifications, scroll down to LoopFollow and enable notifications with the options you want.
+From Mac system settings/notifications, scroll down to *LoopFollow* and enable notifications with the options you want.
 
-### Run LoopFollow on your Mac with Mac-Xcode Build
+### Run *LoopFollow* on Mac with Mac-Xcode Build
 
-1. Build LoopFollow to your Mac with Xcode (choose My Mac (Mac Catalyst) as the device)
+1. Build *LoopFollow* to your Mac with Xcode (choose My Mac (Mac Catalyst) as the device)
 2. Click Stop to close the running app that is started by Xcode
 3. On the left side of Xcode, click on the Folder icon
-4. Click to open the LoopFollow folder list
-5. Click to open the LoopFollow/Products folder
+4. Click to open the *LoopFollow* folder list
+5. Click to open the *LoopFollow*/Products folder
 6. Right-click (or Control-click) on “LoopFollow.app” and select Show in Finder
 7. First time on the Mac:
     * Drag the LoopFollow.app icon to your Applications folder in Finder
-    * From Mac system settings/notifications, scroll down to LoopFollow and enable notifications with the options you want
+    * From Mac system settings/notifications, scroll down to *LoopFollow* and enable notifications with the options you want
 8. When updating on your Mac
-    * Make sure you close the LoopFollow app currently running on your computer
+    * Make sure you close the *LoopFollow* app currently running on your computer
     * Drag the LoopFollow.app icon to your Applications folder in Finder
     * Most people choose to replace the application, but you can keep both if you prefer
     * All configurations and settings are maintained
@@ -122,13 +83,13 @@ From Mac system settings/notifications, scroll down to LoopFollow and enable not
 
 ### Updates
 
-When modifications and versions are updated, you might see activity at GitHub. Please wait for the release message to be posted at [LoopFollow Releases](https://github.com/loopandlearn/LoopFollow/releases) before using the updated versions for the `main` branch of LoopFollow, LoopFollow_Second and LoopFollow_Third.
+When modifications and versions are updated, you might see activity at GitHub. Please wait for the release message to be posted at [*LoopFollow* Releases](https://github.com/loopandlearn/LoopFollow/releases) before using the updated versions for the `main` branch of *LoopFollow*, *LoopFollow_Second* and *LoopFollow_Third*.
 
 ### Version Numbers
 
 Updates to the `main` branch (releases) have a version number that ends in 0; for example, 3.1.0.
 
 * Immediately following the release, the `dev` branch is at the same version as `main` indicating the code is identical
 * Each time a feature is merged into the `dev` branch, the final number increments; for example, 3.1.1, 3.1.2
-* When the next release is made, the second digit is incremented and the final digit is restore to 0 for both `main` and `dev`; for example, 3.2.0
+* When the next release is made, the second digit is incremented and the final digit is restored to 0 for both `main` and `dev`; for example, 3.2.0