diff options
| author | Sein Lee <95391720+wiggy-oink@users.noreply.github.com> | 2022-04-29 23:53:17 +0300 |
|---|---|---|
| committer | Charles Giessen <46324611+charles-lunarg@users.noreply.github.com> | 2022-05-03 01:29:21 +0300 |
| commit | 191e2614953908c5829d7826a5ac5265e4ad2a03 (patch) | |
| tree | 5812cb22784875c440637b31bd524cf38bb80924 | |
| parent | 155ca6b8686feb92cd6c06d6edefd43787856552 (diff) | |
Fix typo
| -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 73a50e40b..fbf1e9c1b 100644 --- a/docs/LoaderInterfaceArchitecture.md +++ b/docs/LoaderInterfaceArchitecture.md @@ -340,7 +340,7 @@ More information about device extensions can be found later in this document. Vulkan uses an object model to control the scope of a particular action or operation. The object to be acted on is always the first parameter of a Vulkan call and is -a dispatchable object (see Vulkan specification section 2.3 Object Model). +a dispatchable object (see Vulkan specification section 3.3 Object Model). Under the covers, the dispatchable object handle is a pointer to a structure, which in turn, contains a pointer to a dispatch table maintained by the loader. This dispatch table contains pointers to the Vulkan functions appropriate to |