more work on README

README.md

@@ -21,7 +21,7 @@ repository see the [gitlab-package-build-stanford GitLab project][1].
 (Note: the [gitlab-package-build-stanford][1] project is access-restricted
 to Stanford.)
 
-At the heart of the biuld scripts this repository provides is the
+At the heart of the build scripts this repository provides is the
 [`debian-package` Docker container][2].
 
 Depending on the value of certain environment variables this is what
@@ -66,6 +66,16 @@ with the new release information.
 
 Note 2: "sbp" stands for 'Stanford back-port".
 
+### Uploading the same version package twice
+
+The Stanford Debian package repository will generate an error if you
+attempt to upload the package twice using the same Debian version number.
+However, since the `dput` step itself is a child CI/CD process it will
+appear as if your CI/CD has succeeded even with this sort of error.
+
+You might want to include the text `[skip c]` in the commit message to
+avoid any attempt at a `dput` until you are ready to upload.
+
 ## `dput` configuration
 
 Most of the complexity of the configuration centers around the `dput`
@@ -116,6 +126,9 @@ the SSH key-pair used by the login credentials you want to use for
 accessing the Debian repository server. Note that this value is a _secret_
 so be sure that the only people how have access to maintain your
 repository have permission to see this value.
+*Warning.* Be sure that the string containing the private key you set in the
+CI/CD File variable has a _trailing new-line_. If not then OpenSSH will
+not be able to parse it and return an invalid format error.
 
 ### Debian repository server local account