fix(docs): change the references from RC's to deploments

Author: kmala

src/installing-workflow/configuring-postgres.md

@@ -48,9 +48,9 @@ The Helm Classic chart for Deis Workflow can be easily configured to connect the
     * Note: Whether using environment variables or `tpl/generate_params.toml`, you do not need to (and must not) base64 encode any values, as the Helm Classic chart will automatically handle encoding as necessary.
 * **Step 3:** Re-generate the Helm Classic chart by running `helmc generate -x manifests workflow-v2.5.0`
 * **Step 4:** Check the generated files in your `manifests` directory. You should see:
-    * `deis-controller-rc.yaml` contains relevant connection details.
+    * `deis-controller-deployment.yaml` contains relevant connection details.
     * `deis-database-secret-creds.yaml` exists and contains base64 encoded database username and password.
-    * No other database-related Kubernetes resources are defined. i.e. none of `database-database-service-account.yaml`, `database-database-service.yaml`, or `database-database-rc.yaml` exist.
+    * No other database-related Kubernetes resources are defined. i.e. none of `database-database-service-account.yaml`, `database-database-service.yaml`, or `database-database-deployment.yaml` exist.
 
 You are now ready to `helmc install workflow-v2.5.0` [as usual][installing].
 

src/managing-workflow/platform-monitoring.md

@@ -43,7 +43,7 @@ We now include a monitoring stack for introspection on a running Kubernetes clus
 Deis Workflow exposes Grafana through the router using [service annotations](https://github.com/deis/router#how-it-works). This
 allows users to access the Grafana UI at `http://grafana.mydomain.com`. The default username/password of
 `admin/admin` can be overridden at any time by setting the following environment variables in
-`$CHART_HOME/workspace/workflow-$WORKFLOW_RELEASE/manifests/deis-monitor-grafana-rc.yaml`: `GRAFANA_USER` and
+`$CHART_HOME/workspace/workflow-$WORKFLOW_RELEASE/manifests/deis-monitor-grafana-deployment.yaml`: `GRAFANA_USER` and
 `GRAFANA_PASSWD`.
 
 Grafana will preload several dashboards to help operators get started with monitoring Kubernetes and Deis Workflow.

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

@@ -7,11 +7,11 @@ is to Homebrew.
 
 After you fetch the Workflow chart, you can customize the chart using `helmc edit` before using
 `helmc generate` and `helmc install` to complete the installation. To customize the respective
-component, edit `tpl/deis-<component>-rc.yaml` and modify the `env` section of the component to
+component, edit `tpl/deis-<component>-deployment.yaml` and modify the `env` section of the component to
 tune these settings.
 
 For example, to allow only administrators to register new accounts in the controller,
-edit `tpl/deis-controller-rc.yaml` and add the following under the `env` section:
+edit `tpl/deis-controller-deployment.yaml` and add the following under the `env` section:
 
 ```
 env:

src/roadmap/releases.md

@@ -193,7 +193,7 @@ Change the `generate_params.toml` file in **each** new chart as follows:
   1. If there's a `[workflowManager]` section, change `versionsApiURL` to
      `"https://versions.deis.com"` and `doctorApiURL` to `"https://doctor.deis.com"`
 
-Change the `workflow-$WORKFLOW_RELEASE/tpl/deis-controller-rc.yaml` file:
+Change the `workflow-$WORKFLOW_RELEASE/tpl/deis-controller-deployment.yaml` file:
 
   1. Remove the `KUBERNETES_POD_TERMINATION_GRACE_PERIOD_SECONDS` env var
 

src/understanding-workflow/concepts.md

@@ -22,8 +22,8 @@ donated to the [Cloud Native Compute Foundation][cncf]. Kubernetes manages all
 the activity on your cluster, including: desired state convergence, stable
 service addresses, health monitoring, service discovery, and DNS resolution.
 
-Workflow builds upon Kubernetes abstractions like Services, Replication
-Controllers, Deployments and Pods to provide a developer-friendly experience.
+Workflow builds upon Kubernetes abstractions like Services,
+Deployments and Pods to provide a developer-friendly experience.
 Building containers directly from application source code, aggregating logs,
 and managing deployment configurations and app releases are just some of the
 features Workflow adds.
@@ -99,7 +99,7 @@ build is created or application configuration is changed. Tracking releases as a
 ### Run Stage
 
 The run stage deploys the new release to the underlying Kubernetes cluster by
-launching a new Replication Controller which references the new release.
+changing the Deployment object which references the new release.
 By managing the desired replica count, Workflow
 orchestrates a zero-downtime, rolling update of your application. Once
 successfully updated, Workflow removes the last reference to the old release.