Skip to content

Commit d3aa2f9

Browse files
authored
Update service-fabric-concept-resource-model.md
1 parent 9ce80f2 commit d3aa2f9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/service-fabric/service-fabric-concept-resource-model.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.custom: sfrev
88

99
# Service Fabric application resource model
1010

11-
You have multiple options for deploying Service Fabric applications on your Service Fabric cluster. We recommend using Azure Resource Manager. If you use Resource Manager, you can describe applications and services in JSON, and then deploy them in the same Resource Manager template as your cluster. Unlike using PowerShell or Azure CLI to deploy and manage applications, if you use Resource Manager, you don't have to wait for the cluster to be ready; application registration, provisioning, and deployment can all happen in one step. Using Resource Manager is the best way to manage the application life cycle in your cluster. For more information, see [Best practices: Infrastructure as code](service-fabric-best-practices-infrastructure-as-code.md#azure-service-fabric-resources).
11+
You have multiple options for deploying Azure Service Fabric applications on your Service Fabric cluster. We recommend using Azure Resource Manager. If you use Resource Manager, you can describe applications and services in JSON, and then deploy them in the same Resource Manager template as your cluster. Unlike using PowerShell or Azure CLI to deploy and manage applications, if you use Resource Manager, you don't have to wait for the cluster to be ready; application registration, provisioning, and deployment can all happen in one step. Using Resource Manager is the best way to manage the application life cycle in your cluster. For more information, see [Best practices: Infrastructure as code](service-fabric-best-practices-infrastructure-as-code.md#azure-service-fabric-resources).
1212

1313
Managing your applications as resources in Resource Manager can help you gain improvements in these areas:
1414

@@ -33,7 +33,7 @@ The high-level steps you take to deploy an application and its services by using
3333

3434
For more information, view [Package an application](service-fabric-package-apps.md#create-an-sfpkg).
3535

36-
Then, you create a Resource Manager template, update the parameters file with application details, and then deploy the template on the Service Fabric cluster. Explore [samples](https://github.com/Azure-Samples/service-fabric-dotnet-quickstart/tree/master/ARM).
36+
Then, you create a Resource Manager template, update the parameters file with application details, and deploy the template on the Service Fabric cluster. [Explore samples](https://github.com/Azure-Samples/service-fabric-dotnet-quickstart/tree/master/ARM).
3737

3838
### Create a storage account
3939

@@ -180,7 +180,7 @@ Get information about the application resource model:
180180
* [Model an application in Service Fabric](service-fabric-application-model.md)
181181
* [Service Fabric application and service manifests](service-fabric-application-and-service-manifests.md)
182182
* [Best practices: Infrastructure as code](service-fabric-best-practices-infrastructure-as-code.md#azure-service-fabric-resources)
183-
* [Manage applications and services as Azure Resources](service-fabric-best-practices-infrastructure-as-code.md)
183+
* [Manage applications and services as Azure resources](service-fabric-best-practices-infrastructure-as-code.md)
184184

185185

186186
<!--Image references-->

0 commit comments

Comments
 (0)