nixo
/
guix-devel
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

doc: Fix minor typos. 

* doc/guix.texi (Invoking guix-daemon, Application Setup, The Store): Fix
  typos.
This commit is contained in:
Steve Sprang 2015-08-02 13:24:38 -07:00 committed by Mark H Weaver
parent 8d801045ff
commit 4988dd4008
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/guix.texi
View File

@ -861,7 +861,7 @@ Disable automatic file ``deduplication'' in the store.
By default, files added to the store are automatically ``deduplicated'': By default, files added to the store are automatically ``deduplicated'':
if a newly added file is identical to another one found in the store, if a newly added file is identical to another one found in the store,
the daemon makes the new file a hard link to the other file. This can the daemon makes the new file a hard link to the other file. This can
noticeably reduce disk usage, at the expense of slightly increasde noticeably reduce disk usage, at the expense of slightly increased
input/output load at the end of a build process. This option disables input/output load at the end of a build process. This option disables
this optimization. this optimization.
@ -942,7 +942,7 @@ limited to a few UTF-8 locales.
@subsection X11 Fonts @subsection X11 Fonts
The majority of graphical applications uses Fontconfig to locate and The majority of graphical applications use Fontconfig to locate and
load fonts and perform X11-client-side rendering. Guix's load fonts and perform X11-client-side rendering. Guix's
@code{fontconfig} package looks for fonts in @file{$HOME/.guix-profile} @code{fontconfig} package looks for fonts in @file{$HOME/.guix-profile}
by default. Thus, to allow graphical applications installed with Guix by default. Thus, to allow graphical applications installed with Guix
@ -2541,7 +2541,7 @@ with @code{build-expression->derivation} (@pxref{Derivations,
Conceptually, the @dfn{store} is where derivations that have been Conceptually, the @dfn{store} is where derivations that have been
successfully built are stored---by default, under @file{/gnu/store}. successfully built are stored---by default, under @file{/gnu/store}.
Sub-directories in the store are referred to as @dfn{store paths}. The Sub-directories in the store are referred to as @dfn{store paths}. The
store has an associated database that contains information such has the store has an associated database that contains information such as the
store paths referred to by each store path, and the list of @emph{valid} store paths referred to by each store path, and the list of @emph{valid}
store paths---paths that result from a successful build. store paths---paths that result from a successful build.