diff --git a/content/events/2016-philadelphia/conduct.md b/content/events/2016-philadelphia/conduct.md
index e8f71cd9580..a523191836f 100644
--- a/content/events/2016-philadelphia/conduct.md
+++ b/content/events/2016-philadelphia/conduct.md
@@ -7,7 +7,7 @@ type = "event"
 
 +++
 
-##ANTI-HARASSMENT POLICY
+## ANTI-HARASSMENT POLICY
 
 DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
 
@@ -23,7 +23,7 @@ Conference staff can be identified by distinct staff badges. Conference staff wi
 
 We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
 
-##CODE OF CONDUCT
+## CODE OF CONDUCT
 
 I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
 
diff --git a/content/events/2016-philadelphia/contact.md b/content/events/2016-philadelphia/contact.md
index a91e9da82a2..137293bed59 100644
--- a/content/events/2016-philadelphia/contact.md
+++ b/content/events/2016-philadelphia/contact.md
@@ -10,10 +10,10 @@ type = "event"
 
 If you'd like to contact us by email: {{< email_organizers >}}
 
-** Our local team**
+**Our local team**
 
 {{< list_organizers >}}
 
-** The core devopsdays organizer group**
+**The core devopsdays organizer group**
 
 {{< list_core >}}
diff --git a/yyyy-city.yml b/yyyy-city.yml
index 0b13dca01ff..d72e2b4443b 100644
--- a/yyyy-city.yml
+++ b/yyyy-city.yml
@@ -5,12 +5,12 @@ friendly: "yyyy-city" # Four digit year and the city name in lower-case. Don't f
 status: "current" # Options are "past" or "current". Use "current" for upcoming.
 
 # All dates are in unquoted YYYY-MM-DD, like this:   variable: 2016-01-05
-startdate: 2016-01-01  # The start date of your event. Leave blank if you don't have a venue reserved yet.
-enddate: 2016-01-01  # The end date of your event. Leave blank if you don't have a venue reserved yet.
+startdate:  # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate:  # The end date of your event. Leave blank if you don't have a venue reserved yet.
 # Leave CFP dates blank if you don't know yet, or set all three at once.
-cfp_date_start: 2016-01-01 # start accepting talk proposals.
-cfp_date_end: 2016-01-01 # close your call for proposals.
-cfp_date_announce: 2016-01-01 # inform proposers of status
+cfp_date_start:  # start accepting talk proposals.
+cfp_date_end:  # close your call for proposals.
+cfp_date_announce:  # inform proposers of status
 
 # Location
 #