Fix typos in docs.

BUG=None

Change-Id: Ib201d91c586717b3027996b379240619173d828d
Reviewed-on: https://chromium-review.googlesource.com/418337
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Frank Henigman <fjhenigman@chromium.org>

doc/BufferImplementation.md

@@ -80,7 +80,7 @@ Aside from using array buffers to feed attribute data to the vertex shader,
 OpenGL also supports attributes which remain constant for all vertices used in a
 draw call. Direct3D 9 doesn't have a similar concept, at least not explicitly.
 
-Constant attributes are implementated using separate (static) vertex buffers,
+Constant attributes are implemented using separate (static) vertex buffers,
 and uses a stride of 0 to ensure that every vertex retrieves the same data.
 Using a stride of 0 is not possible with streaming buffers because on some
 hardware it is incompatible with the D3DUSAGE\_DYNAMIC flag. We found that with

doc/BuildingAngleForChromiumDevelopment.md

@@ -9,7 +9,7 @@ Steps:
   * Checkout and build [Chromium](http://dev.chromium.org/Home).
   * You should now be able to use `ninja -C out/Debug angle_end2end_tests`, for example.
 
-## Building Standalone ANGLE insinde Chromium
+## Building Standalone ANGLE inside Chromium
 
 On Mac, ANGLE doesn't yet include the dEQP tests or the API translation libraries as part of Chromium. ANGLE also includes some sample applications and a few other targets that don't build on Chromium. These steps describe how to build such targets within a Chromium checkout.
 

doc/ContributingCode.md

@@ -24,7 +24,7 @@
 ### Testing
  * ANGLE uses trybots to test on a variety of platforms.  Please run your changes against our trybots and check the results before requesting a review.
     * Upload your change (see [Making changes](ContributingCode.md#Making-changes)).
-    * Run `git try`.  If you are not part of the `angle-commiters` group, you will need to either ask to be added or ask a member of the group to submit the tryjob for you.
+    * Run `git try`.  If you are not part of the `angle-committers` group, you will need to either ask to be added or ask a member of the group to submit the tryjob for you.
     * Wait for the bots to report the result on the code review page, this can take up to two hours for some of the debug bots.
     * Sometimes the bots report failures that are not due to the patch being tested.  If a failure is unexpected, ask an ANGLE project member for advice.
     * The `-b` flag can be used with `git try` to target individual bots.  Ex: `git try -b win_angle_rel_ng`.
@@ -36,7 +36,7 @@
       * Your failures must be a subset of the expected WebGL failures located in [`src/tests/WebGL-CTS-known-failures.txt`](../src/tests/WebGL-CTS-known-failures.txt). If you believe there are failing tests missing from the known failures file, please notify project members.
    * If your code isn't covered by an existing test, you are *strongly encouraged* to add new test coverage. This both ensures that your code is correct and that new contributors won't break it in the future.
    * If you are submitting a performance fix, test your code with `angle_perftests` and add a new performance test if it is not covered by the existing benchmarks.
-   * The [Chromium GPU FYI bot waterfall](http://build.chromium.org/p/chromium.gpu.fyi/console) provides continuous integration for ANGLE patches that have been committed.  There may be hardware configurations that are not tested by the ANGLE trybots, if you notice breakage on this waterfall after landing a patch, please notify a project memeber.
+   * The [Chromium GPU FYI bot waterfall](http://build.chromium.org/p/chromium.gpu.fyi/console) provides continuous integration for ANGLE patches that have been committed.  There may be hardware configurations that are not tested by the ANGLE trybots, if you notice breakage on this waterfall after landing a patch, please notify a project member.
    * ANGLE also includes the [drawElements Quality Program (dEQP)](dEQP.md) for additional testing. If you're working on a new feature, there may be some extensive tests for it already written.
 
 ### Legal

doc/VTF.md

@@ -14,7 +14,7 @@ Tasks to implement vertex texture support.
     *   ensure other (non-bias/non-LOD) texture functions work in vertex shaders
     *   non-mipmapped textures use the only level available
     *   mipmapped textures use only the base level (ie level 0).
-2.  update implementation-dependant constants in Context.h
+2.  update implementation-dependent constants in Context.h
     *   MAX\_VERTEX\_TEXTURE\_IMAGE\_UNITS = 4
     *   MAX\_COMBINED\_TEXTURE\_IMAGE\_UNITS =
         MAX\_VERTEX\_TEXTURE\_IMAGE\_UNITS + MAX\_TEXTURE\_IMAGE\_UNITS (ie 20).