diff --git a/_en/items/inventories.md b/_en/items/inventories.md
index baa2d93..31d35ba 100644
--- a/_en/items/inventories.md
+++ b/_en/items/inventories.md
@@ -101,7 +101,7 @@ An inventory is directly tied to one and only one location - updating the invent
 will cause it to update immediately.
 
 Node inventories are related to the position of a specific node, such as a chest.
-The node must be loaded because it is stored in [node metadata](node_metadata.html).
+The node must be loaded because it is stored in [node metadata](../map/storage.html#metadata).
 
 ```lua
 local inv = minetest.get_inventory({ type="node", pos={x=1, y=2, z=3} })
@@ -112,6 +112,12 @@ Inventory references are used to manipulate an inventory.
 *Reference* means that the data isn't actually stored inside that object,
 but the object instead directly updates the data in-place.
 
+The location of an inventory reference can be found like so:
+
+```lua
+local location = inv:get_location()
+```
+
 Player inventories can be obtained similarly or using a player reference.
 The player must be online to access their inventory.
 
@@ -131,12 +137,45 @@ local inv = minetest.get_inventory({
     type="detached", name="inventory_name" })
 ```
 
-The location of an inventory reference can be found like so:
+Unlike the other types of inventory, you must first create a detached inventory:
 
 ```lua
-local location = inv:get_location()
+minetest.create_detached_inventory("inventory_name")
 ```
 
+The create_detached_inventory function accepts 3 arguments, only first is required.
+The second argument takes a table of callbacks, which can be used to control how
+players interact with the inventory:
+
+```lua
+-- Input only detached inventory
+minetest.create_detached_inventory("inventory_name", {
+    allow_move = function(inv, from_list, from_index, to_list, to_index, count, player)
+        return count -- allow moving
+    end,
+
+    allow_put = function(inv, listname, index, stack, player)
+        return stack:get_count() -- allow putting
+    end,
+
+    allow_take = function(inv, listname, index, stack, player)
+        return -1 -- don't allow taking
+    end,
+
+    on_put = function(inv, listname, index, stack, player)
+        minetest.chat_send_all(player:get_player_name() ..
+            " gave " .. stack:to_string() ..
+            " to the donation chest at " .. minetest.pos_to_str(pos))
+    end,
+})
+```
+
+Permission callbacks - ie: those starting with `allow_`- return the number
+of items to transfer, with -1 being used to prevent transfer completely.
+
+Action callbacks - starting with `on_` - don't have a return value and
+can't prevent transfers.
+
 ## Lists
 
 Inventory Lists are a concept used to allow multiple grids to be stored inside a single location.
diff --git a/_en/map/storage.md b/_en/map/storage.md
index 534e40f..9727467 100644
--- a/_en/map/storage.md
+++ b/_en/map/storage.md
@@ -13,18 +13,18 @@ redirect_from:
 
 In this chapter, you will learn how you can store data.
 
-- [Metadata](#metadata)
-  - [What is Metadata?](#what-is-metadata)
-  - [Obtaining a Metadata Object](#obtaining-a-metadata-object)
-  - [Reading and Writing](#reading-and-writing)
-  - [Special Keys](#special-keys)
-  - [Storing Tables](#storing-tables)
-  - [Private Metadata](#private-metadata)
-  - [Lua Tables](#lua-tables)
-- [Mod Storage](#mod-storage)
-- [Databases](#databases)
-- [Deciding Which to Use](#deciding-which-to-use)
-- [Your Turn](#your-turn)
+- [Metadata](#Metadata)
+  - [What is Metadata?](#What-is-Metadata)
+  - [Obtaining a Metadata Object](#Obtaining-a-Metadata-Object)
+  - [Reading and Writing](#Reading-and-Writing)
+  - [Special Keys](#Special-Keys)
+  - [Storing Tables](#Storing-Tables)
+  - [Private Metadata](#Private-Metadata)
+  - [Lua Tables](#Lua-Tables)
+- [Mod Storage](#Mod-Storage)
+- [Databases](#Databases)
+- [Deciding Which to Use](#Deciding-Which-to-Use)
+- [Your Turn](#Your-Turn)
 
 ## Metadata