Browse Source

3.x spellchecker fixes

Max Hilbrunner 11 months ago
parent
commit
3e04a31149
2 changed files with 3 additions and 1 deletions
  1. 2 0
      _tools/codespell-ignore.txt
  2. 1 1
      tutorials/rendering/jitter_stutter.rst

+ 2 - 0
_tools/codespell-ignore.txt

@@ -5,3 +5,5 @@ que
 raison
 raison
 uint
 uint
 subtile
 subtile
+implementors
+thirdparty

+ 1 - 1
tutorials/rendering/jitter_stutter.rst

@@ -155,7 +155,7 @@ default ``60``, or set ``Engine.physics_fps`` at run-time in a
 script. Values that are a multiple of the monitor refresh rate (typically
 script. Values that are a multiple of the monitor refresh rate (typically
 ``60``) work best when physics interpolation is disabled, as they will avoid
 ``60``) work best when physics interpolation is disabled, as they will avoid
 jitter. This means values such as ``120``, ``180`` and ``240`` are good starting
 jitter. This means values such as ``120``, ``180`` and ``240`` are good starting
-points. As a bonus, higher physics FPSes make tunneling and physics unstability
+points. As a bonus, higher physics FPSes make tunneling and physics instability
 issues less likely to occur.
 issues less likely to occur.
 
 
 The downside of increasing physics FPS is that CPU usage will increase, which
 The downside of increasing physics FPS is that CPU usage will increase, which