Fix case in naming of structure

Overv · Overv · commit 2ddae4e83385 · 2018-11-06T20:27:12.000+01:00
diff --git a/01_Overview.md b/01_Overview.md
@@ -54,11 +54,11 @@ An instance is created by describing your application and any API extensions you
 will be using. After creating the instance, you can query for Vulkan supported
 hardware and select one or more `VkPhysicalDevice`s to use for operations. You
 can query for properties like VRAM size and device capabilities to select
-desired devices, for example to prefer using dedicated graphics cards. 
+desired devices, for example to prefer using dedicated graphics cards.
 
 ### Step 2 - Logical device and queue families
 
-After selecting the right hardware device to use, you need to create a VkDevice 
+After selecting the right hardware device to use, you need to create a VkDevice
 (logical device), where you describe more specifically which
 VkPhysicalDeviceFeatures you will be using, like multi viewport rendering and
 64 bit floats. You also need to specify which queue families you would like to
@@ -79,8 +79,8 @@ window to present rendered images to. Windows can be created with the native
 platform APIs or libraries like [GLFW](http://www.glfw.org/) and [SDL](https://www.libsdl.org/).
 We will be using GLFW in this tutorial, but more about that in the next chapter.
 
-We need two more components to actually render to a window: a window surface 
-(VkSurfaceKHR) and a swap chain (VkSwapChainKHR). Note the `KHR` postfix, which
+We need two more components to actually render to a window: a window surface
+(VkSurfaceKHR) and a swap chain (VkSwapchainKHR). Note the `KHR` postfix, which
 means that these objects are part of a Vulkan extension. The Vulkan API itself
 is completely platform agnostic, which is why we need to use the standardized
 WSI (Window System Interface) extension to interact with the window manager. The
@@ -274,4 +274,4 @@ 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 [setting
-up the development environment](!Development_environment).
+up the development environment](!Development_environment).
