Skip to content

Commit 313a004

Browse files
Spelling/Grammar fixes in docs
Hi, thanks for writing these docs! I'm reading through them and hoping to give back by fixing up some spelling and grammatical issues.
1 parent ad251e9 commit 313a004

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/relay/nodes.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ Nodes
33

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

99

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

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

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

0 commit comments

Comments
 (0)