Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAnton Hvornum <anton@hvornum.se>2021-05-18 13:39:57 +0000
committerGitHub <noreply@github.com>2021-05-18 13:39:57 +0000
commite1c58185790ccb5945e993046e7d51e0040327e7 (patch)
tree5350a481808ad376400eb9fe2baa36b9e70abe30 /docs
parent9bf71da867554f956d370694eb32b6392e352a06 (diff)
parentda0da729c5f3ef0aaf832229901dda221de654ab (diff)
Merge pull request #472 from dylanmtaylor/proofreading
Proofreading: Fix misc. spelling and grammar issues
Diffstat (limited to 'docs')
-rw-r--r--docs/examples/python.rst4
-rw-r--r--docs/installing/guided.rst2
-rw-r--r--docs/pull_request_template.md4
3 files changed, 5 insertions, 5 deletions
diff --git a/docs/examples/python.rst b/docs/examples/python.rst
index f6388738..342ec5c7 100644
--- a/docs/examples/python.rst
+++ b/docs/examples/python.rst
@@ -27,7 +27,7 @@ Lets create a `test_installer` - installer as an example. This is assuming that
We begin by creating `./archinstall/examples/test_installer.py`. The placement here is important later.
This script can now already be called using `python -m archinstall test_installer` after a successful installation of the library itself.
-But the script won't do much. So we'll do something simple like list all the harddrives as an example.
+But the script won't do much. So we'll do something simple like list all the hard drives as an example.
To do this, we'll begin by importing `archinstall` in our `./archinstall/examples/test_installer.py` and call some functions.
@@ -56,4 +56,4 @@ This should now print all available drives on your system.
.. note::
- This should work on any system, not just Arch Linux based ones. But note that other functions in the library relies heavily on Arch Linux based commands to execute the installation steps. Such as `arch-chroot`. \ No newline at end of file
+ This should work on any system, not just Arch Linux based ones. But note that other functions in the library relies heavily on Arch Linux based commands to execute the installation steps. Such as `arch-chroot`.
diff --git a/docs/installing/guided.rst b/docs/installing/guided.rst
index 8699ae62..88b4e480 100644
--- a/docs/installing/guided.rst
+++ b/docs/installing/guided.rst
@@ -3,7 +3,7 @@ Guided installation
This is the default scripted installation you'll encounter on the official Arch Linux Archinstall package as well as the unofficial ISO found on `https://archlinux.life <https://archlinux.life>`_. It will guide your through a very basic installation of Arch Linux.
-The installer has two pre-requisits:
+The installer has two pre-requisites:
* A Physical or Virtual machine to install on
* An active internet connection prior to running archinstall
diff --git a/docs/pull_request_template.md b/docs/pull_request_template.md
index 1cbcf76a..5e6daf51 100644
--- a/docs/pull_request_template.md
+++ b/docs/pull_request_template.md
@@ -3,11 +3,11 @@
# New features *(v2.2.0)*
All future work towards *`v2.2.0`* is done against `master` now.<br>
-Any patch work to existing verions will have to create a new branch against the tagged versions.
+Any patch work to existing versions will have to create a new branch against the tagged versions.
# Describe your PR
-If the changes has been discussed in an Issue, please tag it so we can backtrace from the Issue later on.<br>
+If the changes has been discussed in an Issue, please tag it so that we can backtrace from the issue later on.<br>
If the PR is larger than ~20 lines, please describe it here unless described in an issue.
# Testing