Merge pull request braydie#29 from claflamme/patch-4

braydie · braydie · commit 822e6f8800be · 2016-01-09T22:39:38.000Z
Change incorrect usage of 'you' to 'your'
diff --git a/2-Intermediate/Team-Skills/01-How to Manage Development Time.md b/2-Intermediate/Team-Skills/01-How to Manage Development Time.md
@@ -6,6 +6,6 @@ The project plan exists to help make decisions, not to show how organized you ar
 
 If you miss a milestone, you should take immediate action such as informing your boss that the scheduled completion of that project has slipped by that amount. The estimate and schedule could never have been perfect to begin with; this creates the illusion that you might be able to make up the days you missed in the latter part of the project. You might. But it is just as likely that you have underestimated that part as that you have overestimated it. Therefore the scheduled completion of the project has already slipped, whether you like it or not.
 
-Make sure you plan includes time for: internal team meetings, demos, documentation, scheduled periodic activities, integration testing, dealing with outsiders, sickness, vacations, maintenance of existing products, and maintenance of the development environment. The project plan can serve as a way to give outsiders or your boss a view into what you or your team is doing. For this reason it should be short and up-to-date.
+Make sure your plan includes time for: internal team meetings, demos, documentation, scheduled periodic activities, integration testing, dealing with outsiders, sickness, vacations, maintenance of existing products, and maintenance of the development environment. The project plan can serve as a way to give outsiders or your boss a view into what you or your team is doing. For this reason it should be short and up-to-date.
 
-Next [How to Manage Third-Party Software Risks](02-How to Manage Third-Party Software Risks.md)
+Next [How to Manage Third-Party Software Risks](02-How to Manage Third-Party Software Risks.md)
