Cleanup v14 docs

Author: jemayn

14/umbraco-cms/extending/packages/README.md

@@ -45,10 +45,6 @@ Workspace Views are almost like dashboards for content nodes that are intended t
 
 This type of package can be a lot of things, and can include a number of the other package types. They are generally integrating a larger system into Umbraco. A good example could be an e-commerce package such as [Umbraco Commerce](https://docs.umbraco.com/umbraco-commerce), that includes an entire webshop module for Umbraco.
 
-## [Types of Packages](types-of-packages.md)
-
-Packages for Umbraco 10 and above are installed as NuGet packages.
-
 ## [Creating a Package](creating-a-package.md)
 
 This short tutorial will teach you how to create a package in the Umbraco backoffice. It will also give a quick overview of what a generated package will contain.

14/umbraco-cms/extending/packages/good-practice-and-defaults.md

@@ -46,7 +46,7 @@ The `/umbraco/Licenses` folder does not exist on a fresh installation of Umbraco
 
 ## Operating system considerations
 
-Umbraco (version 9 and up) is an ASP.NET Core application and can be run on multiple operating systems (Windows, Linux and macOS). When developing packages there are a few things you should be aware of for your package to run on all possible operating systems.
+Umbraco is an .NET application and can be run on multiple operating systems (Windows, Linux and macOS). When developing packages there are a few things you should be aware of for your package to run on all possible operating systems.
 
 ### Case sensitivity
 
@@ -69,7 +69,7 @@ Some folders within Umbraco will already exist for all installations. If you acc
 | Folder                 | Note                                                                                  |
 | ---------------------- | ------------------------------------------------------------------------------------- |
 | /App\_Plugins          | Uppercase `A` and `P`                                                                 |
-| /App\_Plugins/\[Ll]ang | Uppercase `L` (in Umbraco 9.3 and higher can be either uppercase `L` or lowercase `l` |
+| /App\_Plugins/\[Ll]ang | Uppercase `L` |
 | /Views                 | Uppercase `V`                                                                         |
 | /umbraco/Licenses      | Lowercase `u` and uppercase `L`                                                       |
 | /config                | Lowercase `c`                                                                         |

14/umbraco-cms/extending/packages/installing-and-uninstalling-packages.md

@@ -1,28 +1,19 @@
 ---
 description: >-
   The process of installing and, in turn, uninstalling packages in your Umbraco
-  CMS website depends on the version and package type.
+  CMS website.
 ---
 
 # Installing and Uninstalling Packages
 
 This article will cover the process of installing as well as uninstalling packages from your Umbraco CMS website.
 
-As the article will cover both NuGet packages and zip file packages, it is important to know the distinction:
-
-* **NuGet packages**: Modern Umbraco (Umbraco 10+) and Legacy Umbraco (Umbraco 8 and earlier versions).
-* **Package zip files**: Legacy Umbraco (Umbraco 8 and earlier versions) only.
-
-Learn more about the different types of packages in the [Types of packages](types-of-packages.md) article.
-
 ## Installing packages
 
 In the Umbraco Backoffice, you will find a **Packages** section that displays the [Umbraco Marketplace](https://marketplace.umbraco.com/). From here you can browse all community-made as well as official Umbraco packages for the Umbraco CMS.
 
 ![Backoffice - Packages section](images/backoffice-packages-section.png)
 
-{% tabs %}
-{% tab title="NuGet package" %}
 Navigating to a specific package in the section will present you with an overview of the package, as well as an install snippet for NuGet CLI.
 
 ![Backoffice - Starter Kit package](images/backoffice-packages-section-package.png)
@@ -48,31 +39,6 @@ The Package Manager has an integrated search function that allows you to find an
 Once the package has been installed, it will show up under the **Packages** section in the backoffice, under **Installed** tab.
 
 ![Backoffice - installed packages](../../../../10/umbraco-cms/extending/packages/images/backoffice-installed-packages.png)
-{% endtab %}
-
-{% tab title="Package zip file" %}
-{% hint style="warning" %}
-Package zip files are only available for Umbraco 8 or earlier versions.
-{% endhint %}
-
-Once you have downloaded an Umbraco package zip file, you can install it in the Umbraco backoffice by following the steps below:
-
-* Navigate to the **Packages** section.
-* Select **Install local** on the top-right side of the page.
-* Drag'n drop the package onto the page or use the file explorer to select the package zip file.
-* Accept terms of use to confirm the package installation.
-
-The package will be installed and any necessary reboots of the site will be initiated.
-
-You can also install packages directly when browsing the packages in the Umbraco backoffice. This is usually preferred in order to ensure that the package is compatible with the Umbraco CMS version used.
-
-* Navigate to the specific package you want to install.
-* Click **Install package** in the right-hand side of the page.
-* Confirm the installation.
-
-The package will be install and the site will be rebooted.
-{% endtab %}
-{% endtabs %}
 
 ## Uninstalling packages
 
@@ -94,14 +60,6 @@ To uninstall a package, either run a command or use the NuGet Package Manager in
 
 ![Visual Studio - uninstalling via Package Manager](images/uninstalling-via-nuget-package-manager.png)
 
-{% hint style="info" %}
-If you are using Umbraco 8 or an earlier version you uninstall the packages directly from the **Packages** section of the Umbraco backoffice.
-
-1. Navigate to the **Installed** tab in the **Packages** section.
-2. Click **Uninstall package** next to the package you want to uninstall.
-3. Confirm that action by checking **Confirm package uninstall**.
-{% endhint %}
-
 It is recommended to clean the solution after removing any package. This can be done by right-clicking the project in Visual Studio and choosing the _Clean_ option, or using the `dotnet clean` command.
 
 ![Visual Studio - clean solution](images/vs-cleaning-solution.png)