.

Author: matklad

_posts/2022-10-19-why-linux-troubleshooting-advice-sucks.adoc

@@ -31,7 +31,7 @@ The advice tells you the remedy ("`add this kernel parameter`"), but it doesn't
 That is, if the potential problem is a not loaded kernel driver, it would really help me to know how to check which kernel driver is in use, so that I can do both:
 
 * _Before_ adding the parameter, check that `46a6` doesn't have a driver
-* _After_ the fix, verify that `i915` is indeed use.
+* _After_ the fix, verify that `i915` is indeed used.
 
 If a "`fix`" doesn't come with a linked "`diagnostic`", a very common outcome is: