modify language to small and capital letters

Author: marionbarker

docs/browser/intro-summary.md

@@ -118,7 +118,7 @@ You need to keep a digital copy of your 6 <code>Secrets</code>.
 !!! important "Use a Text-Only Editor"
     **Be sure to use a Text-Only editor like NotePad (PC) or TextEdit (Mac) to archive your information.**
 
-    If you use a "smart" editor, it may change little letters to capital letters at the beginning of a line when you paste items into your archive file.
+    If you use a "smart" editor, it may change small letters to capital letters at the beginning of a line when you paste items into your archive file.
 
     If even one character is capitalized when it should not be, you will get errors.
 

docs/browser/prepare-fork.md

@@ -188,7 +188,7 @@ Once all six <code>Secrets</code> have been added to your <code>LoopWorkspace</c
 ![all secrets entered](img/gh-done-adding-secrets.png){width="700"}
 {align="center"}
 
-### Enter Variables
+### Add Variable
 
 This is a new step. It is already included in the `dev` branch and will be included in the `main` branch when `Loop 3.6.0` is released.
 

docs/build/build-errors.md

@@ -462,7 +462,7 @@ Or you may see `Unable to process request - PLA Update available. You currently
 ![img/container-1.png](img/container-1.png){width="750"}
 {align="center"}
 
-**Solution**: To resolve this error, you will need to click on the Loop target's signing area and then the plus-sign in the App Groups area under the signing. Copy and paste the bundle indentifier into the new container that starts with `group.` and then add `Group` to the end of the name. Click OK to save. Note, the line will start with lower case `group.` followed by your bundle identifier and an upper case `Group` added to the end of the bundle identifier.
+**Solution**: To resolve this error, you will need to click on the Loop target's signing area and then the plus-sign in the App Groups area under the signing. Copy and paste the bundle indentifier into the new container that starts with `group.` and then add `Group` to the end of the name. Click OK to save. Note, the line will start with small letter `group.` followed by your bundle identifier and a capital letter `Group` added to the end of the bundle identifier.
 
 ![img/container-2.png](img/container-2.png){width="750"}
 {align="center"}

docs/version/build-time-flag.md

@@ -15,7 +15,7 @@ The `Build Time Flags` are available for both build methods:
     * You can edit the version in your LoopWorkspace folder (it shows up as the top item in the Xcode folder view) - or - if you use the build script, you can edit the copy found in ~/Downloads/BuildLoop after the first time you use the script. 
         * If you edit `~/Downloads/BuildLoop/LoopConfigOverride.xcconfig`, the "flags" you add are applied to this download and all subsequent downloads created with the script.
 
-These flags are always upper case with underscore separating words for clarity, for example `MY_EXAMPLE_FLAG`. If you have more than one flag, they are separated by a space. Do not enter a line break between selections; in other words, do not hit return or enter. Xcode will automatically word-wrap the line for clarity. All values need to be on a single line.
+These flags are always capital letters with underscore separating words for clarity, for example `MY_EXAMPLE_FLAG`. If you have more than one flag, they are separated by a space. Do not enter a line break between selections; in other words, do not hit return or enter. Xcode will automatically word-wrap the line for clarity. All values need to be on a single line.
 
 Copy the text below, add it to the end of your LoopConfigOverride.xcconfig file and then insert the desired flags in place of `MY_EXAMPLE_FLAG`. If you want more than one flag, separate them by a space.