another readme pass

Author: grokspawn

README.md

@@ -40,10 +40,11 @@ activate RemoteRepo
 User-->RemoteRepo: fork and clone repository
 activate LocalRepo
 User->>LocalRepo: update CI destination
+LocalRepo->>RemoteRepo: push CI changes to remote
+activate RemoteRepo
 User->>LocalRepo: update 'catalog' target
+LocalRepo->>RemoteRepo: push changes to remote
 deactivate LocalRepo
-activate RemoteRepo
-User->>RemoteRepo: push changes to remote
 deactivate User
 RemoteRepo--xGHAction: <<push trigger>
 deactivate RemoteRepo
@@ -54,8 +55,28 @@ activate CatalogRepo
 GHAction->>CatalogRepo: Open PR in catalog destination
 deactivate GHAction
 deactivate CatalogRepo
+
 ```
 
+1. Fork and Clone Remote Repository  
+IMPORTANT!  Skip this step, and any changes will be ignored.
+
+2. Update CI Destination  
+Customize ci.yaml in .github/workflows/ci.yaml to your needs, setting the destination_repo to the URI of your catalog repository. 
+
+3. Push Changes to Remote
+Push the CI changes to the remote branch so they will be ready/able to trigger when you later push catalog contributions
+
+4. Update 'catalog' target
+Locally, update the catalog target in the Makefile to generate your FBC.  Example targets are provided in the Makefile (with supporting artifacts) to support to the following scenarios:  
+   1. basic veneer generates FBC
+   2. semver veneer generates FBC
+   3. compound veneer generates and post-processes FBC  
+5. Push Changes to Remote  
+Once happy with the state of the `catalog` make target and the resulting FBC, push the changes to the remote repository.  This will trigger the remote actions to generate a pull request against the destination catalog repository as specified in #2.
+
+
+
 <!--
 ## Demo
 Recorded demo of modifying a `basic veneer` file "basic-veneer.yaml", generating an FBC from it, and pushing that FBC as a PR to a catalog repository.