Merge pull request #203510 from kgremban/patch-2

Update how-to-control-access.md

Author: PRMerger13

articles/iot-dps/how-to-control-access.md

@@ -30,7 +30,7 @@ When using key-based authentication, the Device Provisioning Service uses securi
 
 In some cases you may need to use the HTTP Device Provisioning Service REST APIs directly, without using the SDKs. The following sections describe how to authenticate directly against the REST APIs.
 
-## Device API Authentication
+## Device API authentication
 
 The [Device API](/rest/api/iot-dps/device/runtime-registration) is used by devices to attest to the Device Provisioning Service and receive an IoT Hub connection.
 
@@ -129,7 +129,7 @@ curl -L -i -X PUT –cert ./[device_cert].pem –key ./[device_cert_private_key]
 
 ```
 
-## Service API Authentication
+## Service API authentication
 
 The [Service API](/rest/api/iot-dps/service/device-registration-state) is used to retrieve registration state and remove device registrations. The service is also used by backend apps to programmatically manage both [individual groups](/rest/api/iot-dps/service/individual-enrollment) and [enrollment groups](/rest/api/iot-dps/service/enrollment-group). The Service API supports key-based authentication for backend apps.  
 
@@ -176,7 +176,7 @@ The security token has the following format:
 
 `SharedAccessSignature sig={signature}&se={expiry}&skn={policyName}&sr={URL-encoded-resourceURI}`
 
-Here are the expected values:
+Here are the expected values
 
 | Value | Description |
 | --- | --- |
@@ -302,4 +302,4 @@ The following table lists the permissions you can use to control access to your
 [lnk-sdks]: ../iot-hub/iot-hub-devguide-sdks.md
 [lnk-management-portal]: https://portal.azure.com
 [lnk-azure-resource-manager]: ../azure-resource-manager/management/overview.md
-[lnk-resource-provider-apis]: /rest/api/iot-dps/
+[lnk-resource-provider-apis]: /rest/api/iot-dps/