Update following code review

NCAR_tips.md

@@ -5,21 +5,29 @@ A few tips and tricks tailored for the CISL's compute environment.
 ## Running in Parallel
 
 There are two ways to request multiple cores on either casper or derecho.
-If you want to release the cores immediately after `cupid-run` finishes:
+Both cases are requesting 12 cores and 120 GB of memory.
+
+
+The recommended approach releases the cores immediately after `cupid-run` finishes:
 
 ```
 [login-node] $ conda activate cupid-dev
 (cupid-dev) [login-node] $ qcmd -l select=1:ncpus=12:mem=120GB -- cupid-run config.yml
 ```
 
-Alternatively, you can start an interactive session and remain on the compute nodes after CUPiD completes:
+Alternatively, you can start an interactive session and remain on the compute nodes after `cupid-run` completes:
 
 ```
 [login-node] $ qinteractive -l select=1:ncpus=12:mem=120GB
 [compute-node] $ conda activate cupid-dev
 (cupid-dev) [compute-node] $ cupid-run config.yml
 ```
 
+Notes:
+1. If you chose to run on derecho, specify the `develop` queue by adding the option `-q develop` to either `qcmd` or `qinteractive`
+   (the `develop` queue is a shared resource and you are charged by the core hour rather than the node hour).
+1. `cupid-build` is not computationally expensive, and can be run on a login node for either machine.
+
 ## Looking at Output
 
 You can visualize the web page in a browser using the FastX service.

docs/conf.py

@@ -18,7 +18,7 @@
 
 print("sys.path:", sys.path)
 
-# Copy README and NCAR_tipsinto docs
+# Copy README and NCAR_tips into docs
 # This block allows us to remove the header image from any md files
 # without affecting the original version, but still pull the source
 # into the docs build fresh each time.