anchor.diff:    /// substantial additional information, ideally sufficient to develop a
     /// correct solution to the problem.
     ///
  -  /// In some cases, when a FlutterError is reported to the user, only the first
  +  /// In some cases, when a [FlutterError] is reported to the user, only the first
     /// line is included. For example, Flutter will typically only fully report
     /// the first exception at runtime, displaying only the first line of
     /// subsequent errors.
  
positive.code: 
  /// Class for information provided to [FlutterExceptionHandler] callbacks.
  ///
  ///  {@tool snippet}
  /// This is an example of using [FlutterErrorDetails] when calling
  /// [FlutterError.reportError].
  ///
  
negative.code: /// A [FlutterError] must start with an [ErrorSummary] and may not contain
  /// multiple summaries.
  ///
  /// In debug builds, values interpolated into the `message` are
  /// expanded and placed into [value], which is of type [List<Object>].
  /// This allows IDEs to examine values interpolated into error messages.
  ///
  /// See also:
  ///
  ///  * [ErrorDescription], which provides an explanation of the problem and its
  