Permalink
Browse files

docs: fix typos

1 parent 6a2176d commit 83481ca4a82b56fc32d1a95ed77f5b2093381282 @maitai maitai committed Oct 7, 2014
Showing with 3 additions and 3 deletions.
  1. +1 −1 CONTRIBUTING.rst
  2. +2 −2 docs/features.rst
View
@@ -17,7 +17,7 @@ Making Changes
* Fork_ the repository on GitHub.
* Create a topic branch from where you want to base your work.
* This is usually the ``develop`` branch.
-* Please avoid working directly on ``develop`` branch.
+* Please avoid working directly on the ``develop`` branch.
* Make commits of logical units (if needed rebase your feature branch before
submitting it).
* Check for unnecessary whitespace with ``git diff --check`` before committing.
View
@@ -145,7 +145,7 @@ would be queried like:
Please note that when designing your API, most of the time you can get away
without resorting to sub-resources. In the example above the same result would
-be achieved by simply exposing a ``invoices`` endpoint that clients could query
+be achieved by simply exposing an ``invoices`` endpoint that clients could query
this way:
::
@@ -232,7 +232,7 @@ As you can see, item endpoints provide their own HATEOAS_ directives.
According to REST principles resource items should only have one unique
identifier. Eve abides by providing one default endpoint per item. Adding
- a secondary endpoint is a decision that should pondered carefully.
+ a secondary endpoint is a decision that should be pondered carefully.
Consider our example above. Even without the ``/people/<lastname>``
endpoint, a client could always retrieve a person by querying the resource

0 comments on commit 83481ca

Please sign in to comment.