From bf7a5cc4ac12f439384a6f2b2bafdde664093446 Mon Sep 17 00:00:00 2001
From: Jon Griffith <32052562+arretx@users.noreply.github.com>
Date: Wed, 10 Jul 2019 03:26:13 -0700
Subject: [PATCH] Slight process change (#9823)

Added a bit of clarification for the way the process currently looks in the Google Dev console.
---
 source/_components/calendar.google.markdown | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/source/_components/calendar.google.markdown b/source/_components/calendar.google.markdown
index 9ee52b731e1..f53d2987bb0 100644
--- a/source/_components/calendar.google.markdown
+++ b/source/_components/calendar.google.markdown
@@ -30,14 +30,14 @@ Generate a Client ID and Client Secret on
 1. Follow the wizard using the following information.
 1. When it gets to the point of asking _Which API are you using?_ just click cancel.
 1. Under APIs & Services > Credentials, click on the tab 'OAuth consent screen'.
-1. Set 'Product name shown to users' to anything you want. We suggest "Home-Assistant".
+1. Set the 'Application Name' (the name of the application asking for consent) to anything you want. We suggest "Home-Assistant".
 1. Save this page. You don't have to fill out anything else there.
 1. Click 'Create credentials' -> OAuth client ID.
 1. Set the Application type to 'Other' and give this credential set a name then click Create.
-1. Save the client ID and secret as you will need to put these in your `configuration.yaml` file.
-1. Click on "Library", search for "Google Calendar API" and enable it.
+1. Copy the client ID and secret to a text editor temporarily as you will need to put these in your `configuration.yaml` file.
+1. Under "API's and Services" (left sidebar), click on "Library."  Search for "Google Calendar API" and enable it if it isn't already enabled automatically through this process.
 
-If you are adding more Google API scopes later to the OAuth than just "Google Calendar API" then you need to delete your token file. You will lose your refresh token due to the re-authenticating to add more API access. It's recommended to use different authorizations for different pieces of Google.
+If you will be adding more scopes than just the "Google Calendar API" to the OAuth for this application, you will need to delete your token file. You will lose your refresh token due to the re-authenticating to add more API access. It's recommended to use different authorizations for different pieces of Google.
 
 ## Configuration