document grabbing output

src/bicep/README.md

@@ -260,7 +260,7 @@ Before giving this a try, it's probably a good idea to [review the Azure CLI's d
 
 First off, let's say you deployed Mission Landing Zone with a deployment name of `myMissionLandingZone`:
 
-```azcli
+```plaintext
 az deployment sub create \
   --name "myMissionLandingZone" \
   --location "East US" \
@@ -269,39 +269,39 @@ az deployment sub create \
 
 Once it's complete, you could see all the resources provisioned by that deployment querying the `properties.outputResources` property:
 
-```azcli
+```plaintext
 az deployment sub show \
   --name "myMissionLandingZone" \
   --query "properties.outputResources"
 ```
 
 That's a lot of resources. Thankfully, the template produces outputs for just the things you probably need at `properties.outputs`:
 
-```azcli
+```plaintext
 az deployment sub show \
   --name "myMissionLandingZone" \
   --query "properties.outputs"
 ```
 
 For example, if you need just the Firewall Private IP address you could retrieve it like this:
 
-```azcli
+```plaintext
 az deployment sub show \
   --name "myMissionLandingZone" \
   --query "properties.outputs.firewallPrivateIPAddress.value"
 ```
 
 Or, if you need just the Log Analytics Workspace that performs central logging you could retrieve it like this:
 
-```azcli
+```plaintext
 az deployment sub show \
   --name "myMissionLandingZone" \
   --query "properties.outputs.logAnalyticsWorkspaceResourceId.value"
 ```
 
 Or, say you wanted to deploy resources into the Identity spoke. You could retrieve information about the Identity spoke by querying it from the `properties.outputs.spokes` array like this:
 
-```azcli
+```plaintext
 az deployment sub show \
   --name "myMissionLandingZone" \
   --query "properties.outputs.spokes.value[?name=='identity']"