Replace services with products.

content/GCP/02_intro_to_compute.ipynb

@@ -20,7 +20,7 @@
     "* How do I create my own computer in the cloud?\n",
     "\n",
     "**Objectives:**\n",
-    "* Navigate the Google Compute Engine service and terminology.\n",
+    "* Navigate the Google Compute Engine product and terminology.\n",
     "* Allocate a virtual machine in Google Compute Engine.\n",
     "* Choose a machine type based on the application.\n",
     "* Use the cost estimator for Google Compute Engine.\n",
@@ -46,7 +46,7 @@
    "source": [
     "## Google Compute Engine\n",
     "\n",
-    "To learn more about the Google Compute Engine service we will use the web console to create, explore, and destroy a Virtual Machine.  The ability to quickly create, explore, and then discard resources in the web-console is a powerful tool to learn more about a service.  After an initial exploration with the web-console, programmatic access using scripts or configuration management systems should be used.\n",
+    "To learn more about the Google Compute Engine product we will use the web console to create, explore, and destroy a Virtual Machine.  The ability to quickly create, explore, and then discard resources in the web-console is a powerful tool to learn more about a product.  After an initial exploration with the web-console, programmatic access using scripts or configuration management systems should be used.\n",
     "\n",
     "Unfortunately, the terminology used for cloud computing differs from one commercial cloud provider to another. Google Compute Engine uses the term **VM instance** to refer to a running virtual machine, **image** for the boot disk containing the operating system, and **disk** for the writable storage used for a running *VM Instance*.\n",
     "\n",
@@ -62,7 +62,7 @@
    "source": [
     "## Allocate a VM Instance\n",
     "\n",
-    "We will first create an *VM instance* with defaults to explore the Google Compute Engine service.\n",
+    "We will first create an *VM instance* with defaults to explore the Google Compute Engine product.\n",
     "\n",
     "To create a VM Instance we do the following:\n",
     "  * Click **Navigation Menu** -> **Compute Engine** (under Compute) -> **VM Instances** -> **+Create Instance** (just under the blue bar) to open the *Create an instance* page.\n",
@@ -99,7 +99,7 @@
    "source": [
     "## More on Security (Optional)\n",
     "\n",
-    "Everything in the cloud requires permission (authorization). Ordinary we would configure and check security first but in the case of exploring services it is often easier to do things out of order.  We noted that the *VM instance* was created with the *Compute Engine default service account*, and if the \"Allow full access to all Cloud Api's\" scope is enable, then everyone on the VM has access to all the resources in your project.\n",
+    "Everything in the cloud requires permission (authorization). Ordinary we would configure and check security first but in the case of exploring products it is often easier to do things out of order.  We noted that the *VM instance* was created with the *Compute Engine default service account*, and if the \"Allow full access to all Cloud Api's\" scope is enable, then everyone on the VM has access to all the resources in your project.\n",
     "\n",
     "In the case of Drew, this is useful since they will be storing results of the analysis in Cloud Storage and the VM that will be doing the processing will need to have access to the storage. This is the mechanism that allows this.\n",
     "\n",
@@ -113,9 +113,9 @@
     "\n",
     "There are three important pieces of information that work together to form the **IAM policy**. The permission (role), the identity (principal or member), and the resource (project).\n",
     "\n",
-    "There is one additional tool that is used, **scope**.  Scope describes the services that are accessible by an identity and is a simple way of limiting access to services.  \n",
+    "There is one additional tool that is used, **scope**.  Scope describes the products that are accessible by an identity and is a simple way of limiting access to products.  \n",
     "\n",
-    "When we previously created the virtual machine we selected the default **scope**, which limits what services the virtual machine has access to.   In other words, these scopes can only *limit* what a virtual machine instance can do, it can not add any permissions that are not already granted to the service account through IAM.  In general, access should be managed through IAM policy, not scope.\n"
+    "When we previously created the virtual machine we selected the default **scope**, which limits what products the virtual machine has access to.   In other words, these scopes can only *limit* what a virtual machine instance can do, it can not add any permissions that are not already granted to the service account through IAM.  In general, access should be managed through IAM policy, not scope.\n"
    ]
   },
   {
@@ -308,7 +308,7 @@
     "\n",
     "Did you \"Follow\" the VM instance by looking at the **activity** page as discussed above?\n",
     "\n",
-    "Since we care about paying for resources we are not using we review our project by visiting the *compute engine* service and reviewing that we no longer have any *VM instances* running. \n",
+    "Since we care about paying for resources we are not using we review our project by visiting the *compute engine* product and reviewing that we no longer have any *VM instances* running. \n",
     "  * Go to **Navigation Menu** -> **Compute Engine** (under Compute) -> **Instances** and look for your virtual machine.  It should be gone!\n",
     "\n",
     "In a later episode we will show how to easily list all the resources in a project."