Standardize placeholders in attestation, confidential-ledger, and payment-hsm docsets

Author: msmbaldwin

articles/attestation/private-endpoint-powershell.md

@@ -34,7 +34,7 @@ Create a resource group with [New-AzResourceGroup](/powershell/module/az.resourc
 ```azurepowershell-interactive
 ## Create to your Azure account subscription and create a resource group in a desired location. ##
 Connect-AzAccount
-Set-AzSubscription "mySubscription"
+Set-AzSubscription "<subscription-name>"
 $rg = "CreateAttestationPrivateLinkTutorial-rg"
 $loc= "eastus"
 New-AzResourceGroup -Name $rg -Location $loc
@@ -109,7 +109,7 @@ $attestationProvider = New-AzAttestation -Name $attestationProviderName -Resourc
 $attestationProviderId = $attestationProvider.Id
 ```
 ## Access the attestation provider from local machine ##
-Enter `nslookup <provider-name>.attest.azure.net`. Replace **\<provider-name>** with the name of the attestation provider instance you created in the previous steps. 
+Enter `nslookup <provider-name>.attest.azure.net`. Replace `<provider-name>` with the name of the attestation provider instance you created in the previous steps. 
 ```azurepowershell-interactive
 ## Access the attestation provider from local machine ##
 nslookup myattestationprovider.eus.attest.azure.net
@@ -189,7 +189,7 @@ In this section, you'll use the virtual machine you created in the previous step
 
 8. Open Windows PowerShell on the server after you connect.
 
-9. Enter `nslookup <provider-name>.attest.azure.net`. Replace **\<provider-name>** with the name of the attestation provider instance you created in the previous steps:
+9. Enter `nslookup <provider-name>.attest.azure.net`. Replace `<provider-name>` with the name of the attestation provider instance you created in the previous steps:
 
     ```azurepowershell-interactive
     ## Access the attestation provider from local machine ##

articles/attestation/quickstart-azure-cli.md

@@ -68,13 +68,13 @@ Here are commands you can use to create and manage the attestation provider:
 1. Run the [az attestation create](/cli/azure/attestation#az-attestation-create) command to create an attestation provider without policy signing requirement:
 
    ```azurecli
-   az attestation create --name "myattestationprovider" --resource-group "MyResourceGroup" --location westus
+   az attestation create --name "<attestation-provider-name>" --resource-group "<resource-group>" --location westus
    ```
 
 1. Run the [az attestation show](/cli/azure/attestation#az-attestation-show) command to retrieve attestation provider properties such as status and AttestURI:
 
    ```azurecli
-   az attestation show --name "myattestationprovider" --resource-group "MyResourceGroup"
+   az attestation show --name "<attestation-provider-name>" --resource-group "<resource-group>"
    ```
 
    This command displays values like the following output:
@@ -94,7 +94,7 @@ Here are commands you can use to create and manage the attestation provider:
 You can delete an attestation provider by using the [az attestation delete](/cli/azure/attestation#az-attestation-delete) command:
 
 ```azurecli
-az attestation delete --name "myattestationprovider" --resource-group "sample-resource-group"
+az attestation delete --name "<attestation-provider-name>" --resource-group "<resource-group>"
 ```
 
 ## Policy management
@@ -104,7 +104,7 @@ Use the commands described here to provide policy management for an attestation
 The [az attestation policy show](/cli/azure/attestation/policy#az-attestation-policy-show) command returns the current policy for the specified TEE:
 
 ```azurecli
-az attestation policy show --name "myattestationprovider" --resource-group "MyResourceGroup" --attestation-type SGX-IntelSDK
+az attestation policy show --name "<attestation-provider-name>" --resource-group "<resource-group>" --attestation-type SGX-IntelSDK
 ```
 
 > [!NOTE]
@@ -127,7 +127,7 @@ az attestation policy set --name testatt1 --resource-group testrg --attestation-
 To set policy in JWT format for a given kind of attestation type using file path:
 
 ```azurecli
-az attestation policy set --name "myattestationprovider" --resource-group "MyResourceGroup" \
+az attestation policy set --name "<attestation-provider-name>" --resource-group "<resource-group>" \
 --attestation-type SGX-IntelSDK -f "{file_path}" --policy-format JWT
 ```
 

articles/confidential-ledger/create-power-automate-workflow.md

@@ -174,7 +174,7 @@ Create a workflow that:
 
 1. Create a ledger entry action:
 
-   - **Ledger name**: Use `your-ledger-name` (not the full URL, just the name).
+   - **Ledger name**: Use `<ledger-name>` (not the full URL, just the name).
    - **Collection ID**: Use `audit-logs` (optional: leave empty for default collection).
    - **Entry contents**: Use the following command:
 

articles/confidential-ledger/includes/confidential-ledger-rg-create.md

@@ -7,15 +7,15 @@ ms.author: msmbaldwin
 
 ---
 
-A resource group is a logical container into which Azure resources are deployed and managed. Use the Azure CLI [az group create](/cli/azure/group#az-group-create) command or the Azure PowerShell [New-AzResourceGroup](/powershell/module/az.resources/new-azresourcegroup) cmdlet to create a resource group named *myResourceGroup* in the *eastus* location.
+A resource group is a logical container into which Azure resources are deployed and managed. Use the Azure CLI [az group create](/cli/azure/group#az-group-create) command or the Azure PowerShell [New-AzResourceGroup](/powershell/module/az.resources/new-azresourcegroup) cmdlet to create a resource group in your desired location.
 
 # [Azure CLI](#tab/azure-cli)
 ```azurecli
-az group create --name "myResourceGroup" -l "EastUS"
+az group create --name "<resource-group>" -l "EastUS"
 ```
 # [Azure PowerShell](#tab/azurepowershell)
 
 ```azurepowershell
-New-AzResourceGroup -Name myResourceGroup -Location eastus
+New-AzResourceGroup -Name <resource-group> -Location eastus
 ```
 ---

articles/confidential-ledger/quickstart-cli.md

@@ -40,7 +40,7 @@ Your result is in the format `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`.
 Use the Azure CLI [az confidentialledger create](/cli/azure/confidentialledger#az-confidentialledger-create) command to create a confidential ledger in your new resource group.
 
 ```azurecli
-az confidentialledger create --name "myLedger" --resource-group "myResourceGroup" --location "EastUS" --ledger-type "Public" --aad-based-security-principals ledger-role-name="Administrator" principal-id="<your-principal-id>"
+az confidentialledger create --name "<ledger-name>" --resource-group "<resource-group>" --location "EastUS" --ledger-type "Public" --aad-based-security-principals ledger-role-name="Administrator" principal-id="<principal-id>"
 ```
 
 A successful operation returns the properties of the newly created ledger. Take note of the **ledgerUri**. In our example, this URI is "https://myledger.confidential-ledger.azure.com".
@@ -52,7 +52,7 @@ You need this URI to transact with the confidential ledger from the data plane.
 You can view the properties associated with your newly created confidential ledger using the Azure CLI [az confidentialledger show](/cli/azure/confidentialledger#az-confidentialledger-show) command.
 
 ```azurecli
-az confidentialledger show --name "myLedger" --resource-group "myResourceGroup"
+az confidentialledger show --name "<ledger-name>" --resource-group "<resource-group>"
 ```
 
 The returned JSON object displays the ledger's properties, including your role:
@@ -64,7 +64,7 @@ The returned JSON object displays the ledger's properties, including your role:
 To update the properties of a confidential ledger, use do so, use the Azure CLI [az confidentialledger update](/cli/azure/confidentialledger#az-confidentialledger-update) command. For instance, to update your ledger to change your role to "Reader", run:
 
 ```azurecli
-az confidentialledger update --name "myLedger" --resource-group "myResourceGroup" --ledger-type "Public" --aad-based-security-principals ledger-role-name="Reader" principal-id="<your-principal-id>" 
+az confidentialledger update --name "<ledger-name>" --resource-group "<resource-group>" --ledger-type "Public" --aad-based-security-principals ledger-role-name="Reader" principal-id="<principal-id>" 
 ```
 
 If you again run [az confidentialledger show](/cli/azure/confidentialledger#az-confidentialledger-show), you see that the role is updated.

articles/confidential-ledger/quickstart-net.md

@@ -82,7 +82,7 @@ using Azure.Security.ConfidentialLedger.Certificate;
 
 ### Authenticate and create a client
 
-In this quickstart, logged in user is used to authenticate to Azure confidential ledger, which is preferred method for local development. The name of your confidential ledger is expanded to the key vault URI, in the format "https://\<your-confidential-ledger-name\>.confidential-ledger.azure.com". This example is using ['DefaultAzureCredential()'](/dotnet/api/azure.identity.defaultazurecredential) class from [Azure Identity Library](/dotnet/api/overview/azure/identity-readme), which allows to use the same code across different environments with different options to provide identity. 
+In this quickstart, logged in user is used to authenticate to Azure confidential ledger, which is preferred method for local development. The name of your confidential ledger is expanded to the key vault URI, in the format `https://<ledger-name>.confidential-ledger.azure.com`. This example is using ['DefaultAzureCredential()'](/dotnet/api/azure.identity.defaultazurecredential) class from [Azure Identity Library](/dotnet/api/overview/azure/identity-readme), which allows to use the same code across different environments with different options to provide identity. 
 
 ```csharp
 credential = DefaultAzureCredential()
@@ -151,7 +151,7 @@ namespace acl_app
 
             // Replace with the name of your confidential ledger
 
-            const string ledgerName = "myLedger";
+            const string ledgerName = "<ledger-name>";
             var ledgerUri = $"https://{ledgerName}.confidential-ledger.azure.com";
 
             // Create a confidential ledger client using the ledger URI and DefaultAzureCredential

articles/confidential-ledger/quickstart-powershell.md

@@ -42,8 +42,7 @@ Your result is listed under "Id", in the format `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxx
 Use the Azure PowerShell [New-AzConfidentialLedger](/powershell/module/az.confidentialledger/new-azconfidentialledger) command to create a confidential ledger in your new resource group.
 
 ```azurepowershell
-New-AzConfidentialLedger -Name "myLedger" -ResourceGroupName "myResourceGroup" -Location "EastUS" -LedgerType "Public" -AadBasedSecurityPrincipal @{ LedgerRoleName="Administrator"; PrincipalId="aaaaaaaa-bbbb-cccc-1111-222222222222"; }
-
+New-AzConfidentialLedger -Name "<ledger-name>" -ResourceGroupName "<resource-group>" -Location "EastUS" -LedgerType "Public" -AadBasedSecurityPrincipal @{ LedgerRoleName="Administrator"; PrincipalId="<principal-id>"; }
 ```
 
 A successful operation returns the properties of the newly created ledger. Take note of the **ledgerUri**. In the example above, this URI is "https://myledger.confidential-ledger.azure.com".
@@ -55,13 +54,13 @@ You need this URI to transact with the confidential ledger from the data plane.
 You can view the properties associated with your newly created confidential ledger using the Azure PowerShell [Get-AzConfidentialLedger](/powershell/module/az.confidentialledger/get-azconfidentialledger) cmdlet.
 
 ```azurepowershell
-Get-AzConfidentialLedger -Name "myLedger" -ResourceGroupName "myResourceGroup"
+Get-AzConfidentialLedger -Name "<ledger-name>" -ResourceGroupName "<resource-group>"
 ```
 
 To update the properties of a confidential ledger, use do so, use the Azure PowerShell [Update-AzConfidentialLedger](/powershell/module/az.confidentialledger/update-azconfidentialledger) cmdlet. For instance, to update your ledger to change your role to "Reader", run:
 
 ```azurepowershell
-Update-AzConfidentialLedger -Name "myLedger" -ResourceGroupName "myResourceGroup" -Location "EastUS" -LedgerType "Public" -AadBasedSecurityPrincipal @{ LedgerRoleName="Reader"; PrincipalId="aaaaaaaa-bbbb-cccc-1111-222222222222"; }
+Update-AzConfidentialLedger -Name "<ledger-name>" -ResourceGroupName "<resource-group>" -Location "EastUS" -LedgerType "Public" -AadBasedSecurityPrincipal @{ LedgerRoleName="Reader"; PrincipalId="<principal-id>"; }
 ```
 
 If you again run [Get-AzConfidentialLedger](/powershell/module/az.confidentialledger/get-azconfidentialledger), you see that the role is updated.

articles/confidential-ledger/quickstart-python.md

@@ -92,15 +92,15 @@ Next, use the [DefaultAzureCredential Class](/python/api/azure-identity/azure.id
 credential = DefaultAzureCredential()
 ```
 
-Finish setup by setting some variables for use in your application: the resource group (myResourceGroup), the name of ledger you want to create, and two urls to be used by the data plane client library.
+Finish setup by setting some variables for use in your application: the resource group, the name of ledger you want to create, and two urls to be used by the data plane client library.
 
   > [!Important]
-  > Each ledger must have a globally unique name. Replace \<your-unique-ledger-name\> with the name of your ledger in the following example.
+  > Each ledger must have a globally unique name. Replace `<ledger-name>` with the name of your ledger in the following example.
 
 ```python
-resource_group = "<azure-resource-group>"
-ledger_name = "<your-unique-ledger-name>"
-subscription_id = "<azure-subscription-id>"
+resource_group = "<resource-group>"
+ledger_name = "<ledger-name>"
+subscription_id = "<subscription-id>"
 
 identity_url = "https://identity.confidential-ledger.core.azure.com"
 ledger_url = "https://" + ledger_name + ".confidential-ledger.azure.com"
@@ -223,9 +223,9 @@ from azure.confidentialledger.certificate import ConfidentialLedgerCertificateCl
 
 # Set variables
 
-resource_group = "<azure-resource-group>"
-ledger_name = "<your-unique-ledger-name>"
-subscription_id = "<azure-subscription-id>"
+resource_group = "<resource-group>"
+ledger_name = "<ledger-name>"
+subscription_id = "<subscription-id>"
 
 identity_url = "https://identity.confidential-ledger.core.azure.com"
 ledger_url = "https://" + ledger_name + ".confidential-ledger.azure.com"
@@ -329,7 +329,7 @@ Other Azure confidential ledger articles can build upon this quickstart. If you
 Otherwise, when you're finished with the resources created in this article, use the Azure CLI [az group delete](/cli/azure/group?#az-group-delete) command to delete the resource group and all its contained resources:
 
 ```azurecli
-az group delete --resource-group myResourceGroup
+az group delete --resource-group <resource-group>
 ```
 
 ## Next steps

articles/confidential-ledger/verify-write-transaction-receipts.md

@@ -102,8 +102,8 @@ It's assumed that both the receipt and the service certificate can be loaded fro
 import json 
 
 # Constants
-service_certificate_file_name = "<your-service-certificate-file>"
-receipt_file_name = "<your-receipt-file>"
+service_certificate_file_name = "<service-certificate-file>"
+receipt_file_name = "<receipt-file>"
 
 # Use the receipt and the service identity to verify the receipt content 
 with open(service_certificate_file_name, "r") as service_certificate_file, open( 

articles/confidential-ledger/write-transaction-receipts.md

@@ -42,7 +42,7 @@ The following are the constant values used to set up the Azure Confidential Ledg
 
 ```python
 # Constants for our program 
-ledger_name = "<your-unique-ledger-name>" 
+ledger_name = "<ledger-name>" 
 identity_url = "https://identity.confidential-ledger.core.azure.com" 
 ledger_url = "https://" + ledger_name + ".confidential-ledger.azure.com" 
 ```
@@ -123,7 +123,7 @@ from azure.confidentialledger.certificate import ConfidentialLedgerCertificateCl
 from receipt_verification import verify_receipt 
 
 # Constants 
-ledger_name = "<your-unique-ledger-name>" 
+ledger_name = "<ledger-name>" 
 identity_url = "https://identity.confidential-ledger.core.azure.com" 
 ledger_url = "https://" + ledger_name + ".confidential-ledger.azure.com"