superh port

[musl] / INSTALL

diff --git a/INSTALL b/INSTALL
index 017900d..27ed9d7 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -20,7 +20,7 @@ weak aliases, and stand-alone assembly source files.
 The system used to build musl does not need to be Linux-based, nor do
 the Linux kernel headers need to be available.
 
-If support for dynamic linking is desired, some further requriements
+If support for dynamic linking is desired, some further requirements
 are placed on the compiler and linker. In particular, the linker must
 support the -Bsymbolic-functions option.
 
@@ -43,6 +43,7 @@ and ABI combinations:
 - arm (EABI)
 - mips (o32 ABI, requires fpu or float emulation in kernel)
 - microblaze (requires a cpu with lwx/swx instructions)
+- powerpc (32-bit, must use "secure plt" mode for dynamic linking)
 
 For architectures with both little- and big-endian options, both are
 supported unless otherwise noted.
@@ -119,7 +120,7 @@ main host system library directories.
 
 Finally, it's worth noting that musl's include and lib directories in
 the build tree are setup to be usable without installation, if
-necessary. Just modify the the paths in the spec file used by musl-gcc
+necessary. Just modify the paths in the spec file used by musl-gcc
 (it's located at $prefix/lib/musl-gcc.specs) to point to the
 source/build tree.
 
@@ -128,7 +129,7 @@ source/build tree.
 ==== Option 2: Installing musl as the primary C library ====
 
 In this setup, you will need an existing compiler/toolchain. It
-shouldnt matter whether it was configured for glibc, uClibc, musl, or
+shouldn't matter whether it was configured for glibc, uClibc, musl, or
 something else entirely, but sometimes gcc can be uncooperative,
 especially if the system distributor has built gcc with strange
 options. It probably makes the most sense to perform the following