[maven-site] branch master updated: [MNGSITE-371] Clarify that the issue number is an example

[mi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

michaelo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 3e37bdd  [MNGSITE-371] Clarify that the issue number is an example
3e37bdd is described below

commit 3e37bdd142f00e47d9286a329b002e4b05af2044
Author: Maarten Mulders <ma...@infosupport.com>
AuthorDate: Wed Jun 5 08:17:18 2019 +0200

    [MNGSITE-371] Clarify that the issue number is an example
---
 content/apt/guides/development/guide-maven-development.apt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/apt/guides/development/guide-maven-development.apt b/content/apt/guides/development/guide-maven-development.apt
index 9d3d9e4..282ca0e 100644
--- a/content/apt/guides/development/guide-maven-development.apt
+++ b/content/apt/guides/development/guide-maven-development.apt
@@ -72,7 +72,7 @@ Developing Maven
 
  * If this was a new piece of work without a JIRA issue, create a JIRA issue for it now.
 
- * Name the branch <<<MNG-<issue number>>>>.
+ * Name the branch after the issue number; the branch name would start with <<<\<jira-project-id>-<ticket-id\>>>>.
 
  * Push your branch with the commit(s) to your fork.