From cc860d56900a23e69ca905af668d5378dbce5e12 Mon Sep 17 00:00:00 2001
From: John Zulauf <32470354+jzulauf-lunarg@users.noreply.github.com>
Date: Wed, 17 Apr 2019 15:39:44 -0600
Subject: [PATCH] Update Dispatch Table update to actual location

DispatchTable struct now has it's own file.  Updated references to the correct file.
---
 loader/LoaderAndLayerInterface.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/loader/LoaderAndLayerInterface.md b/loader/LoaderAndLayerInterface.md
index 4fd4fe39..9f5bcd04 100644
--- a/loader/LoaderAndLayerInterface.md
+++ b/loader/LoaderAndLayerInterface.md
@@ -1247,9 +1247,9 @@ appropriate type to call into the next entity.
   * This can be implemented in various ways but
 for clarity, will be referred to as a dispatch table.
 - A layer can use the `VkLayerDispatchTable` structure as a device dispatch
-table (see include/vulkan/vk_layer.h).
+table (see include/vulkan/vk_dispatch_table_helper.h).
 - A layer can use the `VkLayerInstanceDispatchTable` structure as a instance
-dispatch table (see include/vulkan/vk_layer.h).
+dispatch table (see include/vulkan/vk_dispatch_table_helper.h).
 - A Layer's `vkGetInstanceProcAddr` function uses the next entity's
 `vkGetInstanceProcAddr` to call down the chain for unknown (i.e.
 non-intercepted) functions.