commit 8814630f0b59421e558f4403b79f5dc3a025a386
author Michael Witten <mfwitten@gmail.com> Thu Aug 25 18:46:10 2011 +0000
committer Michael Witten <mfwitten@gmail.com> Mon Aug 29 19:30:53 2011 +0000
tree dc010afe533ca552bb5eb7e3106866b27002c066
parent 57a15fd663d6680dc100a537f0ed328993c33af2

DocBook/drm: Insert missing `that'

Signed-off-by: Michael Witten <mfwitten@gmail.com>

Documentation/DocBook/drm.tmpl

diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index 33290e3..25e0f46 100644
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -321,10 +321,10 @@
       <para>
 	Finding &amp; mapping resources is fairly straightforward.  The
 	DRM wrapper functions, drm_get_resource_start() and
-	drm_get_resource_len() may be used to find BARs on the given
+	drm_get_resource_len(), may be used to find BARs on the given
 	drm_device struct.  Once those values have been retrieved, the
 	driver load function can call drm_addmap() to create a new
-	mapping for the BAR in question.  Note you probably want a
+	mapping for the BAR in question.  Note that you probably want a
 	drm_local_map_t in your driver private structure to track any
 	mappings you create.
 <!-- !Fdrivers/gpu/drm/drm_bufs.c drm_get_resource_* -->