From 6c46a48c402864146cbc499ee4120a12aef14e1c Mon Sep 17 00:00:00 2001
From: Andreas Jaeger <aj@suse.com>
Date: Fri, 16 Nov 2018 10:31:52 +0100
Subject: [PATCH] Small update for opendevelopment

Convert paragraph to a list, this looks like a formatting problem.

Add reference to the opencommunity chapter.

Change-Id: Ib342de96058a891a6e0999ee2e09a743b45001a3
---
 doc/source/opendevelopment.rst | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/doc/source/opendevelopment.rst b/doc/source/opendevelopment.rst
index 96c6ce0..d0779f0 100644
--- a/doc/source/opendevelopment.rst
+++ b/doc/source/opendevelopment.rst
@@ -38,12 +38,15 @@ and trust within a community. Aspects of the open development process must
 include facilities for anyone (not just existing projects contributors and
 leaders) to:
 
-Discover current priorities and tasks. Report bugs and vulnerabilities. Leave
-reviews on existing patches. Submit patches to a project.
+- Discover current priorities and tasks.
+- Report bugs and vulnerabilities.
+- Leave reviews on existing patches.
+- Submit patches to a project.
 
 There must also be a clearly defined process that describes how a contributor
 can graduate to different levels of leadership within a project. The success of
 Open Development relies not just on the availability and accessibility of
 tooling in a project, but also upon the healthy governance of a community
-(which we will discuss further in the next chapter on "Open Community").
+(which we will discuss further in the next chapter on :doc:`Open
+Community <opencommunity>`).