summaryrefslogtreecommitdiff
path: root/HOWTO
diff options
context:
space:
mode:
authorKian-Meng, Ang <kianmeng@cpan.org>2021-11-08 10:10:34 +0800
committerKian-Meng, Ang <kianmeng@cpan.org>2021-11-08 10:10:34 +0800
commit0bd52f35a8f7734b06b41949c75d78e545dfb404 (patch)
tree6696504e947ef66a5a4cc3e367398f477742b811 /HOWTO
parentb3d4affcf9880255f6edc2e67095015e6ed2aca2 (diff)
downloaderlang-0bd52f35a8f7734b06b41949c75d78e545dfb404.tar.gz
Fix typos in howto
Diffstat (limited to 'HOWTO')
-rw-r--r--HOWTO/INSTALL-ANDROID.md4
-rw-r--r--HOWTO/INSTALL-CROSS.md2
-rw-r--r--HOWTO/INSTALL-WIN32-OLD.md2
-rw-r--r--HOWTO/INSTALL-WIN32.md2
-rw-r--r--HOWTO/INSTALL.md2
-rw-r--r--HOWTO/MARKDOWN.md2
-rw-r--r--HOWTO/SYSTEMTAP.md2
7 files changed, 8 insertions, 8 deletions
diff --git a/HOWTO/INSTALL-ANDROID.md b/HOWTO/INSTALL-ANDROID.md
index 4ca225ba3b..a4bca5ffed 100644
--- a/HOWTO/INSTALL-ANDROID.md
+++ b/HOWTO/INSTALL-ANDROID.md
@@ -4,7 +4,7 @@ Cross Compiling Erlang/OTP - ANDROID
Introduction
------------
-This document describes how to cross compile Erlang/OTP to Android/Rasberry Pi platforms.
+This document describes how to cross compile Erlang/OTP to Android/Raspberry Pi platforms.
### Download and Install the Android NDK ###
@@ -135,7 +135,7 @@ Use the following commands when compiling an x86 64-bit version.
$ make RELEASE_ROOT=/path/to/release/erlang release
-### Target Deployment for Rasberry Pi ###
+### Target Deployment for Raspberry Pi ###
Make a tarball out of /path/to/release/erlang and copy it to target
device. Extract it and install.
diff --git a/HOWTO/INSTALL-CROSS.md b/HOWTO/INSTALL-CROSS.md
index 7366811a43..c1985f02cb 100644
--- a/HOWTO/INSTALL-CROSS.md
+++ b/HOWTO/INSTALL-CROSS.md
@@ -265,7 +265,7 @@ have to be passed one way or the other; either by using `erl_xcomp_host=<HOST>`
and `erl_xcomp_build=<BUILD>` in the configuration file, or by using the
`--host=<HOST>`, and `--build=<BUILD>` command line arguments.
-`otp_build configure` will configure both for the boostrap system on the
+`otp_build configure` will configure both for the bootstrap system on the
build machine and the cross host system.
(10)
diff --git a/HOWTO/INSTALL-WIN32-OLD.md b/HOWTO/INSTALL-WIN32-OLD.md
index 4722771202..d819fb18aa 100644
--- a/HOWTO/INSTALL-WIN32-OLD.md
+++ b/HOWTO/INSTALL-WIN32-OLD.md
@@ -728,7 +728,7 @@ Lets get into more detail:
2. `$ ./otp_build boot -a` - This uses the bootstrap directory (shipped
with the source, `$ERL_TOP/bootstrap`) to build a complete OTP
system. When this is done you can run erl from within the source tree;
- just type `$ERL_TOP/bin/erl` and you whould have the prompt.
+ just type `$ERL_TOP/bin/erl` and you would have the prompt.
3. `$ ./otp_build release -a` - Builds a commercial release tree from the
source tree. The default is to put it in `$ERL_TOP/release/win32`. You can
diff --git a/HOWTO/INSTALL-WIN32.md b/HOWTO/INSTALL-WIN32.md
index c17cfbe5a3..a4b01d83a2 100644
--- a/HOWTO/INSTALL-WIN32.md
+++ b/HOWTO/INSTALL-WIN32.md
@@ -143,7 +143,7 @@ the different tools:
You need this to build crypto, ssh and ssl libs.
We recommend v1.1.1d or later.
- There are prebuilt avaiable binaries, which you can just
+ There are prebuilt available binaries, which you can just
download and install, available here:
URL: <http://wiki.openssl.org/index.php/Binaries>
diff --git a/HOWTO/INSTALL.md b/HOWTO/INSTALL.md
index 3a041f7e6c..dd06828e91 100644
--- a/HOWTO/INSTALL.md
+++ b/HOWTO/INSTALL.md
@@ -409,7 +409,7 @@ Some of the available `configure` options are:
should be compiled without one or more applications, i.e. `--without-wx`. There is
no automatic dependency handling between applications. If you disable
an application that another application depends on, you also have to disable the
- dependant application.
+ dependent application.
* `--enable-gettimeofday-as-os-system-time` - Force usage of `gettimeofday()` for
OS system time.
* `--enable-prefer-elapsed-monotonic-time-during-suspend` - Prefer an OS monotonic
diff --git a/HOWTO/MARKDOWN.md b/HOWTO/MARKDOWN.md
index e6773a0a8e..180cf85114 100644
--- a/HOWTO/MARKDOWN.md
+++ b/HOWTO/MARKDOWN.md
@@ -202,7 +202,7 @@ places. Appropriate attributes to the `X` tag will also be generated.
This way it is relatively easy to make sure that all marker ids of a
document are unique, but there is of course no guarantee that they are.
- The upside of these auto generated markers is that we wont have to clutter
+ The upside of these auto generated markers is that we won't have to clutter
the document with XML or something else while being able to refer into
the document. The downside is that if you change a level 2 heading you
change a lot of marker ids which may break links into a document from
diff --git a/HOWTO/SYSTEMTAP.md b/HOWTO/SYSTEMTAP.md
index 76deac97e5..01b1fe8a47 100644
--- a/HOWTO/SYSTEMTAP.md
+++ b/HOWTO/SYSTEMTAP.md
@@ -43,7 +43,7 @@ Testing
SystemTap, unlike DTrace, needs to know what binary it is tracing and has to
be able to read that binary before it starts tracing. Your probe script
-therefor has to reference the correct beam emulator and stap needs to be able
+therefore has to reference the correct beam emulator and stap needs to be able
to find that binary.
The examples are written for "beam", but other versions such as "beam.smp" or
"beam.debug.smp" might exist (depending on your configuration). Make sure you