README.md in fridge-0.1.0 vs README.md in fridge-0.1.1

@@ -21,10 +21,10 @@
 | Parameter | Description | Possible Values |
 | --------- | ----------- | --------------- |
 | `private_key` | Private token signing key | A PEM-formatted key |
 | `public_key` | Public token verification key (the private key's complement) | A PEM-formatted key |
 | `signing_algorithm` | Algorithm to use for sigining and verification | `RS512`, `RS256` |
-| `validator` | A lambda used to perform custom validation of tokens  | Any `Proc` |
+| `validator` | A lambda used to perform custom validation of tokens | Any `Proc` |
 
 Resource servers must configure a public key corresponding to an authorization server, in order to verify tokens issued by that server. Authorization servers must configure a private key.
 
 By default, public key-verified tokens are considered valid if and only iff they have not expired (i.e., `expires_at > Time.now`). However, some applications may want to perform additional validations. (For example, an authorization server may allow online revocation of tokens before their natural expiration, and need to check the current ). This is possible by configuring a custom validator: