link fixes

JnHs · JnHs · commit efceaf872230 · 2020-05-21T11:09:17.000-07:00
diff --git a/articles/batch/TOC.yml b/articles/batch/TOC.yml
@@ -53,11 +53,9 @@
     items:
     - name: Security baseline
       href: security-baseline.md
-  - name: OLD - Developer features
-    href: batch-api-basics.md
   - name: Batch service workflow and resources
     displayName: developer features
-    href: batch-service-workflow-resources.md
+    href: batch-service-workflow-features.md
     items:
     - name: Batch accounts
       displayName: storage account
diff --git a/articles/batch/accounts.md b/articles/batch/accounts.md
@@ -7,7 +7,7 @@ ms.date: 05/12/2020
 ---
 # Batch accounts and Azure Storage accounts
 
-An Azure Batch account is a uniquely identified entity within the Batch service. Most Batch solutions use [Azure Storage](../azure/storage/index.yml) for storing resource files and output files, so each Batch account is usually associated with a corresponding storage account.
+An Azure Batch account is a uniquely identified entity within the Batch service. Most Batch solutions use [Azure Storage](../storage/index.yml) for storing resource files and output files, so each Batch account is usually associated with a corresponding storage account.
 
 ## Batch accounts
 
diff --git a/articles/batch/batch-api-basics.md b/articles/batch/batch-api-basics.md
diff --git a/articles/batch/batch-retry-after-errors.md b/articles/batch/batch-retry-after-errors.md
@@ -77,7 +77,7 @@ In situations where some of your tasks are failing, your Batch client applicatio
 - **Remove the node from the pool** ([REST](https://docs.microsoft.com/rest/api/batchservice/pool/removenodes) | [.NET](https://docs.microsoft.com/dotnet/api/microsoft.azure.batch.pooloperations))
 
     Sometimes it is necessary to completely remove the node from the pool.
-- **Disable task scheduling on the node** ([REST](https://docs.microsoft.com/en-us/rest/api/batchservice/computenode/disablescheduling) | [.NET](https://docs.microsoft.com/dotnet/api/microsoft.azure.batch.computenode.disablescheduling))
+- **Disable task scheduling on the node** ([REST](https://docs.microsoft.com/rest/api/batchservice/computenode/disablescheduling) | [.NET](https://docs.microsoft.com/dotnet/api/microsoft.azure.batch.computenode.disablescheduling))
 
     This effectively takes the node offline so that no further tasks are assigned to it, but allows the node to remain running and in the pool. This enables you to perform further investigation into the cause of the failures without losing the failed task's data, and without the node causing additional task failures. For example, you can disable task scheduling on the node, then sign in remotely to examine the node's event logs or perform other troubleshooting. After you've finished your investigation, you can then bring the node back online by enabling task scheduling ([REST](https://docs.microsoft.com/rest/api/batchservice/computenode/enablescheduling) | [.NET](https://docs.microsoft.com/dotnet/api/microsoft.azure.batch.computenode.enablescheduling), or perform one of the other actions discussed earlier.
 
diff --git a/articles/batch/batch-service-workflow-features.md b/articles/batch/batch-service-workflow-features.md
@@ -18,11 +18,11 @@ Whether you're developing a distributed computational application or service tha
 
 The following high-level workflow is typical of nearly all applications and services that use the Batch service for processing parallel workloads:
 
-1. Upload the **data files** that you want to process to an [Azure Storage](../azure/storage/index.yml) account. Batch includes built-in support for accessing Azure Blob storage, and your tasks can download these files to [compute nodes](nodes-and-pools.md#nodes) when the tasks are run.
+1. Upload the **data files** that you want to process to an [Azure Storage](../storage/index.yml) account. Batch includes built-in support for accessing Azure Blob storage, and your tasks can download these files to [compute nodes](nodes-and-pools.md#nodes) when the tasks are run.
 2. Upload the **application files** that your tasks will run. These files can be binaries or scripts and their dependencies, and are executed by the tasks in your jobs. Your tasks can download these files from your Storage account, or you can use the [application packages](nodes-and-pools.md#application-packages) feature of Batch for application management and deployment.
 3. Create a [pool](nodes-and-pools.md#pools) of compute nodes. When you create a pool, you specify the number of compute nodes for the pool, their size, and the operating system. When each task in your job runs, it's assigned to execute on one of the nodes in your pool.
 4. Create a [job](jobs-and-tasks.md#jobs). A job manages a collection of tasks. You associate each job to a specific pool where that job's tasks will run.
-5. Add [tasks](jobs-and-tasks#tasks) to the job. Each task runs the application or script that you uploaded to process the data files it downloads from your Storage account. As each task completes, it can upload its output to Azure Storage.
+5. Add [tasks](jobs-and-tasks.md#tasks) to the job. Each task runs the application or script that you uploaded to process the data files it downloads from your Storage account. As each task completes, it can upload its output to Azure Storage.
 6. Monitor job progress and retrieve the task output from Azure Storage.
 
 > [!NOTE]
diff --git a/articles/batch/jobs-and-tasks.md b/articles/batch/jobs-and-tasks.md
@@ -26,6 +26,7 @@ Job scheduling across pools is independent. Between different pools, it is not g
 ### Job constraints
 
 You can use job constraints to specify certain limits for your jobs:
+
 - You can set a **maximum wallclock time**, so that if a job runs for longer than the maximum wallclock time that is specified, the job and all of its tasks are terminated.
 - You can specify the **maximum number of task retries** as a constraint, including whether a task is always retried or never retried. Retrying a task means that if the task fails, it will be requeued to run again.
 
@@ -79,9 +80,9 @@ By associating a start task with a pool, you can prepare the operating environme
 
 A primary benefit of the start task is that it can contain all the information necessary to configure a compute node and install the applications required for task execution. Therefore, increasing the number of nodes in a pool is as simple as specifying the new target node count. The start task provides the information needed for the Batch service to configure the new nodes and get them ready for accepting tasks.
 
-As with any Azure Batch task, you can specify a list of resource files in [Azure Storage](../azure/storage/index.yml), in addition to a command line to be executed. The Batch service first copies the resource files to the node from Azure Storage, and then runs the command line. For a pool start task, the file list typically contains the task application and its dependencies.
+As with any Azure Batch task, you can specify a list of resource files in [Azure Storage](../storage/index.yml), in addition to a command line to be executed. The Batch service first copies the resource files to the node from Azure Storage, and then runs the command line. For a pool start task, the file list typically contains the task application and its dependencies.
 
-However, the start task could also include reference data to be used by all tasks that are running on the compute node. For example, a start task's command line could perform a `robocopy` operation to copy application files (which were specified as resource files and downloaded to the node) from the start task's [working directory](files-and-directories.md#working-directory) to the [shared folder](files-and-directories.md#shared-folder), and then run an MSI or `setup.exe`.
+However, the start task could also include reference data to be used by all tasks that are running on the compute node. For example, a start task's command line could perform a `robocopy` operation to copy application files (which were specified as resource files and downloaded to the node) from the start task's [working directory](files-and-directories.md) to the **shared** folder, and then run an MSI or `setup.exe`.
 
 It is typically desirable for the Batch service to wait for the start task to complete before considering the node ready to be assigned tasks, but you can configure this.
 
diff --git a/articles/batch/nodes-and-pools.md b/articles/batch/nodes-and-pools.md
@@ -21,29 +21,29 @@ All compute nodes in Batch also include:
 
 - A standard [folder structure](files-and-directories.md) and associated [environment variables](jobs-and-tasks.md) that are available for reference by tasks.
 - **Firewall** settings that are configured to control access.
-- [Remote access](#connecting-to-compute-nodes) to both Windows (Remote Desktop Protocol (RDP)) and Linux (Secure Shell (SSH)) nodes.
+- [Remote access](batch-retry-after-errors.md#connect-to-compute-nodes) to both Windows (Remote Desktop Protocol (RDP)) and Linux (Secure Shell (SSH)) nodes.
 
 ## Pools
 
 A pool is the collection of nodes that your application runs on.
 
-Azure Batch pools build on top of the core Azure compute platform. They provide large-scale allocation, application installation, data distribution, health monitoring, and flexible adjustment ([scaling](#scaling-compute-resources)) of the number of compute nodes within a pool.
+Azure Batch pools build on top of the core Azure compute platform. They provide large-scale allocation, application installation, data distribution, health monitoring, and flexible adjustment ([scaling](#automatic-scaling-policy)) of the number of compute nodes within a pool.
 
 Every node that is added to a pool is assigned a unique name and IP address. When a node is removed from a pool, any changes that are made to the operating system or files are lost, and its name and IP address are released for future use. When a node leaves a pool, its lifetime is over.
 
 A pool can be used only by the Batch account in which it was created. A Batch account can create multiple pools to meet the resource requirements of the applications it will run.
 
 The pool can be created manually, or automatically by the Batch service when you specify the work to be done. When you create a pool, you can specify the following attributes:
 
-- [Node operating system and version](compute-node-operating-system-and-version)
+- [Node operating system and version](#compute-node-operating-system-and-version)
 - [Node type and target number of nodes](#node-type-and-target)
 - [Size of the compute nodes](#node-size)
-- [Automatic scaling policy](#scaling-policy)
+- [Automatic scaling policy](#automatic-scaling-policy)
 - [Task scheduling policy](#task-scheduling-policy)
 - [Communication status](#communication-status)
 - [Start tasks for compute nodes](#start-tasks)
 - [Application packages](#application-packages)
-- [Network configuration](#network-configuration)
+- [Virtual network (VNet) and firewall configuration](#virtual-network-vnet-and-firewall-configuration)
 - [Lifetime](#pool-and-compute-node-lifetime)
 
 > [!IMPORTANT]
@@ -153,7 +153,7 @@ You can specify application packages to deploy to the compute nodes in the pool.
 
 For more information about using application packages to deploy your applications to your Batch nodes, see [Deploy applications to compute nodes with Batch application packages](batch-application-packages.md).
 
-## Virtual network (VNet) and firewall configuration 
+## Virtual network (VNet) and firewall configuration
 
 When you provision a pool of compute nodes in Batch, you can associate the pool with a subnet of an Azure [virtual network (VNet)](../virtual-network/virtual-networks-overview.md). To use an Azure VNet, the Batch client API must use Azure Active Directory (AD) authentication. Azure Batch support for Azure AD is documented in [Authenticate Batch service solutions with Active Directory](batch-aad-auth.md).  
 
