+ some more

appendices/VK_ANDROID_external_memory_android_hardware_buffer.txt

@@ -141,9 +141,9 @@ The extension version number will be incremented when this additional
 documentation is added, but the version number doesn't indicate that an
 implementaiton supports Vulkan memory or resources that map to the new
 +AHardwareBuffer+ features: support for that must be queried with
-flink:vkGetPhysicalDeviceImageFormatSupport2 or is implied by successfully
-allocating a +AHardwareBuffer+ outside of Vulkan that uses the new feature
-and has a GPU usage flag.
+flink:vkGetPhysicalDeviceImageFormatProperties2 or is implied by
+successfully allocating a +AHardwareBuffer+ outside of Vulkan that uses the
+new feature and has a GPU usage flag.
 
 In essence, these are new features added to a new Android API level, rather
 than new Vulkan features.

chapters/memory.txt

@@ -2776,7 +2776,7 @@ usage requirements associated with external formats, even if the Android
 hardware buffer's format has a Vulkan equivalent.
 The external format of an Android hardware buffer can: be obtained by
 passing an instance of
-slink:VkAndroidHardwareBufferExternalFormatPropertiesANDROID to
+slink:VkAndroidHardwareBufferFormatPropertiesANDROID to
 flink:vkGetAndroidHardwareBufferPropertiesANDROID.
 
 [[memory-external-android-hardware-buffer-image-resources]]
@@ -2792,7 +2792,7 @@ ename:VK_EXTERNAL_MEMORY_HANDLE_TYPE_ANDROID_HARDWARE_BUFFER_BIT_ANDROID.
 When creating an image that will be bound to an imported Android hardware
 buffer, the image creation parameters must: be equivalent to the
 code:AHardwareBuffer properties as described by the valid usage of
-slink:vkMemoryAllocateInfo.
+slink:VkMemoryAllocateInfo.
 Similarly, device memory allocated for a dedicated image must: not be
 exported to an Android hardware buffer until it has been bound to that
 image, and the implementation must: return an Android hardware buffer with

chapters/resources.txt

@@ -2933,8 +2933,7 @@ buffer memory is unknown until the memory has been imported or allocated, so
 calling flink:vkGetImageMemoryRequirements with such an image before it has
 been bound to memory will result in undefined behavior.
 When importing Android hardware buffer memory, the pname:allocationSize can:
-be determined by calling
-flink:vkGetMemoryAndroidHardwareBufferPropertiesANDROID.
+be determined by calling flink:vkGetAndroidHardwareBufferPropertiesANDROID.
 When allocating new memory for an image that can: be exported to a Android
 hardware buffer, the memory's pname:allocationSize must: be zero; the actual
 size will be determined by the dedicated image's parameters.