diff --git a/solr/solr-ref-guide/src/package-manager.adoc b/solr/solr-ref-guide/src/package-manager.adoc
index 41fee102616..89da4aaa6ad 100644
--- a/solr/solr-ref-guide/src/package-manager.adoc
+++ b/solr/solr-ref-guide/src/package-manager.adoc
@@ -30,13 +30,12 @@ For technical details, see the section <<package-manager-internals.adoc#package-
 
 == Interacting with the Package Manager
 
-The package manager CLI includes allows you to:
+The package manager (CLI) allows you to:
 
-* Start Solr with support for package management
 * Add trusted repositories
 * List packages at a repository
 * Install desired packages
-* Deploy packages to collections
+* Deploy and undeploy packages to/from collections or cluster
 * Update packages when updates are available
 
 === Enable the Package Manager
@@ -53,7 +52,7 @@ If an unauthorized user gained access to the system, they would have write acces
 
 === Add Trusted Repositories
 
-A _repository_ is a a location hosting one or many packages. Often this is a web service that serves meta-information about packages, the package artifacts for downloading, and a public key to validate the jar file signatures while installing.
+A _repository_ is a location hosting one or many packages. Often, this is a web service that serves meta-information about packages, the package artifacts for downloading, and a public key to validate the jar file signatures while installing.
 
 In order to install packages into Solr, one has to add a repository hosting the packages.
 
@@ -170,7 +169,7 @@ You can run the `list-deployed` command to verify that this collection is using
 
 === Undeploy a Package
 
-If a package supports undeploying the plugins it contains (check package manager's documentation for every package), then a previously deployed package can be undeployed as follows:
+If a package supports undeploying the plugins it contains (check package author's documentation), then a previously deployed package can be undeployed as follows:
 
 [source,bash]
 ----
diff --git a/solr/solr-ref-guide/src/solr-plugins.adoc b/solr/solr-ref-guide/src/solr-plugins.adoc
index fc05cbfbfc9..115bbd1e0ac 100644
--- a/solr/solr-ref-guide/src/solr-plugins.adoc
+++ b/solr/solr-ref-guide/src/solr-plugins.adoc
@@ -37,7 +37,7 @@ There are essentially two types of plugins in Solr:
 
 * Collection level plugins. These are registered on individual collections, either by hand-editing the `solrconfig.xml` or schema files for the collection's configset or by using the <<config-api.adoc#config-api,config API>> or <<schema-api.adoc#schema-api,schema API>>. Examples of these are query parsers, request handlers, update request processors, value source parsers, response writers etc.
 
-* Cluster level (or Core Container level) plugins. These are plugins that are installed at a cluster level and usually every Solr node has one instance each of these plugins. Examples of these are <<authentication-and-authorization-plugins.adoc#authentication-and-authorization-plugins,authentication and authorization plugins>>, <<metrics-reporting.adoc#reporters,metrics reporters>>, https://issues.apache.org/jira/browse/SOLR-14404[cluster level request handlers] etc.
+* Cluster level (or Core Container level) plugins. These are plugins that are installed at a cluster level and every Solr node has one instance each of these plugins. Examples of these are <<authentication-and-authorization-plugins.adoc#authentication-and-authorization-plugins,authentication and authorization plugins>>, <<metrics-reporting.adoc#reporters,metrics reporters>>, https://issues.apache.org/jira/browse/SOLR-14404[cluster level request handlers] etc.
 
 == Installing Plugins ==