Update links and and documentation based on feedback from open source repo

- Harden URLs by linking to the official docs rather than lines of code.
- Fix link to Angular (not AngularDart) GitHub repo.
- Add the parenthesis to method names to match other documentation.

PiperOrigin-RevId: 225335014

Author: nshahan

angular_components/lib/simple_html/README.md

@@ -13,7 +13,7 @@ HTML in the following use cases:
 Mixing these features with text that cannot appear verbatim in the template (due
 to, for example, use of the `Intl` library for localization) is otherwise
 difficult. This component is the recommended alternative to calling methods like
-[`bypassSecurityTrustHtml`](https://github.com/dart-lang/angular/blob/master/angular/lib/src/security/dom_sanitization_service.dart#L53)
+[`bypassSecurityTrustHtml()`](https://pub.dartlang.org/documentation/angular/latest/angular.security/DomSanitizationService/bypassSecurityTrustHtml.html)
 when inserting HTML into the DOM.
 
 
@@ -44,7 +44,7 @@ The alternatives include:
         and the permitted URLs by the
         [_SameOriginUriPolicy](https://raw.githubusercontent.com/dart-lang/sdk/master/sdk/lib/html/dart2js/html_dart2js.dart).
 *   Using the `[safeInnerHtml]` directive, or the `[innerHtml]` directive with a
-    `SafeHtml` argument generated by `bypassSecurityTrustHtml`.
+    `SafeHtml` argument generated by `bypassSecurityTrustHtml()`.
     *   This is generally not secure, since absolutely all tags are allowed and
         there is no further line of defense between you and
         [XSS](https://en.wikipedia.org/wiki/Cross-site_scripting). This should
@@ -108,9 +108,9 @@ You have a few options:
     If `seeHelpCenterMessage` is a plain string, it will be strictly sanitized
     and disallowed elements silently removed. To work around this,
     `seeHelpCenterMessage` may instead return a
-    [`SafeHtml`](https://github.com/dart-lang/angular/blob/master/angular/lib/src/security/dom_sanitization_service.dart#L5)
+    [`SafeHtml`](https://pub.dartlang.org/documentation/angular/latest/angular.security/SafeHtml-class.html)
     object. This object can be constructed by calling
-    [`bypassSecurityTrustHtml`](https://github.com/dart-lang/angular/blob/master/angular/lib/src/security/dom_sanitization_service.dart#L53)
+    [`bypassSecurityTrustHtml()`](https://pub.dartlang.org/documentation/angular/latest/angular.security/DomSanitizationService/bypassSecurityTrustHtml.html)
     on the string. However, this is very dangerous because it disables _all_
     sanitization and allows all tags (even `<script>`). If the string
     accidentally contains user-controlled data, or the translator made a mistake
@@ -251,17 +251,17 @@ The following is not yet supported:
 
 ## Migration
 
-Migration from an existing `bypassSecurityTrustHtml` solution is generally
+Migration from an existing `bypassSecurityTrustHtml()` solution is generally
 straightforward. Basic steps:
 
 1.  Import the Dart library
     `package:angular_components/simple_html/simple_html.dart` in your component
     file.
 1.  Add the `SimpleHtmlComponent` to your
-    [@Component](https://github.com/angular/angular/blob/master/packages/core/src/metadata/directives.ts#L101)'s
+    [@Component](https://pub.dartlang.org/documentation/angular/latest/angular/Component-class.html)'s
     directive list.
-1.  For each message that previously used `bypassSecurityTrustHtml`, remove that
-    call and use the string directly.
+1.  For each message that previously used `bypassSecurityTrustHtml()`, remove
+    that call and use the string directly.
 1.  In your template file, bind the message with either:
     *   `<simple-html [contents]="msg"></simple-html>` rather than `<span
         [innerHtml]="msg"></span>` (if only inline elements are required).
@@ -280,7 +280,7 @@ so, if you need other display types, you will need to apply a custom CSS class
 or wrap it inside another element. Likewise `<simple-html-block>` is a
 block-level element and therefore should not be placed inside inline elements.
 
-### Testing {#testing}
+### Testing
 
 The easiest way to debug quickly is to test that the text appears correctly in a
 local build of your application. Due to SimpleHtml's atomic updates, you will