Skip to content

Commit cd5d443

Browse files
committed
fixing a typo
1 parent 280cffc commit cd5d443

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/search/search-create-service-portal.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,9 @@ If you have more than one subscription, choose one that also has data or file st
4242

4343
A resource group is required and is useful for managing resources all-up, including cost management. A resource group can consist of one service, or multiple services used together. For example, if you are using Azure Search to index an Azure Cosmos DB database, you could make both services part of the same resource group for management purposes.
4444

45-
If you aren't combining resources into a single group, or if existing resource groups are filled with resources used in unrelated solutions, create a new resource group just for your Azure Search resource.
45+
If you aren't combining resources into a single group, or if existing resource groups are filled with resources used in unrelated solutions, create a new resource group just for your Azure Search resource.
46+
47+
As you use the service, you can track current and projected costs all-up (as shown in the screenshot) or scroll down to view charges for individual resources.
4648

4749
![Manage costs at the resource group level](./media/search-create-service-portal/resource-group-cost-management.png "Manage costs at the resource group level")
4850

@@ -62,7 +64,7 @@ Service name requirements:
6264
* No consecutive dashes ("--") anywhere
6365

6466
> [!TIP]
65-
> If you think you'll be using multiple services, we recommend including the region (or location) in the service name as a naming convention. Services within the same region can exchange data at no charge, so if Azure Search is in West US, and you have other services also in West US, a name like `mysearchservice-westus` can save you a trip to the properties page when combing resources into a resource group.
67+
> If you think you'll be using multiple services, we recommend including the region (or location) in the service name as a naming convention. Services within the same region can exchange data at no charge, so if Azure Search is in West US, and you have other services also in West US, a name like `mysearchservice-westus` can save you a trip to the properties page when deciding how to combine or attach resources.
6668
6769
## Select a location
6870

0 commit comments

Comments
 (0)