summaryrefslogtreecommitdiff
path: root/tests/spec/arb_geometry_shader4/execution/program-parameter/vertices-out.c
diff options
context:
space:
mode:
Diffstat (limited to 'tests/spec/arb_geometry_shader4/execution/program-parameter/vertices-out.c')
-rw-r--r--tests/spec/arb_geometry_shader4/execution/program-parameter/vertices-out.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/spec/arb_geometry_shader4/execution/program-parameter/vertices-out.c b/tests/spec/arb_geometry_shader4/execution/program-parameter/vertices-out.c
index 4d23526a4..b4b7488c1 100644
--- a/tests/spec/arb_geometry_shader4/execution/program-parameter/vertices-out.c
+++ b/tests/spec/arb_geometry_shader4/execution/program-parameter/vertices-out.c
@@ -28,7 +28,7 @@
* variable number of output components.
*
* The value of GEOMETRY_VERTICES_OUT is limited by the implementation
- * dependend constants MAX_GEOMETRY_OUTPUT_VERTICES and
+ * dependent constants MAX_GEOMETRY_OUTPUT_VERTICES and
* MAX_GEOMETRY_TOTAL_OUTPUT_COMPONENTS.
*
* From the ARB_geometry_shader4 spec (section Errors):
@@ -126,7 +126,7 @@ test_geometry_vertices_out(const GLuint prog)
* > MAX_GEOMETRY_TOTAL_OUTPUT_COMPONENTS, the spec requires
* ProgramParameter to throw an INVALID_VALUE and subsequent linking to
* fail.
- * But the number of output components can only be infered from the
+ * But the number of output components can only be inferred from the
* geometry shader source (and a geometry shader might not even be
* attached to the program object when ProgramParameter is called).
* So, ignore any errors generated from ProgramParameter and only check