Refactor tutorial phrasing and modernize Vulkan instance creation.

Updated tutorial text to use inclusive language ("we" instead of "I") and improved readability. Modernized Vulkan instance creation using RAII and cleaner initialization code in compliance with up-to-date Vulkan best practices.

Author: gpx1000

en/03_Drawing_a_triangle/00_Setup/00_Base_code.adoc

@@ -83,16 +83,16 @@ Just like each chunk of memory allocated with `malloc` requires a call to
 `free`, every Vulkan object that we create needs to be explicitly destroyed when
 we no longer need it. In c{pp} it is possible to perform automatic resource
 management using https://en.wikipedia.org/wiki/Resource_Acquisition_Is_Initialization[RAII]
-or smart pointers provided in the `<memory>` header. In an attempt to make
-Vulkan easier to work with, and demonstrate modern Vulkan programming.  This
-tutorial will not only use RAII with smart pointers, it will endeavor to
-demonstrate the latest methods and extensions which should hopefully make
-Vulkan a joy to use.  Just because we enjoy working with low level graphics
-APIs, we shouldn't make the bar too high to learn how to do so.  Where
- appropriate, we will discuss concerns for resource management for freeing
-resources.  However, for this tutorial, we'll demonstrate
-that we can get pretty far with a basic destructor to clean up after
-our work.
+or smart pointers provided in the `<memory>` header. This tutorial is an attempt
+to make Vulkan easier to work with, and demonstrate modern Vulkan
+programming.  This tutorial will not only use RAII with smart pointers, it
+will endeavor to demonstrate the latest methods and extensions which should
+hopefully make Vulkan a joy to use.  Just because we enjoy working with
+low level graphics APIs, we shouldn't make the bar too high to learn how
+to do so.  Where appropriate, we will discuss concerns for resource
+management for freeing resources.  However, for this tutorial, we'll
+demonstrate that we can get pretty far with a basic destructor to clean up
+after our work.
 
 Vulkan objects are either created directly with functions like `vkCreateXXX`, or
 allocated through another object with functions like `vkAllocateXXX`. After
@@ -158,7 +158,7 @@ specification and everything else works perfectly fine.
 #include <GLFW/glfw3.h>
 ----
 
-That way GLFW will include its own definitions and automatically load the Vulkan
+That way, GLFW will include its own definitions and automatically load the Vulkan
 C header with it. Add a `initWindow` function and add a call to it from the
 `run` function before the other calls. We'll use that function to initialize
 GLFW and create a window.

en/03_Drawing_a_triangle/00_Setup/01_Instance.adoc

@@ -197,20 +197,6 @@ for (const auto& extension : extensions) {
 }
 ----
 
-You can add this code to the `createInstance` function if you'd like to provide some details about the Vulkan support.
-As a challenge, try to create a function that checks if all the extensions returned by `glfwGetRequiredInstanceExtensions` are included in the supported extensions list.
-
-== Cleaning up
-
-The `VkInstance` should be only destroyed right before the program exits.
-It can be destroyed in `cleanup` with the `vkDestroyInstance` function:
-
-[,c++]
-----
-void cleanup() {
-    vkDestroyInstance(instance, nullptr);
-----
-
 You can add this code to the `createInstance` function if you'd like to provide
 some details about the Vulkan support. As a challenge, try to create a function
 that checks if all the extensions returned by

en/03_Drawing_a_triangle/00_Setup/02_Validation_layers.adoc

@@ -84,7 +84,7 @@ specifying their name. All the useful standard validation is bundled into a
 layer included in the SDK that is known as `VK_LAYER_KHRONOS_validation`.
 
 Let's first add two configuration variables to the program to specify the layers
-to enable and whether to enable them or not. I've chosen to base that value on
+to enable and whether to enable them or not. We've chosen to base that value on
 whether the program is being compiled in debug mode or not. The `NDEBUG` macro
 is part of the c{pp} standard and means "not debug".
 
@@ -188,7 +188,7 @@ std::vector<const char*> getRequiredExtensions() {
 
 The extensions specified by GLFW are always required, as we're working with
 the GLFW dependency for windowing, but the debug messenger extension is
-conditionally added. Note that I've used the
+conditionally added. Note that We've used the
 `VK_EXT_DEBUG_UTILS_EXTENSION_NAME` macro here which is equal to the literal
 string "VK_EXT_debug_utils". Using this macro lets you avoid typos.
 
@@ -299,13 +299,13 @@ debugMessenger = std::make_unique<vk::raii::DebugUtilsMessengerEXT>( *instance,
 ----
 
 The `messageSeverity` field allows you to specify all the types of
-severities you would like your callback to be called for. I've specified
+severities you would like your callback to be called for. We've specified
 all types except for `VK_DEBUG_UTILS_MESSAGE_SEVERITY_INFO_BIT_EXT` here to
 receive notifications about possible problems while leaving out verbose
 general debug info.
 
 Similarly, the `messageType` field lets you filter which types of messages
-your callback is notified about. I've simply enabled all types here. You
+your callback is notified about. We've simply enabled all types here. You
 can always disable some if they're not useful to you.
 
 Finally, the `pfnUserCallback` field specifies the pointer to the callback
@@ -344,11 +344,11 @@ to the Vulkan SDK and go to the `Config` directory. There you will find a
 
 To configure the layer settings for your own application, copy the file to the
 `Debug` and `Release` directories of your project and follow the instructions to
-set the desired behavior. However, for the remainder of this tutorial, I'll
+set the desired behavior. However, for the remainder of this tutorial, We will
 assume that you're using the default settings.
 
-Throughout this tutorial, I'll be making a couple of intentional mistakes to show
-you how helpful the validation layers are with catching them and to teach you
+Throughout this tutorial, we will be making a couple of intentional mistakes
+to show you how helpful the validation layers are with catching them and to teach you
 how important it is to know exactly what you're doing with Vulkan. Now it's time
 to look at link:03_Physical_devices_and_queue_families.adoc[Vulkan devices in the system].
 

en/90_FAQ.adoc

@@ -42,14 +42,8 @@ for(uint32_t i = 0; i < glfwExtensionCount; i++) {
     requiredExtensions.emplace_back(glfwExtensions[i]);
 }
 
-requiredExtensions.emplace_back(VK_KHR_PORTABILITY_ENUMERATION_EXTENSION_NAME);
+requiredExtensions.emplace_back(vk::KHRPortabilityEnumerationExtensionName);
 
-createInfo.flags |= VK_INSTANCE_CREATE_ENUMERATE_PORTABILITY_BIT_KHR;
-
-createInfo.enabledExtensionCount = (uint32_t) requiredExtensions.size();
-createInfo.ppEnabledExtensionNames = requiredExtensions.data();
-
-if (vkCreateInstance(&createInfo, nullptr, &instance) != VK_SUCCESS) {
-    throw std::runtime_error("failed to create instance!");
-}
+vk::InstanceCreateInfo createInfo(vk::InstanceCreateFlagBits::eEnumeratePortabilityKHR, &appInfo, {}, requiredExtensions);
+instance = std::make_unique<vk::raii::Instance>(context, createInfo);
 ----