Reachability.swift: Connection.none can cause confusion

Hi,

the documentation says "isReachable has been deprecated. Use connection != .none instead".
This can cause confusion when used together with optionals. Here is an example:

Assume you store the reachability instance into an optional property:
var reachability = Reachability()

And then later you want to do something if you are not connected:

if reachability?.connection == .none {
    // show offline message, for example
}

The code inside the if statement will only be called if reachability is nil, not if it has a value and connection equals .none (because Swift checks if the optional value _reachability_ equals Optional.none). To make it work when _reachability_ is an optional property, you have to write

if reachability?.connection == Reachability.Connection.none {
    // show offline message, for example
}

Thats why it might be better to rename Connection.none to something else or mention it in the documentation.