More edits

Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>

Author: IanMadd

components/docs-chef-io/content/habitat/builder_origins.md

@@ -13,9 +13,19 @@ gh_repo = "habitat"
 
 {{< readfile file="/habitat/reusable/md/builder_origins.md" >}}
 
+## Chef-owned origins
+
+Progress Chef maintains the following origins:
+
+- **core**: Hosts packages for common dependencies and compilers maintained by Progress Chef.
+- **chef**: Hosts packages for Chef products like Chef Infra Client, Chef InSpec, and Chef Automate.
+- **chef-platform**: Hosts packages for Chef 360 Platform skills.
+- **habitat**: Hosts packages required for an on-prem Habitat Builder deployment.
+
 ## Where can I create an origin
 
-You can create new origins in an on-prem Habitat Builder deployment.
+You can create origins in an on-prem Habitat Builder deployment.
+[Chef's public Habitat Builder](https://bldr.habitat.sh) doesn't support creating new origins.
 
 ## Create an origin
 
@@ -276,7 +286,7 @@ On Linux or macOS:
 ls -la ~/.hab/cache/keys
 ```
 
-##### Find your existing origin keys from inside of the Chef Habitat Studio:
+##### Find your existing origin keys from inside of the Chef Habitat Studio
 
 On Windows:
 

components/docs-chef-io/content/habitat/get_started.md

@@ -1,6 +1,7 @@
 +++
 title = "Get Started with Chef Habitat"
 gh_repo = "habitat"
+draft = true
 
 [menu]
   [menu.habitat]
@@ -134,7 +135,7 @@ Use the Habitat Studio to generate a Habitat package and preview the running Nod
 
 ## Manage the Service with Habitat Builder
 
-[Chef Habitat Builder]({{< relref "/habitat/builder_overview" >}}) acts as the core of Chef’s Application Delivery Enterprise hub. The Chef Habitat Builder SaaS stores plan files where they can be viewed and accessed by the Chef Habitat community and then deployed by the Chef Habitat Supervisor.
+[Chef Habitat Builder]({{< relref "/habitat/builder_overview" >}}) acts as the core of Chef's Application Delivery Enterprise hub. The Chef Habitat Builder SaaS stores plan files where they can be viewed and accessed by the Chef Habitat community and then deployed by the Chef Habitat Supervisor.
 
 Add your package to your Builder origin and then connect that package to your clone of the sample-node-app repository. Any changes made to your clone of the sample-node-app will trigger the Chef Habitat Builder to rebuild the package.
 

components/docs-chef-io/content/habitat/origins.md

@@ -14,7 +14,7 @@ gh_repo = "habitat"
 
 ## Chef-owned origins
 
-Chef maintains the following origins:
+Progress Chef maintains the following origins:
 
 - **core**: Hosts packages for common dependencies and compilers maintained by Progress Chef.
 - **chef**: Hosts packages for Chef products like Chef Infra Client, Chef InSpec, and Chef Automate.
@@ -23,7 +23,8 @@ Chef maintains the following origins:
 
 ## Where can I create an origin
 
-You can create a new origin in an on-prem Habitat Builder deployment.
+You can create origins in an on-prem Habitat Builder deployment.
+[Chef's public Habitat Builder](https://bldr.habitat.sh) doesn't support creating new origins.
 
 ## Create an origin