Skip to content

Commit a9cdafd

Browse files
author
ecfan
committed
Updates per feedback
1 parent b21cb24 commit a9cdafd

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/logic-apps/add-run-powershell-scripts.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -339,16 +339,16 @@ When you're done, your complete logic app file structure appears similar to the
339339
```text
340340
MyLogicApp
341341
-- execute_powershell_script.ps1
342-
- host.json
342+
-- mytestworkflow.json
343343
- Modules
344344
-- MyPrivateModule
345345
--- MyPrivateModule.psd1
346346
--- MyPrivateModule.psm1
347347
-- MyPrivateModule2
348348
--- MyPrivateModule2.psd1
349349
--- MyPrivateModule2.psm1
350-
- mytestworkflow.json
351350
- requirements.psd1
351+
- host.json
352352
```
353353

354354
## Compilation errors
@@ -363,7 +363,7 @@ Make sure that you use the **Push-WorkflowOutput** cmdlet.
363363

364364
### Execute PowerShell Code action fails: "The term '{some-text}' is not recognized..."
365365

366-
If you incorrectly reference a public module in the **requirements.psd1** file or when your private module doesn't exist in the following path: **C:\home\site\wwwroot\Modules\{moduleName}, you get the following error:
366+
If you incorrectly reference a public module in the **requirements.psd1** file or when your private module doesn't exist in the following path: **C:\home\site\wwwroot\Modules\{module-name}**, you get the following error:
367367

368368
**The term '{some-text}' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name or if a path was included, verify the path is correct and try again.**
369369

0 commit comments

Comments
 (0)