Change class names in documentation

Summary: Ref T5655. Update class names in documentation after D9983.

Test Plan: N/A

Reviewers: epriestley, #blessed_reviewers

Reviewed By: epriestley, #blessed_reviewers

Subscribers: epriestley, Korvin

Maniphest Tasks: T5655

Differential Revision: https://secure.phabricator.com/D9984

src/docs/user/userguide/arcanist_lint_unit.diviner

@@ -17,7 +17,7 @@ you need to build new classes. For instance:
   - if you want to configure linters, or add new linters, you need to create a
     new class which extends @{class@arcanist:ArcanistLintEngine}.
   - if you want to integrate with a unit testing framework, you need to create a
-    new class which extends @{class@arcanist:ArcanistBaseUnitTestEngine}.
+    new class which extends @{class@arcanist:ArcanistUnitTestEngine}.
   - if you you want to change how workflows behave, or add new workflows, you
     need to create a new class which extends
     @{class@arcanist:ArcanistConfiguration}.

src/docs/user/userguide/arcanist_new_project.diviner

@@ -59,7 +59,7 @@ Other options include:
     @{class@arcanist:ArcanistLintEngine}, which should be used to apply lint
     rules to this project. See @{article:Arcanist User Guide: Lint}.
   - **unit.engine**: the name of a subclass of
-    @{class@arcanist:ArcanistBaseUnitTestEngine}, which should be used to apply
+    @{class@arcanist:ArcanistUnitTestEngine}, which should be used to apply
     unit test rules to this project. See
     @{article:Arcanist User Guide: Customizing Lint, Unit Tests and Workflows}.
 

src/docs/user/userguide/events.diviner

@@ -91,7 +91,7 @@ Arcanist event constants are listed in @{class@arcanist:ArcanistEventType}.
 
 All Arcanist events have this data available:
 
-  - `workflow` The active @{class@arcanist:ArcanistBaseWorkflow}.
+  - `workflow` The active @{class@arcanist:ArcanistWorkflow}.
 
 == Arcanist: Commit: Will Commit SVN ==