Merge pull request #234589 from aahill/ta4h-article-fixes-2

adding ta4h references + commented blocks

Author: denrea

articles/cognitive-services/language-service/custom-text-analytics-for-health/concepts/data-formats.md

@@ -147,7 +147,7 @@ Your Labels file should be in the `json` format below to be used when importing
 | `prebuilts` | `MedicationName` | The name of the prebuilt component populating the prebuilt entity. [Prebuilt entities](../../text-analytics-for-health/concepts/health-entity-categories.md) are automatically loaded into your project by default but you can extend them with list components in your labels file.  | `MedicationName` |
 | `documents` | | Array containing all the documents in your project and list of the entities labeled within each document. | [] |
 | `location` | `{DOCUMENT-NAME}` |  The location of the documents in the storage container. Since all the documents are in the root of the container this should be the document name.|`doc1.txt`|
-| `dataset` | `{DATASET}` |  The test set to which this file goes to when split before training. <!--Learn more about data splitting [here](../how-to/train-model.md#data-splitting).--> Possible values for this field are `Train` and `Test`.      |`Train`|
+| `dataset` | `{DATASET}` |  The test set to which this file goes to when split before training. Learn more about data splitting [here](../how-to/train-model.md#data-splitting). Possible values for this field are `Train` and `Test`.      |`Train`|
 | `regionOffset` |  |  The inclusive character position of the start of the text.      |`0`|
 | `regionLength` |  |  The length of the bounding box in terms of UTF16 characters. Training only considers the data in this region.      |`500`|
 | `category` |  |  The type of entity associated with the span of text specified. | `Entity1`|
@@ -166,4 +166,4 @@ Your Labels file should be in the `json` format below to be used when importing
 ## Next steps
 * You can import your labeled data into your project directly. Learn how to [import project](../how-to/create-project.md#import-project)
 * See the [how-to article](../how-to/label-data.md)  more information about labeling your data. 
- <!--* When you're done labeling your data, you can [train your model](../how-to/train-model.md).-->  
+* When you're done labeling your data, you can [train your model](../how-to/train-model.md).  

articles/cognitive-services/language-service/custom-text-analytics-for-health/concepts/evaluation-metrics.md

@@ -15,7 +15,7 @@ ms.custom: language-service-custom-ta4h
 
 # Evaluation metrics for custom Text Analytics for health models
 
-<!--Your [dataset is split](../how-to/train-model.md#data-splitting) into two parts: a set for training, and a set for testing. The training set is used to train the model, while the testing set is used as a test for model after training to calculate the model performance and evaluation. The testing set is not introduced to the model through the training process, to make sure that the model is tested on new data.-->
+Your [dataset is split](../how-to/train-model.md#data-splitting) into two parts: a set for training, and a set for testing. The training set is used to train the model, while the testing set is used as a test for model after training to calculate the model performance and evaluation. The testing set is not introduced to the model through the training process, to make sure that the model is tested on new data.
 
 Model evaluation is triggered automatically after training is completed successfully. The evaluation process starts by using the trained model to predict user defined entities for documents in the test set, and compares them with the provided data labels (which establishes a baseline of truth). The results are returned so you can review the model’s performance. User defined entities are **included** in the evaluation factoring in Learned and List components; Text Analytics for health prebuilt entities are **not** factored in the model evaluation. For evaluation, custom Text Analytics for health uses the following metrics:
 
@@ -149,7 +149,5 @@ Similarly,
 ## Next steps
 
 * [Custom text analytics for health overview](../overview.md)
-<!--
 * [View a model's performance in Language Studio](../how-to/view-model-evaluation.md)
-* [Train a model](../how-to/train-model.md)
--->
+* [Train a model](../how-to/train-model.md)

articles/cognitive-services/language-service/custom-text-analytics-for-health/how-to/label-data.md

@@ -22,7 +22,7 @@ Data labeling is a crucial step in development lifecycle. In this step, you  lab
 Before you can label your data, you need:
 
 * A successfully [created project](create-project.md) with a configured Azure blob storage account
-<!--* Text data that [has been uploaded](design-schema.md#data-preparation) to your storage account.-->
+* Text data that [has been uploaded](design-schema.md#data-preparation) to your storage account.
 
 See the [project development lifecycle](../overview.md#project-development-lifecycle) for more information.
 
@@ -34,7 +34,7 @@ As you label your data, keep in mind:
 
 * You can't add labels for Text Analytics for health entities as they're pretrained prebuilt entities. You can only add labels to new entity categories that you defined during schema definition. 
 
-<!--If you want to improve the recall for a prebuilt entity, you can extend it by adding a list component while you are [defining your schema](design-schema.md).-->
+If you want to improve the recall for a prebuilt entity, you can extend it by adding a list component while you are [defining your schema](design-schema.md).
 
 * In general, more labeled data leads to better results, provided the data is labeled accurately.
 
@@ -83,7 +83,7 @@ Use the following steps to label your data:
 
 6. In the right side pane under the **Labels** pivot you can find all the entity types in your project and the count of labeled instances per each. The prebuilt entities will be shown for reference but you will not be able to label for these prebuilt entities as they are pretrained.
 
-7. In the bottom section of the right side pane you can add the current document you are viewing to the training set or the testing set. By default all the documents are added to your training set. <!--Learn more about [training and testing sets](train-model.md#data-splitting) and how they are used for model training and evaluation.-->
+7. In the bottom section of the right side pane you can add the current document you are viewing to the training set or the testing set. By default all the documents are added to your training set. See [training and testing sets](train-model.md#data-splitting) for information on how they are used for model training and evaluation.
 
     > [!TIP]
     > If you are planning on using **Automatic** data splitting, use the default option of assigning all the documents into your training set.
@@ -107,6 +107,4 @@ You cannot delete any of the Text Analytics for health pretrained entities becau
 
 ## Next steps
 
-[Custom text analytics for health overview](../overview.md)
-
-<!--After you've labeled your data, you can begin [training a model](train-model.md) that will learn based on your data.-->
+After you've labeled your data, you can begin [training a model](train-model.md) that will learn based on your data.

articles/cognitive-services/language-service/custom-text-analytics-for-health/how-to/view-model-evaluation.md

@@ -28,7 +28,7 @@ Before viewing model evaluation, you need:
 * A successfully [created project](create-project.md) with a configured Azure blob storage account.
 * Text data that [has been uploaded](design-schema.md#data-preparation) to your storage account.
 * [Labeled data](label-data.md)
-<!--* A [successfully trained model](train-model.md)-->
+* A [successfully trained model](train-model.md)
 
 
 ## Model details
@@ -72,5 +72,5 @@ There are several metrics you can use to evaluate your mode. See the [performanc
 
 ## Next steps
 
-<!--* [Deploy your model](deploy-model.md)-->
+* [Deploy your model](deploy-model.md)
 * Learn about the [metrics used in evaluation](../concepts/evaluation-metrics.md). 

articles/cognitive-services/language-service/custom-text-analytics-for-health/includes/language-studio/test-model.md

@@ -21,7 +21,7 @@ To test your deployed models from within the [Language Studio](https://aka.ms/La
 
 5. Click on **Run the test** from the top menu.
 
-6. In the **Result** tab, you can see the extracted entities from your text and their types. You can also view the JSON response under the **JSON** tab. <!--[learn more](../rest-api/get-results.md#response-body) about the structure of the JSON response.-->
+6. In the **Result** tab, you can see the extracted entities from your text and their types. You can also view the [JSON response](../../how-to/call-api.md#get-task-results) under the **JSON** tab.
 
     :::image type="content" source="../../media/test-model-results.png" alt-text="A screenshot showing the deployment testing screen in Language Studio." lightbox="../../media/test-model-results.png":::
 

articles/cognitive-services/language-service/custom-text-analytics-for-health/includes/language-studio/train-model.md

@@ -20,9 +20,7 @@ To start training your model from within the [Language Studio](https://aka.ms/La
 
     :::image type="content" source="../../media/train-model.png" alt-text="A screenshot showing the training job creation screen in Language Studio." lightbox="../../media/train-model.png":::
 
-4. Select data splitting method. You can choose **Automatically splitting the testing set from training data** where the system will split your labeled data between the training and testing sets, according to the specified percentages. Or you can **Use a manual split of training and testing data**, this option is only enabled if you have added documents to your testing set.
-
-<!-- see [data labeling](../../how-to/tag-data.md) and [how to train a model](../../how-to/train-model.md#data-splitting) for information about data splitting. -->
+4. Select data splitting method. You can choose **Automatically splitting the testing set from training data** where the system will split your labeled data between the training and testing sets, according to the specified percentages. Or you can **Use a manual split of training and testing data**, this option is only enabled if you have added documents to your testing set. See [data labeling](../../how-to/label-data.md) and [how to train a model](../../how-to/train-model.md#data-splitting) for information about data splitting.
 
 5. Click on the **Train** button.
 

articles/cognitive-services/language-service/custom-text-analytics-for-health/includes/quickstarts/language-studio.md

@@ -19,13 +19,13 @@ ms.author: aahi
 
 ## Create a new Azure Language resource and Azure storage account
 
-Before you can use custom Text Analytics for health, you'll need to create an Azure Language resource, which will give you the credentials that you need to create a project and start training a model. You'll also need an Azure storage account, where you can upload your dataset that will be used to build your model.
+Before you can use custom Text Analytics for health, you need to create an Azure Language resource, which will give you the credentials that you need to create a project and start training a model. You'll also need an Azure storage account, where you can upload your dataset that is used to build your model.
 
 > [!IMPORTANT]
 > To quickly get started, we recommend creating a new Azure Language resource using the steps provided in this article. Using the steps in this article will let you create the Language resource and storage account at the same time, which is easier than doing it later.
 >
-<!-- If you have a pre-existing resource that you'd like to use, you will need to connect it to storage account. See [guidance to using a pre-existing resource](../../how-to/create-project.md#using-a-pre-existing-language-resource) for information.
--->
+> If you have a pre-existing resource that you'd like to use, you will need to connect it to storage account. For more information, see [guidance to using a pre-existing resource](../../how-to/create-project.md#using-a-pre-existing-language-resource).
+
 [!INCLUDE [create a new resource from the Azure portal](../resource-creation-azure-portal.md)]
 
 > [!div class="nextstepaction"]

articles/cognitive-services/language-service/custom-text-analytics-for-health/includes/quickstarts/rest-api.md

@@ -22,10 +22,9 @@ Before you can use custom Text Analytics for health, you'll need to create an Az
 
 > [!IMPORTANT]
 > To get started quickly, we recommend creating a new Azure Language resource using the steps provided in this article, which will let you create the Language resource, and create and/or connect a storage account at the same time, which is easier than doing it later.
+>
+> If you have a pre-existing resource that you'd like to use, you will need to connect it to storage account. See [create project](../../how-to/create-project.md#using-a-pre-existing-language-resource) for more information.
 
-<!--
-> If you have a pre-existing resource that you'd like to use, you will need to connect it to storage account. See [create project](../../how-to/create-project.md#using-a-pre-existing-language-resource)  for information.
--->
 [!INCLUDE [create a new resource from the Azure portal](../resource-creation-azure-portal.md)]
 
 > [!div class="nextstepaction"]

articles/cognitive-services/language-service/custom-text-analytics-for-health/includes/rest-api/create-project.md

@@ -57,9 +57,9 @@ Use the following JSON in your request. Replace the placeholder values below wit
 |Key  |Placeholder|Value  | Example |
 |---------|---------|---------|--|
 | projectName | `{PROJECT-NAME}` | The name of your project. This value is case-sensitive. | `myProject` |
-| language | `{LANGUAGE-CODE}` |  A string specifying the language code for the documents used in your project. If your project is a multilingual project, choose the language code of the majority of the documents. <!--See [language support](../../language-support.md) to learn more about supported language codes.--> |`en-us`|
+| language | `{LANGUAGE-CODE}` |  A string specifying the language code for the documents used in your project. If your project is a multilingual project, choose the language code of the majority of the documents. See [language support](../../language-support.md) to learn more about supported language codes. |`en-us`|
 | projectKind | `CustomHealthcare` | Your project kind. | `CustomHealthcare` |
-| multilingual | `true`| A boolean value that enables you to have documents in multiple languages in your dataset and when your model is deployed you can query the model in any supported language (not necessarily included in your training documents. <!--See [language support](../../language-support.md) to learn more about multilingual support.-->  | `true`|
+| multilingual | `true`| A boolean value that enables you to have documents in multiple languages in your dataset and when your model is deployed you can query the model in any supported language (not necessarily ones included in your training documents). See [language support](../../language-support.md) to learn more about multilingual support.  | `true`|
 | storageInputContainerName | `{CONTAINER-NAME` | The name of your Azure storage container where you have uploaded your documents.   | `myContainer` |
 
 

articles/cognitive-services/language-service/custom-text-analytics-for-health/includes/rest-api/get-results.md

@@ -270,7 +270,7 @@ The response is a JSON document with the following parameters
 }
 
 ```
-<!--
+
 |Key|Sample Value|Description|
 |--|--|--|
 |entities|[]|An array containing all the extracted entities.|
@@ -280,12 +280,11 @@ The response is a JSON document with the following parameters
 |text|`first entity`| The text that was extracted for a specific entity.|
 |category|`MedicationName`| The name of the entity type or category corresponding to the extracted text.|
 |confidenceScore|`0.9`| A number denoting the model's certainty level of the extracted entity ranging from 0 to 1 with higher number denoting higher certainty.|
-|assertion|`certainty`| [Assertions](../../../text-analytics-for-health/concepts/assertion-detection.md) associated with the extracted entity. Assertions are only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
-|name|`Ibuprofen`| The normalized name for the [entity linking](../../../text-analytics-for-health/includes/features.md#entity-linking) associated with the extracted entity. Entity linking is only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
-|links| [] | An array containing all the results from the [entity linking](../../../text-analytics-for-health/includes/features.md#entity-linking) associated with the extracted entity. Entity linking is only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
-|dataSource| `UMLS` | The reference standard resulting from the [entity linking](../../../text-analytics-for-health/includes/features.md#entity-linking) associated with the extracted entity. Entity linking is only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
-|id| `C0020740` | The reference code resulting from the [entity linking](../../../text-analytics-for-health/includes/features.md#entity-linking) associated with the extracted entity belonging to the extracted data source. Entity linking is only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
+|assertion|`certainty`| [Assertions](../../../text-analytics-for-health/concepts/assertion-detection.md) associated with the extracted entity. Assertions are only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/overview.md?tabs=entity-linking#text-analytics-for-health-features).|
+|name|`Ibuprofen`| The normalized name for the [entity linking](../../../text-analytics-for-health/overview.md?tabs=entity-linking#text-analytics-for-health-features) associated with the extracted entity. Entity linking is only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
+|links| [] | An array containing all the results from the [entity linking](../../../text-analytics-for-health/overview.md?tabs=entity-linking#text-analytics-for-health-features) associated with the extracted entity. Entity linking is only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
+|dataSource| `UMLS` | The reference standard resulting from the [entity linking](../../../text-analytics-for-health/overview.md?tabs=entity-linking#text-analytics-for-health-features) associated with the extracted entity. Entity linking is only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
+|ID| `C0020740` | The reference code resulting from the [entity linking](../../../text-analytics-for-health/overview.md?tabs=entity-linking#text-analytics-for-health-features) associated with the extracted entity belonging to the extracted data source. Entity linking is only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
 |relations| [] | Array containing all the extracted relationships. [Relationship extraction](../../../text-analytics-for-health/concepts/relation-extraction.md) is only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
 |relationType| `DosageOfMedication` | The category of the extracted [relationship](../../../text-analytics-for-health/concepts/relation-extraction.md). Relationship extraction is only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
 |entities| `"Dosage", "Medication"` | The entities associated with the extracted relationship. Relationship extraction is only supported for prebuilt [Text Analytics for health entities](../../../text-analytics-for-health/concepts/health-entity-categories.md).|
--->