unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jelle Licht <jlicht@fsfe.org>
To: 33177@debbugs.gnu.org
Subject: bug#33177: Sound Services manual typo
Date: Sat, 27 Oct 2018 17:37:52 +0200	[thread overview]
Message-ID: <87sh0r4cz3.fsf@fsfe.org> (raw)

The "Sound Services" section[1] of the manual starts of on a confusing
note for me, but this might just be a typo.

The confusing sentence is:
> The ‘(gnu services sound)’ module provides a service to configure the
> Advanced Linux Sound Architecture (ALSA) system, which making
                                                         ^^^^^^
> PulseAudio the preferred ALSA output driver.

I was thinking of simply replacing "making" with "makes" in that
snippet, but I am not sure whether this still keeps the (intended)
meaning intact.

[1]: `(info "(Guix)Sound Services")'

NB. When creating patches for the manual, can one just commit the
changes and be done with it, or does this involve some extra steps? I
ask since I found the offending sentence in both guix.texi and
guix.fr.texi.

             reply	other threads:[~2018-10-27 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-27 15:37 Jelle Licht [this message]
2018-11-03 13:54 ` bug#33177: Sound Services manual typo Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sh0r4cz3.fsf@fsfe.org \
    --to=jlicht@fsfe.org \
    --cc=33177@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).