remove absolute

Author: v-thepet

articles/batch/batch-task-output-file-conventions.md

@@ -31,7 +31,7 @@ For other scenarios, you might want to consider a different approach. For more i
 
 ## What is the Batch File Conventions standard?
 
-The [Batch File Conventions standard](https://learn.microsoft.com/dotnet/api/microsoft.azure.batch.conventions.files) provides a naming scheme for the destination containers and blob paths to which your output files are written. Files persisted to Azure storage that follow the standard are [automatically viewable in the Azure portal](#view-output-files-in-the-azure-portal). 
+The [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files) provides a naming scheme for the destination containers and blob paths to which your output files are written. Files persisted to Azure storage that follow the standard are [automatically viewable in the Azure portal](#view-output-files-in-the-azure-portal). 
 
 The File Conventions library for .NET automatically names your storage containers and task output files according to the standard. The library also provides methods to query output files in Azure Storage. You can query by job ID, task ID, or purpose.
 
@@ -176,7 +176,7 @@ foreach (CloudTask task in myJob.ListTasks())
 
 ## View output files in the Azure portal
 
-If your task output files use the [Batch File Conventions standard](https://learn.microsoft.com/dotnet/api/microsoft.azure.batch.conventions.files), you can view the files in the Azure portal. 
+If your task output files use the [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files), you can view the files in the Azure portal. 
 
 To enable the display of your output files in the portal, you must satisfy the following requirements:
 
@@ -210,7 +210,7 @@ The [PersistOutputs](https://github.com/Azure/azure-batch-samples/tree/master/CS
 
 The Batch File Conventions library for .NET is available on [NuGet](https://www.nuget.org/packages/Microsoft.Azure.Batch.Conventions.Files). The library extends the [CloudJob](/dotnet/api/microsoft.azure.batch.cloudjob) and [CloudTask](/dotnet/api/microsoft.azure.batch.cloudtask) classes with new methods. For more information, see the [File Conventions library reference documentation](/dotnet/api/microsoft.azure.batch.conventions.files).
 
-The [File Conventions library source code](https://learn.microsoft.com/dotnet/api/microsoft.azure.batch.conventions.files) is available on GitHub. 
+The [File Conventions library source code](/dotnet/api/microsoft.azure.batch.conventions.files) is available on GitHub. 
 
 ### Next steps
 

articles/batch/batch-task-output-files.md

@@ -26,7 +26,7 @@ Azure Batch provides more than one way to persist task output. Using the Batch s
 - You want to write code to persist task output from within your client application, without modifying the application that your task is running.
 - You want to persist output from Batch tasks and job manager tasks in pools created with the virtual machine configuration.
 - You want to persist output to an Azure Storage container with an arbitrary name.
-- You want to persist output to an Azure Storage container named according to the [Batch File Conventions standard](https://learn.microsoft.com/dotnet/api/microsoft.azure.batch.conventions.files).
+- You want to persist output to an Azure Storage container named according to the [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files).
 
 If your scenario differs from those listed above, you may need to consider a different approach. For example, the Batch service API does not currently support streaming output to Azure Storage while the task is running. To stream output, consider using the Batch File Conventions library, available for .NET. For other languages, you'll need to implement your own solution. For more information about other options, see [Persist job and task output to Azure Storage](batch-task-output.md).
 
@@ -190,7 +190,7 @@ there are many contributing factors to upload performance, including the size of
 
 ## Use the Batch service API with the Batch File Conventions standard
 
-When you persist task output with the Batch service API, you can name your destination container and blobs however you like. You can also choose to name them according to the [Batch File Conventions standard](https://learn.microsoft.com/dotnet/api/microsoft.azure.batch.conventions.files). The File Conventions standard determines the names of the destination container and blob in Azure Storage for a given output file based on the names of the job and task. If you do use the File Conventions standard for naming output files, then your output files are available for viewing in the [Azure portal](https://portal.azure.com).
+When you persist task output with the Batch service API, you can name your destination container and blobs however you like. You can also choose to name them according to the [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files). The File Conventions standard determines the names of the destination container and blob in Azure Storage for a given output file based on the names of the job and task. If you do use the File Conventions standard for naming output files, then your output files are available for viewing in the [Azure portal](https://portal.azure.com).
 
 If you are developing in C#, you can use the methods built into the [Batch File Conventions library for .NET](https://www.nuget.org/packages/Microsoft.Azure.Batch.Conventions.Files). This library creates the properly named containers and blob paths for you. For example, you can call the API to get the correct name for the container, based on the job name:
 

articles/batch/batch-task-output.md

@@ -36,7 +36,7 @@ For more information, see [Persist task data to Azure Storage with the Batch ser
 
 ### Batch File Conventions library
 
-The [Batch File Conventions standard](https://learn.microsoft.com/dotnet/api/microsoft.azure.batch.conventions.files) is an optional set of conventions for naming task output files in Azure Storage. The standard provides naming conventions for a file's destination container and blob path, based on the names of the job and task.
+The [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files) is an optional set of conventions for naming task output files in Azure Storage. The standard provides naming conventions for a file's destination container and blob path, based on the names of the job and task.
 
 It's optional to use the File Conventions standard for naming your output data files. You can choose to name the destination container and blob path instead. If you do use the File Conventions standard, then you can view your output files in the [Azure portal](https://portal.azure.com). 
 
@@ -46,7 +46,7 @@ For more information, see [Persist job and task data to Azure Storage with the B
 
 ### Batch File Conventions standard
 
-If you're using a language other than .NET, you can implement the [Batch File Conventions standard](https://learn.microsoft.com/dotnet/api/microsoft.azure.batch.conventions.files) in your own application. Use this approach when:
+If you're using a language other than .NET, you can implement the [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files) in your own application. Use this approach when:
 
 - You want to use a common naming scheme.
 - You want to view task output in the [Azure portal](https://portal.azure.com).