From eb2b8d4273fb8b73821ca8dbc9c0de10e9879833 Mon Sep 17 00:00:00 2001
From: Michael Witten <mfwitten@gmail.com>
Date: Thu, 25 Aug 2011 18:58:42 +0000
Subject: DocBook/drm: , -> :

Signed-off-by: Michael Witten <mfwitten@gmail.com>
---
 Documentation/DocBook/drm.tmpl | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'Documentation/DocBook')

diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index 60ddf4be11c7..953c4cb726bb 100644
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -389,7 +389,7 @@
       <para>
 	If your driver supports memory management (it should!), you
 	need to set that up at load time as well.  How you initialize
-	it depends on which memory manager you're using, TTM or GEM.
+	it depends on which memory manager you're using: TTM or GEM.
       </para>
       <sect3>
 	<title>TTM initialization</title>
@@ -647,7 +647,7 @@ void intel_crt_init(struct drm_device *dev)
     <para>
       The memory manager lies at the heart of many DRM operations; it
       is required to support advanced client features like OpenGL
-      pbuffers.  The DRM currently contains two memory managers, TTM
+      pbuffers.  The DRM currently contains two memory managers: TTM
       and GEM.
     </para>
 
-- 
cgit v1.2.3