Merge pull request #107499 from PatAltimore/patricka-blockchain-tiers

PRMerger12 · web-flow · commit f622bc53fdda · 2020-03-12T11:24:19.000-07:00
Clarify pricing tier scenarios
diff --git a/articles/blockchain/service/create-member-cli.md b/articles/blockchain/service/create-member-cli.md
@@ -1,9 +1,9 @@
 ---
 title: Create an Azure Blockchain Service member - Azure CLI
 description: Create an Azure Blockchain Service member for a blockchain consortium using the Azure CLI.
-ms.date: 01/23/2020
+ms.date: 03/12/2020
 ms.topic: quickstart
-ms.reviewer: janders
+ms.reviewer: ravastra
 #Customer intent: As a network operator, I want use Azure Blockchain Service so that I can create a blockchain member on Azure
 ---
 
@@ -54,7 +54,7 @@ az resource create \
 | **password** | The password for the member's default transaction node. Use the password for basic authentication when connecting to blockchain member's default transaction node public endpoint.
 | **consortium** | Name of the consortium to join or create. For more information on consortia, see [Azure Blockchain Service consortium](consortium.md).
 | **consortiumAccountPassword** | The consortium account password is also known as the member account password. The member account password is used to encrypt the private key for the Ethereum account that is created for your member. You use the member account and member account password for consortium management.
-| **skuName** | Tier type. Use S0 for Standard and B0 for Basic.
+| **skuName** | Tier type. Use S0 for Standard and B0 for Basic. Use the *Basic* tier for development, testing, and proof of concepts. Use the *Standard* tier for production grade deployments.
 
 It takes about 10 minutes to create the blockchain member and supporting resources.
 
diff --git a/articles/blockchain/service/create-member.md b/articles/blockchain/service/create-member.md
@@ -1,9 +1,9 @@
 ---
 title: Create an Azure Blockchain Service member - Azure portal
 description: Create an Azure Blockchain Service member for a blockchain consortium using the Azure portal.
-ms.date: 01/23/2020
+ms.date: 03/12/2020
 ms.topic: quickstart
-ms.reviewer: janders
+ms.reviewer: ravastra
 #Customer intent: As a network operator, I want use Azure Blockchain Service so that I can create a managed ledger on Azure.
 ---
 
@@ -32,7 +32,7 @@ An Azure Blockchain Service member is a blockchain node in a private consortium
     Consortium | For a new consortium, enter a unique name. If joining a consortium through an invite, choose the consortium you are joining. For more information on consortia, see [Azure Blockchain Service consortium](consortium.md).
     Name | Choose a unique name for the Azure Blockchain Service member. The blockchain member name can only contain lowercase letters and numbers. The first character must be a letter. The value must be between 2 and 20 characters long.
     Member account password | The member account password is used to encrypt the private key for the Ethereum account that is created for your member. You use the member account and member account password for consortium management.
-    Pricing | The node configuration and cost for your new service. Select the **Change** link to choose between **Standard** and **Basic** tiers.
+    Pricing | The node configuration and cost for your new service. Select the **Change** link to choose between **Standard** and **Basic** tiers. Use the *Basic* tier is for development, testing, and proof of concepts. Use the *Standard* tier for production grade deployments.
     Node password | The password for the member's default transaction node. Use the password for basic authentication when connecting to blockchain member's default transaction node public endpoint.
 
 1. Select **Review + create** to validate your settings. Select **Create** to provision the service. Provisioning takes about 10 minutes.
diff --git a/articles/blockchain/service/overview.md b/articles/blockchain/service/overview.md
@@ -1,9 +1,9 @@
 ---
 title: Azure Blockchain Service overview
 description: Overview of Azure Blockchain Service
-ms.date: 11/21/2019
+ms.date: 03/12/2020
 ms.topic: overview
-ms.reviewer: janders
+ms.reviewer: ravastra
 #Customer intent: As a network operator or developer, I want to understand how I can use Azure Blockchain Service to build and manage consortium blockchain networks on Azure
 ---
 
@@ -25,7 +25,7 @@ Deploying Azure Blockchain Service is done through the Azure portal, Azure CLI,
 
 ### Performance and service tiers
 
-Azure Blockchain Service offers two service tiers: *Basic* and *Standard*. Each tier offers different performance and capabilities to support lightweight development and test workloads up to massively scaled production blockchain deployments. Both tiers include at least one transaction node, and one validator node (Basic) or two validator nodes (Standard).
+Azure Blockchain Service offers two service tiers: *Basic* and *Standard*. Each tier offers different performance and capabilities to support lightweight development and test workloads up to massively scaled production blockchain deployments. Use the *Basic* tier for development, testing, and proof of concepts. Use the *Standard* tier for production grade deployments. Both tiers include at least one transaction node, and one validator node (Basic) or two validator nodes (Standard). 
 
 ![Pricing tiers](./media/overview/pricing-tiers.png)
 
diff --git a/articles/blockchain/workbench/overview.md b/articles/blockchain/workbench/overview.md
@@ -24,7 +24,7 @@ Azure Blockchain Workbench provides a web application and REST APIs for managing
 
 You can use the Blockchain Workbench REST APIs and message-based APIs to integrate with existing systems. The APIs provide an interface to allow for replacing or using multiple distributed ledger technologies, storage, and database offerings.
 
-Blockchain Workbench can transform messages sent to its message-based API to build transactions in a format expected by that blockchain’s native API.  Workbench can sign and route transactions to the appropriate blockchain. 
+Blockchain Workbench can transform messages sent to its message-based API to build transactions in a format expected by that blockchain's native API.  Workbench can sign and route transactions to the appropriate blockchain. 
 
 Workbench automatically delivers events to Service Bus and Event Grid to send messages to downstream consumers. Developers can integrate with either of these messaging systems to drive transactions and to look at results.
 
