Skip to content

Commit a31d431

Browse files
committed
fixing issues
1 parent b5f2597 commit a31d431

File tree

2 files changed

+16
-16
lines changed

2 files changed

+16
-16
lines changed

articles/cognitive-services/language-service/concepts/migrate-from-text-analytics-v2.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,13 @@ If your applications are using version 2.1 of the Text Analytics API, this artic
2121
> [!TIP]
2222
> Want to use the latest version of the API in your application? See the [sentiment analysis](../sentiment-opinion-mining/how-to/call-api.md) how-to article and [quickstart](../sentiment-opinion-mining/quickstart.md) for information on the current version of the API.
2323
24-
### Feature changes
24+
## Feature changes
2525

2626
Sentiment Analysis in version 2.1 returns sentiment scores between 0 and 1 for each document sent to the API, with scores closer to 1 indicating more positive sentiment. The current version of this feature returns sentiment labels (such as "positive" or "negative") for both the sentences and the document as a whole, and their associated confidence scores.
2727

28-
### Steps to migrate
28+
## Steps to migrate
2929

30-
#### REST API
30+
### REST API
3131

3232
If your application uses the REST API, update its request endpoint to use the [current endpoint](../sentiment-opinion-mining/quickstart.md?pivots=rest-api) for sentiment analysis. For example:`https://<your-custom-subdomain>.cognitiveservices.azure.com/text/analytics/v3.1/sentiment`. You will also need to update the application to use the sentiment labels returned in the [API's response](../sentiment-opinion-mining/how-to/call-api.md).
3333

@@ -36,7 +36,7 @@ See the reference documentation for examples of the JSON response.
3636
* [Version 3.0](https://westus.dev.cognitive.microsoft.com/docs/services/TextAnalytics-v3-0/operations/Sentiment)
3737
* [Version 3.1](https://westcentralus.dev.cognitive.microsoft.com/docs/services/TextAnalytics-v3-1/operations/Sentiment)
3838

39-
#### Client libraries
39+
### Client libraries
4040

4141
To use the latest version of the sentiment analysis client library, you will need to download the latest software package in the `Azure.AI.TextAnalytics` namespace. The [quickstart article](../sentiment-opinion-mining/quickstart.md) lists the commands you can use for your preferred language, with example code.
4242

@@ -51,13 +51,13 @@ To use the latest version of the sentiment analysis client library, you will nee
5151
> * [Quickstart](../entity-linking/quickstart.md)
5252
> * [how to call the API](../entity-linking/how-to/call-api.md)
5353
54-
### Feature changes
54+
## Feature changes
5555

5656
In version 2.1, the Text Analytics API uses one endpoint for Named Entity Recognition (NER) and entity linking. The current version of this feature provides expanded named entity detection, and uses separate endpoints for NER and entity linking requests. Additionally, you can use another feature offered in the Language service that lets you detect [detect personal (pii) and health (phi) information](../personally-identifiable-information/overview.md).
5757

58-
### Steps to migrate
58+
## Steps to migrate
5959

60-
#### REST API
60+
### REST API
6161

6262
If your application uses the REST API, update its request endpoint to the [current endpoints](../named-entity-recognition/quickstart.md?pivots=rest-api) for NER and/or entity linking. For example:
6363

@@ -74,7 +74,7 @@ See the reference documentation for examples of the JSON response.
7474
* [Version 3.0](https://westus.dev.cognitive.microsoft.com/docs/services/TextAnalytics-v3-0/operations/EntitiesRecognitionGeneral)
7575
* [Version 3.1](https://westcentralus.dev.cognitive.microsoft.com/docs/services/TextAnalytics-v3-1/operations/EntitiesRecognitionGeneral)
7676

77-
#### Client libraries
77+
### Client libraries
7878

7979
To use the latest version of the NER and entity linking client libraries, you will need to download the latest software package in the `Azure.AI.TextAnalytics` namespace. The quickstart article for [Named Entity Recognition](../named-entity-recognition/quickstart.md) and [entity linking](../entity-linking/quickstart.md) lists the commands you can use for your preferred language, with example code.
8080

@@ -112,13 +112,13 @@ The following table lists the entity categories returned for NER v2.1.
112112
> [!TIP]
113113
> Want to use the latest version of the API in your application? See the [language detection](../language-detection/how-to/call-api.md) how-to article and [quickstart](../language-detection/quickstart.md) for information on the current version of the API.
114114
115-
### Feature changes
115+
## Feature changes
116116

117117
The language detection feature output has changed in the current version. The JSON response will contain `ConfidenceScore` instead of `score`. The current version also only returns one language in a `detectedLanguage` attribute for each document.
118118

119-
### Steps to migrate
119+
## Steps to migrate
120120

121-
#### REST API
121+
### REST API
122122

123123
If your application uses the REST API, update its request endpoint to the [current endpoint](../language-detection/quickstart.md?pivots=rest-api) for language detection. For example:`https://<your-custom-subdomain>.cognitiveservices.azure.com/text/analytics/v3.1/languages`. You will also need to update the application to use `ConfidenceScore` instead of `score` in the [API's response](../language-detection/how-to/call-api.md).
124124

@@ -136,13 +136,13 @@ To use the latest version of the sentiment analysis client library, you will nee
136136
> [!TIP]
137137
> Want to use the latest version of the API in your application? See the [key phrase extraction](../key-phrase-extraction/how-to/call-api.md) how-to article and [quickstart](../key-phrase-extraction/quickstart.md) for information on the current version of the API.
138138
139-
### Feature changes
139+
## Feature changes
140140

141141
The key phrase extraction feature currently has not changed outside of the endpoint version.
142142

143-
### Steps to migrate
143+
## Steps to migrate
144144

145-
#### REST API
145+
### REST API
146146

147147
If your application uses the REST API, update its request endpoint to the [current endpoint](../key-phrase-extraction/quickstart.md?pivots=rest-api) for key phrase extraction. For example: `https://<your-custom-subdomain>.api.cognitiveservices.azure.com/text/analytics/v3.1/keyPhrases`
148148

@@ -151,7 +151,7 @@ See the reference documentation for examples of the JSON response.
151151
* [Version 3.0](https://westus.dev.cognitive.microsoft.com/docs/services/TextAnalytics-v3-0/operations/KeyPhrases)
152152
* [Version 3.1](https://westcentralus.dev.cognitive.microsoft.com/docs/services/TextAnalytics-v3-1/operations/KeyPhrases)
153153

154-
#### Client libraries
154+
### Client libraries
155155

156156
To use the latest version of the sentiment analysis client library, you will need to download the latest software package in the `Azure.AI.TextAnalytics` namespace. The [quickstart article](../key-phrase-extraction/quickstart.md) lists the commands you can use for your preferred language, with example code.
157157

articles/cognitive-services/language-service/concepts/migrate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ On November 2nd 2021, Azure Cognitive Service for Language was released into pub
1717

1818
## Do I need to migrate to the language service if I am using Text Analytics?
1919

20-
Text Analytics has been incorporated into the language service, and its features are still available. If you were using Text Analytics, your applications should continue to work without breaking changes. you can also see the [Text Analytics v2 migration guide](migrate-from-text-analytics-v2.md), if you need to update an older application.
20+
Text Analytics has been incorporated into the language service, and its features are still available. If you were using Text Analytics, your applications should continue to work without breaking changes. You can also see the [Text Analytics v2 migration guide](migrate-from-text-analytics-v2.md), if you need to update an older application.
2121

2222
Consider using one of the available quickstart articles to see the latest information on service endpoints, and API calls.
2323

0 commit comments

Comments
 (0)