Changed wording on chapter intro, moved dynamic state paragraph to th…

…e top
Overv · Overv · Jul 3, 2022 · Apr 1, 2022 · Apr 2, 2022 · Apr 2, 2022
commit 35dd1d6cca92e891ccb36b111bf1be055ee41260
diff --git a/en/03_Drawing_a_triangle/02_Graphics_pipeline_basics/02_Fixed_functions.md b/en/03_Drawing_a_triangle/02_Graphics_pipeline_basics/02_Fixed_functions.md
@@ -1,8 +1,35 @@
 
 The older graphics APIs provided default state for most of the stages of the
-graphics pipeline. In Vulkan you have to be explicit about everything, from
-viewport size to color blending function. In this chapter we'll fill in all of
-the structures to configure these fixed-function operations.
+graphics pipeline. In Vulkan you have to be explicit about most pipeline state as
+it'll be baked into an immutable pipeline state object. In this chapter we'll fill 
+in all of the structures to configure these fixed-function operations.
+
+<a name="dynamic-state"></a>
+
+## Dynamic state
+
+While *most* of the pipeline state needs to be baked into the pipeline state, 
+a limited amount of the state *can* actually be changed without recreating the 
+pipeline at draw time instead. Examples are the size of the viewport, line width 
+and blend constants. If you want to use dynamic state and keep these properties out, 
+then you'll have to fill in a `VkPipelineDynamicStateCreateInfo` structure like this:
+
+```c++
+std::vector<VkDynamicState> dynamicStates = {
+    VK_DYNAMIC_STATE_VIEWPORT,
+    VK_DYNAMIC_STATE_SCISSROR
+};
+
+VkPipelineDynamicStateCreateInfo dynamicState{};
+dynamicState.sType = VK_STRUCTURE_TYPE_PIPELINE_DYNAMIC_STATE_CREATE_INFO;
+dynamicState.dynamicStateCount = static_cast<uint32_t>(dynamicStates.size());
+dynamicState.pDynamicStates = dynamicStates.data();
+```
+
+This will cause the configuration of these values to be ignored and you will be
+able (and required) to specify the data at drawing time. This results in a more flexible
+setup and is very common for things like viewport and scissor state, which would
+result in a more complex setup when being baked into the pipeline state.
 
 ## Vertex input
 
@@ -362,31 +389,6 @@ determine which channels in the framebuffer will actually be affected. It is
 also possible to disable both modes, as we've done here, in which case the
 fragment colors will be written to the framebuffer unmodified.
 
-<a name="dynamic-state"></a>
-
-## Dynamic state
-
-A limited amount of the state that we've specified in the previous structs *can*
-actually be changed without recreating the pipeline. Examples are the size of
-the viewport, line width and blend constants. If you want to do that, then
-you'll have to fill in a `VkPipelineDynamicStateCreateInfo` structure like this:
-
-```c++
-std::vector<VkDynamicState> dynamicStates = {
-    VK_DYNAMIC_STATE_VIEWPORT,
-    VK_DYNAMIC_STATE_LINE_WIDTH
-};
-
-VkPipelineDynamicStateCreateInfo dynamicState{};
-dynamicState.sType = VK_STRUCTURE_TYPE_PIPELINE_DYNAMIC_STATE_CREATE_INFO;
-dynamicState.dynamicStateCount = static_cast<uint32_t>(dynamicStates.size());
-dynamicState.pDynamicStates = dynamicStates.data();
-```
-
-This will cause the configuration of these values to be ignored and you will be
-required to specify the data at drawing time. As noted earlier we'll make use
-of dynamic viewport and scissor state.
-
 ## Pipeline layout
 
 You can use `uniform` values in shaders, which are globals similar to dynamic