Cleanup: Grammar in comments

"it's own" -> "its own" again. Start new sentences properly.
This commit is contained in:
Hans Goudey 2024-01-06 00:03:31 -05:00
parent 5179e66756
commit e90d844dd7
4 changed files with 6 additions and 6 deletions

View File

@ -41,7 +41,7 @@ else()
# using the system directory `/etc/ssl` might seem the obvious choice,
# there is no guarantee the version of SSL used with Blender is compatible with the systems,
# where changes to the SSL configuration format can cause SSL not to load (see #114452).
# So reference a directory known not to exist. Ideally Blender could distribute it's own SSL
# So reference a directory known not to exist. Ideally Blender could distribute its own SSL
# directory, but this isn't compatible with hard coded paths.
# See #111132 & https://github.com/openssl/openssl/issues/20185 for details.
-DOPENSSLDIR=\\"/dev/null\\"

View File

@ -2395,12 +2395,12 @@ bool GHOST_WindowWayland::outputs_changed_update_scale()
#ifdef WITH_GHOST_WAYLAND_LIBDECOR
if (use_libdecor) {
/* LIBDECOR needs it's own logic, failing to do this causes the window border
/* LIBDECOR needs its own logic. Failing to do this causes the window border
* not to follow the GHOST window on startup - with multiple monitors,
* each with different fractional scale, see: #109194.
*
* Note that the window will show larger, then resize to be smaller soon
* after opening, this would be nice to avoid but but would require DPI
* after opening. This would be nice to avoid but but would require DPI
* to be stored in the window (as noted above). */
int size_next[2] = {0, 0};
int size_orig[2] = {0, 0};

View File

@ -18,7 +18,7 @@
#pragma BLENDER_REQUIRE(eevee_shadow_lib.glsl)
#pragma BLENDER_REQUIRE(gpu_shader_codegen_lib.glsl)
/* If using compute, the shader should define it's own pixel. */
/* If using compute, the shader should define its own pixel. */
#if !defined(PIXEL) && defined(GPU_FRAGMENT_SHADER)
# define PIXEL gl_FragCoord.xy
#endif

View File

@ -5,10 +5,10 @@
"""
Wrapper for Blender that launches a graphical instances of Blender
in it's own display-server.
in its own display-server.
This can be useful when a graphical context is required (when ``--background`` can't be used)
and it's preferable not to have windows opening on the users system.
and it's preferable not to have windows opening on the user's system.
The main use case for this is tests that run simulated events, see: ``bl_run_operators_event_simulate.py``.