AWS drs documentation change
Summary
Fixed various typos and grammatical errors in the failback performing guide (e.g., 'by via' to 'via', 'clock the on' to 'clock on', 'sutable' to 'suitable').
Security assessment
The changes are purely editorial corrections to improve clarity and readability. There is no mention of security vulnerabilities, patches, or new security features. The content about network requirements (TCP 1500) and UTC clock settings remains unchanged in substance.
Diff
diff --git a/drs/latest/userguide/failback-performing.md b/drs/latest/userguide/failback-performing.md index c8f879040..2e91adc12 100644 --- a//drs/latest/userguide/failback-performing.md +++ b//drs/latest/userguide/failback-performing.md @@ -36 +36 @@ Prior to performing a failback, ensure that you meet all [replication network re - * The Failback Client must be able to communicate with the Recovery instance on TCP 1500, this can be done either by via a private route (VPN/DX) or a public route (public IP assigned to the recovery instance) + * The Failback Client must be able to communicate with the Recovery instance on TCP 1500, this can be done either via a private route (VPN/DX) or a public route (public IP assigned to the recovery instance) @@ -48 +48 @@ Prior to performing a failback, ensure that you meet all [replication network re - * Ensure the hardware clock the on the server on which the Failback Client is run is set to UTC rather than Local Time. + * Ensure the hardware clock on the server on which the Failback Client is run is set to UTC rather than Local Time. @@ -110 +110 @@ Replication from the source instance to the source server (in the target AWS Reg - 4. Boot the Failback Client ISO on the server you want fail back to. This can be the original source server that is paired with the recovery instance, or a different server. + 4. Boot the Failback Client ISO on the server you want to fail back to. This can be the original source server that is paired with the recovery instance, or a different server. @@ -122 +122 @@ Ensure that the server you are failing back to has the same number of volumes or - 5. If you plan on using a static IP for the Failback Client, run following once the Failback Client ISO boots: + 5. If you plan on using a static IP for the Failback Client, run the following once the Failback Client ISO boots: @@ -260 +260 @@ There are three formats supported: -You may use either ":" or "=" as CSV fields separator which is more sutable for Windows drive letters. Examples are: +You may use either ":" or "=" as CSV fields separator which is more suitable for Windows drive letters. Examples are: @@ -312 +312 @@ We will use the example of SCSI identifiers from the command output below: -To use block device SCSI identifies like 'pci-0000:00:10.0-scsi-0:0:0:0' you need to add to command line:`--dm-value-format by-path` +To use block device SCSI identifiers like 'pci-0000:00:10.0-scsi-0:0:0:0' you need to add to command line:`--dm-value-format by-path` @@ -328 +328 @@ When using the failback client, you can fail back to the original source server -Te ensure that the original source server has not been deleted and still exists, check its status in the AWS DRS console. Source servers that have been deleted or no longer exist will show as having **Lag** and being **Stalled**. +To ensure that the original source server has not been deleted and still exists, check its status in the AWS DRS console. Source servers that have been deleted or no longer exist will show as having **Lag** and being **Stalled**. @@ -336 +336 @@ If the original source server is healthy and you decide to fail back to it, it w -You can tell whether you are failing back to the original or a new source servers in the recovery instance details view under **Failback status**. +You can tell whether you are failing back to the original or a new source server in the recovery instance details view under **Failback status**.