Merge pull request #291 from clwesene/master

Correcting spelling errors

Author: GitHubber17

powerapps-docs/maker/common-data-service/data-platform-create-entity.md

@@ -34,7 +34,7 @@ These instructions will show you how to create a custom entity manually, you can
 3. In the **Display name** field, enter a name that's easily recognizable for you to refer to this entity in the future. This is also used in forms, charts and other objects created using this entity. You'll notice two other fields also be populated:
 
     * Plural display name - this is used when interacting with this entity from PowerApps or Flow, and used as the name of the entity through the Common Data Service WebAPI. The Plural name should be automatically generated, but can be changed.
-    * Name - this is the unqiue name of the entity, it cannot contain special charecters or spaces and must be unqiue. The name also includes a prefix which was setup when your environment was created, this is used ensure the entities you create can be exported and imported into other environemnts with colliding with other entity names. This prefix can be changed by updating the prefix on your Publisher for the Common Data Service Default Solution.
+    * Name - this is the unique name of the entity, it cannot contain special characters or spaces and must be unique. The name also includes a prefix which was setup when your environment was created, this is used ensure the entities you create can be exported and imported into other environments with colliding with other entity names. This prefix can be changed by updating the prefix on your Publisher for the Common Data Service Default Solution.
 
     > [!NOTE]
     > The **Display name** fields can be updated at anytime to display differently in your apps, the **Name** field cannot be changed after your entity has been saved as this could result in breaking an existing app.
@@ -56,12 +56,12 @@ These instructions will show you how to create a custom entity manually, you can
 6. Click **Done** to add the field, and repeat step 5 to add additional fields.
 7. Click **Save entity** to save your entity and make it available for use in apps.
 
-    Your entity appears in the list of entities in your database. To see entties you've created, you can change the filter in the command bar from "Default" to "Custom"
+    Your entity appears in the list of entities in your database. To see entities you've created, you can change the filter in the command bar from "Default" to "Custom"
 
 ## System fields
 All entities have system fields. These fields are read-only. Therefore, you can't change or delete these fields, and you don't assign values to them. By default system fields will not be shown in the list of fields even though they exist on the entity. To see all fields, you can change the filter on the Command Bar from **Default** to **All**.
 
-For more inforamtion on the metadata related to an entity, see [Entity metadata](../../developer/common-data-service/entity-metadata.md)
+For more information on the metadata related to an entity, see [Entity metadata](../../developer/common-data-service/entity-metadata.md)
 
 ## Next steps
 * [Manage fields in an entity](data-platform-manage-fields.md)

powerapps-docs/maker/common-data-service/data-platform-intro.md

@@ -24,14 +24,14 @@ The Common Data Service allows you to securely store and manage data which is us
 * Leverage existing standard entities or create custom entities to support your scenario and application.
 * Create PowerApps and Flows directly against the Common Data Service.
 * Add custom fields, and relationships to standard entities where additional information is needed.
-* Create calculated and roll up fields to your entities to provide consistent caculations across apps and analytics.
+* Create calculated and roll up fields to your entities to provide consistent calculations across apps and analytics.
 * Define business rules to ensure data quality within entities, regardless of the which app is accessing or editing your data.
 * Create workflows and leverage integration with Microsoft Flow to drive additional actions and business processes against your data.
 * Incorporate standard and custom entities into an app that you're developing as easily as you would with data in other sources.
 * Connect to your data from Microsoft Excel using the Common Data Service productivity add-ins.
-* Easily import and syncronise your data using Power Query.
+* Easily import and synchronize your data using Power Query.
 * Secure your data within your organization using role-based security against standard and custom entities.
-* Provide global support for your data and applications by leveraging translation of entity and field names in your users language.
+* Provide global support for your data and applications by leveraging translation of entity and field names in your user's language.
 
 Each entity contains a set of records that users can create, read, update, and delete depending on their permissions. You can create relationships between entities so that you can look up information in one entity based on a record in another entity. For example, you could create a custom entity to track events which a customer had attended. By adding the Customer to your custom entity as a lookup field, you establish a relationship between the two entities which can be leveraged in your app and in reporting.
 
@@ -57,21 +57,23 @@ When you develop an app, you can use standard entities, custom entities, or both
 
 ## Interacting with entities
 
-When using a standard entity, or creating a custom entity there are multiple elements available within each one and different actions that can be performed. Depending on how simple or advanced your business scenario is will determine which features you will need to use. To see the entities available within your environment, sign in to [PowerApps](https://web.powerapps.com), and click Data and then Entities from the left  menu.
+When using a standard entity or creating a custom entity there are multiple elements available within each one and different actions that can be performed. Depending on how simple or advanced your business scenario is will determine which features you will need to use. To see the entities available within your environment, sign in to [PowerApps](https://web.powerapps.com), and click Data and then Entities from the left menu.
 
-### System fields
-All entities, whether standard or custom, are created with a set of read-only fields that you can't change, delete, or set to a value. These are the most important system fields:
+![Entity Details](./media/data-platform-cds-intro/entitylist.png "Entity Details")
 
 * Each **field** allows you to define a piece of information to be collected, and the data type or format you would like to display it. Fields are similar to columns in databases or Excel.
-* Alternate **keys** allow effiecient and accurate search and interaction with records in the entity when not using the standard unique identifier. This is particular important when using a Business Key or intergrating with an external system.
-* Each entity can have multiple **relationships** to other entities to support look ups and queries across entities. Relationiships can create to support Many-to-one, One-to-many and Many-to-many relationships.
-* **Views** allow each entity can be presented in multiple ways, including which fields are displayed, filtering and sorting of the data. These presenations are saved as views and can be consumed in different apps, for example you may only want to see Active Accounts within your app so you would use a view which is pre filtered to only show Active accounts to avoid repeating the filter in each consuming app.
+* Alternate **keys** allow efficient and accurate search and interaction with records in the entity when not using the standard unique identifier. This is important when using a Business Key or integrating with an external system.
+* Each entity can have multiple **relationships** to other entities to support look ups and queries across entities. Relationships can create to support Many-to-one, One-to-many and Many-to-many relationships.
+* **Views** allow each entity can be presented in multiple ways, including which fields are displayed, filtering and sorting of the data. These presentations are saved as views and can be consumed in different apps, for example you may only want to see Active Accounts within your app so you would use a view which is pre filtered to only show Active accounts to avoid repeating the filter in each consuming app.
 * **Business rules**  can be used to validate data being created and updated in entities to ensure data quality. Each business rule can validate data across multiple fields and entities, prompt warning and error messages regardless of the app being used to create the data.
-* **Data** stored within the Common Data Service is availalbe through the PowerApps portal, PowerApps, Microsoft Excel and Web APIs for Developers.
+* **Data** stored within the Common Data Service is available through the PowerApps portal, PowerApps, Microsoft Excel and Web APIs for Developers.
+
+### System fields
+All entities, whether standard or custom, are created with a set of read-only fields that you can't change, delete, or set to a value. These are the most important system fields:
 
 ## Logic and validation
 
-Entities within the Common Data Service can leverage rich server-side logic and validation to ensure data quality, and reduce repeatitive code in each app creating and using data in the entity.
+Entities within the Common Data Service can leverage rich server-side logic and validation to ensure data quality and reduce repetitive code in each app creating and using data in the entity.
 
 * **Business rules** can validate data across multiple fields and entities, prompt warning and error messages regardless of the app being used to create the data. For more information, see [Create a business rule](./data-platform-create-business-rule.md).
 * **Business process flows** guide users to ensure data is entered consistently and follow the same steps every time. Business process flows are currently only supported for Model driven apps. For more information, see [Business process flows overview](/dynamics365/customer-engagement/customize/business-process-flows-overview).
@@ -83,11 +85,11 @@ Entities within the Common Data Service can leverage rich server-side logic and
 There are several ways to start getting data into the Common Data Service:
 
 * Create a PowerApp or Flow to start creating data.
-* Use Power Query to connect to an online or on-premise data source and import it directly into the Commmon Data Service. Power Query also allows you to create the entities during import based off the schema of your source as well as perform transformations to your data during import. For more information, see [Add data to an entity in the Common Data Service by using Power Query](./data-platform-cds-newentity-pq.md).
+* Use Power Query to connect to an online or on-premise data source and import it directly into the Common Data Service. Power Query also allows you to create the entities during import based off the schema of your source as well as perform transformations to your data during import. For more information, see [Add data to an entity in the Common Data Service by using Power Query](./data-platform-cds-newentity-pq.md).
 
 ## Developer Capabilities
 
-In addition to the features available through the [PowerApps](https://web.powerapps.com) portal, the Common Data Service also includes features for developers to programatically access metadata and data to create entities and business logic, as well as interact with data. For more information, see [Common Data Service for Apps Developer Overview](../../developer/common-data-service/overview.md)
+In addition to the features available through the [PowerApps](https://web.powerapps.com) portal, the Common Data Service also includes features for developers to programmatically access metadata and data to create entities and business logic, as well as interact with data. For more information, see [Common Data Service for Apps Developer Overview](../../developer/common-data-service/overview.md)
 
 ## Get started
 Try it out by creating an app using a standard entity or [create a custom entity](create-custom-entity.md), and then [create an app that uses that entity](../canvas-apps/data-platform-create-app.md).