More doc changes to use new binary

Author: JasonVranek

docs/docs/get_started/running/binary.md

@@ -57,7 +57,7 @@ Modules might also have additional envs required, which should be detailed by th
 After creating the `cb-config.toml` file, setup the required envs and run the binary. For example:
 
 ```bash
-CB_CONFIG=./cb-config.toml commit-boost-pbs
+CB_CONFIG=./cb-config.toml commit-boost pbs
 ```
 
 ## Security

docs/docs/get_started/running/metrics.md

@@ -12,7 +12,7 @@ Make sure to add the `[metrics]` section to your config file:
 [metrics]
 enabled = true
 ```
-If the section is missing, metrics collection will be disabled. If you generated the `docker-compose.yml` file with `commit-boost-cli`, metrics ports will be automatically configured, and a sample `target.json` file will be created. If you're running the binaries directly, you will need to set the correct environment variables, as described in the [previous section](/get_started/running/binary#common).
+If the section is missing, metrics collection will be disabled. If you generated the `docker-compose.yml` file with `commit-boost init`, metrics ports will be automatically configured, and a sample `target.json` file will be created. If you're running the binaries directly, you will need to set the correct environment variables, as described in the [previous section](/get_started/running/binary#common).
 
 ## Example setup