AWS eks documentation change
Summary
Corrected grammatical errors in checksum verification instructions for kubectl installation
Security assessment
Changes improve clarity but don't alter security content. Checksum verification remains a security best practice, but these are minor grammatical fixes.
Diff
diff --git a/eks/latest/userguide/install-kubectl.md b/eks/latest/userguide/install-kubectl.md index 03560f17f..f04310ebc 100644 --- a//eks/latest/userguide/install-kubectl.md +++ b//eks/latest/userguide/install-kubectl.md @@ -150 +150 @@ Procedure: - 3. Make sure that the generated checksum in the output matches in the checksum in the downloaded `kubectl.sha256` file. + 3. Make sure that the generated checksum in the output matches the checksum in the downloaded `kubectl.sha256` file. @@ -248 +248 @@ or - 3. For the first, you should see `kubectl: OK`, for the second, you can check that the generated checksum in the output matches in the checksum in the downloaded `kubectl.sha256` file. + 3. For the first, you should see `kubectl: OK`, for the second, you can check that the generated checksum in the output matches the checksum in the downloaded `kubectl.sha256` file. @@ -350 +350 @@ or - 3. For the first, you should see `kubectl: OK`, for the second, you can check that the generated checksum in the output matches in the checksum in the downloaded `kubectl.sha256` file. + 3. For the first, you should see `kubectl: OK`, for the second, you can check that the generated checksum in the output matches the checksum in the downloaded `kubectl.sha256` file. @@ -448 +448 @@ Procedure: - 3. Make sure that the generated checksum in the output matches in the checksum in the downloaded `kubectl.sha256` file. The PowerShell output should be an uppercase equivalent string of characters. + 3. Make sure that the generated checksum in the output matches the checksum in the downloaded `kubectl.sha256` file. The PowerShell output should be an uppercase equivalent string of characters.