01/01: doc: Fix typos.

[Alex Kost]

alezost pushed a commit to branch master
in repository guix.

commit e1a65ae57afb791683fbf70dea094f04bb04a07e
Author: Alex Kost <address@hidden>
Date:   Sat Jan 28 13:00:56 2017 +0300

    doc: Fix typos.
    
    Fixes a regression introduced in commit
    f31f1acac2efb4bc6558b604a07b56f826423177.
    
    Reported-by roptat on #guix.
    
    * doc/guix.texi (Invoking guix build): Use "@@" instead of "@".
---
 doc/guix.texi |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 719ebd9..8c4067f 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -4511,7 +4511,7 @@ guix build --quiet --keep-going \
 
 @var{package-or-derivation} may be either the name of a package found in
 the software distribution such as @code{coreutils} or
address@hidden@8.20}, or a derivation such as
address@hidden@@8.20}, or a derivation such as
 @file{/gnu/store/@dots{}-coreutils-8.19.drv}.  In the former case, a
 package with the corresponding name (and optionally version) is searched
 for among the GNU distribution modules (@pxref{Package Modules}).
@@ -5671,7 +5671,7 @@ single output for a package that could easily be split 
(@pxref{Packages
 with Multiple Outputs}).  Such are the typical issues that
 @command{guix size} can highlight.
 
-The command can be passed a package specification such as @address@hidden
+The command can be passed a package specification such as @code{gcc@@4.8}
 or @code{guile:debug}, or a file name in the store.  Consider this
 example: