Fixed grammar and whitespace issues#110
Open
dczarnota wants to merge 1 commit intothomasdavis:gh-pagesfrom
Open
Fixed grammar and whitespace issues#110dczarnota wants to merge 1 commit intothomasdavis:gh-pagesfrom
dczarnota wants to merge 1 commit intothomasdavis:gh-pagesfrom
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
saveapi call which is intelligent and will send a PUT request instead of a POST request if anidis present(conforming to RESTful conventions)333:
When a model has an
idwe know that it exist on the server, so if we wish to remove it from the server we can calldestroy.destroywill 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
saveapi call which is intelligent and will send a PUT request instead of a POST request if anidis present (conforming to RESTful conventions).333:
When a model has an
idwe know that it exists on the server, so if we wish to remove it from the server we can calldestroy.destroywill fire off a DELETE /user/id (conforming to RESTful conventions).