couple more links

Author: JnHs

articles/batch/batch-visual-studio-templates.md

@@ -11,9 +11,7 @@ ms.custom: seodec18
 The **Job Manager** and **Task Processor Visual Studio templates** for Batch provide code to help you to implement and run your compute-intensive workloads on Batch with the least amount of effort. This document describes these templates and provides guidance for how to use them.
 
 > [!IMPORTANT]
-> This article discusses only information applicable to these two templates, and assumes that you are familiar with the Batch service and key concepts related to it: pools, compute nodes, jobs and tasks, job manager tasks, environment variables, and other relevant information. You can find more information in [Basics of Azure Batch](batch-technical-overview.md) and [Batch feature overview for developers](batch-api-basics.md).
-> 
-> 
+> This article discusses only information applicable to these two templates, and assumes that you are familiar with the Batch service and key concepts related to it: pools, compute nodes, jobs and tasks, job manager tasks, environment variables, and other relevant information. You can find more information in [Basics of Azure Batch](batch-technical-overview.md) and [Batch service workflow and resources](batch-service-workflow-features.md). 
 
 ## High-level overview
 The Job Manager and Task Processor templates can be used to create two useful components:
@@ -64,7 +62,7 @@ The Job Manager template helps you to implement a job manager task that can perf
 * Submit those tasks to run on Batch.
 
 > [!NOTE]
-> For more information about job manager tasks, see [Batch feature overview for developers](batch-api-basics.md#job-manager-task).
+> For more information about job manager tasks, see [Jobs and tasks](jobs-and-tasks.md#job-manager-task).
 > 
 > 
 

includes/batch-task-output-include.md

@@ -2,14 +2,14 @@
  title: include file
  description: include file
  services: batch
- author: laurenhughes
+ author: JnHs
  ms.service: batch
  ms.topic: include
  ms.date: 04/06/2018
- ms.author: lahugh
+ ms.author: jenhayes
  ms.custom: include file
 ---
 
 A task running in Azure Batch may produce output data when it runs. Task output data often needs to be stored for retrieval by other tasks in the job, the client application that executed the job, or both. Tasks write output data to the file system of a Batch compute node, but all data on the node is lost when it is reimaged or when the node leaves the pool. Tasks may also have a file retention period, after which files created by the task are deleted. For these reasons, it's important to persist task output that you'll need later to a data store such as [Azure Storage](https://docs.microsoft.com/azure/storage/).
 
-For storage account options in Batch, see the [Batch feature overview](../articles/batch/batch-api-basics.md#azure-storage-account).
+For storage account options in Batch, see [Batch accounts and Azure Storage accounts](../articles/batch/accounts.md#azure-storage-accounts).