From 2d9dc0bb36a1561f241afefefce05f5ff887edd5 Mon Sep 17 00:00:00 2001 From: Ori Zohar Date: Tue, 5 May 2020 20:22:53 -0700 Subject: [PATCH] Typo fix --- contributing/howto-template.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contributing/howto-template.md b/contributing/howto-template.md index 483c19c91..d43cdb084 100644 --- a/contributing/howto-template.md +++ b/contributing/howto-template.md @@ -34,7 +34,7 @@ > >Name each step section in a clear descriptive way which allows readers to understand what this section covers. Example: **Create a configuration file** > ->If using terminal commands, make sure to allow easy copy/paste by having each terminal command in a separate line with the markdown (indented as needed when appearing in bullets or numbered lists). If Windows/Linux/MacOS instructions defer, make sure to include instructions for each. +>If using terminal commands, make sure to allow easy copy/paste by having each terminal command in a separate line with the markdown (indented as needed when appearing in bullets or numbered lists). If Windows/Linux/MacOS instructions differ, make sure to include instructions for each. > >Example (note the indentation of the commands): > @@ -53,7 +53,7 @@ ## Cleanup > -> If possible, provide steps that undo the steps above. These should bring the user environment back to the pre-requisites stage. If using terminal commands, make sure to allow easy copy/paste by having each terminal command in a separate line with the markdown (indented as needed when appearing in bullets or numbered lists). If Windows/Linux/MacOS instructions defer, make sure to include instructions for each. +> If possible, provide steps that undo the steps above. These should bring the user environment back to the pre-requisites stage. If using terminal commands, make sure to allow easy copy/paste by having each terminal command in a separate line with the markdown (indented as needed when appearing in bullets or numbered lists). If Windows/Linux/MacOS instructions differ, make sure to include instructions for each. > >Example: >