From a61ee5036dc5f3f1da9075bcd322568d27fcaf61 Mon Sep 17 00:00:00 2001 From: David Pursehouse Date: Tue, 6 Sep 2016 16:27:09 +0900 Subject: [PATCH] Fix various typos, spelling mistakes, and inconsistencies Change-Id: If8a00ab24285a32840dc9c92697366037554cbca --- Documentation/cmd-plugin-install.txt | 2 +- Documentation/config-gerrit.txt | 4 ++-- Documentation/config-mail.txt | 2 +- Documentation/config-plugins.txt | 4 ++-- Documentation/database-setup.txt | 2 +- Documentation/dev-buck.txt | 2 +- Documentation/dev-contributing.txt | 2 +- Documentation/dev-plugins.txt | 6 +++--- Documentation/dev-stars.txt | 4 ++-- Documentation/intro-project-owner.txt | 2 +- Documentation/intro-user.txt | 2 +- Documentation/rest-api-changes.txt | 4 ++-- Documentation/rest-api-config.txt | 2 +- Documentation/user-inline-edit.txt | 2 +- 14 files changed, 20 insertions(+), 20 deletions(-) diff --git a/Documentation/cmd-plugin-install.txt b/Documentation/cmd-plugin-install.txt index 274b446ab0..5443613c92 100644 --- a/Documentation/cmd-plugin-install.txt +++ b/Documentation/cmd-plugin-install.txt @@ -50,7 +50,7 @@ Install a plugin from an absolute file path on the server's host: $(pwd)/my-plugin.jar ---- -Install a WebUi plugin from an absolute file path on the server's host: +Install a WebUI plugin from an absolute file path on the server's host: ---- ssh -p 29418 localhost gerrit plugin install -n name.js \ diff --git a/Documentation/config-gerrit.txt b/Documentation/config-gerrit.txt index 234d2c50ab..1c08a68642 100644 --- a/Documentation/config-gerrit.txt +++ b/Documentation/config-gerrit.txt @@ -530,7 +530,7 @@ future lookup. This local disk cache is used to retain potentially expensive to compute information across restarts. If the location does not exist, Gerrit will try to create it. + -Tehnically, cached entities are persisted as a set of H2 databases +Technically, cached entities are persisted as a set of H2 databases inside this directory. + If not absolute, the path is resolved relative to `$site_path`. @@ -1030,7 +1030,7 @@ Defaults to "Submit whole topic" [[change.submitTopicTooltip]]change.submitTopicTooltip:: + -If `change.submitWholeTopic` is configuerd to true and a change has a +If `change.submitWholeTopic` is configured to true and a change has a topic, this configuration determines the tooltip for the submit button instead of `change.submitTooltip`. The variable `${topicSize}` is available for the number of changes in the same topic to be submitted. The number of diff --git a/Documentation/config-mail.txt b/Documentation/config-mail.txt index c6eac0005b..51ea9c5b58 100644 --- a/Documentation/config-mail.txt +++ b/Documentation/config-mail.txt @@ -64,7 +64,7 @@ and `ChangeFooter.vm`. === DeleteReviewer.vm -The `DeleteReiewer.vm` template will determine the contents of the email related +The `DeleteReviewer.vm` template will determine the contents of the email related to a user removing a reviewer (with a vote) from a change. It is a `ChangeEmail`: see `ChangeSubject.vm` and `ChangeFooter.vm`. diff --git a/Documentation/config-plugins.txt b/Documentation/config-plugins.txt index 2ada886f25..6676c9d424 100644 --- a/Documentation/config-plugins.txt +++ b/Documentation/config-plugins.txt @@ -207,7 +207,7 @@ This plugin allows to display a static info message on the change screen. link:https://gerrit-review.googlesource.com/#/admin/projects/plugins/changemessage[ Project] | link:https://gerrit.googlesource.com/plugins/changemessage/+doc/master/src/main/resources/Documentation/about.md[ -Plugin Documenatation] | +Plugin Documentation] | link:https://gerrit.googlesource.com/plugins/changemessage/+doc/master/src/main/resources/Documentation/config.md[ Configuration] @@ -657,7 +657,7 @@ Configuration] === websession-flatfile This plugin replaces the built-in Gerrit H2 based websession cache with -a flatfile based implementation. This implemantation is shareable +a flatfile based implementation. This implementation is shareable amongst multiple Gerrit servers, making it useful for multi-master Gerrit installations. diff --git a/Documentation/database-setup.txt b/Documentation/database-setup.txt index 02074c0228..08d0a54176 100644 --- a/Documentation/database-setup.txt +++ b/Documentation/database-setup.txt @@ -39,7 +39,7 @@ This option is more complicated than the H2 option but is recommended for larger installations. It's the database backend with the largest userbase in the Gerrit community. -Create a user for the web application within Postgres, assign it a +Create a user for the web application within PostgreSQL, assign it a password, create a database to store the metadata, and grant the user full rights on the newly created database: diff --git a/Documentation/dev-buck.txt b/Documentation/dev-buck.txt index 73d2e98faf..315c0b06b3 100644 --- a/Documentation/dev-buck.txt +++ b/Documentation/dev-buck.txt @@ -635,7 +635,7 @@ The following tests should be executed, when Buck version is upgraded: [known bug](https://github.com/facebook/buck/issues/341) related to symbolic links. The symbolic links are used very often with external plugins, that are linked per symbolic link to the plugins directory. -With this use case Buck is failing to rebuild the plugin artefact +With this use case Buck is failing to rebuild the plugin artifact after it was built. All attempts to convince Buck to rebuild will fail. The only known way to recover is to weep out `buck-out` directory. The better workaround is to avoid using Watchman in this specific use case. diff --git a/Documentation/dev-contributing.txt b/Documentation/dev-contributing.txt index dd230d306a..775fe21571 100644 --- a/Documentation/dev-contributing.txt +++ b/Documentation/dev-contributing.txt @@ -183,7 +183,7 @@ When to use `final` modifier and when not (in new code): Always: * final fields: marking fields as final forces them to be - initialised in the constructor or at declaration + initialized in the constructor or at declaration * final static fields: clearly communicates the intent * to use final variables in inner anonymous classes diff --git a/Documentation/dev-plugins.txt b/Documentation/dev-plugins.txt index 9313b8fe05..71ed460445 100644 --- a/Documentation/dev-plugins.txt +++ b/Documentation/dev-plugins.txt @@ -457,7 +457,7 @@ class MyPlugin { Plugins which define new Events should register them via the `com.google.gerrit.server.events.EventTypes.registerClass()` method. This will make the EventType known to the system. -Deserialzing events with the +Deserializing events with the `com.google.gerrit.server.events.EventDeserializer` class requires that the event be registered in EventTypes. @@ -657,7 +657,7 @@ The search operator itself is implemented by ensuring that the `create()` method of the class implementing the `ChangeQueryBuilder.ChangeOperatorFactory` interface returns a `Predicate`. Here is a sample operator factory -defintion which creates a `MyPredicate`: +definition which creates a `MyPredicate`: [source,java] ---- @@ -1394,7 +1394,7 @@ capability check is done during the `UiAction` gathering, so the plugin author doesn't have to set `UiAction.Description.setVisible()` explicitly in this case. -The following prerequisities must be met, to satisfy the capability check: +The following prerequisites must be met, to satisfy the capability check: * user is authenticated * user is a member of a group which has the `Administrate Server` capability, or diff --git a/Documentation/dev-stars.txt b/Documentation/dev-stars.txt index d9fd10c19c..dfcbb6f637 100644 --- a/Documentation/dev-stars.txt +++ b/Documentation/dev-stars.txt @@ -29,8 +29,8 @@ returned by the link:rest-api-changes.html[changes REST API]. There are link:rest-api-accounts.html#default-star-endpoints[ additional REST endpoints] for the link:#default-star[default star]. -Only the link:#default-star[default star] is shown in the WebUi and -can be updated from there. Other stars do not show up in the WebUi. +Only the link:#default-star[default star] is shown in the WebUI and +can be updated from there. Other stars do not show up in the WebUI. [[default-star]] == Default Star diff --git a/Documentation/intro-project-owner.txt b/Documentation/intro-project-owner.txt index f98221292e..7a724f7c07 100644 --- a/Documentation/intro-project-owner.txt +++ b/Documentation/intro-project-owner.txt @@ -652,7 +652,7 @@ extension points, e.g. plugins can How to develop a Gerrit plugin is described in the link:dev-plugins.html[ Plugin Development] section. -[[prject-lifecycle]] +[[project-lifecycle]] == Project Lifecycle [[project-creation]] diff --git a/Documentation/intro-user.txt b/Documentation/intro-user.txt index 535248d36a..9bf6842fda 100644 --- a/Documentation/intro-user.txt +++ b/Documentation/intro-user.txt @@ -591,7 +591,7 @@ lists and dashboards are visualized. ** `None`: + For each review label only the voting value is shown. Approvals are -rendered as a green check mark icon, vetos as a red X icon. +rendered as a green check mark icon, vetoes as a red X icon. + ** `Show Name`: + diff --git a/Documentation/rest-api-changes.txt b/Documentation/rest-api-changes.txt index ec1335bc1e..ed8fc04392 100644 --- a/Documentation/rest-api-changes.txt +++ b/Documentation/rest-api-changes.txt @@ -5285,8 +5285,8 @@ whose behalf the action should be done. To use this option the caller must have been granted both `Submit` and `Submit (On Behalf Of)` permissions. The user named by `on_behalf_of` does not need to be granted the `Submit` permission. This feature is aimed for CI solutions: the CI account can be -granted both permssions, so individual users don't need `Submit` permission -themselves. Still the changes can be submited on behalf of real users and +granted both permissions, so individual users don't need `Submit` permission +themselves. Still the changes can be submitted on behalf of real users and not with the identity of the CI account. |========================== diff --git a/Documentation/rest-api-config.txt b/Documentation/rest-api-config.txt index a378462e91..c7c08789d5 100644 --- a/Documentation/rest-api-config.txt +++ b/Documentation/rest-api-config.txt @@ -1572,7 +1572,7 @@ Information about the configuration from the link:config-gerrit.html#gerrit[gerrit] section as link:#gerrit-info[ GerritInfo] entity. |`note_db_enabled` |not set if `false`| -Whether the NoteDB storage backend is fully enabled. +Whether the NoteDb storage backend is fully enabled. |`plugin ` || Information about Gerrit extensions by plugins as link:#plugin-config-info[PluginConfigInfo] entity. diff --git a/Documentation/user-inline-edit.txt b/Documentation/user-inline-edit.txt index 05932df124..f3c8b0015c 100644 --- a/Documentation/user-inline-edit.txt +++ b/Documentation/user-inline-edit.txt @@ -173,7 +173,7 @@ in context of change edit, this is not the best workflow to open one file in edi change it, save it, close edit screen and select next file from the file table to edit. "<-" | "->" icons in header of edit screen could be used to navigate to the next file to change from the file table. This would behave like the navigation icons in side by side -with thefollowing logic on click: +with the following logic on click: ** "save-when-file-was-changed" or ** "close-when-no-changes"