From a3088f046cf344057079389d56927395ecba9df0 Mon Sep 17 00:00:00 2001
From: Dan Rios <36534747+riosengineer@users.noreply.github.com>
Date: Tue, 21 Nov 2023 09:49:05 +0000
Subject: [PATCH] Summary

Adding context
---
 README.md                             | 4 ++--
 bicep-examples/dependencies/README.md | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index b20e8d3..4d803c2 100644
--- a/README.md
+++ b/README.md
@@ -15,7 +15,7 @@ If you find this repository useful, please save the repository by hitting the 
 
 2. Install the [Bicep extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-bicep)
 
-3. To test, deploy (resources to Azure) and debug Bicep files:
+3. To deploy Bicep files:
     - Install [AzureCLI](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?tabs=azure-cli) **[recommended method]** or
     - [Azure PowerShell](https://learn.microsoft.com/en-us/powershell/azure/install-azure-powershell?view=azps-10.3.0) (must install [Bicep manually](https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/install#install-manually) if you want to use with PowerShell)
 
@@ -23,7 +23,7 @@ If you find this repository useful, please save the repository by hitting the 
 
 5. In your forked repository, click the green Code and Open with VisualStudio for a quick start
 
-6. Read the README files for further information and deployment commands to test
+6. Read the README files for further information, explanations and deployment commands to test the example
 
 ## 🧪 About the project
 
diff --git a/bicep-examples/dependencies/README.md b/bicep-examples/dependencies/README.md
index c770402..09d028e 100644
--- a/bicep-examples/dependencies/README.md
+++ b/bicep-examples/dependencies/README.md
@@ -61,7 +61,7 @@ resource frontDoorProfile 'Microsoft.Cdn/profiles@2021-06-01' = {
 }
 ```
 
-For explicit dependencies, we can use the `dependsOn` property to describe explicitly which resources we want this deployment to depend on.
+For explicit dependencies, we can use the `dependsOn` property to describe explicitly which resources we want this deployment to depend on. You don't need to, and shouldn't add an implicit and explicit dependency in the same resource, it's a one or the other use case.
 
 In the case above, I don't want my Front Door deployment to start before the App service and App Plan have been deployed first, as I need them to exist for my origin backend in Front Door.