Tidy

docs/docs/tutorial-basics/class-data-source.md

@@ -47,12 +47,12 @@ public class MyTestClass
 
         public Task InitializeAsync() 
         {
-            await StopServer();
+            await StartServer();
         }
 
         public ValueTask DisposeAsync() 
         {
-            await StartServer();
+            await StopServer();
         }
     }
 }

docs/docs/tutorial-basics/method-data-source.md

@@ -2,19 +2,13 @@
 sidebar_position: 5
 ---
 
-# Data Source Driven Tests
+# Method Data Sources
 
 A limitation of passing data in with `[Arguments(...)]` is that the data must be `constant` values. For example, we can't new up an object and pass it into this attribute as an argument. This is a constraint of the language and we can't change that.
 
 If we want test data represented in the form of objects, or just to use something that isn't a constant, we can declare a test data source.
 
-This can come in 3 forms, with help of the following attributes:
-- `[MethodDataSource]`
-- `[ClassDataSource]`
-- `[ClassConstructorAttribute]` (for constructors only)
-
-## MethodDataSource
-This has two options:
+`MethodDataSource` has two options:
 - If you pass in one argument, this is the method name containing your data. TUnit will assume this is in the current test class.
 - If you pass in two arguments, the first should be the `Type` of the class containing your test source data method, and the second should be the name of the method.