AWS Security ChangesHomeSearch

AWS linux documentation change

Service: linux · 2025-05-01 · Documentation low

File: linux/al2023/ug/managing-repos-os-updates.md

Summary

Fixed spelling of 'priviledged' to 'privileged' in multiple sections discussing package update operations

Security assessment

The change corrects a spelling error but does not address any security vulnerability or introduce new security documentation. The content remains focused on standard update procedures without security context.

Diff

diff --git a/linux/al2023/ug/managing-repos-os-updates.md b/linux/al2023/ug/managing-repos-os-updates.md
index cf6df80d4..1c79cf644 100644
--- a//linux/al2023/ug/managing-repos-os-updates.md
+++ b//linux/al2023/ug/managing-repos-os-updates.md
@@ -85 +85 @@ The `dnf check-update` command is now used to check updates available in the [20
-Applying package updates is a priviledged operation. Although elevating privileges is typically not required when running in a container, if running in a non-containerized environment such as an Amazon EC2 instance, you can _check_ for updates without elevating privileges. 
+Applying package updates is a privileged operation. Although elevating privileges is typically not required when running in a container, if running in a non-containerized environment such as an Amazon EC2 instance, you can _check_ for updates without elevating privileges. 
@@ -152 +152 @@ The `dnf check-update` command is now used to check updates available in the `la
-Applying package updates is a priviledged operation. Although elevating privileges is typically not required when running in a container, if running in a non-containerized environment such as an Amazon EC2 instance, you can _check_ for updates without elevating privileges. 
+Applying package updates is a privileged operation. Although elevating privileges is typically not required when running in a container, if running in a non-containerized environment such as an Amazon EC2 instance, you can _check_ for updates without elevating privileges. 
@@ -227 +227 @@ The `dnf upgrade` command is now used to apply all of the updates present in the
-Applying package updates is a priviledged operation. Although elevating privileges is typically not required when running in a container, if running in a non-containerized environment such as an Amazon EC2 instance, you will need to run the `dnf upgrade` command as the `root` user. This can be done using the `sudo` or `su` commands. 
+Applying package updates is a privileged operation. Although elevating privileges is typically not required when running in a container, if running in a non-containerized environment such as an Amazon EC2 instance, you will need to run the `dnf upgrade` command as the `root` user. This can be done using the `sudo` or `su` commands. 
@@ -485 +485 @@ The `dnf upgrade` command is now used to apply updates available in the `latest`
-Applying package updates is a priviledged operation. Although elevating privileges is typically not required when running in a container, if running in a non-containerized environment such as an Amazon EC2 instance, you will need to run the `dnf upgrade` command as the `root` user. This can be done using the `sudo` or `su` commands. 
+Applying package updates is a privileged operation. Although elevating privileges is typically not required when running in a container, if running in a non-containerized environment such as an Amazon EC2 instance, you will need to run the `dnf upgrade` command as the `root` user. This can be done using the `sudo` or `su` commands.