Skip to content

Commit 240bd52

Browse files
committed
PR fixes
1 parent d5481e3 commit 240bd52

File tree

2 files changed

+1
-4
lines changed

2 files changed

+1
-4
lines changed

articles/azure-developer-cli/azd-init-workflow.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -113,9 +113,6 @@ For advanced users who want to start with a minimal setup and customize everythi
113113
azd init --minimal
114114
```
115115

116-
> [!NOTE]
117-
> You can also run `azd init` with the `--minimal` parameter to skip the workflow selection.
118-
119116
2. When prompted, enter a name for your `azd` template and press Enter.
120117

121118
```output

articles/azure-developer-cli/compose-generate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ This command generates the corresponding Bicep files in the `infra` folder of yo
3737

3838
## Managing updates with Bicep generation
3939

40-
When you run the `azd infra gen` command, you exit the `azd compose` workflow and the simplified init process. From this point on, any changes you make to the generated Bicep files are no longer tracked by `azd compose`. If you modify the Bicep files and later run `azd infra synth` (or `azd infra gen`) again, your manual changes will be overwritten by the newly generated code.
40+
When you run the `azd infra gen` command, you exit the `azd compose` workflow and the simplified init process. From this point on, any changes you make to the generated Bicep files are no longer tracked by `azd compose`. If you modify the Bicep files and later run `azd infra gen` again, your manual changes will be overwritten by the newly generated code.
4141

4242
Here's how a typical workflow might look:
4343

0 commit comments

Comments
 (0)