Skip to content

Commit c8ab166

Browse files
authored
fix typos
1 parent 20d3a1a commit c8ab166

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
# arduino-gmail-client
22

3-
A simple gmail client that makes cURL requests using gmail API to check for unread emails, the response is then used to control arduino pins. So if you connect and LED to the right pins, it will light up everytime you recieve an email.
3+
A simple gmail client that makes cURL requests using gmail API to check for unread emails, the response is then used to control arduino pins. So if you connect an LED to the right pins, it will light up everytime you recieve an email!
44

5-
This was just something I wanted to try when I first stumbled up gmail API and OAuth 2.0 protocols, finally got an arduino to implement it.
5+
This was something I wanted to try when I first stumbled upon gmail API and OAuth 2.0 protocol, finally got an arduino to implement it!!
66

77
### How Does It Work?
88

9-
The code is extremely simple if you understand OAuth 2.0, if you don't read [this article from google](https://developers.google.com/identity/protocols/oauth2). In a nutshell, to access information from a user aka resource owner, a client must do the following:
10-
1. Get the authorization grant from the resource owner (via a [consent screen](https://developers.google.com/identity/protocols/oauth2/web-server#userconsentprompt)).
11-
2. In exchange to the grant, you recieve an authorisation code.
9+
The code is extremely simple if you understand OAuth 2.0, if you don't, read [this article from google](https://developers.google.com/identity/protocols/oauth2). In a nutshell, to access information from a user (a.k.a the resource owner), a client must do the following:
10+
1. Get the authorization grant from the resource owner (for example, via a [consent screen](https://developers.google.com/identity/protocols/oauth2/web-server#userconsentprompt)).
11+
2. In exchange to the grant, you recieve an authorization code.
1212
3. Exchange the authorization code for access and refresh tokens from the authorization server.
1313
4. Use the access tokens to make API calls on behalf of the user.
1414
5. If the access token expires, use the refresh token to request another access token.

0 commit comments

Comments
 (0)