diff --git a/content/blog/2022-08-31-announcing-poetry-1-2-0.md b/content/blog/2022-08-31-announcing-poetry-1-2-0.md
index 8b180b3..2cde122 100644
--- a/content/blog/2022-08-31-announcing-poetry-1-2-0.md
+++ b/content/blog/2022-08-31-announcing-poetry-1-2-0.md
@@ -335,7 +335,7 @@ What that means is that if you are using both poetry 1.1.x and 1.2.0 in parallel
 
 ### Keyring
 
-Keyring is a new component in poetry 1.2, and kinks are still being worked out. Depending on your configuration, Keyring may not be able to communicate with a backend or determine that there is no working backend. Error handling will improve, but in the meantime setting the backend to Fail (e.g. through setting `PYTHON_KEYRING_BACKEND="keyring.backends.null.Keyring", see [poetry issue 2692] for more details), will allow you to rule out the keyring component when setting up authentication.
+Keyring is a new component in poetry 1.2, and kinks are still being worked out. Depending on your configuration, Keyring may not be able to communicate with a backend or determine that there is no working backend. Error handling will improve, but in the meantime setting the backend to Fail (e.g. through setting `PYTHON_KEYRING_BACKEND="keyring.backends.null.Keyring"`, see [poetry issue 2692] for more details), will allow you to rule out the keyring component when setting up authentication.
 
 One scenario where Keyring configuration might need the adjustment is using poetry 1.2.0 with a private PyPI repo that uses basic authentication.