From d43187b3647d1e22d7999cf85bc5b80f4da20ab2 Mon Sep 17 00:00:00 2001 From: Waldir Pimenta Date: Fri, 14 Oct 2016 19:19:37 +0100 Subject: [PATCH] contributing.md: adjust line-wrapping --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 591d6d7747..b32e0f2d9d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -33,8 +33,8 @@ Here are a few guidelines to get started: 1. Focus on the 5 or 6 most common usages. It's OK if the page doesn't cover everything; that's what `man` is for. -2. When in doubt, keep new command-line users in mind. - Err on the side of clarity rather than terseness. For example, commands that require `sudo` should include it directly in the examples. +2. When in doubt, keep new command-line users in mind. Err on the side of clarity rather than terseness. + For example, commands that require `sudo` should include it directly in the examples. 3. Try to incorporate the spelled-out version of single-letter options in the example's description. The goal is to allow people to *understand* the syntax of the commands, not just *memorize* it. 4. Introduce options gradually, starting with the simplest command invocations,