Skip to content

Commit bd8dee8

Browse files
committed
fixes after review comments
1 parent 5b1f744 commit bd8dee8

File tree

6 files changed

+10
-10
lines changed

6 files changed

+10
-10
lines changed

articles/iot-central/core/howto-create-and-manage-applications-csp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ To create an Azure IoT Central application, select **Build** in the left menu. C
3535

3636
![Create Application Page for CSPs](media/howto-create-application-csp/image4-1.png)
3737

38-
![Create Application Page for CSPs Billing Inf0](media/howto-create-application-csp/image4-2.png)
38+
![Create Application Page for CSPs Billing Info](media/howto-create-application-csp/image4-2.png)
3939

4040
## Pricing plan
4141

articles/iot-central/core/howto-manage-iot-central-from-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ These commands first create a resource group in the east US location for the app
5151
| location | By default, this command uses the location from the resource group. Currently, you can create an IoT Central application in the **United States**, **Australia**, **Asia Pacific**, or in the **Europe** locations. |
5252
| name | The name of the application in the Azure portal. |
5353
| subdomain | The subdomain in the URL of the application. In the example, the application URL is https://mysubdomain.azureiotcentral.com. |
54-
| sku | Currently, you can use values as either **ST1** or **ST2**. See [Azure IoT Central pricing](https://azure.microsoft.com/pricing/details/iot-central/). |
54+
| sku | Currently, you can use either **ST1** or **ST2**. See [Azure IoT Central pricing](https://azure.microsoft.com/pricing/details/iot-central/). |
5555
| template | The application template to use. For more information, see the following table: |
5656
| display-name | The name of the application as displayed in the UI. |
5757

articles/iot-central/core/howto-manage-iot-central-from-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ The script first creates a resource group in the east US location for the applic
6464
|Location |By default, this cmdlet uses the location from the resource group. Currently, you can create an IoT Central application in the **United States**, **Australia**, **Asia Pacific**, or in the **Europe** locations. |
6565
|Name |The name of the application in the Azure portal. |
6666
|Subdomain |The subdomain in the URL of the application. In the example, the application URL is https://mysubdomain.azureiotcentral.com. |
67-
|Sku |Currently, you can use values as either **ST1** or **ST2**. See [Azure IoT Central pricing](https://azure.microsoft.com/pricing/details/iot-central/). |
67+
|Sku |Currently, you can use either **ST1** or **ST2**. See [Azure IoT Central pricing](https://azure.microsoft.com/pricing/details/iot-central/). |
6868
|Template | The application template to use. For more information, see the following table: |
6969
|DisplayName |The name of the application as displayed in the UI. |
7070

articles/iot-central/core/howto-view-bill.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ manager: philmea
1414

1515
This article describes how, as an administrator, you can manage your bill in Azure IoT Central application in the administration section. You will learn how you can move your application from the free pricing plan to a standard pricing plan, and also how to upgrade or downgrade your pricing plan.
1616

17-
To access and use the **Administration** section, you must be in the *Administrator* role have a *custom user role* that allows you to view billing for an Azure IoT Central application. If you create an Azure IoT Central application, you're automatically assigned to the **Administrator** role for that application.
17+
To access and use the **Administration** section, you must be in the *Administrator* role or have a *custom user role* that allows you to view billing for an Azure IoT Central application. If you create an Azure IoT Central application, you're automatically assigned to the **Administrator** role for that application.
1818

1919
## Move from free to standard pricing plan
2020

@@ -32,9 +32,9 @@ To complete this self-service process, follow these steps:
3232

3333
![Convert trial](media/howto-administer/convert.png)
3434

35-
1. Select the appropriate Azure Active Directory, and then the Azure subscription to use for your paid application.
35+
1. Select the appropriate Azure Active Directory, and then the Azure subscription to use for your application that uses a paid plan.
3636

37-
1. After you select **Convert**, your application is now a paid application and you start getting billed.
37+
1. After you select **Convert**, your application now uses a paid plan and you start getting billed.
3838

3939
> [!Note]
4040
> By default, you are converted to a *Standard 2* pricing plan.

articles/iot-central/preview/howto-export-data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Now that you have a destination to export data to, follow these steps to set up
8282
4. In the drop-down list box, select your **Event Hubs namespace**, **Service Bus namespace**, **Storage Account namespace**, or **Enter a connection string**.
8383

8484
- You only see Storage Accounts, Event Hubs namespaces, and Service Bus namespaces in the same subscription as your IoT Central application. If you want to export to a destination outside of this subscription, choose **Enter a connection string** and see step 5.
85-
- For apps created using the free pricing plan, the only way to configure continuous data export is through a connection string. Apps on the free pricing plan don't have an associated Azure subscription.o
85+
- For apps created using the free pricing plan, the only way to configure continuous data export is through a connection string. Apps on the free pricing plan don't have an associated Azure subscription.
8686

8787
![Create new Event Hub](media/howto-export-data/export-eh.png)
8888

articles/iot-central/preview/howto-view-bill.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ manager: philmea
1616

1717
This article describes how, as an administrator, you can manage your bill in Azure IoT Central application in the administration section. You will learn how you can move your application from the free pricing plan to a standard pricing plan, and also how to upgrade or downgrade your pricing plan.
1818

19-
To access and use the **Administration** section, you must be in the *Administrator* role have a *custom user role* that allows you to view billing for an Azure IoT Central application. If you create an Azure IoT Central application, you're automatically assigned to the **Administrator** role for that application.
19+
To access and use the **Administration** section, you must be in the *Administrator* role or have a *custom user role* that allows you to view billing for an Azure IoT Central application. If you create an Azure IoT Central application, you're automatically assigned to the **Administrator** role for that application.
2020

2121
## Move from free to standard pricing plan
2222

@@ -34,9 +34,9 @@ To complete this self-service process, follow these steps:
3434

3535
![Convert trial](media/howto-view-bill/convert.png)
3636

37-
1. Select the appropriate Azure Active Directory, and then the Azure subscription to use for your paid application.
37+
1. Select the appropriate Azure Active Directory, and then the Azure subscription to use for your application that uses a paid plan.
3838

39-
1. After you select **Convert**, your application is now a paid application and you start getting billed.
39+
1. After you select **Convert**, your application now uses a paid plan and you start getting billed.
4040

4141
> [!Note]
4242
> By default, you are converted to a *Standard 2* pricing plan.

0 commit comments

Comments
 (0)