AWS workspaces documentation change
Summary
Corrected apostrophe usage in contractions (changed curly apostrophes to straight apostrophes) and made minor grammatical improvements without altering technical content.
Security assessment
Changes involve punctuation corrections ('it’s' to 'it's', 'WorkSpaces’' to 'WorkSpaces''') with no modifications to security configurations, protocols, or vulnerability-related content. No evidence of security vulnerability fixes or security feature additions.
Diff
diff --git a/workspaces/latest/adminguide/modify-workspaces.md b/workspaces/latest/adminguide/modify-workspaces.md index b61f88214..3dd06c705 100644 --- a//workspaces/latest/adminguide/modify-workspaces.md +++ b//workspaces/latest/adminguide/modify-workspaces.md @@ -80 +80 @@ If you want to increase both volumes, you must wait 20-30 minutes for the first - * Non-GPU-enabled WorkSpaces’ root volume cannot be less than 175 GB when the user volume is 100 GB. Storage requirements for GPU-enabled WorkSpaces scale proportionally with instance sizing. As you select larger GPU-enabled WorkSpaces configurations, you must allocate correspondingly larger storage volumes to maintain optimal performance and accommodate increased workload demands. For the smallest instance size, begin with the following storage allocation: Root: 100 GB, User: 100 GB. GPU-enabled WorkSpaces support a minimum of 100 GB for the root volume and 100 GB for the user volume. + * Non-GPU-enabled WorkSpaces' root volume cannot be less than 175 GB when the user volume is 100 GB. Storage requirements for GPU-enabled WorkSpaces scale proportionally with instance sizing. As you select larger GPU-enabled WorkSpaces configurations, you must allocate correspondingly larger storage volumes to maintain optimal performance and accommodate increased workload demands. For the smallest instance size, begin with the following storage allocation: Root: 100 GB, User: 100 GB. GPU-enabled WorkSpaces support a minimum of 100 GB for the root volume and 100 GB for the user volume. @@ -239 +239 @@ The console provides a guided experience to change the protocol of a WorkSpace f - 1. [Optional] Reboot your WorkSpace and wait until it’s in the `AVAILABLE` state before modifying the protocol. + 1. [Optional] Reboot your WorkSpace and wait until it's in the `AVAILABLE` state before modifying the protocol. @@ -241 +241 @@ The console provides a guided experience to change the protocol of a WorkSpace f - 2. [Optional] Use the `describe-workspaces` command to list the WorkSpace properties. Ensure that it’s in the `AVAILABLE` state and its current `Protocol` is accurate. + 2. [Optional] Use the `describe-workspaces` command to list the WorkSpace properties. Ensure that it's in the `AVAILABLE` state and its current `Protocol` is accurate. @@ -255 +255 @@ The `Protocols` property is case-sensitive. Ensure that you use `PCOIP` or `WSP` - 5. Use the `describe-workspaces` command again to list the WorkSpace properties and verify that it’s in an `AVAILABLE` state and the current `Protocols` property has been changed to the correct protocol. + 5. Use the `describe-workspaces` command again to list the WorkSpace properties and verify that it's in an `AVAILABLE` state and the current `Protocols` property has been changed to the correct protocol.