diff --git a/net/py-pook/Makefile b/net/py-pook/Makefile
index b37d028100ce..6edf3ad80798 100644
--- a/net/py-pook/Makefile
+++ b/net/py-pook/Makefile
@@ -1,26 +1,26 @@
 PORTNAME=	pook
 PORTVERSION=	2.1.3
 CATEGORIES=	net python
 MASTER_SITES=	PYPI
 PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}
 
 MAINTAINER=	yuri@FreeBSD.org
 COMMENT=	HTTP traffic mocking and expectations made easy
-WWW=		https://pook \
+WWW=		https://pook.readthedocs.io/en/v2.1.2/ \
 		https://github.com/h2non/pook
 
 LICENSE=	MIT
 LICENSE_FILE=	${WRKSRC}/LICENSE
 
 BUILD_DEPENDS=	${PYTHON_PKGNAMEPREFIX}hatchling>0:devel/py-hatchling@${PY_FLAVOR}
 RUN_DEPENDS=	${PYTHON_PKGNAMEPREFIX}furl>=0.5.6:devel/py-furl@${PY_FLAVOR} \
 		${PYTHON_PKGNAMEPREFIX}jsonschema>=2.5.1:devel/py-jsonschema@${PY_FLAVOR} \
 		${PYTHON_PKGNAMEPREFIX}xmltodict>=0.11.0:devel/py-xmltodict@${PY_FLAVOR}
 # some test dependencies aren't ported yet, particularly pytest-pook
 
 USES=		python
 USE_PYTHON=	pep517 autoplist
 
 NO_ARCH=	yes
 
 .include <bsd.port.mk>
diff --git a/net/py-pook/pkg-descr b/net/py-pook/pkg-descr
index 55046f8c04fa..2497db098bcb 100644
--- a/net/py-pook/pkg-descr
+++ b/net/py-pook/pkg-descr
@@ -1,18 +1,5 @@
-Duet takes inspiration from the amazing trio library and the structured
-concurrency approach to async programming that it uses. However, duet differs
-from trio in two major ways:
-* Instead of a full-blown implementation of asynchronous IO, duet relies on the
-  Future interface for parallelism, and provides a way to run async/await
-  coroutines around those Futures. This is useful if you are using an API that
-  returns futures, such as RPC libraries like gRPC. The standard Future
-  interface does not implement __await__ directly, so Future instances must be
-  wrapped in duet.AwaitableFuture.
+pook is a versatile, expressive and hackable utility library for HTTP traffic
+mocking and expectations made easy in Python. Heavily inspired by gock.
 
-* duet is re-entrant. At the top level, you run async code by calling
-  duet.run(foo). Inside foo suppose you call a function that has not yet been
-  fully refactored to be asynchronous, but itself calls duet.run(bar). Most
-  async libraries, including trio and asyncio, will raise an exception if you
-  try to "re-enter" the event loop in this way, but duet allows it. We have
-  found that this can simplify the process of refactoring code to be
-  asynchronous because you don't have to completely separate the sync and async
-  parts of your codebase all at once.
+pook can work with multiple mock engines, however it provides a built-in one by
+default, which currently supports traffic mocking in the several HTTP clients.