1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index 3470c6b2f843..66a114a05c6f 100644
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -455,7 +455,7 @@
          a GTT DRM MM object, which provides an address space pool for
          object allocation.  In a KMS configuration, the driver
          needs to allocate and initialize a command ring buffer following
-          core GEM initialization.  A UMA device usually has a so-called
+          core GEM initialization.  A UMA device usually has what is called a
          "stolen" memory region, which provides space for the initial
          framebuffer and large, contiguous memory regions required by the
          device.  This space is not typically managed by GEM, and must

diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl index 3470c6b2f843..66a114a05c6f 100644 --- a/Documentation/DocBook/drm.tmpl +++ b/Documentation/DocBook/drm.tmpl
@@ -455,7 +455,7 @@
455	a GTT DRM MM object, which provides an address space pool for	455	a GTT DRM MM object, which provides an address space pool for
456	object allocation. In a KMS configuration, the driver	456	object allocation. In a KMS configuration, the driver
457	needs to allocate and initialize a command ring buffer following	457	needs to allocate and initialize a command ring buffer following
458	core GEM initialization. A UMA device usually has a so-called	458	core GEM initialization. A UMA device usually has what is called a
459	"stolen" memory region, which provides space for the initial	459	"stolen" memory region, which provides space for the initial
460	framebuffer and large, contiguous memory regions required by the	460	framebuffer and large, contiguous memory regions required by the
461	device. This space is not typically managed by GEM, and must	461	device. This space is not typically managed by GEM, and must