aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/man/pkgcore.rst6
-rw-r--r--doc/man/pmerge.rst4
2 files changed, 5 insertions, 5 deletions
diff --git a/doc/man/pkgcore.rst b/doc/man/pkgcore.rst
index aaf2f01ee..be3ae1243 100644
--- a/doc/man/pkgcore.rst
+++ b/doc/man/pkgcore.rst
@@ -14,7 +14,7 @@ Portage Compatibility
=====================
In general, pkgcore tries to remain somewhat compatible with much of the
-current portage configuration.
+current **portage**\(5) configuration.
Missing or differing functionality
----------------------------------
@@ -30,7 +30,7 @@ managers.
* /etc/portage/repos.conf
The only way to add repos to pkgcore is to use repos.conf, PORTDIR and
- PORTDIR_OVERLAY settings in make.conf are not respected anymore.
+ PORTDIR_OVERLAY settings in **make.conf**\(5) are not respected anymore.
In addition, not all fields that portage supports are used by pkgcore.
Currently in repo sections the only supported fields are 'location',
@@ -473,4 +473,4 @@ You can also stop by #pkgcore on freenode.
See Also
========
-portage(5), make.conf(5)
+**portage**\(5), **make.conf**\(5)
diff --git a/doc/man/pmerge.rst b/doc/man/pmerge.rst
index ff22f971f..558ea86da 100644
--- a/doc/man/pmerge.rst
+++ b/doc/man/pmerge.rst
@@ -9,7 +9,7 @@ Portage Compatibility
=====================
With regards to portage compatibility, pmerge provides much of the same
-functionality that emerge does. In general, it should be possible to use
+functionality that **emerge**\(1) does. In general, it should be possible to use
both pmerge and emerge on the same system in a sane fashion. For example,
pmerge can be used to install packages and then emerge should be able to
upgrade or uninstall them, or vice versa. Also, binary packages created using
@@ -46,4 +46,4 @@ configuration directory::
See Also
========
-emerge(1), pmaint(1), pebuild(1), pquery(1)
+**emerge**\(1)