aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSebastian Pipping <sebastian@pipping.org>2010-11-06 23:57:53 +0100
committerSebastian Pipping <sebastian@pipping.org>2010-11-06 23:57:53 +0100
commitcd8893c95b7fb6d7bd28c998b4c6d472674035b7 (patch)
treeb02ba2f3bbb5ca325de6db70e0349f64990fb9b2
parentman page: Improve style (diff)
downloadlayman-cd8893c95b7fb6d7bd28c998b4c6d472674035b7.tar.gz
layman-cd8893c95b7fb6d7bd28c998b4c6d472674035b7.tar.bz2
layman-cd8893c95b7fb6d7bd28c998b4c6d472674035b7.zip
man page: Improve style
-rw-r--r--doc/layman.8.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/layman.8.txt b/doc/layman.8.txt
index ba2243a..b817f08 100644
--- a/doc/layman.8.txt
+++ b/doc/layman.8.txt
@@ -39,7 +39,7 @@ WARNING
*layman* makes it easy to retrieve and update overlays for Gentoo.
In addition it makes it TRIVIAL to break your system.
-The main portage tree provides you with high quality ebuilds that
+The Gentoo main tree provides you with high quality ebuilds that
are all maintained by Gentoo developers. This will not be the case
for most of the overlays you can get by using *layman*. Thus you
are removing the security shield that the standard tree provides
@@ -156,7 +156,7 @@ storage::
*layman* uses a location within the '/usr/portage' hierarchy
instead of '/var' in order to store its data. This decision has
been made to support network file systems. If you have your
- portage tree on nfs or a similar file system and several
+ Gentoo tree on NFS or a similar file system and several
machines access the same ebuild repository over the net it
will be necessary to also provide all necessary *layman* data
within the hierarchy of the tree. This way the overlays will