diff --git a/README.md b/readme.md
similarity index 90%
rename from README.md
rename to readme.md
index 1006e70f8286b7e384e0334fab73cae382dfc604..273f9edb4a409cfd554ac653d6bdc5e675ef7a48 100644
--- a/README.md
+++ b/readme.md
@@ -1,27 +1,24 @@
-# Mobile Group Project: Investigating Broadcom & Internet of Things
+# Android Group Project: Investigating Broadcom & Internet of Things
 
-## Author
 
+## Authors
 Jeffrey Martin, Brandon Rodriguez
 
-## Description
 
+## Description
 An attempt to learn about "Internet of Things" concepts with hands-on development, using Broadcom's "WICED SMART"" pre-made mobile application as a base.
 
 Broadcam's sensor associated with the application can detect a number of things including: Device orientation, speed, compass direction, air pressure, humidity, and temperature.
 
 ### Core Function and Minimum Implementation
-
 Our goal is to learn how the program connects to the device (including finding out how the bluetooth conectivity works, if time allows). From there, we will create our own UI, showcasing that we understand how to read the sensor information and accurately display it in real time.
 
 ### Additional functionality, should time allow
-
 Determine a way to store up to a week's worth of data within the app. We will average out the information so that we only store the hourly-average per data type. Any hours with no sensory information will display as "NA" or some equivalent. This data will then be displayed to a clean and easy to read UI. This UI will display both "current data" plus have a tab to show specifics of each data catagory.
 
 Should we accomplish this, we can take it a step further by showing something along the lines of "change this week." For example, we could do "Total distance traveled" or "Highest Temperature Vs Lowest Temperature" type displays.
 
 ### Notes
-
 It might be beneficial to look into a few resources before we start any actual work.
 
 For example, we might want to consider some practices for commenting and organization:
@@ -32,12 +29,3 @@ For example, we might want to consider some practices for commenting and organiz
 We could also investigate how to properly create commit messages and decide on a standard:
 * http://chris.beams.io/posts/git-commit/
 * https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message
-
-
-## Outside Resources Used
-
-
-
-## Known Problems, Issues, And/Or Errors in the Program
-
-