Browse Source

Fix typos with codespell

Also includes #71080.

Co-authored-by: Psychpsyo <[email protected]>
Rémi Verschelde 2 years ago
parent
commit
6a86dfad29

+ 1 - 1
CONTRIBUTING.md

@@ -55,7 +55,7 @@ in the editor, don't hesitate to include screenshots.
 Making your bug report easy to reproduce will make it easier for contributors
 Making your bug report easy to reproduce will make it easier for contributors
 to fix the bug.
 to fix the bug.
 
 
-### Provide a simple, example project
+### Provide a simple example project
 
 
 Sometimes, unexpected behavior can happen in your project. In such case,
 Sometimes, unexpected behavior can happen in your project. In such case,
 understand that:
 understand that:

+ 1 - 1
doc/classes/EditorPlugin.xml

@@ -664,7 +664,7 @@
 			<return type="void" />
 			<return type="void" />
 			<param index="0" name="callable" type="Callable" />
 			<param index="0" name="callable" type="Callable" />
 			<description>
 			<description>
-				Removes a callback previsously added by [method add_undo_redo_inspector_hook_callback].
+				Removes a callback previously added by [method add_undo_redo_inspector_hook_callback].
 			</description>
 			</description>
 		</method>
 		</method>
 		<method name="set_force_draw_over_forwarding_enabled">
 		<method name="set_force_draw_over_forwarding_enabled">

+ 1 - 1
doc/classes/TileMap.xml

@@ -321,7 +321,7 @@
 			<param index="1" name="y_sort_enabled" type="bool" />
 			<param index="1" name="y_sort_enabled" type="bool" />
 			<description>
 			<description>
 				Enables or disables a layer's Y-sorting. If a layer is Y-sorted, the layer will behave as a CanvasItem node where each of its tile gets Y-sorted.
 				Enables or disables a layer's Y-sorting. If a layer is Y-sorted, the layer will behave as a CanvasItem node where each of its tile gets Y-sorted.
-				Y-sorted layers should usually be on different Z-index values than not Y-sorted layers, otherwise, each of those layer will be Y-sorted as whole with the Y-sorted one. This is usually an undesired behvaior.
+				Y-sorted layers should usually be on different Z-index values than not Y-sorted layers, otherwise, each of those layer will be Y-sorted as whole with the Y-sorted one. This is usually an undesired behavior.
 				If [code]layer[/code] is negative, the layers are accessed from the last one.
 				If [code]layer[/code] is negative, the layers are accessed from the last one.
 			</description>
 			</description>
 		</method>
 		</method>

+ 1 - 1
modules/openxr/extensions/openxr_extension_wrapper.h

@@ -73,7 +73,7 @@ public:
 	virtual void on_before_instance_created() {} // `on_before_instance_created` is called before we create our OpenXR instance.
 	virtual void on_before_instance_created() {} // `on_before_instance_created` is called before we create our OpenXR instance.
 	virtual void on_instance_created(const XrInstance p_instance) {} // `on_instance_created` is called right after we've successfully created our OpenXR instance.
 	virtual void on_instance_created(const XrInstance p_instance) {} // `on_instance_created` is called right after we've successfully created our OpenXR instance.
 	virtual void on_instance_destroyed() {} // `on_instance_destroyed` is called right before we destroy our OpenXR instance.
 	virtual void on_instance_destroyed() {} // `on_instance_destroyed` is called right before we destroy our OpenXR instance.
-	virtual void on_session_created(const XrSession p_instance) {} // `on_session_created` is called right after we've successsfully created our OpenXR session.
+	virtual void on_session_created(const XrSession p_instance) {} // `on_session_created` is called right after we've successfully created our OpenXR session.
 	virtual void on_session_destroyed() {} // `on_session_destroyed` is called right before we destroy our OpenXR session.
 	virtual void on_session_destroyed() {} // `on_session_destroyed` is called right before we destroy our OpenXR session.
 
 
 	// `on_process` is called as part of our OpenXR process handling,
 	// `on_process` is called as part of our OpenXR process handling,

+ 2 - 2
tests/scene/test_code_edit.h

@@ -2894,7 +2894,7 @@ TEST_CASE("[SceneTree][CodeEdit] completion") {
 		CHECK(code_edit->get_caret_column() == 6);
 		CHECK(code_edit->get_caret_column() == 6);
 		code_edit->undo();
 		code_edit->undo();
 
 
-		// brace completion disbaled
+		// brace completion disabled
 		code_edit->set_auto_brace_completion_enabled(false);
 		code_edit->set_auto_brace_completion_enabled(false);
 
 
 		// Full completion.
 		// Full completion.
@@ -2934,7 +2934,7 @@ TEST_CASE("[SceneTree][CodeEdit] completion") {
 		CHECK(code_edit->get_caret_column() == 7);
 		CHECK(code_edit->get_caret_column() == 7);
 		code_edit->undo();
 		code_edit->undo();
 
 
-		// brace completion disbaled
+		// brace completion disabled
 		code_edit->set_auto_brace_completion_enabled(false);
 		code_edit->set_auto_brace_completion_enabled(false);
 
 
 		// Full completion.
 		// Full completion.