docs: clarify repository best practices (#79)

docs/best-practices.md

@@ -1,24 +1,27 @@
 # Best practices
 
+This document provides best practices for developing reusable Terraform modules in Equinor.
+
+## Repository
+
 - Use [this template](https://github.com/equinor/terraform-module-template) when creating your repository.
 
-- The following accesses should be configured for the repository:
+- Use the common naming convention `terraform-azurerm-<name>` when naming your repository.
 
-  | Team | Role |
-  | --- | --- |
-  | @equinor/terraform-baseline | `Write` |
-  | @equinor/terraform-baseline-admins | `Admin` |
+    For example, if you want to create a module named `storage`, the repository should be named `terraform-azurerm-storage`.
 
-- The following code owners should be configured in a file `.github/CODEOWNERS`:
+- Configure the following accesses for the repository:
 
-  ```raw
-  * @equinor/terraform-baseline
-  ```
+    | Team | Role |
+    | --- | --- |
+    | @equinor/terraform-baseline | `Write` |
+    | @equinor/terraform-baseline-admins | `Admin` |
 
-## Naming convention
+- Configure the following code owners in a file `.github/CODEOWNERS`:
 
-- Use the common naming convention `terraform-azurerm-<name>` when naming your repository.
-  For example, if you want to create a module named `storage`, the repository should be named `terraform-azurerm-storage`.
+    ```raw
+    * @equinor/terraform-baseline
+    ```
 
 ## Roles and scope