[ALSA] Documentation/sound/alsa/DocBook: typos

Some typos in Documentation/sound/alsa/DocBook.

Signed-off-by: Nicolas Kaiser <nikai@nikai.net>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Jaroslav Kysela <perex@suse.cz>
This commit is contained in:
Nicolas Kaiser 2007-01-22 14:54:33 +01:00 committed by Jaroslav Kysela
parent f7ba7fc617
commit 5bda9fa1ae
2 changed files with 9 additions and 9 deletions

View file

@ -36,7 +36,7 @@
</bookinfo> </bookinfo>
<chapter><title>Management of Cards and Devices</title> <chapter><title>Management of Cards and Devices</title>
<sect1><title>Card Managment</title> <sect1><title>Card Management</title>
!Esound/core/init.c !Esound/core/init.c
</sect1> </sect1>
<sect1><title>Device Components</title> <sect1><title>Device Components</title>
@ -59,7 +59,7 @@
<sect1><title>PCM Format Helpers</title> <sect1><title>PCM Format Helpers</title>
!Esound/core/pcm_misc.c !Esound/core/pcm_misc.c
</sect1> </sect1>
<sect1><title>PCM Memory Managment</title> <sect1><title>PCM Memory Management</title>
!Esound/core/pcm_memory.c !Esound/core/pcm_memory.c
</sect1> </sect1>
</chapter> </chapter>

View file

@ -2126,7 +2126,7 @@
accessible via <constant>substream-&gt;runtime</constant>. accessible via <constant>substream-&gt;runtime</constant>.
This runtime pointer holds the various information; it holds This runtime pointer holds the various information; it holds
the copy of hw_params and sw_params configurations, the buffer the copy of hw_params and sw_params configurations, the buffer
pointers, mmap records, spinlocks, etc. Almost everyhing you pointers, mmap records, spinlocks, etc. Almost everything you
need for controlling the PCM can be found there. need for controlling the PCM can be found there.
</para> </para>
@ -2339,7 +2339,7 @@ struct _snd_pcm_runtime {
<para> <para>
When the PCM substreams can be synchronized (typically, When the PCM substreams can be synchronized (typically,
synchorinized start/stop of a playback and a capture streams), synchronized start/stop of a playback and a capture streams),
you can give <constant>SNDRV_PCM_INFO_SYNC_START</constant>, you can give <constant>SNDRV_PCM_INFO_SYNC_START</constant>,
too. In this case, you'll need to check the linked-list of too. In this case, you'll need to check the linked-list of
PCM substreams in the trigger callback. This will be PCM substreams in the trigger callback. This will be
@ -3244,7 +3244,7 @@ struct _snd_pcm_runtime {
You can even define your own constraint rules. You can even define your own constraint rules.
For example, let's suppose my_chip can manage a substream of 1 channel For example, let's suppose my_chip can manage a substream of 1 channel
if and only if the format is S16_LE, otherwise it supports any format if and only if the format is S16_LE, otherwise it supports any format
specified in the <structname>snd_pcm_hardware</structname> stucture (or in any specified in the <structname>snd_pcm_hardware</structname> structure (or in any
other constraint_list). You can build a rule like this: other constraint_list). You can build a rule like this:
<example> <example>
@ -3767,7 +3767,7 @@ struct _snd_pcm_runtime {
<para> <para>
Like <structfield>get</structfield> callback, Like <structfield>get</structfield> callback,
when the control has more than one elements, when the control has more than one elements,
all elemehts must be evaluated in this callback, too. all elements must be evaluated in this callback, too.
</para> </para>
</section> </section>
@ -5528,12 +5528,12 @@ struct _snd_pcm_runtime {
#ifdef CONFIG_PM #ifdef CONFIG_PM
static int snd_my_suspend(struct pci_dev *pci, pm_message_t state) static int snd_my_suspend(struct pci_dev *pci, pm_message_t state)
{ {
.... /* do things for suspsend */ .... /* do things for suspend */
return 0; return 0;
} }
static int snd_my_resume(struct pci_dev *pci) static int snd_my_resume(struct pci_dev *pci)
{ {
.... /* do things for suspsend */ .... /* do things for suspend */
return 0; return 0;
} }
#endif #endif
@ -6098,7 +6098,7 @@ struct _snd_pcm_runtime {
<!-- ****************************************************** --> <!-- ****************************************************** -->
<!-- Acknowledgments --> <!-- Acknowledgments -->
<!-- ****************************************************** --> <!-- ****************************************************** -->
<chapter id="acknowledments"> <chapter id="acknowledgments">
<title>Acknowledgments</title> <title>Acknowledgments</title>
<para> <para>
I would like to thank Phil Kerr for his help for improvement and I would like to thank Phil Kerr for his help for improvement and