Fix implementation headings

docs/DeveloperGuide.md

@@ -301,8 +301,6 @@ Known bugs:
 
 ### Wedding Feature
 
-#### Implementation
-
 The Wedding Feature allows users to store details of a Wedding in WedLinker. Wedding contains the Contacts involved to facilitate easy planning and consolidation for wedding planners.
 Wedding would support the following functions:
 
@@ -312,6 +310,8 @@ Wedding would support the following functions:
 * `Unassign Wedding` — Unassigns a `Person` from a Wedding.
 * `Delete Wedding` — Deletes the Wedding from WedLinker.
 
+#### Implementation
+
 Given below is an example usage scenario and how Weddings are used in WedLinker.
 
 Step 1. The user launches the application, `Weddings` are loaded into the `Model`.
@@ -347,14 +347,14 @@ Known bugs:
 
 ### Vendors
 
-#### Implementation
-
 The `Vendor` Feature allows users to track which `Person` are `Vendors` and assign `Tasks` to them. Only `Vendors` can be assigned `Tasks`.
 Vendor would support the following functions:
 
 * `Assign Vendor` — Assigns an existing `Person` in WedLinker to become a `Vendor`. 
 * `Unassign Vendor` — Unassigns a `Vendor` to become a non-vendor `Person` contact. 
 
+#### Implementation
+
 Given below is an example usage scenario and how Vendors are used in WedLinker.
 
 Step 1. The user launches the application, `Persons` and `Vendors` are loaded into the `Model`.
@@ -391,6 +391,8 @@ There are different types of `Task` to support different requirements for the us
 * `Unassign Task` —  Unassigns a `Task` from a `Vendor`. 
 * `Delete Task` —  Deletes a `Task` from WedLinker. 
 
+#### Implementation
+
 Given below is an example usage scenario and how Tasks are used in WedLinker.
 
 Step 1. The user launches the application, `Tasks` are loaded into the `Model`.