Fix typos in vkAllocateMemory calls

Overv · Overv · commit 3bc45072c916 · 2016-09-21T15:58:13.000+02:00
diff --git a/04_Vertex_buffers/01_Vertex_buffer_creation.md b/04_Vertex_buffers/01_Vertex_buffer_creation.md
@@ -34,7 +34,7 @@ void initVulkan() {
 ...
 
 void createVertexBuffer() {
-    
+
 }
 ```
 
@@ -204,7 +204,7 @@ VDeleter<VkDeviceMemory> vertexBufferMemory{device, vkFreeMemory};
 
 ...
 
-if (vkAllocateMemory(device, &allocInfo, nullptr, &vertexBufferMemory) != VK_SUCCESS) {
+if (vkAllocateMemory(device, &allocInfo, nullptr, vertexBufferMemory.replace()) != VK_SUCCESS) {
     throw std::runtime_error("failed to allocate vertex buffer memory!");
 }
 ```
@@ -312,4 +312,4 @@ Run the program again and you should see the following:
 In the next chapter we'll look at a different way to copy vertex data to a
 vertex buffer that results in better performance, but takes some more work.
 
-[Full code listing](/code/vertex_buffer.cpp)
+[Full code listing](/code/vertex_buffer.cpp)
diff --git a/04_Vertex_buffers/02_Staging_buffer.md b/04_Vertex_buffers/02_Staging_buffer.md
@@ -63,7 +63,7 @@ void createBuffer(VkDeviceSize size, VkBufferUsageFlags usage, VkMemoryPropertyF
     allocInfo.allocationSize = memRequirements.size;
     allocInfo.memoryTypeIndex = findMemoryType(memRequirements.memoryTypeBits, properties);
 
-    if (vkAllocateMemory(device, &allocInfo, nullptr, &bufferMemory) != VK_SUCCESS) {
+    if (vkAllocateMemory(device, &allocInfo, nullptr, bufferMemory.replace()) != VK_SUCCESS) {
         throw std::runtime_error("failed to allocate buffer memory!");
     }
 
@@ -251,4 +251,4 @@ any Vulkan program to properly handle allocations. It's okay to use a separate
 allocation for every resource for this tutorial, because we won't come close to
 hitting any of these limits for now.
 
-[Full code listing](/code/staging_buffer.cpp)
+[Full code listing](/code/staging_buffer.cpp)
