clarified who can do what

jama22 · web-flow · commit aafa9af9fd6b · 2019-11-07T10:42:47.000-05:00
diff --git a/jekyll/_cci2/orb-author.md b/jekyll/_cci2/orb-author.md
@@ -19,7 +19,7 @@ Before you create your first orb, please see the following notes:
 * Each organization or username can claim one unique namespace.
 * Namespaces are global within the CircleCI orb registry, so pick a unique name!
 * Only users with "owner"/"administrator" privileges within a given GitHub/Bitbucket organization can create a namespace linked to that organization.
-* Any org member can publish `dev` orbs, but only admins can create new orb names or publish production orbs.
+* Once an orb has been created by an org admin, any org member can publish `dev` orbs. When ready, `dev` orbs can be promoted into production by org admins.
 * When stored as a project environment variable or Contexts resource, an [API token]({{ site.baseurl }}/2.0/managing-api-tokens) generated by an org admin can help automate the orb publishing process, enabling _any_ org member to potentially publish a production orb by using the [CircleCI CLI]({{ site.baseurl }}/2.0/local-cli/) in a CircleCI job.
 * To use the orbs you create, you will need to enable the "Allow Uncertified Orbs" setting in the Security section of CircleCI's Organization Settings page for your organization (`https://circleci.com/[vcs]/organizations/[org-name]/settings#security`).
 * If you are creating an orb, you can use development versions to avoid having your orb publicly/permanently listed in CircleCI's orb registry before it is ready.
