diff --git a/data/buildcraft/items/charging_table/item.cg b/data/buildcraft/items/charging_table/item.cg
new file mode 100644
index 00000000..6013800f
--- /dev/null
+++ b/data/buildcraft/items/charging_table/item.cg
@@ -0,0 +1,7 @@
+schema: 1
+
+description: <<-END
+The charging table transfers energy provided by lasers into an item capable of holding charge (e.g., a
+[Redstone Flux Capacitor]).  It works much like an [Assembly Table] in that it requires powered [Laser]s within range to
+provide it with power.  Just place an item in table, and it will automatically start the lasers and charge the item.
+END
\ No newline at end of file
diff --git a/data/buildcraft/items/chute/item.cg b/data/buildcraft/items/chute/item.cg
new file mode 100644
index 00000000..b412ef6d
--- /dev/null
+++ b/data/buildcraft/items/chute/item.cg
@@ -0,0 +1,16 @@
+schema: 1
+
+description: <<-END
+The Chute is a small container (only 4 slots) which will place items into any inventory located directly below it
+whenever that inventory has an available space. This makes it an ideal buffer in a pipe system which feeds machines
+having limited capacity (e.g., like feeding ore to a [Furnace]).  The four slot capacity allows dissimilar items to
+collect in the chute while the furnce it busy with a different type of item.
+
+Since the [Hopper] was added to vanilla Minecraft, the chute is largely redundant. While the Chute ejects items
+considerably faster than a Hopper, the latter offers many advantages.
+
+* the hopper is less expensive to make (no gear required)
+* the hopper has one more slot in its inventory
+* the hopper can direct items to the sides as well and directly underneath
+* the hopper can suck in loose items out in the world (like an [Obsidian Pipe])
+END
\ No newline at end of file
diff --git a/scripts/deploy b/scripts/deploy
index 4544d3f4..8f7da29b 100755
--- a/scripts/deploy
+++ b/scripts/deploy
@@ -3,7 +3,7 @@
 if [[ -e "./aws.config" ]]; then
     export AWS_CONFIG_FILE="./aws.config"
 else
-    export AWS_CONFIG_FILE="~/.aws/config"
+    export AWS_CONFIG_FILE="$HOME/.aws/config"
 fi
 
 SOURCE_DIR="./data/"