Fix typos

aeikum · aeikum · commit 4db368892b8e · 2018-04-06T09:21:21.000-05:00
diff --git a/03_Drawing_a_triangle/02_Graphics_pipeline_basics/02_Fixed_functions.md b/03_Drawing_a_triangle/02_Graphics_pipeline_basics/02_Fixed_functions.md
@@ -385,7 +385,7 @@ if (vkCreatePipelineLayout(device, &pipelineLayoutInfo, nullptr, &pipelineLayout
 
 The structure also specifies *push constants*, which are another way of passing
 dynamic values to shaders that we may get into in a future chapter. The pipeline
-layout is may be referenced throughout the program's lifetime, so it should be
+layout will be referenced throughout the program's lifetime, so it should be
 destroyed at the end:
 
 ```c++
diff --git a/03_Drawing_a_triangle/03_Drawing/00_Framebuffers.md b/03_Drawing_a_triangle/03_Drawing/00_Framebuffers.md
@@ -6,7 +6,7 @@ The attachments specified during render pass creation are bound by wrapping them
 into a `VkFramebuffer` object. A framebuffer object references all of the
 `VkImageView` objects that represent the attachments. In our case that will be
 only a single one: the color attachment. However, the image that we have to use
-as attachment depends on which image the swap chain returns when we retrieve one
+for the attachment depends on which image the swap chain returns when we retrieve one
 for presentation. That means that we have to create a framebuffer for all of the
 images in the swap chain and use the one that corresponds to the retrieved image
 at drawing time.
diff --git a/03_Drawing_a_triangle/03_Drawing/01_Command_buffers.md b/03_Drawing_a_triangle/03_Drawing/01_Command_buffers.md
@@ -93,7 +93,7 @@ We can now start allocating command buffers and recording drawing commands in
 them. Because one of the drawing commands involves binding the right
 `VkFramebuffer`, we'll actually have to record a command buffer for every image
 in the swap chain once again. To that end, create a list of `VkCommandBuffer`
-objects as class member. Command buffers will be automatically freed when their
+objects as a class member. Command buffers will be automatically freed when their
 command pool is destroyed, so we don't need an explicit cleanup.
 
 ```c++
diff --git a/03_Drawing_a_triangle/03_Drawing/02_Rendering_and_presentation.md b/03_Drawing_a_triangle/03_Drawing/02_Rendering_and_presentation.md
@@ -119,7 +119,7 @@ void cleanup() {
 ## Acquiring an image from the swap chain
 
 As mentioned before, the first thing we need to do in the `drawFrame` function
-is acquiring an image from the swap chain. Recall that the swap chain is an
+is acquire an image from the swap chain. Recall that the swap chain is an
 extension feature, so we must use a function with the `vk*KHR` naming
 convention:
 
@@ -167,7 +167,7 @@ begins and in which stage(s) of the pipeline to wait. We want to wait with
 writing colors to the image until it's available, so we're specifying the stage
 of the graphics pipeline that writes to the color attachment. That means that
 theoretically the implementation can already start executing our vertex shader
-and such while the image is not available yet. Each entry in the `waitStages`
+and such while the image is not yet available. Each entry in the `waitStages`
 array corresponds to the semaphore with the same index in `pWaitSemaphores`.
 
 ```c++
diff --git a/06_Texture_mapping/00_Images.md b/06_Texture_mapping/00_Images.md
@@ -502,7 +502,7 @@ barrier.subresourceRange.layerCount = 1;
 ```
 
 The `image` and `subresourceRange` specify the image that is affected and the
-specific part of the image. Our image is not an array and does not mipmapping
+specific part of the image. Our image is not an array and does not have mipmapping
 levels, so only one level and layer are specified.
 
 ```c++
@@ -649,7 +649,7 @@ transitionImageLayout(textureImage, VK_FORMAT_R8G8B8A8_UNORM, VK_IMAGE_LAYOUT_TR
 
 ## Transition barrier masks
 
-If run your application with validation layers enabled now, then you'll see that
+If you run your application with validation layers enabled now, then you'll see that
 it complains about the access masks and pipeline stages in
 `transitionImageLayout` being invalid. We still need to set those based on the
 layouts in the transition.
