grammar and spelling

Author: ANordmoe

tests/integration/components/guide-section/subsection-test.js

@@ -61,7 +61,7 @@ module('Integration | Component | guide-section/subsection', function (hooks) {
     assert
       .dom('[data-test-field="Subsection Description"]')
       .includesText(
-        'Examples here are shown for apps that use JSON:API. Apps using other paradigms should use the builders for REST or ActiveRecord if applicable, or author their own (or a new community lib!) if not.'
+        'Examples here are shown for apps that use JSON:API. Apps using other paradigms should use the builders for REST or ActiveRecord if applicable, or author their own (or a new community library!) if not.'
       );
 
     const emberClassic = this.element.querySelector(
@@ -97,7 +97,7 @@ module('Integration | Component | guide-section/subsection', function (hooks) {
     assert
       .dom('[data-test-field="Subsection Description"]')
       .includesText(
-        'To create a new record using Ember Data you should use createRecord request and attach "body" to it. In case of JSON:API backend - you can use serializeResources request utility.'
+        'To create a new record using Ember Data, you should use createRecord request and attach "body" to it. Use serializeResources request utility when working with a JSON:API backend.'
       );
 
     const emberClassic = this.element.querySelector(
@@ -133,7 +133,7 @@ module('Integration | Component | guide-section/subsection', function (hooks) {
     assert
       .dom('[data-test-field="Subsection Description"]')
       .includesText(
-        'To delete an existing record using Ember Data you should use deleteRecord builder to issue the request.'
+        'To delete an existing record using Ember Data, you should use deleteRecord builder to issue the request.'
       );
 
     const emberClassic = this.element.querySelector(

translations/adapters/path-for-type/en-us.yaml

@@ -2,4 +2,4 @@ title: Use request builders instead of pathForType
 description: >
   To modify a URL for a request you can use the '<code>'resourcePath'</code>' option for every request builder. Default configuration for '<code>'JSON:API'</code>', '<code>'REST'</code>', and '<code>'ActiveRecord'</code>' builders will be provided by EmberData.
   <br />
-  We recommend creating your own utility file with request builders that suite your backend's needs.
+  We recommend creating your own utility file with request builders that suit your backend's needs.

translations/deleting-data/delete-record/en-us.yaml

@@ -1,2 +1,2 @@
 title: deleteRecord
-description: To delete an existing record using Ember Data you should use <code>deleteRecord</code> builder to issue the request.
+description: To delete an existing record using Ember Data, you should use <code>deleteRecord</code> builder to issue the request.

translations/fetching-data/find-all/en-us.yaml

@@ -1,4 +1,4 @@
 title: findAll
 description: |
-  There is no direct replacement for <code>findAll</code>, you can use <code>query</code> without extra options instead. Here is how to achieve exact <code>findAll</code> behavior:
-  We discourage using <code>peekAll</code>. When you made a request, you need to guarantee that everything you requested is part of response you get back.
+  There is no direct replacement for <code>findAll</code>, so you can use <code>query</code> with extra options instead. Here's how to achieve exact <code>findAll</code> behavior:
+  We discourage using <code>peekAll</code>, but it is currently the best way to guarantee that everything you requested is part of the response you get back.

translations/fetching-data/find-record/en-us.yaml

@@ -1,3 +1,3 @@
 title: findRecord
 description: |
-  Examples here are shown for apps that use JSON:API. Apps using other paradigms should use the builders for REST or ActiveRecord if applicable, or author their own (or a new community lib!) if not.
+  Examples here are shown for apps that use JSON:API. Apps using other paradigms should use the builders for REST or ActiveRecord if applicable, or author their own (or a new community library!) if not.

translations/fetching-data/query/en-us.yaml

@@ -1,2 +1,2 @@
 title: query
-description: The <code>query</code> just moved out from being on <code>Store</code> public interface to builders.
+description: The <code>query</code> has moved from the <code>Store</code> public interface to builders.

translations/serializers/general/en-us.yaml

@@ -8,8 +8,8 @@ description: |
   <br />
   Similarly, the methods '<code>'adapterFor'</code>' and '<code>'serializerFor'</code>' will not be deprecated until at least 6.0; however, it should no longer be assumed that an application has an adapter or serializer at all.
   <br />
-  Serializers previously was used to accomplish two main things: serialization and normalization.
+  Serializers previously were used to accomplish two main things: serialization and normalization.
   <br />
   Normalization is now done in handlers, before returning the response.
   <br />
-  Serialization can be done in handler, but we encourage application developers to do it in request builder.
+  Serialization can be done in a handler, but we encourage application developers to do it in request builder.

translations/updating-data/create-record/en-us.yaml

@@ -1,2 +1,2 @@
 title: createRecord
-description: To create a new record using Ember Data you should use <code>createRecord</code> request and attach <code>"body"</code> to it. In case of JSON:API backend - you can use <code>serializeResources</code> request utility.
+description: To create a new record using Ember Data, you should use a <code>createRecord</code> request and attach <code>"body"</code> to it. Use the <code>serializeResources</code> request utility when working with a JSON:API backend.