Skip to content

Commit

Permalink
Spelling/Grammar fixes in docs
Browse files Browse the repository at this point in the history
Hi, thanks for writing these docs! I'm reading through them and hoping to give back by fixing up some spelling and grammatical issues.
  • Loading branch information
ryanwilsonperkin authored Mar 1, 2017
1 parent ad251e9 commit 313a004
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/relay/nodes.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ Nodes

A ``Node`` is an Interface provided by ``graphene.relay`` that contains
a single field ``id`` (which is a ``ID!``). Any object that inherits
from it have to implement a ``get_node`` method for retrieving a
from it has to implement a ``get_node`` method for retrieving a
``Node`` by an *id*.


Expand All @@ -26,8 +26,8 @@ Example usage (taken from the `Starwars Relay example`_):
return get_ship(id)
The ``id`` returned by the ``Ship`` type when you query it will be a
scalar which contains the enough info for the server for knowing it’s
type and it’s id.
scalar which contains enough info for the server to know its type and
its id.

For example, the instance ``Ship(id=1)`` will return ``U2hpcDox`` as the
id when you query it (which is the base64 encoding of ``Ship:1``), and
Expand Down Expand Up @@ -77,7 +77,7 @@ Accessing node types
If we want to retrieve node instances from a ``global_id`` (scalar that identifies an instance by it's type name and id),
we can simply do ``Node.get_node_from_global_id(global_id, context, info)``.

In the case we want to restrict the instnance retrieval to an specific type, we can do:
In the case we want to restrict the instance retrieval to a specific type, we can do:
``Node.get_node_from_global_id(global_id, context, info, only_type=Ship)``. This will raise an error
if the ``global_id`` doesn't correspond to a Ship type.

Expand Down

0 comments on commit 313a004

Please sign in to comment.