Editorial fix suggestions

draft-ietf-scim-device-model.mkd

@@ -134,18 +134,22 @@ Some might ask why SCIM is well suited for this purpose and not, for
 example, NETCONF {{?RFC6241}} or RESTCONF {{?RFC8040}} with YANG
 {{?RFC7950}}. After all, there are all sorts of existing models
 available. The answer is four fold:
+
 - First, NETCONF and RESTCONF focus on **configuration** rather than
   provisioning.
+
 - Second, SCIM is designed with inter-domain provisioning in mind.
   The use of HTTP as a substrate permits both user-based authentication
   for local provisioning applications, as well as OAUTH or certificate-
-  based authentication.  the inter-domain nature of these operations
+  based authentication.  The inter-domain nature of these operations
   does not expose local policy, which itself must be (and often is)
   configured with other APIs, many of which are not standardized.
+
 - SCIM is also a familiar tool within the enterprise enviroment, used
   extensively to configure federated user accounts.  (Amusingly, one
   author noted a billboard in San Francisco highlighting a SCIM as
   part of a product capability.)
+
 - Finally, once one chooses a vehicle such as SCIM, one is beholden
   to its data model.  The SCM data model is articulated in {{!RFC7643}}.
 
@@ -176,7 +180,7 @@ The client may be one of a number of entities:
    (BRSKI) {{?RFC8995}}.
 
  - A client application that administrators or employees use to add,
-   remove, or get information about devices. An example might be an
+   remove, or get information about devices. An example might be a
    tablet or phone app that scans Wi-fi Easy Connect QR codes.
 
 ~~~~~
@@ -290,7 +294,7 @@ The "active" attribute is of type "boolean" and is a mutable
 attribute, and is required. If set to TRUE, it means that this device
 is intended to be operational. Attempts to control or access a device
 where this value is set to FALSE may fail. For example, when used in
-conjunction with NIPC {{?I-D.brinckman-nipc}}, commands such as
+conjunction with NIPC {{?I-D.ietf-asdf-nipc}}, commands such as
 connect, disconnect, subscribe that control app sends to the
 controller for the devices any command coming from the control app for
 the device will be rejected by the controller.
@@ -1315,4 +1319,4 @@ a trust anchor through FDO's TO2 process.  This is shown below.
 
 ~~~~~~~~
 {::include fdo-example-two.atxt}
-~~~~~~~~
+~~~~~~~~