docs: add beta back to orgs (#15902)

EdwardAngert · web-flow · commit 1eba4c08cbe7 · 2024-12-17T13:37:26.000-05:00
I merged #15888 too early. This PR incorporates @matifali 's edit suggestions --------- Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com>
diff --git a/docs/admin/users/organizations.md b/docs/admin/users/organizations.md
@@ -20,11 +20,11 @@ guide.
 
 ## The default organization
 
-All Coder deployments start with one organization called `Coder`. All new users
+All Coder deployments start with one organization called `coder`. All new users
 are added to this organization by default.
 
-To edit the organization details, navigate to `Deployment -> Organizations` in
-the top bar:
+To edit the organization details, select **Deployment** from the top bar, then
+**Organizations**:
 
 ![Organizations Menu](../../images/admin/users/organizations/deployment-organizations.png)
 
@@ -36,7 +36,7 @@ From there, you can manage the name, icon, description, users, and groups:
 
 Any additional organizations have unique admins, users, templates, provisioners,
 groups, and workspaces. Each organization must have at least one dedicated
-[provisioner](../provisioners.md) since the built-in provisioner only applies to
+[provisioner](../provisioners.md) since the built-in provisioners only apply to
 the default organization.
 
 You can configure [organization/role/group sync](./idp-sync.md) from your
@@ -110,6 +110,12 @@ their organization. Users can be in multiple organizations.
 
 ![Workspace List](../../images/admin/users/organizations/workspace-list.png)
 
+## Beta
+
+Organizations is in beta. If you encounter any issues, please
+[file an issue](https://github.com/coder/internal/issues/new?title=request%28orgs%29%3A+request+title+here&labels=["customer-feedback"]&body=please+enter+your+issue+or+request+here)
+or contact your account team.
+
 ## Next steps
 
 - [Organizations - best practices](../../tutorials/best-practices/organizations.md)
