From 171200ee3cd1cd80f7d3f575cef02f1bd51dbf67 Mon Sep 17 00:00:00 2001
From: snappyapple632 <40573129+snappyapple632@users.noreply.github.com>
Date: Sun, 4 Aug 2019 16:11:45 -0700
Subject: [PATCH] One tiny error

---
 07_maintainers_view.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/07_maintainers_view.md b/07_maintainers_view.md
index cbb09a2..a499fcc 100644
--- a/07_maintainers_view.md
+++ b/07_maintainers_view.md
@@ -13,7 +13,7 @@ code, however in essence NewPipe should be easy to use, even for your average An
 1. __Don't add too many special
   features.__ NewPipe does not have to be an air plane cockpit. Do not try to fill every single niche that might exist. If people wanted more advanced features, they
   would use professional tools. If you add too much functionality, you add complexity, and complexity scares away the average user. Focus on NewPipe's scope as a **media player** for the end user, and only as such. 
-2. __Usability of the user interface should be prioritized.__. Try to make it comply with
+2. __Usability of the user interface should be prioritized.__ Try to make it comply with
   [material design guidelines](https://material.io/design/guidelines-overview/).