Merge pull request #49351 from alexwolfmsft/azd-freshness

Freshness pass

Author: prmerger-automator[bot]

learn-pr/azure/build-first-azd-template/includes/4-create-infrastructure.md

@@ -2,13 +2,14 @@ The Azure Developer CLI (`azd`) can provision resources in Azure using infrastru
 
 In this unit, you'll add Bicep code to your template to provision the necessary resources for your app. Previous knowledge of Bicep isn't required to complete this module. However, if you plan to work with `azd` templates extensively, it's a good idea to become familiar with at least the basics of Bicep or Terraform. Learn more about Bicep on the [Fundamentals of Bicep](/training/paths/fundamentals-bicep/) training path.
 
-The Bicep or Terraform files for your template live in the `infra` folder. The Bicep starter template you selected generated three files as a starting point:
+The Bicep or Terraform files for your template live in the `infra` folder. The `infra` folder of the Bicep starter template you selected contains the following components as a starting point:
 
 * `main.bicep` - Acts as the main entrypoint for Bicep execution and is used to define the resources that will be provisioned in Azure. The `main.bicep` file can also reference other Bicep modules (files) that allow you to extract out resource definitions into more granular, reusable files.
 * `abbreviations.json` - A JSON file that provides many helpful naming abbreviations. This file is loaded into the `main.bicep` file during execution and provides a set of consistent, logical naming prefixes for different Azure resources.
 * `main.parameters.json` - A JSON file that defines default values for important template parameters, such as the default Azure location or the environment name.
+* `core` - A subfolder that includes a variety of reusable Bicep templates you can use to generate common Azure resources by simply passing in configuration parameters.
 
-You can define and provision the required Azure resources for your app by updating the `main.bicep` file and creating more Bicep files. `Main.bicep` generally orchestrates the execution of other Bicep modules by passing parameters between them. For this example, you'll create an additional Bicep module to define the Azure App Service that will host your application.
+You can define and provision the required Azure resources for your app by updating the `main.bicep` file and creating custom Bicep files, or leveraging the templates in the `core` folder. `Main.bicep` generally orchestrates the execution of other Bicep modules by passing parameters between them. For this example, you'll create an additional minimal Bicep module to define the Azure App Service that will host your application.
 
 1. Inside of the `infra` folder of your template, create a new file called `app.bicep`.
 
@@ -46,7 +47,7 @@ You can define and provision the required Azure resources for your app by updati
       properties: {
         serverFarmId: appServicePlan.id
         siteConfig: {
-          linuxFxVersion: 'DOTNETCORE|6.0'
+          linuxFxVersion: 'DOTNETCORE|9.0'
         }
       }
         // Tag used to reference the service in the Azure.yaml file

learn-pr/azure/introduction-to-azure-developer-cli/includes/2-what-is-azure-developer-cli.md

@@ -1,4 +1,4 @@
-The Azure Developer CLI (`azd`) is an open-source command-line tool that reduces the time it takes for you to get your application from a local development environment to Azure. `azd` provides best practice, developer-friendly commands that map to key stages in your workflow, whether you’re working in the terminal, your preferred local development environment (for example, editor or integrated development environment (IDE)), or CI/CD (continuous integration/continuous deployment) pipelines.
+The Azure Developer CLI (`azd`) is an open-source command-line tool that reduces the time it takes for you to get your application from a local development environment to Azure. `azd` provides best practice, developer-friendly commands that map to key stages in your workflow, whether you're working in the terminal, your preferred local development environment (for example, editor or integrated development environment (IDE)), or CI/CD (continuous integration/continuous deployment) pipelines.
 
 You can install `azd` locally on your machine or use it in other environments such as GitHub Codespaces. Visit the [install page](/azure/developer/azure-developer-cli/install-azd) for a full list of supported installation methods and environments. For example, to install `azd` locally on Windows or Mac, you could use one of the following commands:
 
@@ -14,6 +14,8 @@ winget install microsoft.azd
 brew tap azure/azd && brew install azd
 ```
 
+---
+
 The Azure Developer CLI relies on extensible templates that include everything you need to get an application up and running on Azure. These templates include reusable infrastructure as code (IaC) assets written in Bicep or Terraform and proof-of-concept application code that can be replaced with your own app code. You can search for an existing template that uses a similar technology stack to your local app as a starting point. Many of the available templates are listed in the [awesome-azd template library](https://azure.github.io/awesome-azd/). The combination of `azd` commands and templates allows you to streamline many common development workflow stages and tasks:
 
 - **Build and package application code** - `azd` autodetects the language or framework of your application and builds and packages the code for deployment.