Skip to content

Commit 034f112

Browse files
authored
typos (#312)
1 parent d5b9210 commit 034f112

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

tutorial_binary_cache.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -225,7 +225,7 @@ instance before they initiate a build.
225225
Bootstrapping Mirrors
226226
---------------------
227227

228-
In order to run Spack on an airgapped system, or aywhere else without
228+
In order to run Spack on an airgapped system, or anywhere else without
229229
internet access, you also need to install ``clingo`` as a dependency
230230
(``clingo`` is used by spack's concretizer). While you can always
231231
install clingo through your favorite method, we like to think Spack

tutorial_buildsystems.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Package
5858

5959
We've already seen examples of a :code:`Package` class in our walkthrough for writing
6060
package files, so we won't be spending much time with them here. Briefly,
61-
the Package class allows for abitrary control over the build process, whereas
61+
the Package class allows for arbitrary control over the build process, whereas
6262
subclasses rely on certain patterns (e.g. :code:`configure` :code:`make`
6363
:code:`make install`) to be useful. :code:`Package` classes are particularly useful
6464
for packages that have a non-conventional way of being built since the packager
@@ -125,7 +125,7 @@ then we can append to our :code:`build_targets` property:
125125
126126
build_targets = ["foo"]
127127
128-
Which is similiar to invoking make in our Package
128+
Which is similar to invoking make in our Package
129129

130130
.. code-block:: python
131131

0 commit comments

Comments
 (0)