Fix typos

This commit is contained in:
Quentin Santos 2024-09-19 10:51:41 +02:00
parent c6c57eb8dd
commit cf568ab074
4 changed files with 4 additions and 4 deletions

View file

@ -132,6 +132,6 @@ ones are listed below.
* `$out` is the path to the location in the Nix store where the package
will be added.
* `$system` is the system that the package is being built for.
* `$PWD` and `$TMP` both point to a temporary build directories
* `$PWD` and `$TMP` both point to temporary build directories
* `$HOME` and `$PATH` point to nonexistent directories, so the build
cannot rely on them.

View file

@ -48,7 +48,7 @@ hyphenated and non-hyphenated versions of many Nix commands, and yes,
it's confusing. The non-hyphenated commands were introduced when support
for flakes was added to Nix. I predict that eventually all hyphenated
commands will be replaced with non-hyphenated versions. Until then, a
useful rule of thumb is that non-hyphenated commands are for for working
useful rule of thumb is that non-hyphenated commands are for working
directly with flakes; hyphenated commands are for everything else.
====

View file

@ -8,7 +8,7 @@ Within the REPL, type `:?` to see a list of available commands.
[source]
....
$# echo "$ nix repl"
$ nix repl
Welcome to Nix 2.18.1. Type :? for help.
nix-repl> :?

View file

@ -36,7 +36,7 @@ The Boolean values in Nix are `true` and `false`.
[#type-path]
== Paths
File paths are play an important role in building software, so Nix has a special data type for them.
File paths play an important role in building software, so Nix has a special data type for them.
Paths may be absolute (e.g. `/bin/sh`) or relative (e.g. `./data/file1.csv`).
Note that paths are not enclosed in quotation marks; they are not strings!