Some documentation (WIP)

In find documentation much more understandable and useful in general if you follow the pattern of the standard library. This means that:

1. You write the function call with formal parameters.
2. You directly follow with a description of the returned value in terms of the parameters of the function call. 

In this example the documentation would be: 

```
(** [peer client name] is [client] with [name] as [peer_name]. *) 
```

Note the *is* not *return*: we describe the value not the fact that a function is being called, we are in a functional language. The advantage of this style is that it immediately tells the reader how it should read such an expression in code.