Skip to contentSkip to conversation

Documentation: arch: Fix documentation spelling errors

PATCH New Abhash Jha 1 participant 1 message Aug 14, 2024

Subsystems (4)
lore
Share & tools
lore

Abhash Jha

author
#0 lore raw

PATCH v2 1/1 Documentation: arch: Fix documentation spelling errors

In this commit we correct some simple spelling mistakes in the Documentation/arch directory.

---
 Documentation/arch/powerpc/ultravisor.rst | 2 +-
 Documentation/arch/riscv/vector.rst       | 2 +-
 Documentation/arch/x86/cpuinfo.rst        | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
Documentation/arch/powerpc/ultravisor.rst +1 -1
index ba6b1bf1c..6d0407b2f 100644
@@ -134,7 +134,7 @@ Hardware
 
       * PTCR and partition table entries (partition table is in secure
         memory). An attempt to write to PTCR will cause a Hypervisor
-        Emulation Assitance interrupt.
+        Emulation Assistance interrupt.
 
       * LDBAR (LD Base Address Register) and IMC (In-Memory Collection)
         non-architected registers. An attempt to write to them will cause a
Documentation/arch/riscv/vector.rst +1 -1
index 75dd88a62..e638cf9ba 100644
@@ -15,7 +15,7 @@ status for the use of Vector in userspace. The intended usage guideline for
 these interfaces is to give init systems a way to modify the availability of V
 for processes running under its domain. Calling these interfaces is not
 recommended in libraries routines because libraries should not override policies
-configured from the parant process. Also, users must noted that these interfaces
+configured from the parent process. Also, users must be noted that these interfaces
 are not portable to non-Linux, nor non-RISC-V environments, so it is discourage
 to use in a portable code. To get the availability of V in an ELF program,
 please read :c:macro:`COMPAT_HWCAP_ISA_V` bit of :c:macro:`ELF_HWCAP` in the
Documentation/arch/x86/cpuinfo.rst +1 -1
index 8895784d4..fd7999c4a 100644
@@ -12,7 +12,7 @@ represents an ill-fated attempt from long time ago to put feature flags
 in an easy to find place for userspace.
 
 However, the amount of feature flags is growing by the CPU generation,
-leading to unparseable and unwieldy /proc/cpuinfo.
+leading to unparsable and unwieldy /proc/cpuinfo.
 
 What is more, those feature flags do not even need to be in that file
 because userspace doesn't care about them - glibc et al already use
Signature · 1 line
2.43.0