Addressing comments

Author: SimonDarksideJ

articles/getting_to_know/howto/graphics/camera/HowTo_Understand_Different_Camera_Modes.md

@@ -51,7 +51,7 @@ The project of the view is also normally fixed for any single camera (although y
 > [!TIP]
 > Elements drawn outside of the camera view / projection are culled or ignored by the graphics device.  However, unless you control what data is sent, you are still paying for the performance to send to the graphics card and consider it for drawing.  This is where techniques are used to limit the data sent to the graphics card and ONLY send models and textures that you know will be actually drawn and limiting what is discarded.
 
-### Camera Views
+## Camera Views
 
 The sample separates out the actual work in drawing each camera mode based on what is active at the time in the `Update` loop, as shown here:
 
@@ -86,7 +86,7 @@ The sample separates out the actual work in drawing each camera mode based on wh
 
 You would not normally do this, it is only done this way for the purposes of the sample.  In reality you would only use the mode relevant to the current game view (although a lot of first person games do allow switching between First Person and Third Person), however, as you will see, you are only updating the way the View Matrix is generated along with the camera position, in 3D the content is always drawn the same regardless.
 
-#### The Fixed Camera view
+### The Fixed Camera view
 
 This is the simplest way of rendering a camera, you just create a `View Matrix` using the Camera's current position and looking at the center of the world (or whatever you want it to look at).  For example:
 

articles/getting_to_know/whatis/graphics/WhatIs_Camera.md

@@ -22,7 +22,7 @@ The following diagram shows how this looks.
 
 Everything within the "cone of view" is recognized by the graphics pipeline and is rendered into a Texture for displaying on the screen.  Everything outside these bounds is ignored (culled) and left on the cutting room floor.
 
-> [!NOTE]
+> [!CAUTION]
 > Be aware, that in 3D rendering EVERYTHING is evaluated to determine if it is in "View", EVERYTHING you send to the graphics card that you want to be rendered.  So if you send a massive scene and ALL your Models, ALL your textures, etc, then everything is evaluated.  Sure, Graphics Processing has evolved considerably over the years and the processes running on Graphics Cards keep getting quicker, but you still want to make that as efficient as possible.
 
 ## What defines a camera
@@ -33,7 +33,7 @@ Beyond the View Frustrum above, a Camera exists in graphical terms as:
 - A direction - Which direction is the camera pointing?
 - The Target of the camera - What is it looking at? The central point.
 - The View Frustrum of the camera - What is in the field of view?
-- The world transformational matrix applied to the camera (how does the camera see the world)
+- The World Matrix, where in the world is the camera in relation to the center and other objects?
 
 You will see this defined in many samples as the `World`, `View` and `Projection` Matrices, as shown below:
 
@@ -82,6 +82,9 @@ void DrawTexture(SpriteBatch spriteBatch, Texture2D spriteTexture, Vector2 sprit
 }
 ```
 
+> [!NOTE]
+> For more on 2D / Sprite rendering, check the [How To](https://docs.monogame.net/articles/getting_to_know/howto/graphics/#2d-sprite-rendering) series for 2D rendering.
+
 The functionality does provide some techniques to sort what is drawn, provide some additional depth and layers, as well as blending options to effectively merge what is drawn.
 
 ## [3D Drawing](../../howto/graphics/HowTo_RenderModel.md)