diff --git a/docs/community/community-structure b/docs/community/community-structure.md
similarity index 100%
rename from docs/community/community-structure
rename to docs/community/community-structure.md
diff --git a/docs/community/how-to-grow-our-community.md b/docs/community/how-to-grow-our-community.md
index 6dcbb8d..54ff3d2 100644
--- a/docs/community/how-to-grow-our-community.md
+++ b/docs/community/how-to-grow-our-community.md
@@ -5,11 +5,11 @@ This is a list of practical tips and suggestions on how you can take part in, he
 If you haven’t done so yet, please read our [Mission and Core Values](../getting-started/mission-and-core-values.md) and ensure you follow our [Code of Conduct](../getting-started/code-of-conduct.md), as these are closely aligned.
 
 
-## Get involved with the status.im community
+## How to Get Involved
 
-- at the moment much of the community communication takes place on slack.   A first step to getting involved can be as simple as joining [status-im.slack](status-im.slack.com) and saying “hi”.
+- At the moment much of the community communication takes place on slack. A first step to getting involved can be as simple as joining [our Slack](status-im.slack.com) and saying “hi” (we're friendly people!).
 
-- Take a look around the [Slack](http://slack.status.im) channels, where you will find #dev-status, #dapp-chat, #lll etc.
+- Take a look around the Slack channels, where you will find #dev-status, #dapp-chat, #lll etc.
 
 - When you get to know people in the community who have interests or skills then let them know about or invite them to join the channels that play to their strengths.
 
@@ -18,7 +18,7 @@ If you haven’t done so yet, please read our [Mission and Core Values](../getti
         *  The description should help others make a quick decision which channels they need to join.
 
 
-## Highlighting / Managing Needs
+## Highlighting & Managing Needs
 
 - Share your ideas on how we can make the list of tasks and needed contributions more easily visible. The more accessible and manageable tasks become to the community the better.
 
diff --git a/docs/contributing/ux-and-design.md b/docs/contributing/design-guidelines.md
similarity index 100%
rename from docs/contributing/ux-and-design.md
rename to docs/contributing/design-guidelines.md
diff --git a/docs/getting-started/branding b/docs/getting-started/branding
deleted file mode 100644
index 7149402..0000000
--- a/docs/getting-started/branding
+++ /dev/null
@@ -1,24 +0,0 @@
-This document is a guide to contributors and community members on how to maintain the "brand" and present Status.im both to the wider public
-and when integrating external content within Status
-
-
-## Brand guidlines
-
-
-
-## DApps in status
-
-
-
-
-
-
-
-
-
-
-##Appearance
-
-- Try to maintain a professional appearance, whether that is profile pictures or site design, this makes us more attractive.
-
-STUB 
diff --git a/mkdocs.yml b/mkdocs.yml
index b16a7f4..45f13bc 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -20,7 +20,7 @@ pages:
       - Introduction: 'contributing/development/introduction.md'
       - Building Status: 'contributing/development/building-status.md'
       - Adding DApps: 'contributing/development/adding-dapps.md'
-    - UX & Design: 'contributing/ux-and-design.md'
+    - Design Guidelines: 'contributing/design-guidelines.md'
     - Testing & Feedback: 'contributing/testing-and-feedback.md'
     - Documenting: 'contributing/documenting.md'
     - Outreach: 'contributing/outreach.md'