This article explores how informal requirements, like those written in Markdown, often contain ambiguities and gaps that make them unsuitable as specifications for software development. The author demonstrates how Dynamic Logic—a formal method for reasoning about actions and state changes—can be used to express requirements precisely, using a salon appointment booking system as an example.