From db26cd20bc5485127685b0bdebe49077d7ea769b Mon Sep 17 00:00:00 2001 From: Felix Rabe Date: Fri, 10 May 2019 00:43:55 +0200 Subject: [PATCH] Typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9d1c53f..3080a44 100644 --- a/README.md +++ b/README.md @@ -125,7 +125,7 @@ let mut device_create_info = vk::DeviceCreateInfo::builder() .push_next(&mut variable_pointers); ``` -Pointer chains in builders differ from raw Vulkan. Instead of chaining every struct manually, you instead use `.push_next` on the struct that you are going to pass into the function. Those structs then get *pepended* into the chain. +Pointer chains in builders differ from raw Vulkan. Instead of chaining every struct manually, you instead use `.push_next` on the struct that you are going to pass into the function. Those structs then get *prepended* into the chain. `push_next` is also type checked, you can only add valid structs to the chain. Both the structs and the builders can be passed into `push_next`. Only builders for structs that can be passed into functions will implement a `push_next`.