Fix two typos in the MozSurface documentation. No bug, r=typo
authorMarkus Stange <mstange@themasta.com>
Tue, 13 May 2014 13:37:56 +0200
changeset 190311 35af5d1c97c31d1438c296c79218492efe132e12
parent 190310 d7968acde5951468a700f5a50048464548cb8f06
child 190312 4e1e052624c2bd93a8deb2c35f79412a2371ce90
push id3741
push userasasaki@mozilla.com
push dateMon, 21 Jul 2014 20:25:18 +0000
treeherdermozilla-esr52@4d6f46f5af68 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerstypo
milestone32.0a1
Fix two typos in the MozSurface documentation. No bug, r=typo
gfx/doc/MozSurface.md
--- a/gfx/doc/MozSurface.md
+++ b/gfx/doc/MozSurface.md
@@ -34,17 +34,17 @@ Drawing web content into a surface and s
 TextureClient and TextureHost are the closest abstractions we currently have to MozSurface.
 Inline documentation about TextureClient and TextureHost can be found in:
 
 * [gfx/layers/client/TextureClient.h](http://dxr.mozilla.org/mozilla-central/source/gfx/layers/client/TextureClient.h)
 * [gfx/layers/composite/TextureHost.h](http://dxr.mozilla.org/mozilla-central/source/gfx/layers/composite/TextureHost.h)
 
 TextureClient is the client-side handle on a MozSurface, while TextureHost is the equivalent host-side representation. There can only be one TextureClient for a given TextureHost, and one TextureHost for a given TextureClient. Likewise, there can only be one shared object for a given TextureClient/TextureHost pair.
 
-A MozSurface containing data that is shared between a client process and a host process exists in the foolowing form:
+A MozSurface containing data that is shared between a client process and a host process exists in the following form:
 
 ```
                                  .
             Client process       .      Host process
                                  .
      ________________      ______________      ______________
     |                |    |              |    |              |
     | TextureClient  +----+ <SharedData> +----+ TextureHost  |
@@ -83,17 +83,17 @@ Note that it is still required to use th
 In most cases we want to be able to paint directly into a surface through the Moz2D API.
 
 A surface lets you *borrow* a DrawTarget that is only valid between Lock and Unlock.
 
     DrawTarget* GetAsDrawTarget();
 
 It is invalid to hold a reference to the DrawTarget after Unlock, and a different DrawTarget may be obtained during the next Lock/Unlock interval.
 
-In some cases we want to use MozSurface without Drawing into it. For instance to share video frames accross processes. Some surface types may also not be accessible through a DrawTarget (for example YCbCr surfaces).
+In some cases we want to use MozSurface without drawing into it. For instance to share video frames accross processes. Some surface types may also not be accessible through a DrawTarget (for example YCbCr surfaces).
 
     bool CanExposeDrawTarget();
 
 helps with making sure that a Surface supports exposing a Moz2D DrawTarget.
 
 ## Using a MozSurface as a source for Compositing
 
 To interface with the Compositor API, MozSurface gives access to TextureSource objects. TextureSource is the cross-backend representation of a texture that Compositor understands.