X-Git-Url: https://code.delx.au/pulseaudio/blobdiff_plain/3b67ebb63e7920854ef9a972b47dcc2266cacab6..997e369691496be4ecfe38e3516f7e007ed69a7b:/man/pulse-daemon.conf.5.xml.in
diff --git a/man/pulse-daemon.conf.5.xml.in b/man/pulse-daemon.conf.5.xml.in
index 49f9f22f..8bd076d7 100644
--- a/man/pulse-daemon.conf.5.xml.in
+++ b/man/pulse-daemon.conf.5.xml.in
@@ -67,7 +67,7 @@ USA.
@@ -265,7 +265,7 @@ USA.
@@ -322,7 +326,7 @@ USA.
-
log-time= With each logged messages log the
+
log-time= With each logged message log the
relative time since startup. Defaults to no.
@@ -390,7 +394,7 @@ USA.
the default real-time priority level as configured with
realtime-priority= fits in this resource limit, if
realtime-scheduling is enabled. The JACK client
- libraries require a real-time prority of 9 by default.
+ libraries require a real-time priority of 9 by default.
rlimit-rttime Defaults to 1000000.
@@ -433,11 +437,12 @@ USA.
alternate-sample-rate 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 zero, this feature is disabled.
+ If set to the same value as the default sample rate, this feature is
+ disabled.
@@ -448,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.
@@ -469,8 +474,8 @@ USA.
With the flat volume feature enabled, the sink HW volume is set
to the same level as the highest volume input stream. Any other streams
(with lower volumes) have the appropriate adjustment applied in SW to
- bring them to the correct overall level. Sadly hadware mixer changes
- cannot be timed accurately and thus this change of volumes can somtimes
+ bring them to the correct overall level. Sadly hardware mixer changes
+ cannot be timed accurately and thus this change of volumes can sometimes
cause the resulting output sound to be momentarily too loud or too soft.
So to ensure SW and HW volumes are applied concurrently without any
glitches, their application needs to be synchronized. The sink