From 53c3cfbecba041d1a215f7a5689df796b97949e8 Mon Sep 17 00:00:00 2001 From: Alan Coopersmith Date: Sat, 26 Mar 2022 08:56:16 -0700 Subject: Fix spelling/wording issues Found by using: codespell --builtin clear,rare,usage,informal,code,names Signed-off-by: Alan Coopersmith --- README.md | 2 +- XvMC_API.txt | 24 ++++++++++++------------ configure.ac | 2 +- src/XvMC.c | 2 +- wrapper/XvMCWrapper.c | 2 +- 5 files changed, 16 insertions(+), 16 deletions(-) diff --git a/README.md b/README.md index e490c4a..9ae8130 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ Xorg mailing list: https://lists.x.org/mailman/listinfo/xorg -The master development code repository can be found at: +The primary development code repository can be found at: https://gitlab.freedesktop.org/xorg/lib/libXvMC diff --git a/XvMC_API.txt b/XvMC_API.txt index a12dbee..adeea25 100644 --- a/XvMC_API.txt +++ b/XvMC_API.txt @@ -31,7 +31,7 @@ /********************************************************************/ XvMC extends the X-Video extension (Xv) and makes use of the - familar concept of the XvPort. Ports have attributes that can be set + familiar concept of the XvPort. Ports have attributes that can be set and queried through Xv. In XvMC ports can also have hardware motion compensation contexts created for use with them. Ports which support XvImages (ie. they have an "XV_IMAGE" port encoding as described in @@ -343,7 +343,7 @@ XvMCCreateSurface( Creates a surface (Frame) for use with the specified context. The surface structure is filled out and Success is returned if no - error occured. + error occurred. context - pointer to a valid context. The context implies the surface type to be created, and its dimensions. @@ -398,7 +398,7 @@ Status XvMCCreateBlocks ( ); This allocates an array of DCT blocks in the XvMCBlockArray - structure passed to it. Success is returned if no error occured. + structure passed to it. Success is returned if no error occurred. display - The connection to the server. @@ -579,7 +579,7 @@ Status XvMCCreateMacroBlocks ( ); This allocates an array of XvMCMacroBlocks in the XvMCMacroBlockArray - structure passed to it. Success is returned if no error occured. + structure passed to it. Success is returned if no error occurred. display - The connection to the server. @@ -634,7 +634,7 @@ Status XvMCRenderSurface( return until it has read all of the macroblocks, however, rendering will usually not be completed by that time. The return of this function means it is safe to touch the blocks and macroblock_array. - To synchronize rendering see the section on sychronization below. + To synchronize rendering see the section on synchronization below. display - The connection to the server. @@ -1120,9 +1120,9 @@ XvMCFlushSurface (Display *display, XvMCSurface *surface) This function commits pending rendering requests to ensure that they will be completed in a finite amount of time. - display - The connnection to the server. + display - The connection to the server. - surface - The surface whos rendering requests should be flushed. + surface - The surface whose rendering requests should be flushed. Errors: @@ -1134,7 +1134,7 @@ XvMCGetSurfaceStatus (Display *display, XvMCSurface *surface, int *stat) display - The connection to the server. - surface - The surface whos status is being queried. + surface - The surface whose status is being queried. stat - May be any of the following OR'd together: @@ -1181,7 +1181,7 @@ XvMCFlushSubpicture (Display *display, XvMCSubpicture *subpicture) display - The connection to the server. - subpicture - The subpicture whos compositing should be flushed. + subpicture - The subpicture whose compositing should be flushed. Errors: @@ -1193,7 +1193,7 @@ XvMCGetSubpictureStatus (Display *display, XvMCSubpicture *subpic, int *stat) display - The connection to the server. - subpic - The subpicture whos status is being queried. + subpic - The subpicture whose status is being queried. stat - may be any of the following OR'd together: @@ -1231,7 +1231,7 @@ XvMCQueryAttributes ( display - The connection to the server. - context - The context whos attributes we are querying. + context - The context whose attributes we are querying. number - The returned number of recognized atoms. @@ -1279,7 +1279,7 @@ XvMCGetAttribute ( display - The connection to the server. - context - The context whos attribute we are querying. + context - The context whose attribute we are querying. attribute - The X Atom of the attribute to be retrieved. diff --git a/configure.ac b/configure.ac index d8addce..9603741 100644 --- a/configure.ac +++ b/configure.ac @@ -39,7 +39,7 @@ XORG_MACROS_VERSION(1.8) XORG_DEFAULT_OPTIONS XORG_CHECK_MALLOC_ZERO -# Obtain compiler/linker options for depedencies +# Obtain compiler/linker options for dependencies PKG_CHECK_MODULES(XVMC, [x11 >= 1.6] xext xv xextproto videoproto) # Checks for library functions. diff --git a/src/XvMC.c b/src/XvMC.c index 76a8552..e0a1fe2 100644 --- a/src/XvMC.c +++ b/src/XvMC.c @@ -519,7 +519,7 @@ Status XvMCGetDRInfo(Display *dpy, XvPortID port, * X server can read this pattern, we probably have a local connection. * Note that we can trigger the remote X server to read any shared * page on the remote machine, so we shouldn't be able to guess and verify - * any complicated data on those pages. Thats the explanation of this + * any complicated data on those pages. That's the explanation of this * otherwise stupid-looking pattern algorithm. */ diff --git a/wrapper/XvMCWrapper.c b/wrapper/XvMCWrapper.c index 7882323..7a4c86d 100644 --- a/wrapper/XvMCWrapper.c +++ b/wrapper/XvMCWrapper.c @@ -27,7 +27,7 @@ /* * BUGS: The wrapper really should maintain one symbol table per port. This - * could possibly be impemented, To do that, the port-independent symbols need to be lifted out, + * could possibly be implemented. To do that, the port-independent symbols need to be lifted out, * and one would have to create a number of mapping tables: * * port -> symbol table -- cgit v1.2.3