Freshen the README

Author: HoloRin

README.md

@@ -2,33 +2,6 @@
 
 Bazel rules for Erlang sources
 
-## Assumptions
-
-`erlang_app` and `ct_suite` macros require the standard otp layout, relative to the bazel package (to some degree abitrary layout can be handled with with the `erlc`, `app_file`, `erlang_app_info` & `ct_test` rules which those macros utilize). For an erlang application named `my_erlang_app` this means:
-
-```
-my_erlang_app
-├── BUILD.bazel
-├── include
-│   ├── ...
-│   └── my_header.hrl
-├── priv
-│   └── schema
-├── src
-│   ├── ...
-│   └── my_erlang_app.erl
-└── test
-    ├── ...
-    └── unit_SUITE.erl
-```
-
-And that the convention is followed where, using the `dest` attribute of the `erlc` rule:
-1. Compiled production bytecode is placed in `ebin`
-2. Compiled test bytecode is placed in `src`
-3. Compiled test suite and test helper bytecode is placed in `test`
-
-The example below follows this convention.
-
 ## Minimal Example
 
 ### `WORKSPACE` file
@@ -78,23 +51,23 @@ assert_suites([
 ])
 ```
 
-## Compile and run all tests
+### Compile and run all tests
 
 ```shell
 bazel test //... \
     --@rules_erlang//:erlang_home=/path/to/erlang \
     --@rules_erlang//:erlang_version=23.2
 ```
 
-## Run the unit suite only
+### Run the unit suite only
 
 ```shell
 bazel test //:unit_SUITE \
     --@rules_erlang//:erlang_home=/path/to/erlang \
     --@rules_erlang//:erlang_version=23.2
 ```
 
-## Run a single test case
+### Run a single test case
 
 ```shell
 bazel test //:unit_SUITE \
@@ -103,9 +76,36 @@ bazel test //:unit_SUITE \
     --test_env FOCUS="-group my_group -case my_case"
 ```
 
+## Assumptions
+
+`erlang_app` and `ct_suite` macros require the standard otp layout, relative to the bazel package (to some degree abitrary layout can be handled with with the `erlc`, `app_file`, `erlang_app_info` & `ct_test` rules which those macros utilize). For an erlang application named `my_erlang_app` this means:
+
+```
+my_erlang_app
+├── BUILD.bazel
+├── include
+│   ├── ...
+│   └── my_header.hrl
+├── priv
+│   └── schema
+├── src
+│   ├── ...
+│   └── my_erlang_app.erl
+└── test
+    ├── ...
+    └── unit_SUITE.erl
+```
+
+And that the convention is followed where, using the `dest` attribute of the `erlc` rule:
+1. Compiled production bytecode is placed in `ebin`
+2. Compiled test bytecode is placed in `src`
+3. Compiled test suite and test helper bytecode is placed in `test`
+
+The example above follows these conventions.
+
 ## Copyright and License
 
-(c) 2020-2021, VMware Inc or its affiliates.
+(c) 2020-2022, VMware Inc or its affiliates.
 
 Dual licensed under the Apache License Version 2.0 and
 Mozilla Public License Version 2.0.