Apply suggestions from code review

Co-authored-by: A Thousand Ships <[email protected]>

Author: not-bottle

tutorials/shaders/your_first_shader/your_second_3d_shader.rst

@@ -6,13 +6,13 @@ Your second 3D shader
 From a high-level, what Godot does is give the user a bunch of shader parameters 
 that can be optionally set (``AO``, ``SSS_Strength``, ``RIM``, etc.). These
 parameters correspond to different complex effects (Ambient Occlusion,
-SubSurface Scattering, Rim Lighting,  etc.). When not written to, the code is
+SubSurface Scattering, Rim Lighting, etc.). When not written to, the code is
 thrown out before it is compiled and so the shader does not incur the cost of
 the extra feature. This allows users to have complex PBR-correct
 shading, without writing complex shaders. Of course, Godot also allows you to
 ignore all these parameters and write a fully customized shader.
 
-For a full list of these parameters see the :ref:`spatial shader <doc_spatial_shader>` 
+For a full list of these parameters see the :ref:`spatial shader <doc_spatial_shader>`
 reference doc.
 
 A difference between the vertex function and a fragment function is that the
@@ -26,7 +26,7 @@ importantly, sets the ``ALBEDO`` color of the :ref:`MeshInstance3D<class_MeshIns
   fragment function in Godot is to set up different material properties and let
   Godot handle the rest. In order to provide even more flexibility, Godot also
   provides render modes. Render modes are set at the top of the
-  shader, directly below ``shader_type``. They;re used to specify what sort of
+  shader, directly below ``shader_type``. They're used to specify what sort of
   functionality you want the built-in aspects of the shader to have.
 
   For example, if you do not want to have lights affect an object, set the 
@@ -37,8 +37,8 @@ importantly, sets the ``ALBEDO`` color of the :ref:`MeshInstance3D<class_MeshIns
     render_mode unshaded;
 
   You can also stack multiple render modes together. For example, if you want to
-  use toon shading instead of more-realistic PBR shading, set the diffuse mode 
-  and specular mode to toon:
+  use toon shading instead of more-realistic PBR shading, set the diffuse
+  and specular modes to toon:
 
   .. code-block:: glsl
 
@@ -47,7 +47,7 @@ importantly, sets the ``ALBEDO`` color of the :ref:`MeshInstance3D<class_MeshIns
   This model of built-in functionality allows you to write complex custom 
   shaders by changing only a few parameters.
 
-  For a full list of render modes see the :ref:`Spatial shader reference <doc_spatial_shader>`.
+  For a full list of render modes, see the :ref:`Spatial shader reference <doc_spatial_shader>`.
 
 Your first spatial fragment function
 ------------------------------------
@@ -67,7 +67,7 @@ mesh.
 .. code-block:: glsl
 
   void vertex() {
-    tex_position = VERTEX.xz / 10.0 + 0.5; // Scaling factor set to 10 for 10x10 mesh
+    tex_position = VERTEX.xz / 10.0 + 0.5; // Scaling factor set to 10 for 10x10 mesh.
     float height = texture(noise, tex_position).x;
     VERTEX.y += height * height_scale;
   }
@@ -104,7 +104,7 @@ the reflection and the ``ALBEDO`` color. A high ``METALLIC`` almost ignores
 ``METALLIC`` has a more equal representation of sky color and ``ALBEDO`` color.
 
 In the example below, ``ROUGHNESS`` increases from ``0`` to ``1`` from left to
-right while ``METALLIC`` increase from ``0`` to ``1`` from top to bottom.
+right while ``METALLIC`` increases from ``0`` to ``1`` from top to bottom.
 
 .. image:: img/PBR.webp
 
@@ -213,9 +213,9 @@ cosine of ``TIME``.
 .. note::
 
   This will result in texture coordinates that will go out of the bounds of our
-  noise textures and wrap around. The :ref:`NoiseTexture2D <class_NoiseTexture2D>`'s 
+  noise textures and wrap around. The :ref:`NoiseTexture2D <class_NoiseTexture2D>`s
   we are using for **Noise** and **Normalmap** should have their :ref:`Seamless <class_NoiseTexture2D_property_seamless>`
-  property set to ``On`` at this stage, or the seams will start to be visible.
+  property set to ``On`` at this stage, or the seams will be visible.
 
 This results in waves that move slowly, but not in a very natural way. The next
 section will dig deeper into using shaders to create more complex effects, in
@@ -233,7 +233,7 @@ corresponding normal value from our normal map. In the next section we will be
 introducing functions to compute our own height values, making our normal map 
 invalid. This means we will have to compute them manually.
 
-First we will move the height calculation into it's own function. Put the code
+First we will move the height calculation into its own function. Put the code
 into a function called ``height()``.
 
 .. code-block:: glsl
@@ -271,7 +271,7 @@ We will also remove the code assigning to ``NORMAL_MAP`` in ``fragment()``.
 As these are estimates, we have lost some quality. We can partially address this
 by reducing the detail in our noise texture. Open **Mesh > Material > Shader 
 parameters** and then the :ref:`Noise <class_NoiseTexture2D_property_noise>` 
-texture. Set it's :ref:`Noise > Frequency <class_FastNoiseLite_property_frequency>` 
+texture. Set its :ref:`Noise > Frequency <class_FastNoiseLite_property_frequency>` 
 value to ``0.005``. 
 
 .. image:: img/set-frequency.webp
@@ -348,6 +348,7 @@ We do this by scaling ``position``.
     float h = wave(position * 0.4);
     return h;
   }
+
 .. image:: img/wave2.webp
 
 This wave has a more natural shape, but it is a bit smooth. In our material settings 
@@ -429,6 +430,6 @@ the same mesh and noise settings as mentioned above.
   }
 
 For more information about Spatial shaders read the :ref:`Shading Language <doc_shading_language>` 
-doc and the :ref:`Spatial Shaders <doc_spatial_shader>` doc. 
+and :ref:`Spatial Shaders <doc_spatial_shader>` docs.
 Also look at more advanced tutorials in the :ref:`Shading section<toc-learn-features-shading>` 
-and the :ref:`3D <toc-learn-features-3d>` sections.
+and :ref:`3D <toc-learn-features-3d>` sections.