Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed grammar and whitespace issues #110

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from

Conversation

dczarnota
Copy link

Changed "exist" to "exists" on lines 310 and 333. At line 311, added whitespace between "present" and "(conforming to RESTful conventions)" as well as a period at the end of the sentence.

BEFORE:
310-311:

Now that we have a model that exist on the server we can perform an update using a PUT request.
We will use the save api call which is intelligent and will send a PUT request instead of a POST request if an id is present(conforming to RESTful conventions)

333:

When a model has an id we know that it exist on the server, so if we wish to remove it from the server we can call destroy. destroy will fire off a DELETE /user/id (conforming to RESTful conventions).

AFTER:
310-311

Now that we have a model that exists on the server we can perform an update using a PUT request.
We will use the save api call which is intelligent and will send a PUT request instead of a POST request if an id is present (conforming to RESTful conventions).

333:

When a model has an id we know that it exists on the server, so if we wish to remove it from the server we can call destroy. destroy will fire off a DELETE /user/id (conforming to RESTful conventions).

Changed "exist" to "exists" on lines 310 and 333. At line 311, added whitespace between "present" and "(conforming to RESTful conventions)" as well as a period at the end of the sentence.

BEFORE:
310-311: <p>Now that we have a model that exist on the server we can perform an update using a PUT request.
We will use the <code>save</code> api call which is intelligent and will send a PUT request instead of a POST request if an <code>id</code> is present(conforming to RESTful conventions)</p>

333: <p>When a model has an <code>id</code> we know that it exist on the server, so if we wish to remove it from the server we can call <code>destroy</code>.  <code>destroy</code> will fire off a DELETE /user/id (conforming to RESTful conventions).</p>

AFTER:
310-311 <p>Now that we have a model that exists on the server we can perform an update using a PUT request.
We will use the <code>save</code> api call which is intelligent and will send a PUT request instead of a POST request if an <code>id</code> is present (conforming to RESTful conventions).</p>

333: <p>When a model has an <code>id</code> we know that it exists on the server, so if we wish to remove it from the server we can call <code>destroy</code>.  <code>destroy</code> will fire off a DELETE /user/id (conforming to RESTful conventions).</p>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant