Merge pull request #260 from leo-schick/fix-documentation

fix documentation
Azure · Jan 13, 2024 · 265fd17 · 265fd17
2 parents a7d34a3 + ee958b6
commit 265fd17
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/Saas.Identity/Saas.IdentityProvider/readme.md b/src/Saas.Identity/Saas.IdentityProvider/readme.md
@@ -133,7 +133,7 @@ The `initConfig` section of `config.json`must be filled out manually (see more d
     "azureb2c": {
       "location": "Europe", // enter a valid Azure B2C region here. This is not the same as 'location' above.
       "countryCode": "DK", // enter a valid country code.
-      "skuName": "PremiumP1", // can be Standard, PremiumP1 or PremiumP2.
+      "skuName": "PremiumP1", // can be PremiumP1 or PremiumP2.
       "tier": "A0" // leave this as 'A0'
     }
   },... // leave the remaining part of the configuration manifest unchanged for now.

diff --git a/src/Saas.Identity/Saas.Permissions/readme.md b/src/Saas.Identity/Saas.Permissions/readme.md
@@ -96,7 +96,7 @@ This is a two step process:
 1. The Azure App Configuration `connection string` can either be found in the Azure Portal by navigating to your Azure App Configuration instance, that was deployed as part of the Identity Foundation. Or, it can be obtained using this az cli command: 
 
 ```bash
-az appconfig credential list --name "<name of your azure app configuration> --query [0].connectionString"
+az appconfig credential list --name "<name of your azure app configuration>" "--query [0].connectionString"
 ```
 
 In the Azure Portal you can find the connection string here: