aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorEelco Dolstra <edolstra@gmail.com>2022-07-11 13:52:40 +0200
committerGitHub <noreply@github.com>2022-07-11 13:52:40 +0200
commit545383208e100e68bc74680b14d2081cf2f0a715 (patch)
tree41222b6f1e2ad101a734f8f5cc35edaa2326a95c /doc
parent517ce38dadc2c8d6282b6865ec0c620b7e26df3a (diff)
parenteac211a171fa6253b5ae6fdcf56fc5d0aced0201 (diff)
Merge pull request #6777 from laalsaas/master
Fix logical and typographical errors in nix-env man page
Diffstat (limited to 'doc')
-rw-r--r--doc/manual/src/command-ref/nix-env.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/manual/src/command-ref/nix-env.md b/doc/manual/src/command-ref/nix-env.md
index 8d6abaf52..a372c5eae 100644
--- a/doc/manual/src/command-ref/nix-env.md
+++ b/doc/manual/src/command-ref/nix-env.md
@@ -31,7 +31,7 @@ subcommand to be performed. These are documented below.
Several commands, such as `nix-env -q` and `nix-env -i`, take a list of
arguments that specify the packages on which to operate. These are
extended regular expressions that must match the entire name of the
-package. (For details on regular expressions, see regex7.) The match is
+package. (For details on regular expressions, see **regex**(7).) The match is
case-sensitive. The regular expression can optionally be followed by a
dash and a version number; if omitted, any version of the package will
match. Here are some examples:
@@ -412,7 +412,7 @@ The upgrade operation determines whether a derivation `y` is an upgrade
of a derivation `x` by looking at their respective `name` attributes.
The names (e.g., `gcc-3.3.1` are split into two parts: the package name
(`gcc`), and the version (`3.3.1`). The version part starts after the
-first dash not followed by a letter. `x` is considered an upgrade of `y`
+first dash not followed by a letter. `y` is considered an upgrade of `x`
if their package names match, and the version of `y` is higher than that
of `x`.