Skip to content

Commit 47d1f2a

Browse files
fix 3 instances of "exsisting"
1 parent 5931f46 commit 47d1f2a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/cloud-services/applications-dont-support-tls-1-2.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,7 @@ EXIT /B 0
205205

206206
## Step 3: Add the startup task to the role’s service definition (csdef)
207207

208-
Add the following snippet to your exsisting service definition file.
208+
Add the following snippet to your existing service definition file.
209209

210210

211211
```
@@ -249,7 +249,7 @@ Here is an example that shows both the worker role and web role.
249249

250250
1) In Visual Studio, right-click on your WebRole
251251
2) Select **Add**
252-
3) Select **Exsisting Item**
252+
3) Select **Existing Item**
253253
4) In the file explorer, navigate to your desktop where you stored the **TLSsettings.ps1** and **RunTLSSettings.cmd** files
254254
5) Select the two files to add them to your Cloud Services project
255255

@@ -264,7 +264,7 @@ To ensure the scripts are uploaded with every update pushed from Visual Studio,
264264

265265
## Step 7: Publish & Validate
266266

267-
Now that the above steps have been complete, publish the update to your exsisting Cloud Service.
267+
Now that the above steps have been complete, publish the update to your existing Cloud Service.
268268

269269
You can use [SSLLabs](https://www.ssllabs.com/) to validate the TLS status of your endpoints
270270

0 commit comments

Comments
 (0)