From 52a82c9853bb29b073646e47a211ff2a37ab8ced Mon Sep 17 00:00:00 2001 From: Mary Anthony Date: Fri, 19 Apr 2019 11:25:42 -0700 Subject: [PATCH] Fixing Blockstack browser > Blockstack Browser Signed-off-by: Mary Anthony --- _android/tutorial.md | 2 +- _browser/browser-introduction.md | 2 +- _browser/ids-introduction.md | 6 +++--- _develop/add_auth.md | 2 +- _develop/overview_auth.md | 4 ++-- _develop/zero_to_dapp_3.md | 2 +- _develop/zero_to_dapp_3_win.md | 2 +- _ios/tutorial.md | 2 +- overview_auth.md | 6 +++--- 9 files changed, 14 insertions(+), 14 deletions(-) diff --git a/_android/tutorial.md b/_android/tutorial.md index 73af907a..775bfbfe 100644 --- a/_android/tutorial.md +++ b/_android/tutorial.md @@ -223,7 +223,7 @@ In this section, you build an initial React.js application called ### Add a redirect end point to your application -When a user opens the webapp from the Blockstack browser on an Android phone, +When a user opens the webapp from the Blockstack Browser on an Android phone, you want the web app to redirect the user to your Android application. The work you do here will allow it. diff --git a/_browser/browser-introduction.md b/_browser/browser-introduction.md index 54dacfa7..641a46d7 100644 --- a/_browser/browser-introduction.md +++ b/_browser/browser-introduction.md @@ -17,7 +17,7 @@ website or buying an item. ## Understand the Blockstack Browser -Through the Blockstack browser application you can create an identity. An identity +Through the Blockstack Browser application you can create an identity. An identity represents you as you interact with others through DApps. The Blockstack Browser is itself, a simple DApp. It allows you to: diff --git a/_browser/ids-introduction.md b/_browser/ids-introduction.md index 84355423..be9e292b 100644 --- a/_browser/ids-introduction.md +++ b/_browser/ids-introduction.md @@ -142,14 +142,14 @@ not accessible by anyone. The system prompts you for an email address. This email can be one you entered previously or an entirely new one. Blockstack doesn't store this - address; it is used during your current Blockstack browser interaction to communicate + address; it is used during your current Blockstack Browser interaction to communicate important information with you. 5. Enter an email and press **Next**. The system prompts you for a password and its confirmation. This password can be one you entered previously or an entirely new one. Write this password - down. You can use the password during your current Blockstack browser + down. You can use the password during your current Blockstack Browser interaction to reveal your keychain or change your password. Blockstack does not store this information past the session. @@ -179,7 +179,7 @@ not accessible by anyone. The system prompts you for an email address. This email can be one you entered previously or an entirely new one. Blockstack doesn't store this - address; it is used during your current Blockstack browser interaction to + address; it is used during your current Blockstack Browser interaction to communicate important information with you. 5. Enter an email and press **Next**. diff --git a/_develop/add_auth.md b/_develop/add_auth.md index 7d0f20f6..c9d6f731 100644 --- a/_develop/add_auth.md +++ b/_develop/add_auth.md @@ -41,7 +41,7 @@ When your app wants to start the sign in process, typically when the user clicks a **Sign in with Blockstack** button, your app will call the `UserSession.redirectToSignIn`. This creates an ephemeral transit key, stores it in the web browser's `localStorage`. Then, the function is used to create an authentication request token. The Blockstack Browser -redirects the user to the Blockstack browser to approve the sign in request. +redirects the user to the Blockstack Browser to approve the sign in request. When a user approves a sign in request, the Blockstack Browser returns a signed `authResponse` token to the `redirectURI` specified in `UserSession.redirectToSignIn`. diff --git a/_develop/overview_auth.md b/_develop/overview_auth.md index d2b92a9d..66746518 100644 --- a/_develop/overview_auth.md +++ b/_develop/overview_auth.md @@ -123,7 +123,7 @@ transit private key signs the app authentication request. The identity address private key is derived from the user's keychain phrase and is the private key of the Blockstack ID that the user chooses to use to sign in to the app. It is a secret owned by the user and never leaves the user's -instance of the Blockstack browser. +instance of the Blockstack Browser. This private key signs the authentication response token for an app to indicate that the user approves sign in to that app. @@ -134,7 +134,7 @@ user's identity address private key using the `domain_name` as input. It is deterministic in that for a given Blockstack ID and `domain_name`, the same private key is generated each time. -The app private key is securely shared with the app on each authentication, encrypted by the Blockstack browser with the transit public key. +The app private key is securely shared with the app on each authentication, encrypted by the Blockstack Browser with the transit public key. ## JSON Web Token signatures diff --git a/_develop/zero_to_dapp_3.md b/_develop/zero_to_dapp_3.md index 77273acc..b5cd7893 100644 --- a/_develop/zero_to_dapp_3.md +++ b/_develop/zero_to_dapp_3.md @@ -102,7 +102,7 @@ signed into the DApp previously. If not, it opens the `Landing.js` page. This page offers the user an opportunity to **Sign in to Blockstack**. Clicking the button ends up calling the `redirectToSignIn()` method which generates an -authentication request and redirects the user to the Blockstack browser to +authentication request and redirects the user to the Blockstack Browser to approve the sign in request. The actual Blockstack sign-in dialog depends on whether the user already has an existing session in the Blockstack Browser. diff --git a/_develop/zero_to_dapp_3_win.md b/_develop/zero_to_dapp_3_win.md index 43eb6455..852305c3 100644 --- a/_develop/zero_to_dapp_3_win.md +++ b/_develop/zero_to_dapp_3_win.md @@ -102,7 +102,7 @@ signed into the DApp previously. If not, it opens the `Landing.js` page. This page offers the user an opportunity to **Sign in to Blockstack**. Clicking the button ends up calling the `redirectToSignIn()` method which generates an -authentication request and redirects the user to the Blockstack browser to +authentication request and redirects the user to the Blockstack Browser to approve the sign in request. The actual Blockstack sign-in dialog depends on whether the user already has an existing session in the Blockstack Browser. diff --git a/_ios/tutorial.md b/_ios/tutorial.md index bae38e4b..0e06726b 100644 --- a/_ios/tutorial.md +++ b/_ios/tutorial.md @@ -225,7 +225,7 @@ In this section, you build an initial React.js application called ### Add a redirect end point to your application -When a user opens the webapp from the Blockstack browser on an iOS phone, +When a user opens the webapp from the Blockstack Browser on an iOS phone, you want the web app to redirect the user to your iOS application. The work you do here will allow it. diff --git a/overview_auth.md b/overview_auth.md index 63fd2d00..228b0948 100644 --- a/overview_auth.md +++ b/overview_auth.md @@ -125,7 +125,7 @@ transit private key signs the app authentication request. The identity address private key is derived from the user's keychain phrase and is the private key of the Blockstack ID that the user chooses to use to sign in to the app. It is a secret owned by the user and never leaves the user's -instance of the Blockstack browser. This private key signs the authentication +instance of the Blockstack Browser. This private key signs the authentication response token for an app to indicate that the user approves sign in to that app. @@ -135,7 +135,7 @@ The app private key is an app-specific private key that is generated from the user's identity address private key using the `domain_name` as input. It is deterministic in that for a given Blockstack ID and `domain_name`, the same private key will be generated each time. The app private key is securely shared -with the app on each authentication, encrypted by the Blockstack browser with +with the app on each authentication, encrypted by the Blockstack Browser with the transit public key. ## Scopes @@ -271,7 +271,7 @@ method of [blockstack.js](https://github.com/blockstack/blockstack.js). This creates an ephemeral transit key, stores it in the web browser's `localStorage`, uses it to create an authentication request token and finally -redirects the user to the Blockstack browser to approve the sign in request. +redirects the user to the Blockstack Browser to approve the sign in request. ##### Handling an authentication response