Documentation update to show how events are been created and removed dummy data from events.json file

Author: TimOsahenru

CONTRIBUTING.md

@@ -167,9 +167,10 @@ The diagram below explains how information is generated for the about page, show
 
 - Once you’ve committed and pushed all of your changes to GitHub, go to the page for your fork on GitHub, select your development branch, and click the pull request button. Please ensure that you compare your feature branch to the desired branch of the repo you are supposed to make a PR to. If you need to make any adjustments to your pull request, just push the updates to GitHub. Your pull request will automatically track the changes in your development branch and update it. 🥳
 
-
 ## Creating an event
+
 Events are currently created manually by adding entries to `_data/events.json`. To create a conference, use the following JSON structure:
+
 ```
 {
   "name": "Conference name",
@@ -183,7 +184,9 @@ Events are currently created manually by adding entries to `_data/events.json`.
 ```
 
 ### Regular meetups
+
 We have two recurring meetups: **Coffee and Code** and our **Monthly Meetup**. These events remain consistent in format, with only the **date, time, and speaker** subject to change. Updates can be made within the `meetups` list:
+
 ```
  {
       "name": "Coffee and Code",

_data/events.json

@@ -1,9 +1,5 @@
 {
-  "meetups": [
-  
-  ],
-  "conferences": [
-   
-  ],
+  "meetups": [],
+  "conferences": [],
   "partners": []
 }