[jobeet] fixed minor typos and trac tickets

Author: Hugo Hamon

jobeet/en/05.markdown

@@ -2,7 +2,7 @@ Day 5: The Routing
 ==================
 
 If you've completed day 4, you should now be familiar with the MVC pattern
-andit should be feeling like a more and more natural way of coding. Spend a bit
+and it should be feeling like a more and more natural way of coding. Spend a bit
 more time with it and you won't look back. To practice a bit, we customized the
 Jobeet pages and in the process, also reviewed several symfony concepts, like
 the layout, helpers, and slots.

jobeet/en/08.markdown

@@ -33,11 +33,11 @@ Unit Tests
 ----------
 
 Writing unit tests is perhaps one of the hardest web development best practices
-to put into action. As web developers are not really used to test their work, a
-lot of questions arise: Do I have to write tests before implementing a feature?
-What do I need to test? Do my tests need to cover every single ~edge case|Edge
-Cases~? How can I be sure that everything is well tested? But usually, the first
-question is much more basic: Where to start?
+to put into action. As web developers are not really used to testing their work,
+a lot of questions arise: Do I have to write tests before implementing a
+feature? What do I need to test? Do my tests need to cover every single ~edge
+case|Edge Cases~? How can I be sure that everything is well tested? But usually,
+the first question is much more basic: Where to start?
 
 Even if we strongly advocate testing, the symfony approach is pragmatic: it's
 always better to have some tests than no test at all. Do you already have a lot
@@ -47,7 +47,7 @@ you find a bug in your code. Over time, your code will become better, the ~code
 coverage|Code Coverage~ will rise, and you will become more confident about it.
 By starting with a pragmatic approach, you will feel more comfortable with tests
 over time. The next step is to write tests for new features. In no time, you
-will become test addict.
+will become a test addict.
 
 The problem with most testing libraries is their steep learning curve. That's
 why symfony provides a very simple testing library, **lime**, to make writing
@@ -194,7 +194,7 @@ identify the behavior that fails.
 
 All lime test methods take a string as their last argument that serves as the
 description for the test. It's very convenient as it forces you to describe what
-your are really testing. It can also serve as a form of
+you are really testing. It can also serve as a form of
 ~documentation|Documentation~ for a method's expected behavior. Let's add some
 messages to the `slugify` test file:
 

jobeet/en/10.markdown

@@ -178,6 +178,7 @@ from a form is as simple as unsetting them:
 <doctrine>
     // lib/form/doctrine/JobeetJobForm.class.php
 </doctrine>
+
     class JobeetJobForm extends BaseJobeetJobForm
     {
       public function configure()
@@ -398,7 +399,7 @@ We also need to change the default validator:
 >You need to create the logo directory (`web/uploads/jobs/`) and check that it
 >is writable by the web server.
 
-As the validator will save the relative path in the database, change the path
+As the validator only saves the filename in the database, change the path
 used in the `showSuccess` template:
 
     [php]

jobeet/en/17.markdown

@@ -296,6 +296,7 @@ of an error:
 We also need to override the `delete()` method to remove the entry of the
 deleted job from the index:
 
+<propel>
     [php]
     // lib/model/JobeetJob.php
     public function delete(PropelPDO $con = null)