Merge pull request #357 from burtonnr/patch-1

Update 050-docker-setup-postgres-with-adventureworks.Rmd

Author: smithjd

050-docker-setup-postgres-with-adventureworks.Rmd

@@ -123,7 +123,7 @@ con <- dbConnect(          # use in other settings
 
 ## Adventureworks Schemas
 
-Think of the Adventureworks database as a model of the Adventureworks business.  The business is organized around different departments (humanresources, sales, and purchasing), business processes (production), and resources (person).  Each schema is a container for the all the database objects needed to model the departments, business processes, and resources.  As a data analyst, the connections tab has three of the five database objects of interest.  These are schemas, tables and views.  The other two database objects of interest not shown in the connetions tab are the table primary and foreign keys, PK and FK.  Those database objects enforce the referential integrity of the data and the performance of the application.  Let the DBA's worry about them.
+Think of the Adventureworks database as a model of the Adventureworks business.  The business is organized around different departments (human resources, sales, and purchasing), business processes (production), and resources (person).  Each schema is a container for the all the database objects needed to model the departments, business processes, and resources.  As a data analyst, the connections tab has three of the five database objects of interest.  These are schemas, tables and views.  The other two database objects of interest not shown in the connections tab are the table primary and foreign keys, PK and FK.  Those database objects enforce the referential integrity of the data and the performance of the application.  Let the DBA's worry about them.
 
 The Connections tab has three icons.  The node icon represents a schema.  The schema helps organize the structure and design of the database.  The schema contains the views, the grid with the glasses, and tables, the grids without the glasses, that are of interest to the data analyst.  A table is a database object usually represents something useful to a business process.  For example, a sales person may enter a new order.  The first screen is typically called the sales order header screen which contains information about the customer placing the order.  This information is captured in *salesorderheader* table.  The customers ordered items are typically entered via multiple screens.  These are captured in the *salesorderdetail* table.