Skip to content

Commit ebb5ee1

Browse files
authored
Merge pull request #120675 from AzureMentor/patch-52
Improve legibility of "When to add synonyms to a project" section
2 parents 6b98014 + 26b1824 commit ebb5ee1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/ai-services/language-service/question-answering/concepts/best-practices.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -63,9 +63,9 @@ Custom question answering provides the flexibility to use synonyms at the projec
6363

6464
For better relevance, you need to provide a list of acronyms that the end user intends to use interchangeably. The following is a list of acceptable acronyms:
6565

66-
`MSFT` – Microsoft
67-
`ID` – Identification
68-
`ETA` – Estimated time of Arrival
66+
* `MSFT` – Microsoft
67+
* `ID` – Identification
68+
* `ETA` – Estimated time of Arrival
6969

7070
Other than acronyms, if you think your words are similar in context of a particular domain and generic language models won’t consider them similar, it’s better to add them as synonyms. For instance, if an auto company producing a car model X receives queries such as “my car’s audio isn’t working” and the project has questions on “fixing audio for car X”, then we need to add ‘X’ and ‘car’ as synonyms.
7171

0 commit comments

Comments
 (0)