Issue #15: Split usage in 3 segments and fixed badge version

README.md

@@ -17,7 +17,7 @@ Documentation is available at: https://docs.dotkernel.org/dot-totp/.
 ## Badges
 
 ![OSS Lifecycle](https://img.shields.io/osslifecycle/dotkernel/dot-totp)
-![PHP from Packagist (specify version)](https://img.shields.io/packagist/dependency-v/dotkernel/dot-totp/php)
+![PHP from Packagist (specify version)](https://img.shields.io/packagist/php-v/dotkernel/dot-totp/1.0.0)
 
 [![GitHub issues](https://img.shields.io/github/issues/dotkernel/dot-totp)](https://github.com/dotkernel/dot-totp/issues)
 [![GitHub forks](https://img.shields.io/github/forks/dotkernel/dot-totp)](https://github.com/dotkernel/dot-totp/network)

docs/book/v1/methods.md

@@ -4,9 +4,9 @@ A code is derived from a shared secret and the current time step, so the same co
 
 | Method | How the user gets the code | Secret lives |
 | --- | --- | --- |
-| `app` | Scans a QR code once, then their device derives every code offline | Server and device |
-| `email` | The server derives the code and sends it by email | Server only |
-| `sms` | The server derives the code and sends it by SMS | Server only |
+| [`app`](usage/app.md) | Scans a QR code once, then their device derives every code offline | Server and device |
+| [`email`](usage/email.md) | The server derives the code and sends it by email | Server only |
+| [`sms`](usage/sms.md) | The server derives the code and sends it by SMS | Server only |
 
 Generation and verification are the same two calls in all three cases.
 `getCode()` is what lets the server derive the code it expects, so email and SMS need no second implementation.