Typos + disabled autoplay

Author: rougier

02-introduction.rst

@@ -414,7 +414,7 @@ Libraries
 
 .. Note::
 
-   Even though glumpy and vispy shares a number of concept, they are different.
+   Even though glumpy and vispy share a number of concept, they are different.
    vispy offers a high-level interface that may be convenient in some
    situations but this tends to hide the internal machinery. This is one of the
    reason we'll be using glumpy instead (the other reason being that I'm the

03-quickstart.rst

@@ -17,7 +17,7 @@ Preliminaries
 -------------------------------------------------------------------------------
 
 The main difficulty for newcomers in programming modern OpenGL is that it
-requires to underdtand a lot of different concepts at once and then, to perform
+requires to understand a lot of different concepts at once and then, to perform
 a lot of operations before rendering anything on screen. This complexity
 implies that there are many places where your code can be wrong, both at the
 conceptual and code level. To illustrate this difficulty, we'll program our
@@ -109,7 +109,7 @@ GL Primitives
    Common OpenGL rendering primitives.
 
 Ok, now things are getting serious because we need to actually tell OpenGL what
-to do with the vertices, i.e. how to render them? what do they describe in term
+to do with the vertices, i.e. how to render them? What do they describe in term
 of geometrical primitives? This is quite an important topic since this will
 determines how fragments will be actually generated as illustrated on the image
 below:
@@ -380,7 +380,7 @@ equivalent to a C `double`). So let us specify a NumPy array holding 4×2
    # Build data
    data = np.zeros((4,2), dtype=np.float32))
 
-Wen then create a placeholder on the GPU without yet specifying the size:
+We then create a placeholder on the GPU without yet specifying the size:
 
 .. code:: python
 
@@ -395,7 +395,7 @@ We now need to bind the buffer to the program, that is, for each attribute
 present in the vertex shader program, we need to tell OpenGL where to find the
 corresponding data (i.e. GPU buffer) and this requires some computations. More
 precisely, we need to tell the GPU how to read the buffer in order to bind each
-value to the relevant attribute. To do this, GPU needs to kow what is the
+value to the relevant attribute. To do this, GPU needs to know what is the
 stride between 2 consecutive element and what is the offset to read one
 attribute:
 
@@ -412,7 +412,7 @@ attribute:
 
 
 In our simple quad scenario, this is relatively easy to write because we have a
-single attribute ("`position`"). We first requires the attribute location
+single attribute ("`position`"). We first require the attribute location
 inside the program and then we bind the buffer with the relevant offset.
 
 .. code:: python
@@ -750,7 +750,6 @@ the quad program (see `<code/chapter-03/glumpy-quad-varying-color.py>`_):
 
    .. figure:: movies/chapter-03/quad-scale.mp4
       :loop:
-      :autoplay:
       :controls:
       :figwidth: 35%
 
@@ -808,7 +807,6 @@ tricks in the next chapters.
 
 .. figure:: movies/chapter-03/quad-scale.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
 
@@ -830,7 +828,6 @@ Solution: `<code/chapter-03/quad-scale.py>`_
 
 .. figure:: movies/chapter-03/quad-rotate.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
 

05-cube.rst

@@ -171,7 +171,6 @@ Actual rendering
 
 .. figure:: movies/chapter-05/solid-cube.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
 
@@ -254,7 +253,6 @@ shader.
 
 .. figure:: movies/chapter-05/color-cube.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
 
@@ -289,7 +287,6 @@ Outlined cube
 
 .. figure:: movies/chapter-05/outline-cube.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
 
@@ -359,7 +356,6 @@ Textured cube
 
 .. figure:: movies/chapter-05/texture-cube.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
 
@@ -457,7 +453,6 @@ Exercises
 
 .. figure:: movies/chapter-05/color-border-cube-1.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
 
@@ -482,7 +477,6 @@ cube code <code/chapter-05/color-cube.py>`_, try to modify only the shader code
 
 .. figure:: movies/chapter-05/color-border-cube-2.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
 

06-anti-grain.rst

@@ -330,7 +330,6 @@ Distance to a circle is the easiest to compute.
 
 .. figure:: movies/chapter-06/SDF-circle.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 25%
    :figclass: right
@@ -358,7 +357,6 @@ the projection of P onto the place.
 
 .. figure:: movies/chapter-06/SDF-plane.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 25%
    :figclass: right
@@ -387,7 +385,6 @@ vertices defining the box.
 
 .. figure:: movies/chapter-06/SDF-box.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 25%
    :figclass: right
@@ -414,7 +411,6 @@ Rounded Box
 
 .. figure:: movies/chapter-06/SDF-round-box.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 25%
    :figclass: right
@@ -442,7 +438,6 @@ Fake Box
 
 .. figure:: movies/chapter-06/SDF-fake-box.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 25%
    :figclass: right
@@ -469,7 +464,6 @@ True triangle
 
 .. figure:: movies/chapter-06/SDF-triangle.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 25%
    :figclass: right
@@ -515,7 +509,6 @@ Round triangle
 
 .. figure:: movies/chapter-06/SDF-round-triangle.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 25%
    :figclass: right
@@ -543,7 +536,6 @@ Fake triangle
 
 .. figure:: movies/chapter-06/SDF-fake-triangle.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 25%
    :figclass: right
@@ -583,7 +575,6 @@ True ellipse
 
 .. figure:: movies/chapter-06/SDF-ellipse.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 25%
    :figclass: right
@@ -650,7 +641,6 @@ Fake (but fast) ellipse
 
 .. figure:: movies/chapter-06/SDF-fake-ellipse.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 25%
    :figclass: right

07-points.rst

@@ -200,7 +200,6 @@ Ellipses
 
 .. figure:: movies/chapter-07/ellipses.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 30%
    :figclass: right
@@ -451,7 +450,6 @@ Antialiased triangles
 
 .. figure:: movies/chapter-07/triangles.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 30%
 

08-markers.rst

@@ -507,7 +507,6 @@ of your texture...
 
 .. figure:: movies/chapter-08/texture-marker.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 30%
 
@@ -568,7 +567,6 @@ Light and shadows
 
 .. figure:: movies/chapter-08/SDF-light-shadow.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 50%
 

09-lines.rst

@@ -414,7 +414,7 @@ if a given fragment is inside the joint area or not. This requires a specific
 parameterization that relies on having a different tesselation with 4×n
 vertices instead of 2×n. I won't explain all the details here but only provide
 the final result that you can found in `geom-path.py
-<code/chapter-09/geom.path.py>`_.
+<code/chapter-09/geom_path.py>`_.
 
 If you look at the sources, you'll see I'm using a geometry shader, which is a
 new type of shader that is not officially available in GL ES 2.0 but which is
@@ -457,7 +457,7 @@ the details in the provided demo script. See the caption of the image below.
    Figure
 
    Different line joints using a geometry shader. See
-   `geom-path.py <code/chapter-09/geom.path.py>`_.
+   `geom-path.py <code/chapter-09/geom_path.py>`_.
 
 
 
@@ -552,7 +552,6 @@ Simple dotted pattern
 
 .. figure:: movies/chapter-09/linestrip-dotted.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
 
@@ -603,7 +602,6 @@ this line is then just a matter of a modulo.
 
 .. figure:: movies/chapter-09/linestrip-spaded.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
 
@@ -636,7 +634,6 @@ result is illustrated on the movies below.
 
 .. figure:: movies/chapter-09/stars.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 30%
    :figclass: left
@@ -645,7 +642,6 @@ result is illustrated on the movies below.
 
 .. figure:: movies/chapter-09/sphere.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 30%
    :figclass: left
@@ -654,7 +650,6 @@ result is illustrated on the movies below.
 
 .. figure:: movies/chapter-09/tiger.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 30%
    :figclass: left
@@ -671,7 +666,6 @@ PR. Contact me if you're interested.
 
 .. figure:: movies/chapter-09/linestrip-3d.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
    :figclass: right
@@ -767,7 +761,6 @@ Varying apparent thickness
 
 .. figure:: movies/chapter-09/linestrip-3d-better.mp4
    :loop:
-   :autoplay:
    :controls:
    :figwidth: 35%
    :figclass: right

11-meshes.rst

@@ -94,7 +94,6 @@ Work in Progress.
    .. figure:: movies/chapter-11/boy.mp4
       :figclass: right
       :loop:
-      :autoplay:
       :controls:
       :figwidth: 35%
 

14-special.rst

@@ -30,7 +30,6 @@ Work in Progress.
 
    .. figure:: data/quad-grid.mp4
       :loop:
-      :autoplay:
       :controls:
       :figwidth: 35%
       :figclass: left