adding 'see also' headers

recipes/1_install_configure/install_with_installer/recipe.md

@@ -44,3 +44,4 @@ Note that installation and configuration is different based on whether you insta
 
 Solution 2 simply downloads the Redis installer script, and feeds it directly into `bash` to execute the commands.
 
+### See Also

recipes/1_install_configure/install_with_make/recipe.md

@@ -15,4 +15,4 @@ Salvatore Sanfilippo, the creator of Redis, is a strong proponent of a 'zero-con
 install philosophy. Indeed, Redis has no hard dependencies. We've even timed how long it takes
 to go from "download to server interaction": 34 seconds at last check. 
 
-
+### See Also

recipes/2_basic commands/create_unique_ids/recipe.md

@@ -23,3 +23,5 @@ Utilize Redis' built-in atomic INCR function.
 The use of INCR to provide unique ID's is one of the core concepts in Redis. It is often used in the 'primary key' style, replacing the same functionality used in relational databases.
 
 See *Storing Ruby Objects in Redis* for more examples of using unique ID's.
+
+### See Also

recipes/2_basic commands/empty_the_database/recipe.md

@@ -11,4 +11,6 @@ Use Redis' FLUSHALL command.
 
 ### Discussion
 
+### See Also
+
 

recipes/2_basic commands/get_and_delete/recipe.md

@@ -25,10 +25,10 @@ return value
         (integer) 1
         >> GET TOTO
         (nil)
-
-
 
 ### Discussion
 
 This is a simple one, but makes good use of Redis' atomic features. GET and DEL benefit from the RENAME function in order to keep other clients from reading the object data between operations.
 
+### See Also
+

recipes/2_basic commands/pipeline_multiple_commands/recipe.md

@@ -70,7 +70,9 @@ Indeed, M/E is only an 'all or nothing' operation *before* the EXEC command is r
 Redis does provide an interesting way to deal with issue: the familiar Append-Only 
 File. In the upcoming version of Redis, the commands in the queue are only written
 to the AOF upon successful completion of the EXEC command. So if your server crashes
-mid-EXEC, you can rebuild state according to the previous, pre-EXEC state. 
+mid-EXEC, you can rebuild state according to the previous, pre-EXEC state.
+
+### See Also 
 
 
 

recipes/3_object_level_interaction/using_a_ruby_library_to_store_objects/recipe.md

@@ -80,4 +80,5 @@ association are stored under separate keys. `has_many` uses a Redis
 list to store the keys of associated objects, `has_one` uses a Redis
 string to store the single associated key. 
 
+### See Also
 

recipes/4_creating_higher_level_data_structures/implement_a_fifo_queue/recipe.md

@@ -56,4 +56,4 @@ interaction (and uses INCR to ensure a unique ID for each new queue):
             popped_element = redis.rpop(id_name)
             return popped_element
 
-
+### See Also

recipes/5_durability_and_consistency/make_data_more_durable/recipe.md

@@ -20,7 +20,6 @@ tradeoff between durability and speed. These configurations can be set in `redis
 
 The three options are to force a sync every command, sync every second, or never force a sync (that is, leave the process up to the operating system). Redis' default is the sync on every command; however, this will be quite slow. The second option is usually a fair trade-off between safety and speed.
 
-
-
+### See Also