opendev/gerrit
Code Issues Proposed changes

Fix typos in the documentation

Browse Source 
Change-Id: I50dec21003e15cee12bdd847c0890e86911bb18f
This commit is contained in:
Eryk Szymanski 2016-11-15 17:56:28 -08:00
parent 5cca4e5d28
commit 2b93eb0a7d
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/config-plugins.txt
View File

@ -658,7 +658,7 @@ Configuration]
This plugin replaces the built-in Gerrit H2 based websession cache with This plugin replaces the built-in Gerrit H2 based websession cache with
a flatfile based implementation. This implementation is shareable a flatfile based implementation. This implementation is shareable
amongst multiple Gerrit servers, making it useful for multi-master among multiple Gerrit servers, making it useful for multi-master
Gerrit installations. Gerrit installations.
link:https://gerrit-review.googlesource.com/#/admin/projects/plugins/websession-flatfile[ link:https://gerrit-review.googlesource.com/#/admin/projects/plugins/websession-flatfile[

2
Documentation/intro-project-owner.txt
View File

@ -330,7 +330,7 @@ way a four-eyes principle for the reviews can be enforced.
A Prolog submit rule has access to link:prolog-change-facts.html[ A Prolog submit rule has access to link:prolog-change-facts.html[
information] about the change for which it is testing the information] about the change for which it is testing the
submittability. Amongst others the list of the modified files can be submittability. Among others the list of the modified files can be
accessed, which allows special logic if certain files are touched. For accessed, which allows special logic if certain files are touched. For
example, a common practice is to require a vote on an additional label, example, a common practice is to require a vote on an additional label,
like `Library-Compliance`, if the dependencies of the project are like `Library-Compliance`, if the dependencies of the project are

2
Documentation/intro-quick.txt
View File

@ -208,7 +208,7 @@ these views you can add inline comments by double clicking on the line
can add file comment by double clicking anywhere (not just on the can add file comment by double clicking anywhere (not just on the
"Patch Set" words) in the table header or single clicking on the icon "Patch Set" words) in the table header or single clicking on the icon
in the line-number column header. Once published these comments are in the line-number column header. Once published these comments are
viewable to all, allowing discussion of the change to take place. visible to all, allowing discussion of the change to take place.
.Side By Side Patch View .Side By Side Patch View
image::images/intro-quick-review-line-comment.jpg[Adding a Comment] image::images/intro-quick-review-line-comment.jpg[Adding a Comment]

2
Documentation/user-submodules.txt
View File

@ -28,7 +28,7 @@ To take advantage of this feature, one should:
When a commit in a project is merged, Gerrit checks for superprojects When a commit in a project is merged, Gerrit checks for superprojects
that are subscribed to the the project and automatically updates those that are subscribed to the the project and automatically updates those
superprojects with a commit that updates the gilink for the project. superprojects with a commit that updates the gitlink for the project.
This feature is enabled by default and can be disabled This feature is enabled by default and can be disabled
via link:config-gerrit.html#submodule.enableSuperProjectSubscriptions[submodule.enableSuperProjectSubscriptions] via link:config-gerrit.html#submodule.enableSuperProjectSubscriptions[submodule.enableSuperProjectSubscriptions]