Typo in client-server spec: ether -> either

This commit is contained in:
Nathan Musoke 2018-01-20 19:15:01 +13:00 committed by GitHub
parent 849a7662fe
commit 7e94cd5a0b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -192,7 +192,7 @@ requests can be handled correctly.
By default, the `Login`_ and `Registration`_ processes auto-generate a new By default, the `Login`_ and `Registration`_ processes auto-generate a new
``device_id``. A client is also free to generate its own ``device_id`` or, ``device_id``. A client is also free to generate its own ``device_id`` or,
provided the user remains the same, reuse a device: in ether case the client provided the user remains the same, reuse a device: in either case the client
should pass the ``device_id`` in the request body. If the client sets the should pass the ``device_id`` in the request body. If the client sets the
``device_id``, the server will invalidate any access token previously assigned ``device_id``, the server will invalidate any access token previously assigned
to that device. There is therefore at most one active access token assigned to to that device. There is therefore at most one active access token assigned to