Change MuJoCo engine source code function-spacing convention from 3 blank lines to 2

PiperOrigin-RevId: 813754244
Change-Id: I6836e41c3b021cb727e922c25c60f629b9814c93

STYLEGUIDE.md

@@ -6,7 +6,8 @@ possible in your code contributions.
 
 ### Scope of this guide
 
-Most of this guide involves C/C++ code. For Python, jump to the section [below](#python-code). For MuJoCo C/C++, code has three main categories:
+Most of this guide involves C/C++ code. For Python, jump to the section
+[below](#python-code). For MuJoCo C/C++, code has three main categories:
 
 1. **C code:** MuJoCo's core codebase. It consists of public headers under
 `include/` and C source files and internal headers under `src/`. This style
@@ -144,7 +145,7 @@ assignments:
   variable initialisation in `for` loops. For example, inspect the
   `mju_transpose` implementation above.
 
-- Three blank lines are required between function implementations in source files.
+- Two blank lines are required between function implementations in source files.
 
 #### Variable declarations
 
@@ -161,4 +162,7 @@ helping us to complete the migration are very welcome.
 
 ### [Python code](#python-code)
 
-For Python code, run `pyink foo.py` to adhere to Google's [Python style guide](https://google.github.io/styleguide/pyguide.html). For sorting and cleaning imports, run `isort foo.py`. Both `pyink` and `isort` can be pip installed via `pip install pyink isort`.
+For Python code, run `pyink foo.py` to adhere to Google's
+[Python style guide](https://google.github.io/styleguide/pyguide.html). For
+sorting and cleaning imports, run `isort foo.py`. Both `pyink` and `isort` can
+be pip installed via `pip install pyink isort`.