From: Harri Nieminen Date: Mon, 27 Mar 2023 19:09:52 +0000 (+0300) Subject: docs/specs: Fix typos X-Git-Tag: upstream/23.3.3~10994 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=8ebc01ee0bb553cfddefd9938fb3381b7090b211;p=platform%2Fupstream%2Fmesa.git docs/specs: Fix typos Found by codespell Part-of: --- diff --git a/docs/_extra/specs/MESA_bgra.txt b/docs/_extra/specs/MESA_bgra.txt index 05de735..39793e3 100644 --- a/docs/_extra/specs/MESA_bgra.txt +++ b/docs/_extra/specs/MESA_bgra.txt @@ -81,7 +81,7 @@ Additions to Chapter 8 of the GLES 3.2 Specification (Textures and Samplers) BGRA_EXT B, G, R, A Color - Add to table 8.9 (Effective internal format correspondig to + Add to table 8.9 (Effective internal format corresponding to external format). Format Type Effective diff --git a/docs/_extra/specs/MESA_multithread_makecurrent.spec b/docs/_extra/specs/MESA_multithread_makecurrent.spec index 5065c2f..7a58731 100644 --- a/docs/_extra/specs/MESA_multithread_makecurrent.spec +++ b/docs/_extra/specs/MESA_multithread_makecurrent.spec @@ -70,7 +70,7 @@ Changes to Chapter 2 of the GLX 1.3 Specification (Functions and Errors) In addition, an indirect rendering context can be current for only one thread at a time. A direct rendering context may be current to multiple threads, with synchronization of access to - the context thruogh the GL managed by the application through + the context through the GL managed by the application through mutexes. Changes to Chapter 3 of the GLX 1.3 Specification (Functions and Errors) diff --git a/docs/_extra/specs/MESA_query_renderer.spec b/docs/_extra/specs/MESA_query_renderer.spec index 10f68ec..f6209ba 100644 --- a/docs/_extra/specs/MESA_query_renderer.spec +++ b/docs/_extra/specs/MESA_query_renderer.spec @@ -360,7 +360,7 @@ Revision History Version 4, 2013/02/01 - Add issue #12 regarding texture / renderbuffer format queries. - Version 5, 2013/02/14 - Add issues #13 and #14 regarding simpler queires + Version 5, 2013/02/14 - Add issues #13 and #14 regarding simpler queries after the context is created and made current. Add issue #15 regarding the string query. Add issue #16 regarding the value type returned diff --git a/docs/_extra/specs/MESA_shader_integer_functions.txt b/docs/_extra/specs/MESA_shader_integer_functions.txt index 9fcc9b4..27f86de 100644 --- a/docs/_extra/specs/MESA_shader_integer_functions.txt +++ b/docs/_extra/specs/MESA_shader_integer_functions.txt @@ -46,7 +46,7 @@ Overview GL_ARB_gpu_shader5 extends GLSL in a number of useful ways. Much of this added functionality requires significant hardware support. There are many - aspects, however, that can be easily implmented on any GPU with "real" + aspects, however, that can be easily implemented on any GPU with "real" integer support (as opposed to simulating integers using floating point calculations). diff --git a/docs/_extra/specs/OLD/EGL_MESA_screen_surface.txt b/docs/_extra/specs/OLD/EGL_MESA_screen_surface.txt index 698a240..b86a405 100644 --- a/docs/_extra/specs/OLD/EGL_MESA_screen_surface.txt +++ b/docs/_extra/specs/OLD/EGL_MESA_screen_surface.txt @@ -51,7 +51,7 @@ Overview monitor. The screen surface can be scrolled by changing this origin. This extension also defines functions for controlling the monitor's - display mode (width, height, refresh rate, etc), and specifing which + display mode (width, height, refresh rate, etc), and specifying which screen surface is to be displayed on a monitor. The new EGLModeMESA type and related functions are very similar to the diff --git a/docs/_extra/specs/OLD/MESA_trace.spec b/docs/_extra/specs/OLD/MESA_trace.spec index dc4166e..95cb2a6 100644 --- a/docs/_extra/specs/OLD/MESA_trace.spec +++ b/docs/_extra/specs/OLD/MESA_trace.spec @@ -64,7 +64,7 @@ Issues that enjoys privileged access, or that they do not wish to separate the tracing code from their driver code base. - (2) Should the Trace API explicitely support the notion of "frames? + (2) Should the Trace API explicitly support the notion of "frames? This would require hooking into glXSwapBuffers calls as well. RESOLVED: No. The application can use NewTraceMESA/EndTraceMESA @@ -93,7 +93,7 @@ Issues be considered persistent state? RESOLVED: No. The implementation is not forced to use this information - on subsequent occurences of name/pointer, and is free to consider it + on subsequent occurrences of name/pointer, and is free to consider it transient state. (5) Should comment commands be prohibited between Begin/End? @@ -218,7 +218,7 @@ Additions to Chapter 5 of the OpenGL 1.2.1 Specification (Special Functions) Bitmap and DrawPixels commands. TRACE_ERRORS_BIT_MESA controls logging of all errors. If this bit is - set, GetError will be executed whereever applicable, and the result will + set, GetError will be executed wherever applicable, and the result will be added to the trace as a comment. The error returns are cached and returned to the application on its GetError calls. If the user does not wish the additional GetError calls to be performed, this bit should not