diff mbox series

media: v4l2-subdev.rst: two typo fixes

Message ID 20210216064455.18235-1-tomi.valkeinen@ideasonboard.com (mailing list archive)
State New, archived
Headers show
Series media: v4l2-subdev.rst: two typo fixes | expand

Commit Message

Tomi Valkeinen Feb. 16, 2021, 6:44 a.m. UTC 
Fix a few minor typos in the text.

Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
---
 Documentation/driver-api/media/v4l2-subdev.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff mbox series

Patch

diff --git a/Documentation/driver-api/media/v4l2-subdev.rst b/Documentation/driver-api/media/v4l2-subdev.rst
index bb5b1a7cdfd9..f413b11e70de 100644
--- a/Documentation/driver-api/media/v4l2-subdev.rst
+++ b/Documentation/driver-api/media/v4l2-subdev.rst
@@ -207,7 +207,7 @@  begin to form a list of subdevice descriptors that the bridge device
 needs for its operation. Subdevice descriptors are added to the notifier
 using the :c:func:`v4l2_async_notifier_add_subdev` call. This function
 takes two arguments: a pointer to struct :c:type:`v4l2_async_notifier`,
-and a pointer to the subdevice descripter, which is of type struct
+and a pointer to the subdevice descriptor, which is of type struct
 :c:type:`v4l2_async_subdev`.
 
 The V4L2 core will then use these descriptors to match asynchronously
@@ -225,7 +225,7 @@  contain several subdevs that use an I2C bus, but also a subdev that is
 controlled through GPIO pins. This distinction is only relevant when setting
 up the device, but once the subdev is registered it is completely transparent.
 
-Once te subdev has been registered you can call an ops function either
+Once the subdev has been registered you can call an ops function either
 directly:
 
 .. code-block:: c