commit:     de696eecd50a97ad16d00f818974138d450ced22
Author:     ingenarel (NeoJesus) <ingenarel_neojesus <AT> disroot <DOT> org>
AuthorDate: Sun Feb  1 07:47:46 2026 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sat Feb  7 08:12:05 2026 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=de696eec

ebuild-writing/variables: fix accidental double spaces

Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus <AT> disroot.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 ebuild-writing/variables/text.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ebuild-writing/variables/text.xml 
b/ebuild-writing/variables/text.xml
index b1f6755..67cc0d4 100644
--- a/ebuild-writing/variables/text.xml
+++ b/ebuild-writing/variables/text.xml
@@ -514,7 +514,7 @@ list does not outweigh the burden of maintaining it.
 In EAPI 8, individual items in <c>SRC_URI</c> can be exempted from automatic
 mirroring and fetching restrictions (imposed by <c>RESTRICT="mirror"</c> and
 <c>RESTRICT="fetch"</c>) by prefixing the addresses with <c>mirror+</c> or
-<c>fetch+</c>.  For example, in the following ebuild,
+<c>fetch+</c>. For example, in the following ebuild,
 </p>
 
 <codesample lang="ebuild">
@@ -854,7 +854,7 @@ string when it conceptually refers to <c>/</c>.
 
 <p>
 Variables have significant value in ebuilds, making it possible to avoid
-unnecessary repetitions and make maintenance easier.  However,
+unnecessary repetitions and make maintenance easier. However,
 references to constant-value variables should be used with care as their
 excessive use can harm readability and increase maintenance burden (e.g.
 when renaming a package). In particular, using variables whose values

Reply via email to