impl requested changes

Author: johannes-el

en/01_Overview.adoc

@@ -140,13 +140,6 @@ Because there could be many different images in the swap chain,
 we would preemptively create an image view and framebuffer for each
 of them and select the right one at draw time.
 
-However, with dynamic rendering (introduced in Vulkan 1.3),
-you no longer need to create a `vk::Framebuffer` at all.
-Dynamic rendering eliminates the need for predefined render passes and framebuffers,
-allowing you to specify rendering attachments directly during command recording.
-This makes the API much simpler, as we can define the rendering targets on the
-fly without worrying about the overhead of managing framebuffers.
-
 === Step 5 - Dynamic Rendering Overview
 
 In earlier versions of Vulkan, a render pass defined how rendering operations
@@ -155,6 +148,13 @@ and how their contents should be treated (e.g., cleared, loaded, or stored).
 A `vk::RenderPass` would define subpasses and attachment usage, and a `vk::Framebuffer`
 would bind specific image views to these attachments.
 
+However, with dynamic rendering (introduced in Vulkan 1.3),
+you no longer need to create a `vk::Framebuffer` at all.
+Dynamic rendering eliminates the need for predefined render passes and framebuffers,
+allowing you to specify rendering attachments directly during command recording.
+This makes the API much simpler, as we can define the rendering targets on the
+fly without worrying about the overhead of managing framebuffers.
+
 With dynamic rendering, you no longer need to predefine `vk::RenderPass` or `vk::Framebuffer`.
 Instead, you specify the rendering attachments at the start of command recording, using `vk::beginRendering`
 and structs like `vk::RenderingInfo` to provide all necessary attachment information dynamically.
@@ -254,9 +254,9 @@ command buffers first.
 
 So in short, to draw the first triangle, we need to:
 
-* Create a vk::Instance
-* Select a supported graphics card (vk::PhysicalDevice)
-* Create a vk::Device and vk::Queue for drawing and presentation
+* Create an Instance
+* Select a supported graphics card (PhysicalDevice)
+* Create a Device and Queue for drawing and presentation
 * Create a window, window surface and swap chain
 * Wrap the swap chain images into VkImageView
 * Set up dynamic rendering
@@ -342,4 +342,4 @@ layers are so extensive, it can actually be a lot easier to find out why
 your screen is black compared to OpenGL and Direct3D!
 
 There's only one more step before we'll start writing code, and that's
-xref:02_Development_environment.adoc[setting up the development environment].
+xref:02_Development_environment.adoc[setting up the development environment].