Add clarification to MAINTAINERS

Author: foundinblank

docs/MAINTAINERS.md

@@ -1,5 +1,9 @@
 # Contributing to the dbt Artifacts Package as a Maintainer
 
+> [!IMPORTANT]
+> This guide was written for Brooklyn Data engineers and contains details that are specific to the Brooklyn Data workplace (i.e., Slack channel names), but much of this
+> will be useful for all contributors, internal or external to Brooklyn Data. 
+
 ## General Guidance
 - You can create your own branches in the repo - no need to fork. Make sure to ask in the #_dbt_artifacts Slack channel
   if you need to be given permissions to contribute.
@@ -198,4 +202,4 @@ Make sure to check “Approve Integration Tests” and then click “Approve and
 - Merge a PR which applies that change 
 - Make a new release: [Releases · brooklyn-data/dbt_artifacts](https://github.com/brooklyn-data/dbt_artifacts/releases)
   - This will automatically update the documentation through a GH action 
-  - Per the [dbt guidance](https://docs.getdbt.com/guides/legacy/building-packages), the repo ([GitHub - dbt-labs/hubcap](https://github.com/dbt-labs/hubcap)) that adds releases to dbt Hub will run every hour and pick up any new versions. It will only pick up full versions, so use the guidance if you want to create a pre-release.
+  - Per the [dbt guidance](https://docs.getdbt.com/guides/legacy/building-packages), the repo ([GitHub - dbt-labs/hubcap](https://github.com/dbt-labs/hubcap)) that adds releases to dbt Hub will run every hour and pick up any new versions. It will only pick up full versions, so use the guidance if you want to create a pre-release.