[JENKINS-43786] Addressed suggestions from @vilacides, @amuniz and @f…

…cojfernandez
jenkins-infra · Jan 15, 2018 · 0f5b944 · 0f5b944
1 parent acba131
commit 0f5b944
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/content/blog/2018/01/2018-01-15-overhaul-of-manage-jenkins-page.adoc b/content/blog/2018/01/2018-01-15-overhaul-of-manage-jenkins-page.adoc
@@ -37,7 +37,7 @@ image:/images/post-images/2018-01-15-JENKINS-43786/JENKINS-43786_4-before.png[ro
 
 image:/images/post-images/2018-01-15-JENKINS-43786/JENKINS-43786_1.png[role="center"]
 
-Information about how this change can affect the current implementation of https://jenkins.io/doc/developer/extensions/jenkins-core/#administrativemonitor[Administrative Monitors] can be found in the following section
+Information about how this change can affect the current implementations of https://jenkins.io/doc/developer/extensions/jenkins-core/#administrativemonitor[Administrative Monitors] can be found in the following section
 
 == For core developers
 
@@ -131,7 +131,7 @@ In your view (a.k.a. Jelly file or Groovy file):
 </j:jelly>
 ----
 
-If you don't want to keep a _strict_ backward compatibility, the impact is minimum. In fact, you can see an https://github.com/jenkinsci/github-plugin/pull/177#issuecomment-337266953[example] on GitHub Plugin.
+If you don't want to keep a _strict_ backward compatibility, the impact is minimal. In fact, you can see an https://github.com/jenkinsci/github-plugin/pull/177#issuecomment-337266953[example] on GitHub Plugin.
 
 Some helpful references: