From a8fb4d47a4bd039c8bd8349b69e1e1c1183fb96d Mon Sep 17 00:00:00 2001 From: Lars Hvam Date: Wed, 13 Jun 2018 19:08:12 +0200 Subject: [PATCH] docs, rephrase --- docs/collections/_development/guidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/collections/_development/guidelines.md b/docs/collections/_development/guidelines.md index 7bfc673c3..d860140e6 100644 --- a/docs/collections/_development/guidelines.md +++ b/docs/collections/_development/guidelines.md @@ -5,7 +5,7 @@ order: 10 ### Practical -* Make sure there is an open issue for the stuff that you want to work on. When starting the development add a comment in the issue. This will allow for discussing possible solutions, and avoid having multiple people look into the same issue. +* For non-tivial changes make sure there is an open issue. When starting the development add a comment in the issue. This will allow for discussing possible solutions, and avoid having multiple people look into the same issue. * Keep the commits/PR as small as possible, try not to fix multiple issues in one commit/PR if possible. Smaller changes are easier to review, and are more likely to be accepted. @@ -24,4 +24,4 @@ abapGit is targeted for version 702, so the code should only contain expressions [abaplint](https://abaplint.org) will automatically check every PR for language syntax that is not available on 702. #### Pretty Printer -Use pretty printer, keywords upper case + indentation, [abapOpenChecks](http://docs.abapopenchecks.org/checks/06/) can be used for checking this \ No newline at end of file +Use pretty printer, keywords upper case + indentation, [abapOpenChecks](http://docs.abapopenchecks.org/checks/06/) can be used for checking this