remove comment line and fix link?

Author: MaryaBelanger

src/content/effective-dart/usage.md

@@ -8,6 +8,7 @@ prevpage:
   url: /effective-dart/documentation
   title: Documentation
 ---
+<?code-excerpt plaster="none"?>
 <?code-excerpt replace="/([A-Z]\w*)\d\b/$1/g"?>
 <?code-excerpt path-base="misc/lib/effective_dart"?>
 
@@ -325,7 +326,7 @@ Of course, if `null` is a valid initialized value for the variable,
 then it probably does make sense to have a separate boolean field.
 
 
-### CONSIDER work arounds to bypass type promotion limitations
+### CONSIDER work arounds to enable type promotion for nullable fields
 
 Checking that a nullable variable is not equal to `null` promotes the variable
 to a non-nullable type. That lets you access members on the variable and pass it
@@ -355,7 +356,6 @@ class UploadException {
       return 'Could not complete upload to ${response.url} '
           '(error code ${response.errorCode}): ${response.reason}.';
     }
-// ···
     return 'Could not upload (no response).';
   }
 }
@@ -374,7 +374,6 @@ class UploadException {
 
   @override
   String toString() {
-    // ···
     final response = this.response;
     if (response != null) {
       return 'Could not complete upload to ${response.url} '

src/content/guides/whats-new.md

@@ -126,7 +126,7 @@ we made the following changes to this site:
 * Reorganized and simplified site infrastructure across the board, in preparation
   to [move away from using Jekyll][].
 
-[type promotion]: /effective-dart/usage#consider-assigning-a-nullable-field-to-a-local-variable-to-enable-type-promotion
+[type promotion]: /effective-dart/usage#consider-work-arounds-to-enable-type-promotion-for-nullable-fields
 [Understanding Null Safety]: /null-safety/understanding-null-safety
 [C interop]: /interop/c-interop#native-assets
 [Breaking changes]: /resources/breaking-changes