Make the formatting example more like the written text by adding an initial description.
RELNOTES: Make the formatting example more like to the written text by adding an initial description.
PiperOrigin-RevId: 281289075
diff --git a/site/docs/skylark/build-style.md b/site/docs/skylark/build-style.md
index 67ee8fb..d05be26 100644
--- a/site/docs/skylark/build-style.md
+++ b/site/docs/skylark/build-style.md
@@ -19,19 +19,20 @@
## Contents
-- [Formatting example](#formatting-example)
-- [File structure](#file-structure)
-- [References to targets in the current package](#references-to-targets-in-the-current-package)
-- [Target naming](#target-naming)
-- [Visibility](#visibility)
-- [Dependencies](#dependencies)
-- [Globs](#globs)
-- [Other conventions](#other-conventions)
-- [Differences with Python style guide](#differences-with-python-style-guide)
+- [Formatting example](#formatting-example)
+- [File structure](#file-structure)
+- [References to targets in the current package](#references-to-targets-in-the-current-package)
+- [Target naming](#target-naming)
+- [Visibility](#visibility)
+- [Dependencies](#dependencies)
+- [Globs](#globs)
+- [Other conventions](#other-conventions)
+- [Differences with Python style guide](#differences-with-python-style-guide)
## Formatting example
```python
+# Test code implmenting the Foo controller.
package(default_visibility = ["//visibility:public"])
py_test(
@@ -57,13 +58,13 @@
We recommend to use the following order (every element is optional):
- * Package description (a comment)
+* Package description (a comment)
- * All `load()` statements
+* All `load()` statements
- * The `package()` function.
+* The `package()` function.
- * Calls to rules and macros
+* Calls to rules and macros
Buildifier makes a distinction between a standalone comment and a comment
attached to an element. If a comment is not attached to a specific element, use
