Removed references to old .NET versions

src/01. Basics/01. What Is Piranha.md

@@ -1,6 +1,6 @@
 # What Is Piranha
 
-Piranha CMS is a **lightweight**, **unobtrusive** and **cross-platform** CMS library for `.NET 6`. It can be used to add CMS functionality to an already existing application, build a new website from scratch, or even as a backend for a mobile application.
+Piranha CMS is a **lightweight**, **unobtrusive** and **cross-platform** CMS library for `.NET 8`. It can be used to add CMS functionality to an already existing application, build a new website from scratch, or even as a backend for a mobile application.
 
 Piranha CMS is designed as a totally **decoupled** CMS, meaning that you can build your application in any way you want, using any technology you want. We provide packages to give you the options whether you want to use it as an **integrated** or **headless** CMS.
 

src/01. Basics/02. Prerequisites.md

@@ -1,10 +1,10 @@
 # Prerequisites
 
-> Piranha is built on `.NET 6` which is a free, open source, cross platform version of `.NET` provided by Microsoft. You can find more information about `.NET` [here](https://dotnet.microsoft.com).
+> Piranha is built on `.NET 8` which is a free, open source, cross platform version of `.NET` provided by Microsoft. You can find more information about `.NET` [here](https://dotnet.microsoft.com).
 
-## Installing .NET Core
+## Installing .NET
 
-You can download the `.NET Core SDK` from [dotnet.microsoft.com](https://dotnet.microsoft.com/download) for Windows, Linux and MacOS. Make sure to get the latest version of the SDK for version `6`.
+You can download the `.NET SDK` from [dotnet.microsoft.com](https://dotnet.microsoft.com/download) for Windows, Linux and MacOS. Make sure to get the latest version of the SDK for version `8`.
 
 ## Choosing An Editor
 

src/01. Basics/03. Project Templates.md

@@ -8,7 +8,7 @@ If you want to add Piranha into an application, it's still a good start to creat
 
 ## Installing the Templates
 
-Project Templates for .NET Core are installed from the **CLI** using the `dotnet new` command. If you're updating an already installed template, make sure you specify the version you want to install.
+Project Templates for .NET are installed from the **CLI** using the `dotnet new` command. If you're updating an already installed template, make sure you specify the version you want to install.
 
 ~~~ bash
 > dotnet new -i Piranha.Templates

src/01. Basics/04. Project Setup.md

@@ -2,11 +2,11 @@
 
 > This section shows how to setup and configure Piranha in your Application Startup and is intended for users who wants to create their application from scratch and not have this code generated by any of the available [project templates](project-templates).
 >
-> If you want more information on how to create an `ASP.NET Core` web application from Visual Studio you can find this [here](https://docs.microsoft.com/en-us/visualstudio/ide/quickstart-aspnet-core?view=vs-2019&WT.mc_id=DOP-MVP-5003834).
+> If you want more information on how to create an `ASP.NET` web application from Visual Studio you can find this [here](https://docs.microsoft.com/en-us/visualstudio/ide/quickstart-aspnet-core?view=vs-2019&WT.mc_id=DOP-MVP-5003834).
 
 ## Creating The Project
 
-As we're going to setup the application from scratch we're going to start by creating an **empty ASP.NET** application using the standard project template provided with `.NET Core`. Start by creating a new empty directory with the name you want for your project. We will name the directory `PiranhaWeb`. After this is done position yourself in the directory and execute the following command in the terminal.
+As we're going to setup the application from scratch we're going to start by creating an **empty ASP.NET** application using the standard project template provided with `.NET`. Start by creating a new empty directory with the name you want for your project. We will name the directory `PiranhaWeb`. After this is done position yourself in the directory and execute the following command in the terminal.
 
 ~~~ bash
 dotnet new web

src/01. Basics/05. Application Setup.md

@@ -4,7 +4,7 @@
 
 ## About Application Startup
 
-In `ASP.NET Core` application startup is handled in two methods, `ConfigureServices` and `Configure`. In the first method you register the different services that should be available in the `DI Container`, and in the second you perform additional setup on the registered services and configure the middleware pipeline for the application.
+In `ASP.NET` application startup is handled in two methods, `ConfigureServices` and `Configure`. In the first method you register the different services that should be available in the `DI Container`, and in the second you perform additional setup on the registered services and configure the middleware pipeline for the application.
 
 ## Template Startup
 

src/01. Basics/07. Startup Options.md

@@ -126,7 +126,7 @@ services.AddPiranha(options =>
 {
     options.UseManager(o =>
     {
-        o.JsonOptions => 
+        o.JsonOptions =>
         {
             ...
         };
@@ -170,7 +170,7 @@ Sets the name of the header the manager will use to pass along the anti forgery
 
 ### Using appsettings.json
 
-Using the [options pattern](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options) in ASP.NET Core you can also easily configure the routing options in your `appsettings.json`. Please note that this is just an example and your `appsettings.json` can have any structure you want.
+Using the [options pattern](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options) in ASP.NET you can also easily configure the routing options in your `appsettings.json`. Please note that this is just an example and your `appsettings.json` can have any structure you want.
 
 **appsettings.json**
 ~~~

src/04. Architecture/04. Databases/01. SQLite.md

@@ -1,6 +1,6 @@
 # SQLite
 
-> Please remember that if you're going to use our provided packages for ASP.NET Core Identity you will **also need need to include** the SQLite package for Identity. For more information, please refer to article about using [Identity](../authentication/identity) for Piranha.
+> Please remember that if you're going to use our provided packages for ASP.NET Identity you will **also need need to include** the SQLite package for Identity. For more information, please refer to article about using [Identity](../authentication/identity) for Piranha.
 
 ## Installation
 

src/04. Architecture/04. Databases/02. SQL Server.md

@@ -1,6 +1,6 @@
 # SQL Server
 
-> Please remember that if you're going to use our provided packages for ASP.NET Core Identity you will **also need need to include** the SQL Server package for Identity. For more information, please refer to article about using [Identity](../authentication/identity) for Piranha.
+> Please remember that if you're going to use our provided packages for ASP.NET Identity you will **also need need to include** the SQL Server package for Identity. For more information, please refer to article about using [Identity](../authentication/identity) for Piranha.
 
 Whether you're using `SQL Express`, `SQL Server` or `SQL Azure` it's the same setup. SQL Server is a high performance database intended for production usage that can handle very high workloads.
 
@@ -24,7 +24,7 @@ After you've made sure you have the package reference you need you simply specif
 }
 ~~~
 
-When you've setup your configuration string you can access it from `ConfigureServices` in your `Startup.cs`. 
+When you've setup your configuration string you can access it from `ConfigureServices` in your `Startup.cs`.
 
 ~~~ csharp
 using Piranha.Data.EF.SQLServer;

src/04. Architecture/04. Databases/03. MySQL.md

@@ -1,6 +1,6 @@
 # MySQL
 
-> Please remember that if you are going to use our provided packages for ASP.NET Core Identity you will **also need to include** the MySQL package for Identity. For more information, please refer to the article about using [Identity](../authentication/identity) for Piranha.
+> Please remember that if you are going to use our provided packages for ASP.NET Identity you will **also need to include** the MySQL package for Identity. For more information, please refer to the article about using [Identity](../authentication/identity) for Piranha.
 
 ## Installation
 

src/06. Extensions/01. Modules.md

@@ -24,8 +24,6 @@ You have two options when creating your module project. If you are going to embe
 
 If your module will only contains classes you can create it as a standard `Class Library` as you won't need the features of the Razor Class Library.
 
-Also, starting from `.NET Core 3.0` Razor Class Libraries will be dependent on having `netcoreapp3.0` as TargetFramework, but a Library can of course target `NetStandard`, so it all depends if, and where you want to be able to reuse your code.
-
 ## The IModule Interface
 
 In order to be registered in the Piranha App, all modules need to have a class that implement the `Piranha.Extend.IModule` interface.

src/08. Tutorials/01. Securing Pages.md

@@ -57,7 +57,7 @@ After this is done, you can see that when we try to access the post through our
 
 ## Adding Login Redirect
 
-The simplest way of handling the fact that we will have two different login pages is to let the manager area use the `AuthorizeAttribute` and standard redirects of the `cookie options`. Loading a secured model with the `IModelLoader` will result in an `UnathorizedException` which will in turn result in a `401` being returned by `ASP.NET Core`.
+The simplest way of handling the fact that we will have two different login pages is to let the manager area use the `AuthorizeAttribute` and standard redirects of the `cookie options`. Loading a secured model with the `IModelLoader` will result in an `UnathorizedException` which will in turn result in a `401` being returned by `ASP.NET`.
 
 Knowing this, let's add a middleware component first that listens to the result that comes back, if it is a `401` it means it's an unhandled **unauthorized** requests from one of our pages.