AngularJS - Copyedits

docs/framework/angular/files.md

@@ -4,8 +4,8 @@ As a developer working with CiviCRM-Angular, you write *Angular modules* --
 these modules are composed of various JS/CSS/HTML files which define the
 *services*, *directives*, *controllers*, and *HTML partials*.
 
-For sake of predictability, these files follow a naming convention.  All
-major Angular files are placed in the `ang/` folder.
+For sake of predictability, these files are placed in the `ang/` folder, and
+they follow a naming convention.
 
 !!! note "How does this work with `civix`?"
     When you generate Angular code via `civix`, the files are

docs/framework/angular/loader.md

 # AngularJS: Loader
 
-What happens when a user visits a CiviCR-Angular page? For example, let's
+What happens when a user visits a CiviCRM-Angular page? For example, let's
 consider this URL:
 
  * `https://example.org/civicrm/a/#/caseType`
@@ -9,8 +9,8 @@ Broadly speaking, two things happen:
 
  1. (Server-side) CiviCRM processes the request for `civicrm/a`. It
     displays a web-page with all your Angular modules -- such as
-    `crmAttachment`, `crmCaseType`, `crmUi`, and so on.
- 2. (Client-side) AngularJS processes the request.  It finds that the
+    `ngRoute`, `crmAttachment`, `crmCaseType`, `crmUi`, and so on.
+ 2. (Client-side) AngularJS processes the HTML/JS/CSS.  It finds that the
     module `crmCaseType` includes a route for `#/caseType` and loads the
     appropriate HTML template.
 
@@ -19,7 +19,7 @@ The client-side behavior is well-defined by Angular
 server-side in greater depth because that is unique to the CiviCRM-Angular
 integration.
 
-!!! caution "Discusses new/experimental interfaces"
+!!! caution "Caution: Discusses new/experimental interfaces"
 
     Some elements of this document have been around since CiviCRM v4.6
     and should remain well-supported. Other elements are new circa v4.7.21