docs(*): rm no longer needed pipe to sed (#817)

src/installing-workflow/configuring-object-storage.md

@@ -11,7 +11,7 @@ Every component that relies on object storage uses two inputs for configuration:
 1. Component-specific environment variables (e.g. `BUILDER_STORAGE` and `REGISTRY_STORAGE`)
 2. Access credentials stored as a Kubernetes secret named `objectstorage-keyfile`
 
-The helm chart for Deis Workflow can be easily configured to connect Workflow components to off-cluster object storage. Deis Workflow currently supports Google Compute Storage, Amazon S3, Azure Blob Storage and OpenStack Swift Storage.
+The helm chart for Deis Workflow can be easily configured to connect Workflow components to off-cluster object storage. Deis Workflow currently supports Google Compute Storage, Amazon S3, [Azure Blob Storage][] and OpenStack Swift Storage.
 
 ### Step 1: Create storage buckets
 
@@ -35,7 +35,7 @@ If you haven't already added the Helm repo, do so with `helm repo add deis https
 
 Operators should configure object storage by editing the Helm values file before running `helm install`. To do so:
 
-* Fetch the Helm values by running `helm inspect values deis/workflow | sed -n '1!p' > values.yaml`
+* Fetch the Helm values by running `helm inspect values deis/workflow > values.yaml`
 * Update the `global/storage` parameter to reference the platform you are using, e.g. `s3`, `azure`, `gcs`, or `swift`
 * Find the corresponding section for your storage type and provide appropriate values including region, bucket names, and access credentials.
 * Save your changes.
@@ -51,3 +51,4 @@ You are now ready to run `helm install deis/workflow --namespace deis -f values.
 
 [minio]: ../understanding-workflow/components.md#object-storage
 [aws-iam]: http://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html
+[Azure Blob Storage]: https://azure.microsoft.com/en-us/services/storage/blobs/

src/installing-workflow/configuring-postgres.md

@@ -31,7 +31,7 @@ $ psql -h <host> -p <port> -d postgres -U <"postgres" or your own username>
 
 The Helm chart for Deis Workflow can be easily configured to connect the Workflow controller component to an off-cluster PostgreSQL database.
 
-* **Step 1:** If you haven't already fetched the values, do so with `helm inspect values deis/workflow | sed -n '1!p' > values.yaml`
+* **Step 1:** If you haven't already fetched the values, do so with `helm inspect values deis/workflow > values.yaml`
 * **Step 2:** Update database connection details by modifying `values.yaml`:
     * Update the `database_location` parameter to `off-cluster`.
     * Update the values in the `[database]` configuration section to properly reflect all connection details.

src/installing-workflow/configuring-registry.md

@@ -23,7 +23,7 @@ Deis Workflow currently supports:
 
 ## Configuration
 
-  1. If you haven't already fetched the values file, do so with `helm inspect values deis/workflow | sed -n '1!p' > values.yaml`
+  1. If you haven't already fetched the values file, do so with `helm inspect values deis/workflow > values.yaml`
   1. Update registry location details by modifying the values file:
     * Update the `registry_location` parameter to reference the registry location you are using: `off-cluster`, `ecr`, `gcr`
     * Update the values in the section which corresponds to your registry location type.

src/managing-workflow/tuning-component-settings.md

@@ -4,7 +4,7 @@ Helm Charts are a set of Kubernetes manifests that reflect best practices for de
 application or service on Kubernetes.
 
 After you add the Deis Chart Repository, you can customize the chart using
-`helm inspect values deis/workflow | sed -n '1!p' > values.yaml` before using `helm install` to complete the
+`helm inspect values deis/workflow > values.yaml` before using `helm install` to complete the
 installation.
 
 There are a few ways to customize the respective component: