DocBook/media: Some typo fixes

Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

diff --git a/Documentation/DocBook/v4l/capture.c.xml b/Documentation/DocBook/v4l/capture.c.xml
index acf46b6dac2319acfb45bfaf230a574a887712e5..1c5c49a2de59322174c9d89af61feb34585e8fe6 100644 (file)
--- a/Documentation/DocBook/v4l/capture.c.xml
+++ b/Documentation/DocBook/v4l/capture.c.xml
@@ -4,8 +4,8 @@
  *
  *  This program can be used and distributed without restrictions.
  *
- *      This program were got from V4L2 API, Draft 0.20
- *              available at: http://v4l2spec.bytesex.org/
+ *      This program is provided with the V4L2 API
+ * see http://linuxtv.org/docs.php for more information
  */
 
 #include <stdio.h>

diff --git a/Documentation/DocBook/v4l/common.xml b/Documentation/DocBook/v4l/common.xml
index dd598ac9a450d6cc08a6c8a1edd63c4e310d0b8a..d6744b77e59189fd81af34341f280cc62075f030 100644 (file)
--- a/Documentation/DocBook/v4l/common.xml
+++ b/Documentation/DocBook/v4l/common.xml
@@ -802,7 +802,7 @@ optional.</para>
 a special ioctl to enumerate all image formats supported by video
 capture, overlay or output devices is available.<footnote>
          <para>Enumerating formats an application has no a-priori
-knowledge of (otherwise it could explicitely ask for them and need not
+knowledge of (otherwise it could explicitly ask for them and need not
 enumerate) seems useless, but there are applications serving as proxy
 between drivers and the actual video applications for which this is
 useful.</para>

diff --git a/Documentation/DocBook/v4l/remote_controllers.xml b/Documentation/DocBook/v4l/remote_controllers.xml
index eb669537a6413dd31154aef93f74aea60f0bad36..985325cbc9adaee0a84a2278b9c870ab46e9ff5a 100644 (file)
--- a/Documentation/DocBook/v4l/remote_controllers.xml
+++ b/Documentation/DocBook/v4l/remote_controllers.xml
@@ -2,8 +2,13 @@
 <section id="Remote_controllers_Intro">
 <title>Introduction</title>
 
-<para>Currently, most analog and digital devices have a Infrared input for remote controllers. Each manufacturer has their own type of control. It is not rare that the same manufacturer to ship different types of controls, depending on the device.</para>
-<para>Unfortunately, during several years, there weren't any effort to uniform the IR keycodes under different boards. This resulted that the same IR keyname to be mapped completely different on different IR's. Due to that, V4L2 API now specifies a standard for mapping Media keys on IR.</para>
+<para>Currently, most analog and digital devices have a Infrared input for remote controllers. Each 
+manufacturer has their own type of control. It is not rare for the same manufacturer to ship different 
+types of controls, depending on the device.</para>
+<para>Unfortunately, for several years, there was no effort to create uniform IR keycodes for
+different devices.  This caused the same IR keyname to be mapped completely differently on
+different IR devices. This resulted that the same IR keyname to be mapped completely different on 
+different IR's. Due to that, V4L2 API now specifies a standard for mapping Media keys on IR.</para>
 <para>This standard should be used by both V4L/DVB drivers and userspace applications</para>
 <para>The modules register the remote as keyboard within the linux input layer. This means that the IR key strokes will look like normal keyboard key strokes (if CONFIG_INPUT_KEYBOARD is enabled). Using the event devices (CONFIG_INPUT_EVDEV) it is possible for applications to access the remote via /dev/input/event devices.</para>