Fixed grammatic error plus few minor updates

3 files changed, 3 insertions, 3 deletions

diff --git a/Graphics/GraphicsEngineVulkan/include/FenceVkImpl.h b/Graphics/GraphicsEngineVulkan/include/FenceVkImpl.h
index 894451e6..9816bfb1 100644
--- a/Graphics/GraphicsEngineVulkan/include/FenceVkImpl.h
+++ b/Graphics/GraphicsEngineVulkan/include/FenceVkImpl.h
@@ -51,7 +51,7 @@ public:
 
     // Note that this method is not thread-safe. The reason is that VulkanFencePool is not thread
     // safe, and DeviceContextVkImpl::SignalFence() adds the fence to the pending fences list that
-    // are signalled later by the command context when it submits the command list. So there is no
+    // are signaled later by the command context when it submits the command list. So there is no
     // guarantee that the fence pool is not accessed simultaneously by multiple threads even if the
     // fence object itself is protected by mutex.
     virtual Uint64 GetCompletedValue()override final;
diff --git a/Graphics/GraphicsEngineVulkan/src/DeviceContextVkImpl.cpp b/Graphics/GraphicsEngineVulkan/src/DeviceContextVkImpl.cpp
index 03eb0992..d9d9b3bf 100644
--- a/Graphics/GraphicsEngineVulkan/src/DeviceContextVkImpl.cpp
+++ b/Graphics/GraphicsEngineVulkan/src/DeviceContextVkImpl.cpp
@@ -1905,7 +1905,7 @@ namespace Diligent
 
     void DeviceContextVkImpl::SignalFence(IFence* pFence, Uint64 Value)
     {
-        VERIFY(!m_bIsDeferred, "Fence can only be signalled from immediate context");
+        VERIFY(!m_bIsDeferred, "Fence can only be signaled from immediate context");
         m_PendingFences.emplace_back( std::make_pair(Value, pFence) );
     };
 
diff --git a/Graphics/GraphicsEngineVulkan/src/FenceVkImpl.cpp b/Graphics/GraphicsEngineVulkan/src/FenceVkImpl.cpp
index 726cdd41..12273300 100644
--- a/Graphics/GraphicsEngineVulkan/src/FenceVkImpl.cpp
+++ b/Graphics/GraphicsEngineVulkan/src/FenceVkImpl.cpp
@@ -42,7 +42,7 @@ FenceVkImpl :: FenceVkImpl(IReferenceCounters* pRefCounters,
 FenceVkImpl :: ~FenceVkImpl()
 {
     // Do not dispose pending fences as the pool checks that the fence
-    // is signalled, while pending fences may not be.
+    // is signaled, while pending fences may not be.
     // The pool will be destroyed next anyway, so it makes no difference.
     m_PendingFences.clear();
 }