Skip to content

Commit 3d092a9

Browse files
committed
Update hosting static content docs
1 parent 66672e3 commit 3d092a9

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/nginxaas-azure/quickstart/hosting-static-content-blob-storage.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ F5 NGINXaaS for Azure (NGINXaaS) can serve static content stored in Azure Blob S
2020

2121
### Step 1: Upload static files to the $web container
2222

23-
Place your static files in the `$web` container in your storage account. This is the standard container used for static website hosting in Azure.
23+
Upload your static files to the `$web` container in your storage account. This is the standard container used for static website hosting in Azure.
2424

2525
### Step 2: Configure network access
2626

@@ -40,7 +40,7 @@ Place your static files in the `$web` container in your storage account. This is
4040
4. Optionally, set an **Error document path** for 404 errors.
4141
5. Click **Save**.
4242

43-
Note the **Primary endpoint** URL that appears after enabling static website hosting. You'll need this for your NGINX configuration.
43+
Note the **Primary endpoint** URL that appears after enabling static website hosting. You'll use this URL in your NGINX configuration.
4444

4545
## Configure NGINXaaS
4646

@@ -99,10 +99,10 @@ Upload your NGINX configuration to your NGINXaaS deployment following the instru
9999

100100
## Verify traffic routing
101101

102-
You can verify that requests are properly routed through your NGINXaaS deployment by checking the Azure Storage logs:
102+
You can verify that requests are properly routed through your NGINXaaS deployment by examining the Azure Storage logs:
103103

104104
1. Enable logging for your storage account if not already enabled.
105-
2. In the storage logs, you should see requests coming from the private IP address of your NGINXaaS deployment, not from public Internet addresses.
105+
2. In the storage logs, you should see requests originating from the private IP address of your NGINXaaS deployment, not from public Internet addresses.
106106

107107
## Benefits of this approach
108108

0 commit comments

Comments
 (0)