Reconvert

2 files changed, 8 insertions, 8 deletions

diff --git a/doc/manual/src/package-management/basic-package-mgmt.md b/doc/manual/src/package-management/basic-package-mgmt.md
index f5c550fd7..04dad3339 100644
--- a/doc/manual/src/package-management/basic-package-mgmt.md
+++ b/doc/manual/src/package-management/basic-package-mgmt.md
@@ -8,10 +8,10 @@ In Nix, different users can have different “views” on the set of
 installed applications. That is, there might be lots of applications
 present on the system (possibly in many different versions), but users
 can have a specific selection of those active — where “active” just
-means that it appears in a directory in the user’s PATH. Such a view on
-the set of installed applications is called a *user environment*, which
-is just a directory tree consisting of symlinks to the files of the
-active applications.
+means that it appears in a directory in the user’s `PATH`. Such a view
+on the set of installed applications is called a *user environment*,
+which is just a directory tree consisting of symlinks to the files of
+the active applications.
 
 Components are installed from a set of *Nix expressions* that tell Nix
 how to build those packages, including, if necessary, their
diff --git a/doc/manual/src/package-management/profiles.md b/doc/manual/src/package-management/profiles.md
index c46adf538..984afca55 100644
--- a/doc/manual/src/package-management/profiles.md
+++ b/doc/manual/src/package-management/profiles.md
@@ -24,9 +24,9 @@ Of course, you wouldn’t want to type
     $ /nix/store/dpmvp969yhdq...-subversion-1.1.3/bin/svn
 
 every time you want to run Subversion. Of course we could set up the
-PATH environment variable to include the `bin` directory of every
+`PATH` environment variable to include the `bin` directory of every
 package we want to use, but this is not very convenient since changing
-PATH doesn’t take effect for already existing processes. The solution
+`PATH` doesn’t take effect for already existing processes. The solution
 Nix uses is to create directory trees of symlinks to *activated*
 packages. These are called *user environments* and they are packages
 themselves (though automatically generated by `nix-env`), so they too
@@ -89,9 +89,9 @@ also see all available generations:
     $ nix-env --list-generations
 
 You generally wouldn’t have `/nix/var/nix/profiles/some-profile/bin` in
-your PATH. Rather, there is a symlink `~/.nix-profile` that points to
+your `PATH`. Rather, there is a symlink `~/.nix-profile` that points to
 your current profile. This means that you should put
-`~/.nix-profile/bin` in your PATH (and indeed, that’s what the
+`~/.nix-profile/bin` in your `PATH` (and indeed, that’s what the
 initialisation script `/nix/etc/profile.d/nix.sh` does). This makes it
 easier to switch to a different profile. You can do that using the
 command `nix-env --switch-profile`: