diff options
author | Rutwik Choughule <rutwik.choughule@gmail.com> | 2022-05-20 11:18:00 +0300 |
---|---|---|
committer | Charles Giessen <46324611+charles-lunarg@users.noreply.github.com> | 2022-05-21 05:05:21 +0300 |
commit | 3772b036e00ce823aae05bddbbbbf19d796bce21 (patch) | |
tree | a7a432ddcfcb8db91f1cbbea308def1e397b9c1b | |
parent | db0fb163d7453e90fc8e63d4dbe216604bf23686 (diff) |
docs: Fix typo in MoltenVK url
-rw-r--r-- | docs/LoaderInterfaceArchitecture.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/LoaderInterfaceArchitecture.md b/docs/LoaderInterfaceArchitecture.md index fbf1e9c1b..d381cfb94 100644 --- a/docs/LoaderInterfaceArchitecture.md +++ b/docs/LoaderInterfaceArchitecture.md @@ -71,7 +71,7 @@ loader. At the bottom of the stack sits the drivers. A driver can control one or more physical devices capable of rendering Vulkan, implement a conversion from Vulkan into a native graphics API (like -[MoltenVk](https://github.com/KhronosGroup/MoltenVK], or implement a fully +[MoltenVk](https://github.com/KhronosGroup/MoltenVK), or implement a fully software path that can be executed on a CPU to simulate a Vulkan device (like [SwiftShader](https://github.com/google/swiftshader) or LavaPipe). Remember, Vulkan-capable hardware may be graphics-based, compute-based, or |