[pulseaudio-discuss] [PATCH] doc: Fix some typos/wording in man/pulse-daemon.conf.5

[Tanu Kaskinen]

On Mon, 2014-03-17 at 15:37 +0100, Peter Meerwald wrote:
> From: Peter Meerwald <p.meerwald at bct-electronic.com>
> 
> Signed-off-by: Peter Meerwald <pmeerw at pmeerw.net>
> ---
>  man/pulse-daemon.conf.5.xml.in |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/man/pulse-daemon.conf.5.xml.in b/man/pulse-daemon.conf.5.xml.in
> index 9596738..4aa5948 100644
> --- a/man/pulse-daemon.conf.5.xml.in
> +++ b/man/pulse-daemon.conf.5.xml.in
> @@ -394,7 +394,7 @@ USA.
>        the default real-time priority level as configured with
>        <opt>realtime-priority=</opt> fits in this resource limit, if
>        <opt>realtime-scheduling</opt> is enabled. The JACK client
> -      libraries require a real-time prority of 9 by default. </p>
> +      libraries require a real-time priority of 9 by default.</p>
>      </option>
>      <option>
>        <p><opt>rlimit-rttime</opt> Defaults to 1000000.</p>
> @@ -437,11 +437,11 @@ USA.
>      <option>
>        <p><opt>alternate-sample-rate</opt> The alternate sample
>        frequency. Sinks and sources will use either the
> -      default-rate-rate value or this alternate value, typically 44.1
> +      default-sample-rate value or this alternate value, typically 44.1
>        or 48kHz. Switching between default and alternate values is
>        enabled only when the sinks/sources are suspended. This option
>        is ignored in passthrough mode where the stream rate will be used.
> -      If set to the same as the default sample rate, this feature is
> +      If set to the same value as the default sample rate, this feature is
>        disabled.</p>
>      </option>
>  
> @@ -453,7 +453,7 @@ USA.
>      be subdivided into several fragments. It is possible to change
>      these buffer metrics for machines with high scheduling
>      latencies. Not all possible values that may be configured here are
> -    available in all hardware. The driver will to find the nearest
> +    available in all hardware. The driver will find the nearest
>      setting supported. Modern drivers that support timer-based
>      scheduling ignore these options.</p>
>  

Looks good to me.

-- 
Tanu