diff --git a/proposals/4041-retry-after-header-rate-limiting.md b/proposals/4041-retry-after-header-rate-limiting.md
index e2f2ed50..77966563 100644
--- a/proposals/4041-retry-after-header-rate-limiting.md
+++ b/proposals/4041-retry-after-header-rate-limiting.md
@@ -5,7 +5,7 @@ being overloaded by enforcing rate-limits to selected API calls.
 If homeservers limit access to an API they respond with an http error code 429 and a response body
 that includes a property `retry_after_ms` to indicate how long a client has to wait before retrying.
 
-Some http libraries (like [Ky](https://github.com/sindresorhus/ky), [got](https://github.com/sindresorhus/got
+Some http libraries (like [Ky](https://github.com/sindresorhus/ky), [got](https://github.com/sindresorhus/got)
 and [urllib3](https://urllib3.readthedocs.io/en/stable/reference/urllib3.util.html#urllib3.util.Retry)) ease
 the burden of handling retries by honoring the http header `Retry-After`. As explained in
 [RFC 9119 - HTTP Semantics](https://www.rfc-editor.org/rfc/rfc9110#field.retry-after) this header is optional
@@ -47,4 +47,4 @@ Since this MSC is using a standard HTTP header, it will not use a unstable prefi
 
 ## Dependencies
 
-N/A
\ No newline at end of file
+N/A