diff --git a/getting_started/workflow/best_practices/scenes_versus_scripts.rst b/getting_started/workflow/best_practices/scenes_versus_scripts.rst
index 2090b3e19..8437c1af7 100644
--- a/getting_started/workflow/best_practices/scenes_versus_scripts.rst
+++ b/getting_started/workflow/best_practices/scenes_versus_scripts.rst
@@ -186,7 +186,7 @@ with it, and finally adds it as a child of the ``Main`` node:
         {
             Child = new Node();
             Child.Name = "Child";
-            Child.Script = (Script)ResourceLoader.Load("child.gd");
+            Child.Script = ResourceLoader.Load<Script>("child.gd");
             Child.Owner = this;
             AddChild(Child);
         }
diff --git a/getting_started/workflow/best_practices/what_are_godot_classes.rst b/getting_started/workflow/best_practices/what_are_godot_classes.rst
index cf669d95c..75ddfcb56 100644
--- a/getting_started/workflow/best_practices/what_are_godot_classes.rst
+++ b/getting_started/workflow/best_practices/what_are_godot_classes.rst
@@ -63,7 +63,7 @@ The content of a scene helps to define:
 - What signal connections they have with each other
 
 Why is any of this important to scene organization? Because instances of scenes *are* objects. As a
-result, many Object-Oriented principles that apply to written code also apply to scenes: single
+result, many object-oriented principles that apply to written code also apply to scenes: single
 responsibility, encapsulation, and others.
 
 The scene is *always an extension of the script attached to its root node*, so you can interpret it