update quickfort guide and aliases

- move bit of alias documentation from aliases-common to aliases.txt
- document new behavior for 'c'ustom stockpiles

data/quickfort/aliases-common.txt

@@ -17,10 +17,6 @@
 #
 # Aliases that don't fit into those two categories have comments explaining
 # their usage.
-#
-# There is also a non-alphanumeric alias built into the code for the common
-# shorthand for "make room":
-#   r+   expands to r+&
 
 
 ########################################
@@ -41,6 +37,9 @@ give10down: {give move={Down 10}}
 give10left: {give move={Left 10}}
 give10right: {give move={Right 10}}
 
+# usage example: {givename name="myname"}
+givename: {Ctrl}n{name}&
+
 # use to toggle a sequence of stockpile options. for example: {togglesequence 5}
 togglesequence: &{Down}
 togglesequence2: &{Down 2}

dfhack-config/quickfort/aliases.txt

@@ -95,8 +95,12 @@
 #   !   expands to {Ctrl}
 #   ^   expands to {ESC}
 #
+# There is also a non-standard alias built into the code for the common
+# shorthand for "make room":
+#   r+  expands to r+&
+#
 # If you need literal verisons of the shorthand characters, surround them in
-# curly brackets, for example: "{~}"
+# curly brackets, for example: "{!}"
 #
 #
 # Add your custom aliases here:

docs/guides/quickfort-user-guide.rst

@@ -502,12 +502,11 @@ meeting area all at once:
    #zone main pasture and picnic area
    nmg(10x10)
 
-The order of the individual letters doesn't matter. Note that "custom"
-(:kbd:`c`) stockpiles cannot be declared in a blueprint since what would
-get created would depend on what happens to be set in the "custom stockpile
-settings" in your game. Instead, place stockpiles using the keys that
-represent the types you want to store and then use a ``#query`` blueprint to
-customize them.
+The order of the individual letters doesn't matter. If you want to configure the
+stockpile from scratch in a ``#query`` blueprint, you can place unconfigured
+"custom" stockpiles with (:kbd:`c`). It is more efficient, though, to place
+stockpiles using the keys that represent the types you want to store, and
+then only use a ``#query`` blueprint if you need fine-grained customization.
 
 Detailed configuration for zones, such as the pit/pond toggle, can also be set
 by mimicking the hotkeys used to set them. Note that gather flags default to