Standardize spelling of Slang

Offical spelling is "Slang"

Author: SaschaWillems

en/03_Drawing_a_triangle/02_Graphics_pipeline_basics/01_Shader_modules.adoc

@@ -5,7 +5,7 @@
 Unlike earlier APIs, shader code in Vulkan has to be specified in a bytecode
 format as opposed to human-readable syntax like
 https://en.wikipedia.org/wiki/OpenGL_Shading_Language[GLSL]
-https://shader-slang.org/slang/user-guide/[SLANG], and
+https://shader-slang.org/slang/user-guide/[Slang], and
 https://en.wikipedia.org/wiki/High-Level_Shading_Language[HLSL].
 This bytecode format is called https://www.khronos.org/spir[SPIR-V] and is designed
 to be used with Vulkan (a Khronos API). It is a format that

en/11_Compute_Shader.adoc

@@ -119,7 +119,7 @@ shaderStorageBuffers.emplace_back(std::move(shaderStorageBufferTemp));
 shaderStorageBuffersMemory.emplace_back(std::move(shaderStorageBufferTempMemory));
 ----
 
-The SLang shader declaration for accessing such a buffer looks like this:
+The Slang shader declaration for accessing such a buffer looks like this:
 
 [,slang]
 ----
@@ -172,7 +172,7 @@ textureImage = std::make_unique<vk::raii::SwapchainKHR>( *device, swapChainCreat
 
 The two flags `vk::ImageUsageFlagBits::eSampled` and `vk::ImageUsageFlagBits::eStorage` set with `imageInfo.usage` tell the implementation that we want to use this image for two different scenarios: as an image sampled in the fragment shader and as a storage image in the computer shader;
 
-The SLang shader declaration for storage image looks similar to sampled images
+The Slang shader declaration for storage image looks similar to sampled images
 used, e.g.,
 in the fragment shader: