| Index: pkg/scheduled_test/lib/scheduled_test.dart
|
| diff --git a/pkg/scheduled_test/lib/scheduled_test.dart b/pkg/scheduled_test/lib/scheduled_test.dart
|
| index aab455e87c122549702aed9a12c8b76b2bdfb1e9..1be401cdebf58c488f9a3e5dc512ba994a0e5d71 100644
|
| --- a/pkg/scheduled_test/lib/scheduled_test.dart
|
| +++ b/pkg/scheduled_test/lib/scheduled_test.dart
|
| @@ -49,7 +49,7 @@
|
| /// });
|
| /// }
|
| ///
|
| -/// ## Setting Up and Tearing Down
|
| +/// ## Setting up and tearing down
|
| ///
|
| /// The `scheduled_test` package defines its own [setUp] method that works just
|
| /// like the one in `unittest`. Tasks can be scheduled in [setUp]; they'll be
|
| @@ -77,7 +77,7 @@
|
| /// // ...
|
| /// }
|
| ///
|
| -/// ## Passing Values Between Tasks
|
| +/// ## Passing values between tasks
|
| ///
|
| /// It's often useful to use values computed in one task in other tasks that are
|
| /// scheduled afterwards. There are two ways to do this. The most
|
|
|