fix console.log higher-order calls in docs

docs/components.md

@@ -137,10 +137,12 @@ dashboard.controller = function() {
 
 dashboard.view = function(ctrl) {
     return m("#example", [
-        new autocompleter.view(ctrl.autocompleter, {onchange: m.withAttr("value", console.log)}),
+        new autocompleter.view(ctrl.autocompleter, {onchange: m.withAttr("value", log)}),
     ]);
 };
 
+//an FP-friendly console.log
+var log = function(value) {console.log(value)}
 
 
 //initialize

docs/mithril.deferred.md

@@ -136,14 +136,19 @@ For the most part, Mithril promises behave as you'd expect a [Promise/A+](http:/
 Mithril promises forward a value downstream if a resolution callback returns `undefined`. This allows simpler debugging of promise chains:
 
 ```javascript
+//a FP-friendly console.log
+var log = function(value) {
+	console.log(value)
+}
+
 var data = m.request({method: "GET", url: "/data"})
-	.then(console.log) //Mithril promises let us debug like this
+	.then(log) //Mithril promises let us debug like this
 	.then(doStuff)
 	
 var data = m.request({method: "GET", url: "/data"})
-	.then(function(value) { // Promises/A+ would require us to declare an anonymous function
+	.then(function(value) {
 		console.log(value) // here's the debugging snippet
-		return value // and we need to remember to return the value as well
+		return value // Promises/A+ requires us to return a value
 	})
 	.then(doStuff) // or else `doStuff` will break
 

docs/mithril.request.md

@@ -139,8 +139,13 @@ As you saw, you can chain operations that act on the response data. Typically th
 In the example below, we take advantage of queuing to debug the AJAX response data prior to doing further processing on the user list
 
 ```javascript
+//a FP-friendly console.log
+var log = function(value) {
+	console.log(value)
+}
+
 var users = m.request({method: "GET", url: "/user"})
-	.then(console.log);
+	.then(log);
 	.then(function(users) {
 		//add one more user to the response
 		return users.concat({name: "Jane"})