diff --git a/_posts/2017-10-20-totw-77.md b/_posts/2017-10-20-totw-77.md
index bb945dc..f94b885 100644
--- a/_posts/2017-10-20-totw-77.md
+++ b/_posts/2017-10-20-totw-77.md
@@ -113,7 +113,7 @@ them, or let them go out of scope, but don’t make any other assumptions about
 their state.
 
 Clang-tidy provides some some static-checking to catch use-after move with the
-[misc-use-after-move](http://clang.llvm.org/extra/clang-tidy/checks/misc-use-after-move.html)
+[bugprone-use-after-move](https://clang.llvm.org/extra/clang-tidy/checks/bugprone/use-after-move.html)
 check. However, static-analysis won't ever be able to catch all of these - be on
 the lookout. Call these out in code review, and avoid them in your own code.
 Stay away from the zombies.