From 763e1f913e332a2ee5234b5e5cc03214ecdb0324 Mon Sep 17 00:00:00 2001
From: riven <96917554+therealnv6@users.noreply.github.com>
Date: Thu, 25 May 2023 13:46:38 +0200
Subject: [PATCH] Update vk_raii_ProgrammingGuide.md (#1581)

fixed typo (CommanPool -> CommandPool)
---
 vk_raii_ProgrammingGuide.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/vk_raii_ProgrammingGuide.md b/vk_raii_ProgrammingGuide.md
index b23997e..98049ed 100644
--- a/vk_raii_ProgrammingGuide.md
+++ b/vk_raii_ProgrammingGuide.md
@@ -33,7 +33,7 @@ Other than the `vk::Device`, you can assign the `vk::raii::Device` to a smart po
 
 Note that, as the vk::raii objects own the actual Vulkan resource, all vk::raii objects are moveable, but not copyable.
 
-For simplicity, in the rest of this document a vk::raii object is always directly instantiated on the stack. Obviously, that’s not essential. You could assign them as well to a std::unique_ptr, a std::shared_ptr, or any other smart pointer or object managing data structure. And you can even assign them to a dumb pointer by using the new operator.
+For simplicity, in the rest of this document a vk::raii object is always directly instantiated on the stack. Obviously, that's not essential. You could assign them as well to a std::unique_ptr, a std::shared_ptr, or any other smart pointer or object managing data structure. And you can even assign them to a dumb pointer by using the new operator.
 
 Similar to a `vk::Device`, a `vk::raii::Device` provides the functions related to that class. But other than the `vk::Device`, you don't need to provide a device-specific dispatcher to those functions to get multi-device functionality. That's already managed by the `vk::raii::Device`.
 
@@ -428,4 +428,4 @@ With the vk::raii namespace you've got a complete set of Vulkan handle wrapper c
 
 Moreover, the actual function pointer handling is done automatically by `vk::raii::Context`, `vk::raii::Instance`, and `vk::raii::Device`. That is, you always use the correct device-specific functions, no matter how many devices you're using.
 
-Note, though, that there are a few classes, like `vk::raii::CommanPool` and `vk::raii::DescriptorSet`, that need some special handling that deviates from what you can do with the pure C-API or the wrapper classes in the vk-namespace.
\ No newline at end of file
+Note, though, that there are a few classes, like `vk::raii::CommandPool` and `vk::raii::DescriptorSet`, that need some special handling that deviates from what you can do with the pure C-API or the wrapper classes in the vk-namespace.