1 files changed, 1 insertions, 20 deletions

diff --git a/documentation/content/en/articles/contributing/_index.adoc b/documentation/content/en/articles/contributing/_index.adoc
index 63ebc42b39..cd889a2361 100644
--- a/documentation/content/en/articles/contributing/_index.adoc
+++ b/documentation/content/en/articles/contributing/_index.adoc
@@ -265,12 +265,10 @@ There are a large number of unmaintained ports.
 It is a good idea to start with adopting a port that you use regularly.
 
 Unmaintained ports have their `MAINTAINER` set to `ports@FreeBSD.org`.
-A list of unmaintained ports and their current errors and problem reports can be seen at the http://portsmon.FreeBSD.org/portsconcordanceformaintainer.py?maintainer=ports%40FreeBSD.org[FreeBSD Ports Monitoring System].
+Many unmaintained ports can have pending updates, this can be seen at the https://portscout.freebsd.org/ports@freebsd.org.html[FreeBSD Ports distfile scanner].
 
 On https://portsfallout.com/fallout?port=&maintainer=ports%40FreeBSD.org[PortsFallout] can be seen a list of unmaintained ports with errors.
 
-Many unmaintained ports can have pending updates, this can be seen at the https://portscout.freebsd.org/ports@freebsd.org.html[FreeBSD Ports distfile scanner].
-
 Some ports affect a large number of others due to dependencies and slave port relationships.
 Generally, we want people to have some experience before they maintain such ports.
 
@@ -278,11 +276,6 @@ You can find out whether or not a port has dependencies or slave ports by lookin
 (The name of the file varies by release of FreeBSD; for instance, [.filename]#INDEX-8#.) Some ports have conditional dependencies that are not included in a default [.filename]#INDEX# build.
 We expect you to be able to recognize such ports by looking through other ports' [.filename]#Makefile#'s.
 
-[NOTE]
-======
-The FreeBSD Ports Monitoring System (portsmon) is currently not working due to latest Python updates.
-======
-
 ==== How to adopt the port
 
 First make sure you understand your <<maintain-port>>.
@@ -525,9 +518,6 @@ There are some really good places to find a port that needs some attention.
 You can use the https://bugs.freebsd.org/search[web interface] to the Problem Report database to search through and view unresolved PRs.
 The majority of ports PRs are updates, but with a little searching and skimming over synopses you should be able to find something interesting to work on (the `sw-bug` class is a good place to start).
 
-The other place is the http://portsmon.FreeBSD.org/[FreeBSD Ports Monitoring System].
-In particular look for unmaintained ports with build errors and ports that are marked `BROKEN`.
-
 https://portsfallout.com/[PortsFallout] shows port issues gathered from the FreeBSD package building.
 
 It is OK to send changes for a maintained port as well, but remember to ask the maintainer in case they are already working on the problem.
@@ -536,11 +526,6 @@ Once you have found a bug or problem, collect information, investigate and fix!
 Otherwise create a new PR.
 Your changes will be reviewed and, if everything checks out, committed.
 
-[NOTE]
-======
-The FreeBSD Ports Monitoring System (portsmon) is currently not working due to latest Python updates.
-======
-
 [[mortal-coil]]
 === When to call it quits
 
@@ -563,10 +548,6 @@ In 2005 more than eleven thousand ports PRs were submitted! Following this artic
 
 The https://bugs.freebsd.org/bugzilla/query.cgi[Problem Report database].
 
-The http://portsmon.FreeBSD.org/[FreeBSD Ports Monitoring System (portsmon)] can show you cross-referenced information about ports such as build errors and problem reports.
-If you are a maintainer you can use it to check on the build status of your ports.
-As a contributor you can use it to find broken and unmaintained ports that need to be fixed.
-
 The http://portscout.FreeBSD.org[FreeBSD Ports distfile scanner (portscout)] can show you ports for which the distfiles are not fetchable.
 You can check on your own ports or use it to find ports that need their `MASTER_SITES` updated.