Merge pull request #196264 from shshubhe/patch-23

Update adding-synonyms.md

Author: PRMerger16

articles/cognitive-services/language-service/question-answering/tutorials/adding-synonyms.md

@@ -73,11 +73,16 @@ For the question and answer pair “Fix problems with Surface Pen”, we compare
 
 As you can see, when `troubleshoot` was not added as a synonym, we got a low confidence response to the query “How to troubleshoot your surface pen”. However, after we add `troubleshoot` as a synonym to “fix problems”, we received the correct response to the query with a higher confidence score. Once, these synonyms were added, the relevance of results improved thereby improving user experience.
 
-> [!NOTE]
+> [!IMPORTANT]
 > Synonyms are case insensitive. Synonyms also might not work as expected if you add stop words as synonyms. The list of stop words can be found here: [List of stop words](https://github.com/Azure-Samples/azure-search-sample-data/blob/master/STOPWORDS.md).
 > For instance, if you add the abbreviation **IT** for Information technology, the system might not be able to recognize Information Technology because **IT** is a stop word and is filtered when a query is processed.
 > Synonyms do not allow these special characters: ',', '?', ':', ';', '\"', '\'', '(', ')', '{', '}', '[', ']', '-', '+', '.', '/', '!', '*', '-', '_', '@', '#' 
 
+## Notes
+* Synonyms can be added in any order. The ordering is not considered in any computational logic.
+* Special characters are not allowed for synonyms. For hyphenated words like "COVID-19", they are treated the same as "COVID 19", and "space" can be used as a term separator.
+* In case of overlapping synonym words between 2 sets of alterations, it may have unexpected results and it is not recommended to use overlapping sets.
+
 ## Next steps
 
 > [!div class="nextstepaction"]