Merge pull request #177845 from msmbaldwin/acl-misc

Lowercasing service name

Author: Court72

articles/confidential-ledger/architecture.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Confidential Ledger architecture
-description: Azure Confidential Ledger architecture
+title: Azure confidential ledger architecture
+description: Azure confidential ledger architecture
 services: confidential-ledger
 author: msmbaldwin
 ms.service: confidential-ledger
@@ -11,17 +11,17 @@ ms.author: mbaldwin
 ---
 # Architecture
 
-The Azure Confidential Ledger, a REST API service, allows users to interact with the ledger through administrative and functional API calls.  When data is recorded to the ledger, it is sent to the permissioned blockchain nodes that are secure enclaved backed replicas. The replicas follow a consensus concept. A user can also retrieve receipts for the data that has been committed to the ledger.
+The Azure confidential ledger, a REST API service, allows users to interact with the ledger through administrative and functional API calls.  When data is recorded to the ledger, it is sent to the permissioned blockchain nodes that are secure enclaved backed replicas. The replicas follow a consensus concept. A user can also retrieve receipts for the data that has been committed to the ledger.
 
 There is also an optional consortium notion that will support multi-party collaboration in the future.
 
 ## Architecture diagram
 
-This image provides an architectural overview of Azure Confidential Ledger, and shows Azure Confidential Ledger Users interacting with the Cloud APIs for a created ledger.
+This image provides an architectural overview of Azure confidential ledger, and shows Azure confidential ledger Users interacting with the Cloud APIs for a created ledger.
 
 :::image type="content" source="./media/architecture-overview.png" alt-text="Architecture Overview":::
 
 ## Next steps
 
-- [Overview of Microsoft Azure Confidential Ledger](overview.md)
-- [Authenticating Azure Confidential Ledger nodes](authenticate-ledger-nodes.md)
+- [Overview of Microsoft Azure confidential ledger](overview.md)
+- [Authenticating Azure confidential ledger nodes](authenticate-ledger-nodes.md)

articles/confidential-ledger/authenticate-ledger-nodes.md

@@ -1,6 +1,6 @@
 ---
-title: Authenticating Azure Confidential Ledger nodes
-description: Authenticating Azure Confidential Ledger nodes
+title: Authenticating Azure confidential ledger nodes
+description: Authenticating Azure confidential ledger nodes
 services: confidential-ledger
 author: msmbaldwin
 ms.service: confidential-ledger
@@ -9,22 +9,22 @@ ms.date: 04/15/2021
 ms.author: mbaldwin
 
 ---
-# Authenticating Azure Confidential Ledger nodes
+# Authenticating Azure confidential ledger nodes
 
-Azure Confidential Ledger nodes can be authenticated by code samples and by users.
+Azure confidential ledger nodes can be authenticated by code samples and by users.
 
 ## Code samples
 
 When initializing, code samples get the node certificate by querying Identity Service. After retrieving the node certificate, a code sample will query the Ledger network to get a quote, which is then validated using the Host Verify binaries. If the verification succeeds, the code sample proceeds to Ledger operations.
 
 ## Users
 
-Users can validate the authenticity of Confidential Ledger nodes to confirm they are indeed interfacing with their Ledger’s enclave. You can build trust in Confidential Ledger nodes in a few ways, which can be stacked on one another to increase the overall level of confidence. As such, Steps 1-2 help build confidence in that Confidential Ledger enclave as part of the initial TLS handshake and authentication within functional workflows. Beyond that, a persistent client connection is maintained between the user’s client and the Confidential Ledger.
+Users can validate the authenticity of Azure confidential ledger nodes to confirm they are indeed interfacing with their Ledger’s enclave. You can build trust in Azure confidential ledger nodes in a few ways, which can be stacked on one another to increase the overall level of confidence. As such, Steps 1-2 help build confidence in that Azure confidential ledger enclave as part of the initial TLS handshake and authentication within functional workflows. Beyond that, a persistent client connection is maintained between the user's client and the confidential ledger.
 
-- **Validating the Confidential Ledger node**: This is accomplished by querying the identity service hosted by Microsoft, which provides a network cert and thus helps verify that the Ledger node is presenting a cert endorsed/signed by the network cert for that specific instance. Similar to PKI-based HTTPS, a server’s cert is signed by a well-known Certificate Authority (CA) or intermediate CA. In the case of Confidential Ledger, the CA cert is returned by an Identity service in the form of a network cert. This is an important confidence building measure for users of Confidential Ledger. If this node cert isn’t signed by the returned network cert, the client connection should fail (as implemented in the sample code).
-- **Validate the Confidential Ledger enclave**: The Confidential Ledger runs in an Intel® SGX enclave that’s represented by a Quote, a data blob generated inside that enclave. It can be used by any other entity to verify that the quote has been produced from an application running with Intel® SGX protections. The quote is structured in a way that enables easy verification. It contains claims that help identify various properties of the enclave and the application that it’s running. This is an important confidence building mechanism for users of the Confidential Ledger. This can be accomplished by calling a functional workflow API to get an enclave quote. The client connection should fail if the quote is invalid. The retrieved quote can then be validated with the open_enclaves Host_Verify tool. More details about this can be found here.
+- **Validating a confidential ledger node**: This is accomplished by querying the identity service hosted by Microsoft, which provides a network cert and thus helps verify that the Ledger node is presenting a cert endorsed/signed by the network cert for that specific instance. Similar to PKI-based HTTPS, a server’s cert is signed by a well-known Certificate Authority (CA) or intermediate CA. In the case of Azure confidential ledger, the CA cert is returned by an Identity service in the form of a network cert. This is an important confidence building measure for users of confidential ledger. If this node cert isn’t signed by the returned network cert, the client connection should fail (as implemented in the sample code).
+- **Validating a confidential ledger enclave**: A confidential ledger runs in an Intel® SGX enclave that’s represented by a Quote, a data blob generated inside that enclave. It can be used by any other entity to verify that the quote has been produced from an application running with Intel® SGX protections. The quote is structured in a way that enables easy verification. It contains claims that help identify various properties of the enclave and the application that it’s running. This is an important confidence building mechanism for users of the confidential ledger. This can be accomplished by calling a functional workflow API to get an enclave quote. The client connection should fail if the quote is invalid. The retrieved quote can then be validated with the open_enclaves Host_Verify tool. More details about this can be found here.
 
 ## Next steps
 
-- [Overview of Microsoft Azure Confidential Ledger](overview.md)
-- [Azure Confidential Ledger architecture](architecture.md)
+- [Overview of Microsoft Azure confidential ledger](overview.md)
+- [Azure confidential ledger architecture](architecture.md)

articles/confidential-ledger/create-client-certificate.md

@@ -1,6 +1,6 @@
 ---
-title: Creating a Client Certificate with Microsoft Azure Confidential Ledger
-description: Creating a Client Certificate with Microsoft Azure Confidential Ledger
+title: Creating a Client Certificate with Microsoft Azure confidential ledger
+description: Creating a Client Certificate with Microsoft Azure confidential ledger
 services: confidential-ledger
 author: msmbaldwin
 ms.service: confidential-ledger
@@ -11,7 +11,7 @@ ms.author: mbaldwin
 ---
 # Creating a Client Certificate
 
-The Confidential Ledger APIs require client certificate-based authentication. Only those certificates added to an allowlist during Ledger Creation or Ledger Update can be used to call the Confidential Ledger Functional APIs.
+The Azure confidential ledger APIs require client certificate-based authentication. Only those certificates added to an allowlist during Ledger Creation or Ledger Update can be used to call the confidential ledger Functional APIs.
 
 You will need a certificate in PEM format. You can create more than one certificate and add or delete them using Ledger Update API.
 
@@ -31,4 +31,4 @@ openssl req -new -key "privkey_name.pem" -x509 -nodes -days 365 -out "cert.pem"
 
 ## Next steps
 
-- [Overview of Microsoft Azure Confidential Ledger](overview.md)
+- [Overview of Microsoft Azure confidential ledger](overview.md)

articles/confidential-ledger/faq.md

@@ -1,6 +1,6 @@
 ---
-title: Frequently asked questions for Azure Confidential Ledger
-description: Frequently asked questions for Azure Confidential Ledger
+title: Frequently asked questions for Azure confidential ledger
+description: Frequently asked questions for Azure confidential ledger
 services: confidential-ledger
 author: msmbaldwin
 ms.service: confidential-ledger
@@ -11,11 +11,11 @@ ms.author: mbaldwin
 
 ---
 
-# Frequently asked questions for Azure Confidential Ledger
+# Frequently asked questions for Azure confidential ledger
 
 ## How can I tell if the ACC Ledger service would be useful to my organization?
 
-Confidential Ledger is ideal for organizations with records valuable enough for a motivated attacker to try to compromise the underlying logging/storage system, including "insider" scenarios where a rogue employee might attempt to forge, modify, or remove previous records.
+Azure confidential ledger is ideal for organizations with records valuable enough for a motivated attacker to try to compromise the underlying logging/storage system, including "insider" scenarios where a rogue employee might attempt to forge, modify, or remove previous records.
 
 ## What makes ACC Ledger much more secure?
 
@@ -27,10 +27,10 @@ Not necessarily. Some solutions today require users to maintain write receipts f
 
 ## How do I verify Ledger's authenticity?
 
-You can verify that the Ledger server nodes that your client is communicating with are authentic. For details, see [Authenticating Confidential Ledger Nodes](authenticate-ledger-nodes.md).
+You can verify that the Ledger server nodes that your client is communicating with are authentic. For details, see [Authenticating confidential ledger Nodes](authenticate-ledger-nodes.md).
 
 
 
 ## Next steps
 
-- [Overview of Microsoft Azure Confidential Ledger](overview.md)
+- [Overview of Microsoft Azure confidential ledger](overview.md)

articles/confidential-ledger/index.yml

@@ -18,11 +18,11 @@ landingContent:
 # Cards and links should be based on top customer tasks or top subjects
 # Start card title with a verb
   # Card
-  - title: About Azure Confidential Ledger
+  - title: About Azure confidential ledger
     linkLists:
       - linkListType: overview
         links:
-          - text: What is Azure Confidential Ledger?
+          - text: What is Azure confidential ledger?
             url: overview.md
 
   # Card
@@ -56,7 +56,7 @@ landingContent:
             url: create-client-certificate.md
           - text: Register a Ledger service principal
             url: register-ledger-service-principal.md
-          - text: Register the Confidential Ledger resource provider
+          - text: Register the Azure confidential ledger resource provider
             url: register-ledger-resource-provider.md
   # Card
   - title: References