Skip to content

Commit 5d34aa4

Browse files
authored
Update issues-using-vm-extensions-python-3.md
1 parent cd764b8 commit 5d34aa4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/virtual-machines/extensions/issues-using-vm-extensions-python-3.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -41,11 +41,11 @@ Consider these general recommendations before deploying extensions in the known-
4141

4242
- For example, for **Python 2.7**, use: `sudo apt update && sudo apt install python-is-python2`
4343

44-
1. This recommendation is for Azure customers and is not supported in Azure Stack:
44+
1. This recommendation is for Azure customers and isn't supported in Azure Stack:
4545

46-
- If you’ve already deployed an instance that exhibits this problem, use the Run command functionality in the VM blade to run the commands mentioned above. The Run command extension itself is not affected by the transition to Python 3.8.
46+
- If you’ve already deployed an instance that exhibits this problem, use the Run command functionality in the VM blade to run the commands mentioned above. The Run command extension itself isn't affected by the transition to Python 3.8.
4747

48-
1. If you are deploying a new instance, and need to set an extension at provisioning time, use **cloud-init** user data to install the packages mentioned above.
48+
1. If you're deploying a new instance, and need to set an extension at provisioning time, use **cloud-init** user data to install the packages mentioned above.
4949

5050
For example, for Python 2.7:
5151

0 commit comments

Comments
 (0)