Skip to content

Commit e76d5df

Browse files
author
naman-msft
committed
updated doc
1 parent d00a526 commit e76d5df

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

scenarios/azure-docs/articles/confidential-computing/confidential-enclave-nodes-aks-get-started.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,8 +50,8 @@ First, create a resource group for the cluster by using the `az group create` co
5050
```bash
5151
export RANDOM_SUFFIX="$(openssl rand -hex 3)"
5252
export RESOURCE_GROUP="myResourceGroup$RANDOM_SUFFIX"
53-
export LOCATION="eastus2"
54-
az group create --name $RESOURCE_GROUP --location $LOCATION
53+
export REGION="eastus2"
54+
az group create --name $RESOURCE_GROUP --location $REGION
5555
```
5656

5757
Results:

scenarios/azure-management-docs/articles/azure-linux/quickstart-azure-cli.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,8 @@ To deploy the application, you use a manifest file to create all the objects req
103103
104104
1. Create a file named `aks-store-quickstart.yaml` and copy in the following manifest:
105105
106-
```yaml
106+
```bash
107+
cat <<EOF > aks-store-quickstart.yaml
107108
apiVersion: apps/v1
108109
kind: StatefulSet
109110
metadata:
@@ -390,6 +391,7 @@ To deploy the application, you use a manifest file to create all the objects req
390391
selector:
391392
app: store-front
392393
type: LoadBalancer
394+
EOF
393395
```
394396
395397
If you create and save the YAML file locally, then you can upload the manifest file to your default directory in CloudShell by selecting the **Upload/Download files** button and selecting the file from your local file system.

0 commit comments

Comments
 (0)