Skip to content

Commit 302c43b

Browse files
committed
Clarity edits
1 parent 2b8aa78 commit 302c43b

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

articles/logic-apps/logic-apps-serverless-get-started-vs.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Select **Cloud** > **Azure Resource Group**.
8282
Visual Studio prompts you to select a template.
8383
You can start with a blank, Logic App, or other template,
8484
but this example uses an Azure Quickstart Template for building
85-
a serverless app that includes a logic app and Azure function app.
85+
a serverless app that includes a logic app and a call to an Azure function.
8686

8787
To create only a logic app in Visual Studio,
8888
select the **Logic App** template. This template
@@ -94,22 +94,22 @@ Select **Cloud** > **Azure Resource Group**.
9494
select **Azure Quickstart (github/Azure/azure-quickstart-templates)**.
9595

9696
1. In the search box, enter "logic-app" as your filter,
97-
and select this serverless quickstart template:
97+
and select this serverless quickstart template and choose **OK**:
9898
**101-logic-app-and-function-app**
9999

100100
![Select Azure quickstart template](./media/logic-apps-serverless-get-started-vs/select-template.png)
101101

102-
This quickstart template creates a deployment
103-
template inside your resource group project.
104-
The template also includes a simple logic app
105-
that's triggered by an HTTP request,
106-
calls an Azure function, and returns the result
107-
as an HTTP response.
108-
102+
Visual Studio creates and opens a solution for your resource group project.
103+
The quickstart template you selected creates a deployment template
104+
named `azuredeploy.json` inside your resource group project.
105+
This deployment template includes the definition for a simple
106+
logic app that triggers on an HTTP request, calls an Azure function,
107+
and returns the result as an HTTP response.
108+
109109
![New serverless solution](./media/logic-apps-serverless-get-started-vs/create-serverless-solution.png)
110110

111111
1. Next, you must deploy your solution to Azure before you can open
112-
your logic app and review the resources for your serverless app,
112+
the deployment template and review the resources for your serverless app.
113113

114114
## Deploy your solution
115115

@@ -135,13 +135,13 @@ your function app.
135135

136136
![Provide names for your logic app and function app](./media/logic-apps-serverless-get-started-vs/logic-function-app-name-parameters.png)
137137

138-
When your solution starts deployment to your specified resource group,
138+
When Visual Studio starts deployment to your specified resource group,
139139
your solution's deployment status appears in the Visual Studio **Output** window.
140140
After deployment finishes, your logic app is live in the Azure portal.
141141

142142
## Edit logic app in Visual Studio
143143

144-
After your solution deploys to your resource group,
144+
Now that your solution is deployed to your resource group,
145145
open your logic app with the Logic App Designer
146146
so you can edit and change your logic app.
147147

@@ -167,11 +167,11 @@ and then choose **OK**.
167167
To create your Functions project and function with JavaScript, Python,
168168
F#, PowerShell, Batch, or Bash, follow the steps in the article,
169169
[Work with Azure Functions Core Tools](../azure-functions/functions-run-local.md).
170-
If you're developing your Azure function with C# within your solution,
170+
To develop your Azure function with C# inside your solution,
171171
you can use a C# class library by following the steps in the article,
172172
[Publish a .NET class library as a Function App](https://blogs.msdn.microsoft.com/appserviceteam/2017/03/16/publishing-a-net-class-library-as-a-function-app/).
173173

174-
## Build functions in Visual Studio
174+
## Deploy functions from Visual Studio
175175

176176
Your deployment template deploys any Azure functions that you have in your solution
177177
from the Git repo that's specified by variables in the `azuredeploy.json` file.

0 commit comments

Comments
 (0)