anchor.diff:  
   Creating an origin with the `hab origin create` command registers the origin on Chef Habitat Builder without creating an origin key pair. The `hab origin key generate` command creates the key pair and saves them in your local environment, but it does not upload either origin key to Chef Habitat Builder.
   
  +* You can only upload new keys to origins in which your are an "administrator" or "owner".
   * Builder requires the public origin key to upload artifacts for that origin, so you'll need to upload it.
   * Builder requires the private origin key to enable new artifact builds from packages with plans linked to that origin.
   
  
positive.code: 
  ---
  ## <a name="sharing-pkgs" id="sharing-pkgs" data-magellan-target="sharing-pkgs">Upload and Promote Packages</a>
  
  While you can build and run Chef Habitat packages without sharing them on [Chef Habitat Builder](https://bldr.habitat.sh), uploading them there enables greater collaboration and automated package rebuilds as underlying dependencies or your connected GitHub repository are updated.
  
  
negative.code: SETX HAB_AUTH_TOKEN <token> /m
  ```
  
  Replacing <token> with the contents of your generated personal access token.
  
  You can also save your personal access token as a permanent environment variable using the Windows user interface. In your Windows help bar, enter `environment` and select `Edit the system environment variables` from the list of suggestions.
  
  