opendev/gerrit
Code Issues Proposed changes

Minor documentation tidy-up

Browse Source 
Fix a couple of minor grammatical and formatting issues.

Change-Id: Ifb16d30a49d14e5c78fefc6c18469a593c279d9f
This commit is contained in:
David Pursehouse
2013-01-07 17:30:47 +09:00
parent 2ec688ea3d
commit 452ea4c7d8
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/config-cla.txt
View File

@@ -1,5 +1,5 @@
Gerrit Code Review - Contributor Agreements Gerrit Code Review - Contributor Agreements
============================================ ===========================================
Users can be required to sign one or more contributor agreements before Users can be required to sign one or more contributor agreements before
being able to submit a change in a project. being able to submit a change in a project.

6
Documentation/dev-release.txt
View File

@@ -70,13 +70,13 @@ issues.
For security issues it is important that they are only announced For security issues it is important that they are only announced
*after* fixed versions for all relevant releases have been published. *after* fixed versions for all relevant releases have been published.
Because of this `security-fix` releases can't be prepared in the public Because of this, `security-fix` releases can't be prepared in the public
`gerrit` project. `gerrit` project.
`security-fix` releases are prepared in the `gerrit-security-fixes` `security-fix` releases are prepared in the `gerrit-security-fixes`
project which is only readable by the Gerrit Maintainers. Only after project which is only readable by the Gerrit Maintainers. Only after
a `security-fix` release has been published the commits/tags done in a `security-fix` release has been published will the commits/tags made in
the `gerrit-security-fixes` project will be taken over into the public the `gerrit-security-fixes` project be taken over into the public
`gerrit` project. `gerrit` project.