anchor.diff:  /// content. Action chips should appear dynamically and contextually in a UI.
   ///
   /// Action chips can be tapped to trigger an action or show progress and
  -/// confirmation.
  +/// confirmation. They cannot be disabled; if the action is not applicable, the
  +/// chip should not be included in the interface. (This contrasts with buttons,
  +/// where unavailable choices are usually represented as disabled controls.)
   ///
   /// Action chips are displayed after primary content, such as below a card or
   /// persistently at the bottom of a screen.
   ///
  -/// The material button widgets, [RaisedButton], [FlatButton], [OutlineButton]
  -/// are an alternative to action chips, which should appear statically and
  -/// consistently in a UI.
  +/// The material button widgets, [RaisedButton], [FlatButton], and
  +/// [OutlineButton], are an alternative to action chips, which should appear
  +/// statically and consistently in a UI.
   ///
   /// Requires one of its ancestors to be a [Material] widget. The [onPressed],
  -/// [label] and [border] arguments must not be null.
  +/// [label], and [border] arguments must not be null.
   ///
   /// ## Sample code
   ///
  
positive.code: ///  * [FilterChip], uses tags or descriptive words as a way to filter content.
  ///  * <https://material.google.com/components/chips.html>
  abstract class DisabledChipAttributes {
    /// Whether or not this chip is enabled for input.
    ///
    /// If this is true, but all of the user action callbacks are null (i.e.
  
negative.code: /// related descriptive text or categories.
  ///
  /// Requires one of its ancestors to be a [Material] widget. The [selected],
  /// [label], and [border] arguments must not be null.
  ///
  /// ## Sample code
  ///
  