Align docs to OSC governance

[Ranchhand87]

Changelog

- description: |
    <Update documentation to align with Governance Policy> If needed.

# uncomment types applicable to the change:
  type:
  
  # - documentation  # change in code docs, haddocks...

Context

https://committees.docs.intersectmbo.org/intersect-open-source-committee/policies/governance/documentation

How to trust this PR

Highlight important bits of the PR that will make the review faster. If there are commands the reviewer can run to observe the new behavior, describe them.

Checklist

• [ Y ] Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated. See Running tests for more details
• [ Y ] Self-reviewed the diff

[CarlosLopezDeLara]

@Ranchhand87

When creating a PRs, please make sure you follow this directive:

# uncomment types applicable to the change:

For example:

# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - refactoring    # QoL changes
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  - documentation  # change in code docs, haddocks...

This will help the automation that generates changelogs to work correctly.

[carbolymer]

Thanks. I've signed the commits and pushed with force.