aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--ebuild-writing/using-eclasses/text.xml2
-rw-r--r--ebuild-writing/variables/text.xml4
-rw-r--r--general-concepts/ebuild-revisions/text.xml2
-rw-r--r--general-concepts/tree/text.xml2
-rw-r--r--general-concepts/use-flags/text.xml2
-rw-r--r--quickstart/text.xml2
6 files changed, 7 insertions, 7 deletions
diff --git a/ebuild-writing/using-eclasses/text.xml b/ebuild-writing/using-eclasses/text.xml
index 6e8c15b..ddd2b9c 100644
--- a/ebuild-writing/using-eclasses/text.xml
+++ b/ebuild-writing/using-eclasses/text.xml
@@ -6,7 +6,7 @@
<body>
<p>
An eclass is a collection (library) of functions or functionality that is shared
-between packages. See `Eclass Writing Guide`_ for the full story on what
+between packages. See <uri link="::eclass-writing/" /> for the full story on what
eclasses can do, how they work and how to write them, and `Eclass Reference`_
for documentation on various commonly used eclasses. This section only explains
how to use an eclass which has already been written.
diff --git a/ebuild-writing/variables/text.xml b/ebuild-writing/variables/text.xml
index b466536..1e68bef 100644
--- a/ebuild-writing/variables/text.xml
+++ b/ebuild-writing/variables/text.xml
@@ -137,7 +137,7 @@ The following variables must be defined by every ebuild.
<ti><c>KEYWORDS</c></ti>
<ti>
See <uri link="::ebuild-writing/variables#KEYWORDS"/> and
- `Keywording`_.
+ <uri link="::keywording/"/>.
</ti>
</tr>
<tr>
@@ -254,7 +254,7 @@ The only valid construct involving a <c>*</c> inside <c>KEYWORDS</c> is a <c>-*<
</p>
<p>
-See `Keywording`_ for how to handle this variable.
+See <uri link="::keywording/"/> for how to handle this variable.
</p>
</body>
diff --git a/general-concepts/ebuild-revisions/text.xml b/general-concepts/ebuild-revisions/text.xml
index bcc472e..18ae2d1 100644
--- a/general-concepts/ebuild-revisions/text.xml
+++ b/general-concepts/ebuild-revisions/text.xml
@@ -27,7 +27,7 @@ Small documentation fixes are also usually not grounds for a new revision.
<p>
When doing a revision bump, the usual rules about dropping to <c>~arch</c> apply.
-See `Keywording on Upgrades`_.
+See <uri link="::keywording#Keywording on Upgrades"/>.
</p>
</body>
diff --git a/general-concepts/tree/text.xml b/general-concepts/tree/text.xml
index 5cfa59d..6c93aa4 100644
--- a/general-concepts/tree/text.xml
+++ b/general-concepts/tree/text.xml
@@ -110,7 +110,7 @@ Software-wise, in general all of the following should be met in order for a pack
<dd>
<p>
Keep super-experimental things out of the tree. If you must commit them,
- consider using ``package.mask`` until things calm down, or better yet make
+ consider using <c>package.mask</c> until things calm down, or better yet make
them available as overlay ebuilds.
</p>
</dd>
diff --git a/general-concepts/use-flags/text.xml b/general-concepts/use-flags/text.xml
index db8eae6..858aaec 100644
--- a/general-concepts/use-flags/text.xml
+++ b/general-concepts/use-flags/text.xml
@@ -69,7 +69,7 @@ manually edited.
</p>
<p>
-The solution is <c>use.mask</c>, which is documented in `Profiles use.mask File`_.
+The solution is <c>use.mask</c>, which is documented in <uri link="::profiles/use.mask/"/>.
Each profile can have a <c>use.mask</c> file which can be used to forcibly disable
certain USE flags on a given arch (or subarch, or subprofile). So, if the
<c>fakemedia</c> USE flag was use.masked on every non-x86 profile, the following
diff --git a/quickstart/text.xml b/quickstart/text.xml
index d2670a4..29e5077 100644
--- a/quickstart/text.xml
+++ b/quickstart/text.xml
@@ -121,7 +121,7 @@ you've not seen slots before, either just use <c>&quot;0&quot;</c> or read
<p>
The <c>KEYWORDS</c> variable is set to archs upon which this ebuild has been
tested. We use <c>~</c> keywords for newly written ebuilds <d/> packages are not
-committed straight to stable, even if they seem to work. See `Keywording`_ for
+committed straight to stable, even if they seem to work. See <uri link="::keywording"/> for
details.
</p>
</body>