guix-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

01/01: website: profiles-in-practice: Fix more typos.


From: Pierre Neidhardt
Subject: 01/01: website: profiles-in-practice: Fix more typos.
Date: Mon, 28 Oct 2019 04:04:48 -0400 (EDT)

ambrevar pushed a commit to branch master
in repository guix-artwork.

commit bb2359c592f3acd51a57367422c2561b4ab14c80
Author: Pierre Neidhardt <address@hidden>
Date:   Mon Oct 28 09:04:14 2019 +0100

    website: profiles-in-practice: Fix more typos.
    
    * website/posts/profiles-in-practice.md: Fix more typos.
---
 website/posts/profiles-in-practice.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/posts/profiles-in-practice.md 
b/website/posts/profiles-in-practice.md
index e0c8115..7d32f5b 100644
--- a/website/posts/profiles-in-practice.md
+++ b/website/posts/profiles-in-practice.md
@@ -8,7 +8,7 @@ tags: Functional package management, Reproducibility, User 
interfaces, Customiza
 
 Guix provides a very useful feature that may be quite foreign to newcomers:
 *profiles*.  They are a way to group package installations together and all 
users
-on a same system are free to use as many profiles as they want.
+on the same system are free to use as many profiles as they want.
 
 Whether you're a developer or not, you may find that multiple profiles bring 
you
 great power and flexibility.  While they shift the paradigm somewhat compared 
to
@@ -199,7 +199,7 @@ the profile is loaded, you've got two options:
 
 -   Either export the variable manually, e.g.
 
-        export MANPATH=/path/to/profile${MANPATH:+:}$MANPATH"
+        export MANPATH=/path/to/profile${MANPATH:+:}$MANPATH
 
 -   Or include `man-db` to the profile manifest.
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]