fix erors

rules/do-you-manage-clients-expectations/rule.md

@@ -15,7 +15,7 @@ guid: 63337ba8-d206-41dc-920d-f89f5ff3b998
 
 There's no doubt custom software development is a challenging industry. According to [Critical Success Factors In Software Projects by John S. Reel](https://cmapspublic.ihmc.us/rid=1240967873742_627444575_5503/Critical%20Success%20Factors%20In%20Software%20Projects.pdf):
 
-> Nearly 75% of all development projects missed their target release date or never ship at all. 
+> Nearly 75% of all development projects missed their target release date or never ship at all.
 
 But what is so interesting is that at least **7 of the 10 most common signs of product development failure** are present **before the design is created or a single line of code is written**.
 
@@ -25,7 +25,7 @@ Projects often fail because clients think suppliers under-deliver and over-charg
 
 <!--endintro-->
 
-### Tip #1: Don't give ranges!
+### Tip #1: Don't give ranges
 
 Let's say a prospect asks me "How much to do this Release?" I could say "Somewhere between $15k - $20k"... then I hear "20k", the prospect hears "15k". I'm pleased we got it done for "25k" with a whole bunch of changes, the client is annoyed we didn't get it done for "12k". So, never give a range to a client. Tell them something like "The first Release, along with its spec, is likely to take $35k. That's two guys working full time for two weeks."
 
@@ -35,15 +35,15 @@ There is no such thing as bugless software. It's important to admit that bugs wi
 
 ### Tip #3: Don't give fixed prices
 
-A big fixed-price contract can also be dangerous in managing expectations because it removes flexibility. If you deliver exactly what the spec says, the client can quite easily be unhappy, because the hundred and one things they thought of during development weren't included. 
+A big fixed-price contract can also be dangerous in managing expectations because it removes flexibility. If you deliver exactly what the spec says, the client can quite easily be unhappy, because the hundred and one things they thought of during development weren't included.
 
-If you need to go with fixed prices, we recommend to do it in Releases of no more than 2 weeks (1 - 2 releases), which helps alleviate this problem. 
+If you need to go with fixed prices, we recommend to do it in Releases of no more than 2 weeks (1 - 2 releases), which helps alleviate this problem.
 
 It will often occur that in the middle of a fixed price contract a client will ask you to add extra functionality. You should not do any such items straight away, but turn this request into a task for future development. You should generate another release plan for all the extra items once the fixed price contract has been *signed off*. It is important that the customer is always clear on what is part of a fixed price contract and what is not, that is why you should always finish a fixed price contract and have it signed off **before** starting extra work.
 
 ### Tip #4: Talk dollars ASAP
 
-Talking dollars with the client is often something consultants don't like doing after the initial meeting. I've heard of consultants refraining from sending invoices when a project is suffering a few delays, or the client is unhappy with the application state. 
+Talking dollars with the client is often something consultants don't like doing after the initial meeting. I've heard of consultants refraining from sending invoices when a project is suffering a few delays, or the client is unhappy with the application state.
 
 If the client is unhappy to receive an invoice now, they will **not** be happy to receive it in two months!
 
@@ -53,10 +53,10 @@ Send invoices for time and material projects every week. This way the client is
 
 Defining the hourly rates and resources that will be available to clients ensures they are not surprised later. Additionally, explaining the differences between resources makes it clear why specific resources are grouped together and what kind of services they provide. You should have [clear definitions for all of your roles](https://github.com/SSWConsulting/SSW.Roles) so that clients understand the part their resources play.
 
-## Related Rules:
+## Related Rules
 
-**A.** You've already committed to work for this Sprint, so don't take on more than you can do: <https://www.ssw.com.au/rules/triaging-do-you-correctly-triage-additional-item-requests>   
+**A.** You've already committed to work for this Sprint, so don't take on more than you can do: <https://www.ssw.com.au/rules/triaging-do-you-correctly-triage-additional-item-requests>
 
-**B.** Update the client before you hit the deadline: <https://www.ssw.com.au/rules/do-you-keep-your-client-informed-of-progress> and [https://www.ssw.com.au/rules/do-you-email-clients-as-soon-as-you-realise-you-will-overrun-your-original-estimate ](https://www.ssw.com.au/rules/do-you-email-clients-as-soon-as-you-realise-you-will-overrun-your-original-estimate)  
+**B.** Update the client before you hit the deadline: <https://www.ssw.com.au/rules/do-you-keep-your-client-informed-of-progress> and [https://www.ssw.com.au/rules/do-you-email-clients-as-soon-as-you-realise-you-will-overrun-your-original-estimate](https://www.ssw.com.au/rules/do-you-email-clients-as-soon-as-you-realise-you-will-overrun-your-original-estimate)  
 
-**C.** Never make people chase you for a deliverable: <https://www.ssw.com.au/rules/professional-integrity>
+**C.** Never make people chase you for a deliverable: <https://www.ssw.com.au/rules/professional-integrity>