Merge branch 'main' of github.adegeo:dotnet/docs into adegeo-27135-arm

Author: adegeo

.github/ISSUE_TEMPLATE/breaking-change.yml

@@ -18,9 +18,6 @@ body:
       label: Version
       description: What version of .NET introduced the breaking change?
       options:
-        - .NET 6 RC 1
-        - .NET 6 RC 2
-        - .NET 6 GA
         - .NET 7 Preview 1
         - .NET 7 Preview 2
         - .NET 7 Preview 3

.github/workflows/whats-new.yml

@@ -16,14 +16,16 @@ on:
 
 env:
   DOTNET_VERSION: '5.0.301' # set this to the dot net version to use
-  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
 # A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
   # This workflow contains a single job called "create-what-is-new"
   create-what-is-new:
     # The type of runner that the job will run on
     runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
 
     # Steps represent a sequence of tasks that will be executed as part of the job
     steps:
@@ -38,7 +40,7 @@ jobs:
       - name: 'Print manual run reason'
         if: ${{ github.event_name == 'workflow_dispatch' }}
         run: |
-          echo 'Reason: ${{ github.event.inputs.reason }}'
+          echo "Reason: ${{ github.event.inputs.reason }}"
 
       # Print dotnet info
       - name: Display .NET info
@@ -60,7 +62,7 @@ jobs:
 
       # Create the PR for the new article
       - name: create-pull-request
-        uses: peter-evans/create-pull-request@v3.10.0
+        uses: peter-evans/create-pull-request@v3.11.0
         with:
           title: 'What''s new article'
           commit-message: 'Bot 🤖 generated "What''s new article"'

.openpublishing.redirection.json

@@ -89,7 +89,7 @@ The final statement in this method defines the endpoints that ASP.NET Core is li
 
 Technologies for bundling assets like CSS stylesheets and JavaScript files have evolved significantly, with other technologies providing quickly evolving tools and techniques for managing these resources.  To this end, we recommend using a Node command-line tool such as Grunt / Gulp / WebPack to package your static assets.
 
-The Grunt, Gulp, and WebPack command-line tools and their associated configurations can be added to your application and ASP.NET Core will quietly ignore those files during the application build process.  You can add a call to run their tasks by adding a `Target` inside your project file with syntax similar to the following that would trigger a gulp script and the `min` target inside that script
+The Grunt, Gulp, and WebPack command-line tools and their associated configurations can be added to your application and ASP.NET Core will quietly ignore those files during the application build process.  You can add a call to run their tasks by adding a `Target` inside your project file with syntax similar to the following that would trigger a gulp script and the `min` target inside that script:
 
 ```xml
 <Target Name="MyPreCompileTarget" BeforeTargets="Build">

docs/architecture/blazor-for-web-forms-developers/app-startup.md

@@ -19,7 +19,7 @@ Whether you prefer a full and powerful IDE or a lightweight and agile editor, Mi
 
 **Visual Studio Code and Docker CLI**. If you prefer a lightweight and cross-platform editor that supports any development language, you can use Visual Studio Code and the Docker CLI. This IDE is a cross-platform development approach for macOS, Linux, and Windows. Additionally, Visual Studio Code supports extensions for Docker such as IntelliSense for Dockerfiles and shortcut tasks to run Docker commands from the editor.
 
-By installing [Docker Desktop Community Edition (CE)](https://hub.docker.com/search/?type=edition&offering=community), you can use a single Docker CLI to build apps for both Windows and Linux.
+By installing [Docker Desktop](https://hub.docker.com/search/?type=edition&offering=community), you can use a single Docker CLI to build apps for both Windows and Linux.
 
 ### Additional resources
 
@@ -29,10 +29,10 @@ By installing [Docker Desktop Community Edition (CE)](https://hub.docker.com/sea
 - **Visual Studio Code**. Official site. \
   <https://code.visualstudio.com/download>
 
-- **Docker Desktop for Windows Community Edition (CE)** \
+- **Docker Desktop for Windows** \
   [https://hub.docker.com/editions/community/docker-ce-desktop-windows](https://hub.docker.com/editions/community/docker-ce-desktop-windows)
 
-- **Docker Desktop for Mac Community Edition (CE)** \
+- **Docker Desktop for Mac** \
   [https://hub.docker.com/editions/community/docker-ce-desktop-mac](https://hub.docker.com/editions/community/docker-ce-desktop-mac)
 
 ## .NET languages and frameworks for Docker containers

docs/architecture/microservices/docker-application-development-process/index.md

@@ -7,8 +7,6 @@ ms.date: 11/13/2020
 
 # Architectural differences between ASP.NET MVC and ASP.NET Core
 
-[!INCLUDE [book-preview](../../../includes/book-preview.md)]
-
 There are many architectural differences between ASP.NET MVC on .NET Framework and ASP.NET Core. It's important to have a broad understanding of these differences as teams evaluate the work involved in porting their ASP.NET MVC apps to ASP.NET Core. This chapter looks at each of the ways in which ASP.NET Core differs substantially from ASP.NET MVC.
 
 ## Breaking changes

docs/architecture/microservices/multi-container-microservice-net-applications/media/data-driven-crud-microservice/swagger-metadata-eshoponcontainers-catalog-microservice.png

@@ -11,7 +11,7 @@ The largest consideration for most organizations when choosing which version of
 
 Most customers looking to migrate a large .NET Framework app to .NET Core today are probably looking for a stable destination, given that they haven't already made the move to an earlier version of .NET Core. In this case, the best .NET Core version to target for the migration is .NET Core 3.1, which is an LTS version. Support for .NET Core 3.1 ends in December 2022. The latest available LTS release is .NET 6.
 
-Updating from .NET Core 3.1 to .NET 5+ requires much less effort than porting from .NET Framework to .NET Core. For this reason, the recommendation for most customers is to upgrade to .NET Core 3.1 first.
+Updating from .NET Core 3.1 to .NET 6+ requires much less effort than porting from .NET Framework to .NET Core. For this reason, the recommendation for most customers is to upgrade to .NET Core 3.1 first.
 
 This book assumes .NET Framework apps will be upgraded to .NET Core 3.1.
 

docs/architecture/porting-existing-aspnet-apps/architectural-differences.md

@@ -7,8 +7,6 @@ ms.date: 11/13/2020
 
 # Deployment scenarios when migrating to ASP.NET Core
 
-[!INCLUDE [book-preview](../../../includes/book-preview.md)]
-
 Existing ASP.NET MVC and Web API apps run on IIS and Windows. Large apps may require a phased or side-by-side approach when porting to ASP.NET Core. In previous chapters, you learned a number of strategies for migrating large .NET Framework apps to ASP.NET Core in phases. In this chapter, you will see how different deployment scenarios can be achieved when there is a need to maintain the original app in production while migrating portions of it.
 
 ## Split a large web app

docs/architecture/porting-existing-aspnet-apps/choose-net-core-version.md

@@ -7,9 +7,7 @@ ms.date: 11/13/2020
 
 # Example migration of eShop to ASP.NET Core
 
-[!INCLUDE [book-preview](../../../includes/book-preview.md)]
-
-In this chapter, you'll see how to migrate a .NET Framework app to .NET Core. The chapter examines a sample online store app written for ASP.NET 5. The app will use many of the concepts and tools described earlier in this book. You'll find the starting point app in the [*eShopModernizing* GitHub repository](https://github.com/dotnet-architecture/eShopModernizing). There are several different starting point apps. This chapter focuses on the *eShopLegacyMVCSolution*.
+In this chapter, you'll see how to migrate a .NET Framework app to .NET Core. The chapter examines a sample online store app written for ASP.NET MVC 5. The app will use many of the concepts and tools described earlier in this book. You'll find the starting point app in the [*eShopModernizing* GitHub repository](https://github.com/dotnet-architecture/eShopModernizing). There are several different starting point apps. This chapter focuses on the *eShopLegacyMVCSolution*.
 
 The initial version of the project is shown in Figure 4-1. It's a fairly standard ASP.NET MVC 5 app.