diff --git a/README.md b/README.md
index 3dc4499..97f5285 100644
--- a/README.md
+++ b/README.md
@@ -154,6 +154,8 @@
 COPY custom.groovy /usr/share/jenkins/ref/init.groovy.d/custom.groovy
 ```
 
+## Preinstalling plugins
+
 You can rely on the `install-plugins.sh` script to pass a set of plugins to download with their dependencies.
 Use plugin artifact ID, whithout `-plugin` extension, and append the version if needed separated by `:`.
 Dependencies that are already included in the Jenkins war will only be downloaded if their required version is newer than the one included.
@@ -163,7 +165,7 @@
 RUN /usr/local/bin/install-plugins.sh docker-slaves github-branch-source:1.8
 ```
 
-When jenkins container starts, it will check JENKINS_HOME has this reference content, and copy them
+When jenkins container starts, it will check `JENKINS_HOME` has this reference content, and copy them
 there if required. It will not override such files, so if you upgraded some plugins from UI they won't
 be reverted on next start.
 
@@ -172,27 +174,8 @@
 
 Also see [JENKINS-24986](https://issues.jenkins-ci.org/browse/JENKINS-24986)
 
-## Preinstalling plugins
 
-For your convenience, you also can use a plain text file to define plugins to be installed
-(using core-support plugin format).
-All plugins need to be listed in the form `pluginID:version` as there is no transitive dependency resolution.
-
-```
-credentials:1.18
-maven-plugin:2.7.1
-...
-```
-
-And in derived Dockerfile just invoke the utility `plugins.sh` script
-
-```
-FROM jenkins
-COPY plugins.txt /usr/share/jenkins/plugins.txt
-RUN /usr/local/bin/plugins.sh /usr/share/jenkins/plugins.txt
-```
-
-Here is an example to get the list of plugins from an existing server you can use the following curl command:
+Here is an example to get the list of plugins from an existing server:
 
 ```
 JENKINS_HOST=username:password@myhost.com:port