Clarify that maxMemoryAllocationCount is about simultaneous allocations

Overv · Overv · commit ace0630c861f · 2017-04-25T21:14:26.000+02:00
diff --git a/04_Vertex_buffers/02_Staging_buffer.md b/04_Vertex_buffers/02_Staging_buffer.md
@@ -238,12 +238,12 @@ complex geometry.
 
 It should be noted that in a real world application, you're not supposed to
 actually call `vkAllocateMemory` for every individual buffer. The maximum number
-of memory allocations is limited by the `maxMemoryAllocationCount` physical
-device limit, which may be as low as `4096` even on high end hardware like an
-NVIDIA GTX 1080. The right way to allocate memory for a large number of objects
-is to create a custom allocator that splits up a single allocation among many
-different objects by using the `offset` parameters that we've seen in many
-functions.
+of simultaneous memory allocations is limited by the `maxMemoryAllocationCount`
+physical device limit, which may be as low as `4096` even on high end hardware
+like an NVIDIA GTX 1080. The right way to allocate memory for a large number of
+objects at the same time is to create a custom allocator that splits up a single
+allocation among many different objects by using the `offset` parameters that
+we've seen in many functions.
 
 You will currently have to write such an allocator yourself, but the author
 expects that there will be a library at some point that can be integrated into
@@ -253,4 +253,4 @@ hitting any of these limits for now.
 
 [C++ code](/code/staging_buffer.cpp) /
 [Vertex shader](/code/shader_vertexbuffer.vert) /
-[Fragment shader](/code/shader_vertexbuffer.frag)
+[Fragment shader](/code/shader_vertexbuffer.frag)
