[Cogsvcs] LUIS - tutorial - regex

Author: diberry

.openpublishing.redirection.json

@@ -567,6 +567,11 @@
       "redirect_url": "/azure/cognitive-services//QnAMaker/Quickstarts/get-answer-from-knowledge-base-using-url-tool",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/cognitive-services/LUIS/luis-quickstart-intents-regex-entity.md",
+      "redirect_url": "/azure/cognitive-services/LUIS/tutorial-regex-entity",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/cognitive-services/LUIS/luis-quickstart-intent-and-sentiment-analysis.md",
       "redirect_url": "/azure/cognitive-services/LUIS/tutorial-publish-settings",

articles/cognitive-services/LUIS/luis-quickstart-intents-regex-entity.md

@@ -1,7 +1,7 @@
 ---
 title: Regular expression entity type - LUIS
 titleSuffix: Azure Cognitive Services
-description: A regular expression is best for raw utterance text. It ignores case and ignores cultural variant.  Regular expression matching is applied after spell-check alterations at the character level, not the token level.   
+description: A regular expression is best for raw utterance text. It ignores case and ignores cultural variant.  Regular expression matching is applied after spell-check alterations at the character level, not the token level.
 services: cognitive-services
 author: diberry
 manager: nitinme
@@ -11,16 +11,16 @@ ms.topic: reference
 ms.date: 09/29/2019
 ms.author: diberry
 ---
-# Regular expression entity 
+# Regular expression entity
 
 A regular expression entity extracts an entity based on a regular expression pattern you provide.
 
-A regular expression is best for raw utterance text. It ignores case and ignores cultural variant.  Regular expression matching is applied after spell-check alterations at the character level, not the token level. If the regular expression is too complex, such as using many brackets, you're not able to add the expression to the model. Uses part but not all of the [.NET Regex](https://docs.microsoft.com/dotnet/standard/base-types/regular-expressions) library. 
+A regular expression is best for raw utterance text. It ignores case and ignores cultural variant.  Regular expression matching is applied after spell-check alterations at the character level, not the token level. If the regular expression is too complex, such as using many brackets, you're not able to add the expression to the model. Uses part but not all of the [.NET Regex](https://docs.microsoft.com/dotnet/standard/base-types/regular-expressions) library.
 
 **The entity is a good fit when:**
 
 * The data are consistently formatted with any variation that is also consistent.
-* The regular expression does not need more than 2 levels of nesting. 
+* The regular expression does not need more than 2 levels of nesting.
 
 ![Regular expression entity](./media/luis-concept-entities/regex-entity.png)
 
@@ -30,7 +30,7 @@ Regular expressions may match more than you expect to match. An example of this
 
 ```javascript
 (plus )?(zero|one|two|three|four|five|six|seven|eight|nine)(\s+(zero|one|two|three|four|five|six|seven|eight|nine))*
-``` 
+```
 
 This regex expression also matches any words that end with these numbers, such as `phone`. In order to fix issues like this, make sure the regex matches takes into account word boundaries. The regex to use word boundaries for this example is used in the following regex:
 
@@ -96,8 +96,8 @@ This is the JSON if `verbose=true` is set in the query string:
 }
 ```
 
-* * * 
+* * *
 
 ## Next steps
 
-In this [tutorial](luis-quickstart-intents-regex-entity.md), create an app to extract consistently-formatted data from an utterance using the **Regular Expression** entity.
+In this [tutorial](tutorial-regex-entity.md), create an app to extract consistently-formatted data from an utterance using the **Regular Expression** entity.