minor change

Author: lucciz01

support/power-platform/power-automate/desktop-flows/browser-automation/web-automation-action-fails-runtime.md

@@ -30,7 +30,7 @@ To solve this issue, you can try to [repair the CSS selector](/power-automate/de
 
 ## Resolution 2
 
-To solve this issue, you can manually create a new robust CSS selector. It will be able to locate the element of interest even though the HTML structure changes. For more information, see [Build a custom selector](/power-automate/desktop-flows/build-custom-selectors).
+To solve this issue, you can manually create a new robust CSS selector. It will be able to locate the element of interest even though the HTML structure changes.
 
 To achieve that, capture again the web element after the failure, and compare the new CSS selector with the old one.
 CSS selectors can be reviewed and edited through the **Selector builder** window:
@@ -50,3 +50,5 @@ Examples:
 - The selector contains an element that has a class that is dynamic, such as `div[class="some_class123"]`. This can be modified to `div[class^="some_class"]` ("Starts with" operator).
 - The selector contains an element that has many dynamic attributes such as `div[class="some_class123"][id="some_id123"] > a[id="some_id"]`. This can be modified to `a[id="some_id"]` (omitting the first part completely).
 - The element of interest has some static text - the selector can be modified to include only that text. For example, `div[class="some_class123"][id="some_id123"] > a[id="some_id"]` could be modified to `a:contains("the_text_we_see_on_the_webpage")`.
+
+For more information, see [Build a custom selector](/power-automate/desktop-flows/build-custom-selectors).