Add note about how to get patches added to kernel.spec applied

Fix typo s/kublet/kubelet/

modules/ROOT/pages/grub2-bootloader.adoc

@@ -309,7 +309,7 @@ bootable by *GRUB2*.
 
 .Before you start
 
-* Get the Fedora Live ISO from link:https://download.fedoraproject.org/pub/fedora/linux/releases/[getfedora.org].
+* Get the Fedora Live ISO from link:https://fedoraproject.org[fedoraproject.org].
 
 * Prepare a bootable device using the downloaded ISO, either a CD or a USB.
 

modules/ROOT/pages/index.adoc

@@ -6,7 +6,7 @@ This is a collection of short HOW-TO and FAQ-style documentation for Fedora user
 
 This documentation is community-made. Your xref:contribute-to-quick-docs.adoc[contributions and improvements ]are welcome!
 
-If you cannot find an answer here, you may also get help on https://ask.fedoraproject.org[Ask Fedora], our questions-and-answers forum.
+If you cannot find an answer here, you may also get https://discussion.fedoraproject.org/c/ask/6/none[Ask Fedora], our questions-and-answers forum.
 
 Fedora Docs team empowers contributors to create and maintain user documentation by providing https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/tools-file-edit-pagure/[self-starter's guide] and https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/asciidoc-markup/[other resources].
 

modules/ROOT/pages/kernel-build-custom.adoc

@@ -138,8 +138,9 @@ git switch f28
 picked up during the build automatically.
 
 .. Patches can also be kept in seperate files and added to `kernel.spec` with
-`Patch2: foo.patch`, `Patch3: bar.patch`, etc. They should be applied
-automatically during the build process.
+`Patch2: foo.patch`, `Patch3: bar.patch`, etc. Matching `ApplyOptionalPatch foo.patch`,
+`ApplyOptionalPatch bar.patch` lines must be added to apply the patches during
+the build process.
 
 .. To make your own modifications to the kernel source, retrieve the kernel
 sources for your current dist-git branch with `fedpkg sources`, then make

modules/ROOT/pages/reset-root-password.adoc

@@ -27,7 +27,7 @@ While booting the system, the xref:grub2-bootloader.adoc[GRUB2] menu will be dis
 
 . Select the boot entry you wish to edit with the arrow keys.
 
-. Select the entry you with to edit by pressing *e*.
+. Select the entry you wish to edit by pressing *e*.
 
 . Use the arrow keys to go to select the line beginning with `linux`, `linux16`, or `linuxefi`.
 

modules/ROOT/pages/upgrading-fedora-offline.adoc

@@ -66,7 +66,7 @@ You can also use `{NEXTVER}` to upgrade to a link:https://fedoraproject.org/wiki
 * If you want to remove/install some packages manually before running `dnf system-upgrade download` again, it is advisable to perform those operations with `--setopt=keepcache=1` dnf command line option.
   Otherwise the whole package cache will be removed after your operation, and you will need to download all the packages once again.
 
-. When the new GPG key is imported, you are asked to verify the key's fingerprint. Refer to link:https://getfedora.org/security[https://getfedora.org/security] to do so.
+. When the new GPG key is imported, you are asked to verify the key's fingerprint. Refer to link:https://fedoraproject.org/security[https://fedoraproject.org/security] to do so.
 
 . Trigger the upgrade process. This will reboot your machine (immediately!, without a countdown or confirmation, so close other programs and save your work) into the upgrade process running in a console terminal:
 +

modules/ROOT/pages/using-kubernetes-kubelet.adoc

@@ -14,7 +14,7 @@ include::partial$3rdparty-message.adoc[]
 [[overview]]
 == kubelet overview
 
-The ```kublet``` is the Kubernetes agent that runs on every node in a cluster. ```kublet``` is installed using the kubernetes rpm (_e.g._ ```kubernetes1.30``` is a versioned rpm for Kubernetes v1.30). The ```kubelet``` runs as a systemd service on Fedora. In early implementations, the ```kubelet``` was configured via link:https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/[flags] that were set in a systemd unit file and passed to the ```kubelet``` as command line parameters.
+The ```kubelet``` is the Kubernetes agent that runs on every node in a cluster. ```kubelet``` is installed using the kubernetes rpm (_e.g._ ```kubernetes1.30``` is a versioned rpm for Kubernetes v1.30). The ```kubelet``` runs as a systemd service on Fedora. In early implementations, the ```kubelet``` was configured via link:https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/[flags] that were set in a systemd unit file and passed to the ```kubelet``` as command line parameters.
 
 In more recent versions of the ```kubelet``` these flags are deprecated in favor of a link:https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/[configuration file] that uses either JSON or YAML for the configuration syntax.
 
@@ -25,7 +25,7 @@ With both versioned and non-versioned rpms, all files, including systemd related
 [[systemd]]
 == Systemd configuration recommendations
 
-Flags for the ```kublet``` running on a node are set in a systemd unit file with the relevant file dependent on which rpms are installed.
+Flags for the ```kubelet``` running on a node are set in a systemd unit file with the relevant file dependent on which rpms are installed.
 
 The kubernetes rpm (_e.g_ kubernetes1.30 for version 1.30) installs the default ```kubelet``` systemd file at:
 

modules/ROOT/pages/virtualization-getting-started.adoc

@@ -27,7 +27,7 @@ To run virtualization on Fedora, you need:
 KVM requires a CPU with virtualization extensions, found on most consumer CPUs. These extensions are called Intel VT or AMD-V. To check whether you have CPU support, run the following command:
 
 ----
-$ egrep '^flags.*(vmx|svm)' /proc/cpuinfo
+$ grep -E '^flags.*(vmx|svm)' /proc/cpuinfo
 ----
 
 If this command results in nothing printed, your system does not support the relevant virtualization extensions. You can still use QEMU/KVM, but the emulator will fall back to software virtualization, which is much slower.
@@ -118,7 +118,7 @@ The installation of Fedora guests using Anaconda is supported. The installation
 
 `virt-install` is a command-line based tool for creating virtualized guests. Execute `virt-install --help` for command line help, or you can find the manual page at `man 1 virt-install`.
 
-To use the virt-install command, you should first download an ISO of the Fedora version you wish to install.  You can find the latest Fedora images at https://getfedora.org.  This ISO is only needed during Fedora installation, and can be deleted to free up storage space afterwards if desired. 
+To use the virt-install command, you should first download an ISO of the Fedora version you wish to install.  You can find the latest Fedora images at https://fedoraproject.org.  This ISO is only needed during Fedora installation, and can be deleted to free up storage space afterwards if desired. 
 
 //More information about Fedora installation can be found in the xref:f{MAJOROSVER}@fedora:install-guide:index.adoc[Installation Guide].