From 3db9cdfd2fe72f257c4b18d3e589147839972da0 Mon Sep 17 00:00:00 2001
From: Joy <51241057+maniwani@users.noreply.github.com>
Date: Fri, 28 May 2021 14:27:00 -0500
Subject: [PATCH] fixed link typo

---
 implementation_details.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/implementation_details.md b/implementation_details.md
index 865a480a..91351101 100644
--- a/implementation_details.md
+++ b/implementation_details.md
@@ -246,7 +246,7 @@ Messages are good for sending global alerts and any gameplay mechanics you expli
 The example I'm thinking of is buying items from an in-game vendor. The server doesn't simulate UI, but ideally we can write the message transaction in the same system. A macro might end up being the most ergonomic choice.
 
 [1]: https://github.com/bevyengine/rfcs/pull/16
-[2]: https://github.com/lemire/FastPFor/blob/master/headers/simple8b_rle.
+[2]: https://github.com/lemire/FastPFor/blob/master/headers/simple8b_rle.h
 [3]: https://developer.valvesoftware.com/wiki/Source_Multiplayer_Networking
 [4]: https://www.ea.com/games/apex-legends/news/servers-netcode-developer-deep-dive
 [5]: https://youtu.be/W3aieHjyNvw?t=2226 "Tim Ford explains Overwatch's hit registration"