The key to an effective definition of functional requirements is the minimization of incorrect interpretations and ambiguity. Using consistent syntax in your requirements you can improve legibility, to be sure that every team member precisely understands what product needs to be developed. In my talk I will tell how to improve the creation of requirements using Easy Approach to Requirements Syntax (EARS). EARS is a simple and powerful method to obtain functional requirements. High-level requirements to a system are usually formulated in a natural language. Free formulations in a natural language can cause various problems of interpretation of the text and, as a result, influence quality of requirements. I'll suggest the simple manual which will help to write better requirements, will tell how we introduced EARS and what benefit from this we had received.