Don't mention installing add-ons here, activating is enough.

Sure, the Python package of an add-on must be installed before you can activate it, but the same is true for a distribution.
The plone.classicui distribution has basically the same Python package dependencies as CMFPlone, although it activates a few extra ones automatically if they are available (say plone.app.caching).

Author: mauritsvanrees

docs/backend/upgrading/version-specific-migration/upgrade-to-61.md

@@ -153,7 +153,7 @@ Consider, however, the following differences from distributions and from Plone 6
 
 -   The configuration form is simpler and shorter.
 -   The created site has no content, and therefore no {guilabel}`News` or {guilabel}`Events` folders.
--   You must install and then activate add-ons through the {guilabel}`Add-ons` control panel.
+-   You must activate add-ons through the {guilabel}`Add-ons` control panel.
 
 There are a few things you should consider when upgrading a project to, or making an add-on compatible with, Plone 6.1: