Rename to "governance"

4 files changed, 8 insertions, 6 deletions

diff --git a/antora.yml b/antora.yml
index 3481db7..b0bbb2c 100644
--- a/antora.yml
+++ b/antora.yml
@@ -1,5 +1,5 @@
-name: developer-handbook
-title: Developer Handbook
+name: governance
+title: Governance Document
 version: '0.1a'
 nav:
   - modules/ROOT/nav.adoc
diff --git a/modules/Policies/pages/update.adoc b/modules/Policies/pages/update.adoc
index b11a618..db4bb3d 100644
--- a/modules/Policies/pages/update.adoc
+++ b/modules/Policies/pages/update.adoc
@@ -5,7 +5,7 @@ In fact few things are.
 If and when a policy (or any other internal detail, including the internal governance model) needs to be updated, there needs to be a documented procedure.
 
 In order to update a policy, an actionable proposal must be made.
-This proposal shall be made in the form of a fork to the developer handbook, with the proposal made within it.
+This proposal shall be made in the form of a fork to the governance document, with the proposal made within it.
 Ask project members, admins and others for their opinions before submitting the proposal.
 Whenever the proposal is deemed (by the author) to be mature, it may be put to the xref:voting.adoc[Vote].
 If the proposal fails, collect information on why it failed, update (in the same branch) and resubmit, unless you objected to the failure and involved the Base team.
diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
index ba02322..9a7bf52 100644
--- a/modules/ROOT/pages/index.adoc
+++ b/modules/ROOT/pages/index.adoc
@@ -1,8 +1,10 @@
 = Alpine Developer Handbook
 
 == What is It?
-This is the Alpine Developer Handbook, an effort to centralize relevant Alpine Linux information intended for developers and contributors.
-This handbook contains various internal details as to how Alpine is organized, the process of contributing and joining, as well as listing of internal policies and organizational bodies.
+This is the Alpine Governance Document, an effort to centralize relevant Alpine Linux information regarding internal governance.
+This document contains various internal details as to how Alpine is organized, as well as listing of internal policies and organizational bodies.
+
+CAUTION: This document is a proposal draft for standardizing an organizational system within Alpine. It is not currently reflective of the reality. If and when any official system is implemented, this document will be modified (if necessary) to match.
 
 == Project Goals
 - To build and maintain an independent, non-commercial, general purpose Linux distribution designed for power users who appreciate security, simplicity and resource efficiency.
diff --git a/modules/Teams/pages/index.adoc b/modules/Teams/pages/index.adoc
index 42cf5c1..4217013 100644
--- a/modules/Teams/pages/index.adoc
+++ b/modules/Teams/pages/index.adoc
@@ -59,7 +59,7 @@ Being in a team grants grants you the things you need to work on whatever the sc
 You should know your fellow team members well, and cooperate with them (and potentially other teams) to achieve tasks.
 As a team, you may request various workspaces, such as a separate irc channel, git namespace, dedicated host, and more.
 As a team, it is up to you how you manage yourselves internally, but the contents of this document should serve as guidelines.
-However, all team members are expected to follow project-wide policies (all of which are in the developer handbook as well) and the https://alpinelinux.org/community/code-of-conduct.html[Code of Conduct].
+However, all team members are expected to follow project-wide policies (all of which are in the governance document as well) and the https://alpinelinux.org/community/code-of-conduct.html[Code of Conduct].
 
 === Being a Team Administrator
 As a team admin, you have more powers, and thus more responsibility.