formatting fixes

Author: lizbur10

README.md

@@ -1,6 +1,8 @@
 # SQL Bear Organizer
 
-[Timothy Treadwell](http://en.wikipedia.org/wiki/Timothy_Treadwell) has a lot on his plate protecting the bears of the Katmai National Park in Alaska. Help him keep track of all of his bear friends using SQL.
+[Timothy Treadwell](http://en.wikipedia.org/wiki/Timothy_Treadwell) has a lot on
+his plate protecting the bears of the Katmai National Park in Alaska. Help him
+keep track of all of his bear friends using SQL.
 
 ![timothy-treadwell](http://m2.paperblog.com/i/74/746121/lagghiacciante-morte-delluomo-grizzly-sbranat-L-rr7aep.jpeg)
 
@@ -12,7 +14,8 @@
 
 ## Lab Structure
 
-This lab might seem a bit different than what you've seen before. Take a look at the file structure:
+This lab might seem a bit different than what you've seen before. Take a look at
+the file structure:
 
 ```bash
 ├── Gemfile
@@ -44,15 +47,22 @@ before do
   @sql_runner.execute_create_file
 end
 ```
+
 Before each test two important things happen.
 
-First, a new in-memory database is created. Why do we do this? Let's say we run our tests and they add ten items to our database. If we did not use an in-memory store, those would be in there forever. This way our database gets thrown out after every running of the tests. You can learn more about in-memory databases [here](https://www.sqlite.org/inmemorydb.html).
+First, a new in-memory database is created. Why do we do this? Let's say we run
+our tests and they add ten items to our database. If we did not use an in-memory
+store, those would be in there forever. This way our database gets thrown out
+after every running of the tests. You can learn more about in-memory databases
+[here](https://www.sqlite.org/inmemorydb.html).
 
-Next, a new `SqlRunner` class is created. The `SqlRunner` class lives in your `bin` directory and was created to help connect to the database.
+Next, a new `SqlRunner` class is created. The `SqlRunner` class lives in your
+`bin` directory and was created to help connect to the database.
 
 ## Part 1: `CREATE TABLE`
 
-Get the tests in `spec/create_spec.rb` to pass. Your `CREATE` statement should look something like this:
+Get the tests in `spec/create_spec.rb` to pass. Your `CREATE` statement should
+look something like this:
 
 ```sql
 CREATE TABLE bears (
@@ -98,11 +108,14 @@ Your columns should be the following types:
   </tr>
 </table>
 
-Read about [SQLite3 Datatypes](https://www.sqlite.org/datatype3.html) to determine what your insert values are going to be. Be sure to pay attention to how booleans are expressed in SQLite3.
+Read about [SQLite3 Datatypes](https://www.sqlite.org/datatype3.html) to
+determine what your insert values are going to be. Be sure to pay attention to
+how booleans are expressed in SQLite3.
 
 ## Part 2: `INSERT`
 
-Get the tests in `spec/insert_spec.rb` to pass. Input the following 8 bears (you can make up details about them, but make sex either 'M' or 'F'):
+Get the tests in `spec/insert_spec.rb` to pass. Input the following 8 bears (you
+can make up details about them, but make sex either 'M' or 'F'):
 
 * Mr. Chocolate
 * Rowdy
@@ -111,17 +124,20 @@ Get the tests in `spec/insert_spec.rb` to pass. Input the following 8 bears (you
 * Melissa
 * Grinch
 * Wendy
-* unnamed (the bear that killed Tim didn't have a name; refer back to how to create a record that doesn't have one value)
+* unnamed (the bear that killed Tim didn't have a name; refer back to how to
+  create a record that doesn't have one value)
 
 ## Part 3: `SELECT`
 
-Get the tests in `spec/select_spec.rb` to pass. Note that for this section, the database will be seeded with external data from the `lib/seed.sql` file so don't expect it to reflect the data you added above. Note: Since it's a Ruby file, write your queries as strings in the `lib/sql_queries.rb`.
+Get the tests in `spec/select_spec.rb` to pass. Note that for this section, the
+database will be seeded with external data from the `lib/seed.sql` file so don't
+expect it to reflect the data you added above. Note: Since it's a Ruby file,
+write your queries as strings in the `lib/sql_queries.rb`.
 
-You may be expected to use SQL statements that you're not particularly familiar with. Make sure you use the resources and Google to find the right statements.
+You may be expected to use SQL statements that you're not particularly familiar
+with. Make sure you use the resources and Google to find the right statements.
 
 ## Resources
 
 [SQL Datatypes](https://www.sqlite.org/datatype3.html)
 [SQL GROUP BY](https://www.sqlite.org/lang_select.html#resultset)
-
-