Update instructions

Author: stevegrubb

AGENTS.md

@@ -74,10 +74,12 @@ Please follow it if you wish to contribute.
 
 In practice this means:
 
-- Indent with tabs.
+- Indent with tabs - not spaces.
 - Keep lines within ~80 columns.
-- Place braces and other formatting as in the kernel style.
-- Add a comment before any new function describing it, input variables, and return codes.
+- Place braces and other formatting as in the kernel style. However, if the
+  basic block is a 1 liner, do not use curly braces for it.
+- Add a comment before any new function describing it, input variables, and
+  return codes.
 - Comments within a function may be C++ style.
 - Do not do any whitespace adustment of existing code.
 - Keep existing function and variable names.
@@ -114,9 +116,11 @@ intended ordering.
 ## Summary
 
 - Build with `autoreconf`, `configure`, and `make`.
-- Run `make check` to execute the self-tests. (auparse tests are failing because of a mismatch in mapping uid to accounts. Igonore these.)
+- Run `make check` to execute the self-tests. (auparse tests are failing
+  because of a mismatch in mapping uid to accounts. Igonore these.)
 - Follow Linux Kernel coding style (tabs, 80 columns).
 - Keep commit messages short and descriptive.
+- Always add comments to explain new code.
 - Maintain rule file organization as described in `rules/README-rules`.
 
 These guidelines should help future contributors and automated tools