From 29967cde19067df62dbe98e881ebb560740a2d39 Mon Sep 17 00:00:00 2001 From: tigerbot Date: Tue, 7 Mar 2017 14:54:08 -0700 Subject: [PATCH] fixed some spelling errors in the README --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index ec7cb33..1a40080 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ The world's smallest, fastest, and most secure OAuth3 (and OAuth2) JavaScript im Instead of bloating your webapp and ruining the mobile experience, you can use a single, small javascript file for all OAuth3 providers -(and almost all OAuth2 providers) with a seemless experience. +(and almost all OAuth2 providers) with a seamless experience. Also, instead of complicated (or worse - insecure) CLI and Desktop login methods, you can easily integrate an OAuth3 flow (or broker) into any node.js app (i.e. Electron, Node-Webkit) @@ -74,7 +74,7 @@ function onClickLogin() { console.info('Authentication was Successful:'); console.log(session); - // You can use the PPID (or preferrably a hash of it) as the login for your app + // You can use the PPID (or preferably a hash of it) as the login for your app // (it securely functions as both username and password which is known only by your app) // If you use a hash of it as an ID, you can also use the PPID itself as a decryption key // @@ -168,7 +168,7 @@ pushd /path/to/your/web/app # clone the project as assets/org.oauth3 mkdir -p assets git clone git@git.daplie.com:Daplie/oauth3.js.git assets/org.oauth3 -pushd assests/org.oauth3 +pushd assets/org.oauth3 git checkout v1 popd @@ -232,7 +232,7 @@ function onClickLogin() { console.info('Authentication was Successful:'); console.log(session); - // You can use the PPID (or preferrably a hash of it) as the login for your app + // You can use the PPID (or preferably a hash of it) as the login for your app // (it securely functions as both username and password which is known only by your app) // If you use a hash of it as an ID, you can also use the PPID itself as a decryption key // @@ -448,7 +448,7 @@ As a general rule I don't like rules that sometimes apply and sometimes don't, so I may need to rethink this. However, there are cases where including the protocol can be very ugly and confusing and we definitely need to allow relative paths. -A potential work-around would be to assume all paths are relative (elimitate #4 instead) +A potential work-around would be to assume all paths are relative (eliminate #4 instead) and have the path always key off of the base URL - if oauth3 directives are to be found at https://example.com/username/.well-known/oauth3/directives.json then /api/whatever would refer to https://example.com/username/api/whatever.