Remove broken link

docs/index.rst

@@ -32,7 +32,7 @@ Pipenv is primarily meant to provide users and developers of applications with a
 The problems that Pipenv seeks to solve are multi-faceted:
 
 - You no longer need to use ``pip`` and ``virtualenv`` separately. They work together.
-- Managing a ``requirements.txt`` file `can be problematic <https://www.kennethreitz.org/essays/a-better-pip-workflow>`_, so Pipenv uses ``Pipfile`` and ``Pipfile.lock`` to separate abstract dependency declarations from the last tested combination.
+- Managing a ``requirements.txt`` file can be problematic, so Pipenv uses ``Pipfile`` and ``Pipfile.lock`` to separate abstract dependency declarations from the last tested combination.
 - Hashes are used everywhere, always. Security. Automatically expose security vulnerabilities.
 - Strongly encourage the use of the latest versions of dependencies to minimize security risks `arising from outdated components <https://www.owasp.org/index.php/Top_10-2017_A9-Using_Components_with_Known_Vulnerabilities>`_.
 - Give you insight into your dependency graph (e.g. ``$ pipenv graph``).