net/py-pook: Correct WWW and pkg-descr

net/py-pook/Makefile

@@ -6,7 +6,7 @@ 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

net/py-pook/pkg-descr

@@ -1,18 +1,5 @@
-Duet takes inspiration from the amazing trio library and the structured
+pook is a versatile, expressive and hackable utility library for HTTP traffic
-concurrency approach to async programming that it uses. However, duet differs
+mocking and expectations made easy in Python. Heavily inspired by gock.
-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.
 
-* duet is re-entrant. At the top level, you run async code by calling
+pook can work with multiple mock engines, however it provides a built-in one by
-  duet.run(foo). Inside foo suppose you call a function that has not yet been
+default, which currently supports traffic mocking in the several HTTP clients.
-  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.