Revises task content and adds links[#134606323]

Author: sleslie

_tasks_rec_alloc_oss.html.md.erb

@@ -1 +1 @@
-The default memory and disk allocations are defined in the BOSH manifest. See [Deployment Manifest Schema](https://bosh.io/docs/deployment-manifest.html) for more information.
+The default memory and disk allocations for tasks are specified by the `cc.default_app_memory` and `cc.default_app_disk_in_mb` properties defined in the BOSH Cloud Controller Worker job. See [Configuration Properties](http://bosh.io/jobs/cloud_controller_worker?source=github.com/cloudfoundry/cf-release&version=235) for more information.

index.html.md.erb

@@ -40,7 +40,7 @@ ___
 
 <li><a href="./deploy-apps/cf-scale.html" class="subnav">Scaling an Application Using cf scale</a></li>
 
-<li><a href="./using-tasks.html" class="subnav">Using Tasks</a></li>
+<li><a href="./using-tasks.html" class="subnav">Running Tasks</a></li>
 
 <%=vars.autoscaler_bullet%>
 

using-tasks.html.md.erb

@@ -40,9 +40,7 @@ The life-cycle of a task is:
 
 1. Cloud Foundry creates a container specifically for the task.
 1. Cloud Foundry runs the task on the container using the value passed to the `cf run-task` command.
-1. Cloud Foundry destroys the container.
-
-When creating the container, Cloud Foundry uses the disk size and memory allocation specified for the parent application. The new container for the task also respects app, space, and organization-level memory quotas. 
+1. Cloud Foundry destroys the container. 
 
 The container also inherits environment variables, service bindings and security groups bound to the application. 
 
@@ -56,9 +54,9 @@ The task execution history is retained for one month.
 
 ## <a id='manage-tasks'></a> Manage Tasks
 
-From a system-level point of view, a user with admin-level privileges can use the Cloud Controller v3 API to view all tasks that are running within an org or space. For more information, see the documentation for the [Cloud Controller v3 API](http://v3-apidocs.cloudfoundry.org/version/3.0.0/index.html#list-tasks).
+At the system level, a user with admin-level privileges can use the Cloud Controller v3 API to view all tasks that are running within an org or space. For more information, see the documentation for the [Cloud Controller v3 API](http://v3-apidocs.cloudfoundry.org/version/3.0.0/index.html#list-tasks).
 
-In addition, admins can set the default memory and disk usage quotas for tasks on a global level. Tasks use the same memory and disk usage defaults as applications.
+In addition, admins can set the default memory and disk usage quotas for tasks on a global level. Initially, tasks use the same memory and disk usage defaults as applications. However, the default memory and disk allocations for tasks can be defined separately from the default app memory and disk allocations.
 
 <% if vars.product_name == 'CF' %>
 <%= partial 'tasks_rec_alloc_oss' %>
@@ -70,7 +68,7 @@ In addition, admins can set the default memory and disk usage quotas for tasks o
 
 You can use the cf CLI to run a task in the context of an application. 
 
-<p class="note"><strong>Note</strong>: To run tasks with the cf CLI, you must install the cf CLI v6.23 (?) or later. See the <a href="../cf-cli/install-go-cli.html">Installing the Cloud Foundry Command Line Interface</a> topic for information about downloading, installing, and uninstalling the cf CLI.</p>
+<p class="note"><strong>Note</strong>: To run tasks with the cf CLI, you must install the cf CLI v6.23.0 or later. See the <a href="../cf-cli/install-go-cli.html">Installing the Cloud Foundry Command Line Interface</a> topic for information about downloading, installing, and uninstalling the cf CLI.</p>
 
 To run a task on an application, first push your application. Then, use the `cf run-task APP-NAME TASK` command on your deployed application. For example: