Merge pull request #56 from sgwill/patch-1

Spelling fix

Docs/Configuration.md

@@ -47,7 +47,7 @@ The `ConfigurationOptions` object has a wide range of properties, all of which a
 | Configuration string   | `ConfigurationOptions` | Meaning                                                                         |
 | ---------------------- | ---------------------- | ------------------------------------------------------------------------------- |
 | abortConnect={bool}    | `AbortOnConnectFail`   | If true, `Connect` will not create a connection while no servers are available  |
-| allowAdmion={bool}     | `AllowAdmin`           | Enables a range of commands that are considered risky                           |
+| allowAdmin={bool}     | `AllowAdmin`           | Enables a range of commands that are considered risky                           |
 | channelPrefix={string} | `ChannelPrefix`        | Optional channel prefix for all pub/sub operations                              |
 | connectRetry={int}     | `ConnectRetry`         | The number of times to repeat connect attempts during initial `Connect`         |
 | connectTimeout={int}   | `ConnectTimeout`       | Timeout (ms) for connect operations                                             |
@@ -133,4 +133,4 @@ Likewise, when the configuration is changed (especially the master/slave configu
 
 Both options can be customized or disabled (set to `""`), via the `.ConfigurationChannel` and `.TieBreaker` configuration properties.
 
-These settings are also used by the `IServer.MakeMaster()` method, which can set the tie-breaker in the database and broadcast the configuration change message. The configuration message can also be used separately to master/slave changes simply to request all nodes to refresh their configurations, via the `ConnectionMultiplexer.PublishReconfigure` method.
\ No newline at end of file
+These settings are also used by the `IServer.MakeMaster()` method, which can set the tie-breaker in the database and broadcast the configuration change message. The configuration message can also be used separately to master/slave changes simply to request all nodes to refresh their configurations, via the `ConnectionMultiplexer.PublishReconfigure` method.