Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
home:Ledest:erlang:19
erlang
1294-Fix-typos-in-howto.patch
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File 1294-Fix-typos-in-howto.patch of Package erlang
From 0bd52f35a8f7734b06b41949c75d78e545dfb404 Mon Sep 17 00:00:00 2001 From: "Kian-Meng, Ang" <kianmeng@cpan.org> Date: Mon, 8 Nov 2021 10:10:34 +0800 Subject: [PATCH] Fix typos in howto --- HOWTO/INSTALL-ANDROID.md | 4 ++-- HOWTO/INSTALL-CROSS.md | 2 +- HOWTO/INSTALL-WIN32-OLD.md | 2 +- HOWTO/INSTALL-WIN32.md | 2 +- HOWTO/INSTALL.md | 2 +- HOWTO/MARKDOWN.md | 2 +- HOWTO/SYSTEMTAP.md | 2 +- 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 Android NDK ### 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.md b/HOWTO/INSTALL-WIN32.md index c17cfbe5a3..a4b01d83a2 100644 --- a/HOWTO/INSTALL-WIN32.md +++ b/HOWTO/INSTALL-WIN32.md @@ -733,7 +733,7 @@ Lets get into more detail: 3. `$ ./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. 4. `$ ./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.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 -- 2.31.1
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor