Minor fixes and finished up chap10 for now

Author: HarryLovesCode

chap04/chap04-linux.md

@@ -17,7 +17,7 @@ If you're targeting Windows as well, you should surround the include by the `#if
 For this chapter, we're going to be writing the contents of these two methods:
 
 ```cpp
-void initWindow() {}
+void createWindow() {}
 void renderLoop() {}
 ```
 
@@ -35,7 +35,7 @@ xcb_atom_t wmProtocols;
 xcb_atom_t wmDeleteWin;
 ```
 
-to our `VulkanSwapchain` class.
+to our `VulkanExample` class.
 
 ### Getting a Connection
 
@@ -326,7 +326,7 @@ xcb_change_property(connection, XCB_PROP_MODE_REPLACE, window,
 All we need to do now is write the contents of the `renderLoop` method. Again, I'm not going to be going too far into depth because this is just glue and we're focused on Vulkan here. Anyways, we'll be using the `xcb_wait_for_event` method to do just that: wait for events. In order to convert the server's response to a value we can check in a **switch case** block, we need to use the bitwise `AND` (`&`) operator with the value: `~0x80`. You can see what I'm talking about below:
 
 ```cpp
-void VulkanSwapchain::renderLoop() {
+void VulkanExample::renderLoop() {
   bool running = true;
   xcb_generic_event_t *event;
   xcb_client_message_event_t *cm;

chap04/chap04-windows.md

@@ -148,7 +148,7 @@ HWND window;
 In this section we'll be writing the body this method:
 
 ```cpp
-void initWindow(HINSTANCE hInstance) {}
+void createWindow(HINSTANCE hInstance) {}
 ```
 
 Don't worry about `hInstance` for now. It is passed from the `WinMain` method we'll write later on. To setup our window, we'll need to register it with Windows, but first, we need to create a `WNDCLASSEX` object to pass during registration.
@@ -349,7 +349,7 @@ switch (message) {
 For this section, we'll write the body of this method:
 
 ```cpp
-void VulkanSwapchain::renderLoop() {}
+void VulkanExample::renderLoop() {}
 ```
 
 We're calling it `renderLoop` because later we'll make calls to rendering functions within it. For now, however, we're going to:
@@ -374,7 +374,7 @@ while (GetMessage(&message, NULL, 0, 0)) {
 This is our application's new entry-point. We will **not** be using your typical `int main()` entry-point. This is because Windows requires GUI applications to enter at `WinMain`. We need to:
 
 - Create an instance of our class
-- Call our `initWindow` method
+- Call our `createWindow` method
 - Call our `renderLoop`
 
 **Definition for `WinMain`**:
@@ -401,7 +401,7 @@ int CALLBACK WinMain(
 int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance,
                    LPSTR lpCmdLine, int nCmdShow) {
   VulkanSwapchain ve = VulkanSwapchain();
-  ve.initWindow(hInstance);
+  ve.createWindow(hInstance);
   ve.renderLoop();
 }
 ```

chap10/chap10.md

@@ -57,7 +57,7 @@ For this section, we'll be adding a new variable to our `VulkanExample` class:
 VkCommandBuffer initialCmdBuffer;
 ```
 
-In addition to that, we'll also be writing the body of a new method:
+In addition to that, we'll also be writing the body of a new method for the next few sections:
 
 ```cpp
 void VulkanExample::createInitialCommandBuffer() {}
@@ -121,14 +121,14 @@ VkResult vkAllocateCommandBuffers(
 Per usual, in addition to calling the method, we'll also verify it was successful.
 
 ```cpp
-VkResult result = vkAllocateCommandBuffers(device, &cmdBufAllocInfo, 
+VkResult result = vkAllocateCommandBuffers(device, &cmdBufAllocInfo,
                                            &initialCmdBuffer);
 assert(result == VK_SUCCESS);
 ```
 
 ## Preparing Command Buffer for Recording
 
-Before we can start recording to our command buffer, we'll have to first create a `VkCommandBufferBeginInfo` object. 
+Before we can start recording to our command buffer, we'll have to first create a `VkCommandBufferBeginInfo` object.
 
 **Definition for `VkCommandBufferBeginInfo`**:
 
@@ -157,4 +157,26 @@ cmdBufBeginInfo.flags = 0;
 cmdBufBeginInfo.pNext = NULL;
 ```
 
-## Beginning Recording to Command Buffer
+## Begin Recording to a Command Buffer
+
+Now that we've allocated a command buffer and readied the information Vulkan needs to begin recording, we can call `vkBeginCommandBuffer`. This method will take a handle to our command buffer and put it in a recording state.
+
+**Definition for `vkBeginCommandBuffer`**:
+
+```cpp
+VkResult vkBeginCommandBuffer(
+  VkCommandBuffer                 commandBuffer,
+  const VkCommandBufferBeginInfo* pBeginInfo);
+```
+
+**[Documentation](https://www.khronos.org/registry/vulkan/specs/1.0/xhtml/vkspec.html#vkBeginCommandBuffer) for `vkBeginCommandBuffer`**:
+
+- `commandBuffer` is the handle of the command buffer which is to be put in the recording state.
+- `pBeginInfo` is an instance of the `VkCommandBufferBeginInfo` structure, which defines additional information about how the command buffer begins recording.
+
+**Usage for `vkBeginCommandBuffer`**:
+
+```cpp
+result = vkBeginCommandBuffer(initialCmdBuffer, &cmdBufBeginInfo);
+assert(result == VK_SUCCESS);
+```