Merge pull request #1 from gj/patch-2

made more pirates gender neutral

Author: gabe

views/root.erb

@@ -3,15 +3,15 @@
 <p>This is a lab meant to test your understanding of nested forms and how they work. As a convenience, I've added the instructions from the README below:</p>
 
 <ul>
-  <li>Note: YOU DO NOT NEED A DATABASE, we just need to keep track of the forms input long enough to display it, not persist it.  I don't expect the pirate to be there the next time I come to his URL, but it'd be cool if he was.</li>
+  <li>Note: YOU DO NOT NEED A DATABASE, we just need to keep track of the forms input long enough to display it, not persist it.  I don't expect the pirate to be there the next time I come to their URL, but it'd be cool if they were.</li>
 
   <li>Decide what objects/models you want to use, I used pirates and ships, you can use this or anything else.</li>
 
   <li>Other examples: Artists and Songs, Programmers and Languages they know, Schools and Students</li>
 
   <li>Make a nested form (this should probably have html `<label>`s so it makes sense to a user).</li>
 
-  <li>After a user clicks submit they should be taken to a page that displays all the information we just posted from the form.  In my example I'd have a page that showed the pirate I created along with his ships and all the details about the pirate and his ships.</li>
+  <li>After a user clicks submit they should be taken to a page that displays all the information we just posted from the form.  In my example I'd have a page that showed the pirate I created along with their ships and all the details about the pirate and their ships.</li>
 
   <li>I'm intentionally being vague about exactly what routes you need or how to set this all up.  We can all review together how you structured your routes and talk about the postives and negatives.  Do what you think makes the most sense.  Follow REST conventions.  Use the internet to figure it out if need be.</li>