Summary

Adding context

README.md

@@ -15,15 +15,15 @@ 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)
 
 4. [Fork](https://github.com/riosengineer/Bicepify/fork) this repository so you have a copy to lab with our examples
 
 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
 

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.