Fix spelling mistakes in Gerrit documentation
Change-Id: Ieebe909a708fab4408128994aa19d3e028b299b4 Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
This commit is contained in:
parent
a6ac5a5cba
commit
f1acbb8330
@ -64,13 +64,13 @@ link:cmd-query.html[gerrit query]::
|
||||
Query the change database.
|
||||
|
||||
'gerrit receive-pack'::
|
||||
'Depreated alias for `git receive-pack`.'
|
||||
'Deprecated alias for `git receive-pack`.'
|
||||
|
||||
link:cmd-review.html[gerrit review]::
|
||||
Verify, approve and/or submit a patch set from the command line.
|
||||
|
||||
link:cmd-stream-events.html[gerrit stream-events]::
|
||||
Monitor events occuring in real time.
|
||||
Monitor events occurring in real time.
|
||||
|
||||
git upload-pack::
|
||||
Standard Git server side command for client side `git fetch`.
|
||||
@ -81,7 +81,7 @@ link:cmd-receive-pack.html[git receive-pack]::
|
||||
Also implements the magic associated with uploading commits for
|
||||
review. See link:user-upload.html#push_create[Creating Changes].
|
||||
|
||||
[[admin_commands]]Adminstrator Commands
|
||||
[[admin_commands]]Administrator Commands
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
link:cmd-create-account.html[gerrit create-account]::
|
||||
|
@ -3,7 +3,7 @@ gerrit stream-events
|
||||
|
||||
NAME
|
||||
----
|
||||
gerrit stream-events - Monitor events occuring in real time
|
||||
gerrit stream-events - Monitor events occurring in real time
|
||||
|
||||
SYNOPSIS
|
||||
--------
|
||||
@ -13,7 +13,7 @@ SYNOPSIS
|
||||
DESCRIPTION
|
||||
-----------
|
||||
|
||||
Provides a portal into the major events occuring on the server,
|
||||
Provides a portal into the major events occurring on the server,
|
||||
outputing activity data in real-time to the client. Events are
|
||||
filtered by the caller's access permissions, ensuring the caller
|
||||
only receives events for changes they can view on the web, or in
|
||||
|
@ -69,7 +69,7 @@ is impossible to recover contact records.
|
||||
|
||||
Install a contact store implementation somewhere to receive
|
||||
the contact records. To be really paranoid, Gerrit always
|
||||
ships the data to another HTTP server, preferrably over HTTPS.
|
||||
ships the data to another HTTP server, preferably over HTTPS.
|
||||
Existing open-source server implementations can be found in the
|
||||
gerrit-contactstore project.
|
||||
|
||||
|
@ -70,7 +70,7 @@ http://openid.net/[openid.net].
|
||||
* `HTTP`
|
||||
+
|
||||
Gerrit relies upon data presented in the HTTP request. This includes
|
||||
HTTP basic authentication, or some types of commerical single-sign-on
|
||||
HTTP basic authentication, or some types of commercial single-sign-on
|
||||
solutions. With this setting enabled the authentication must
|
||||
take place in the web server or servlet container, and not from
|
||||
within Gerrit.
|
||||
|
@ -11,7 +11,7 @@ affected git repository so that git commands can be easily run.
|
||||
|
||||
Make sure your hook scripts are executable if running on *nix.
|
||||
|
||||
Hooks are run in the background after the relevent change has
|
||||
Hooks are run in the background after the relevant change has
|
||||
taken place so are unable to affect the outcome of any given
|
||||
change. Because of the fact the hooks are run in the background
|
||||
after the activity, a hook might not be notified about an event if
|
||||
|
@ -113,7 +113,7 @@ change submit function.
|
||||
After a change has been scored positively by reviewers, Gerrit
|
||||
enables a submit button on the web interface. Authorized users
|
||||
can push the submit button to have the change enter the project
|
||||
repository. The equivilant in Subversion or Perforce would be
|
||||
repository. The equivalent in Subversion or Perforce would be
|
||||
that Gerrit is invoking `svn commit` or `p4 submit` on behalf of
|
||||
the web user pressing the button. Due to the way Git audit trails
|
||||
are maintained, the user pressing the submit button does not need
|
||||
|
@ -12,7 +12,7 @@ ApprovalCategory
|
||||
The getName() function produces only a single translation of the
|
||||
description string. This name is set by the Gerrit administrator,
|
||||
which may cause problems if the site is translated into multiple
|
||||
langauges and different users want different translations.
|
||||
languages and different users want different translations.
|
||||
|
||||
ApprovalCategoryValue
|
||||
---------------------
|
||||
@ -20,7 +20,7 @@ ApprovalCategoryValue
|
||||
The getName() function produces only a single translation of the
|
||||
description string. This name is set by the Gerrit administrator,
|
||||
which may cause problems if the site is translated into multiple
|
||||
langauges and different users want different translations.
|
||||
languages and different users want different translations.
|
||||
|
||||
/Gerrit Gerrit.html
|
||||
-------------------
|
||||
|
@ -11,7 +11,7 @@ standalone daemon is not desired.
|
||||
|
||||
Gerrit Code Review can be installed into any J2EE servlet container,
|
||||
including popular open source containers such as Jetty or Tomcat, or
|
||||
any commerical server which supports the J2EE servlet specification.
|
||||
any commercial server which supports the J2EE servlet specification.
|
||||
|
||||
|
||||
Installation
|
||||
|
@ -26,7 +26,7 @@ OPTIONS
|
||||
-d::
|
||||
\--site-path::
|
||||
Location of the gerrit.config file, and all other per-site
|
||||
configuration data, supporting libaries and log files.
|
||||
configuration data, supporting libraries and log files.
|
||||
|
||||
\--threads::
|
||||
Number of threads to perform the scan work with. Default: 2.
|
||||
|
@ -26,7 +26,7 @@ OPTIONS
|
||||
-d::
|
||||
\--site-path::
|
||||
Location of the gerrit.config file, and all other per-site
|
||||
configuration data, supporting libaries and log files.
|
||||
configuration data, supporting libraries and log files.
|
||||
|
||||
\--threads::
|
||||
Number of threads to perform the scan work with. Defaults to
|
||||
|
@ -33,7 +33,7 @@ OPTIONS
|
||||
-d::
|
||||
\--site-path::
|
||||
Location of the gerrit.config file, and all other per-site
|
||||
configuration data, supporting libaries and log files.
|
||||
configuration data, supporting libraries and log files.
|
||||
|
||||
\--enable-httpd::
|
||||
\--disable-httpd::
|
||||
@ -48,7 +48,7 @@ OPTIONS
|
||||
\--slave::
|
||||
Run in slave mode, permitting only read operations
|
||||
by clients. Commands which modify state such as
|
||||
link:cmd-receive-pack.html[recieve-pack] (creates new changes
|
||||
link:cmd-receive-pack.html[receive-pack] (creates new changes
|
||||
or updates existing ones) or link:cmd-review.html[review]
|
||||
(sets approve marks) are disabled.
|
||||
+
|
||||
|
@ -26,7 +26,7 @@ OPTIONS
|
||||
-d::
|
||||
\--site-path::
|
||||
Location of the gerrit.config file, and all other per-site
|
||||
configuration data, supporting libaries and log files.
|
||||
configuration data, supporting libraries and log files.
|
||||
|
||||
CONTEXT
|
||||
-------
|
||||
|
@ -31,14 +31,14 @@ OPTIONS
|
||||
|
||||
\--no-auto-start::
|
||||
Don't automatically start the daemon after initializing a
|
||||
newly created site path. This permits the administartor
|
||||
newly created site path. This permits the administrator
|
||||
to inspect and modify the configuration before the daemon
|
||||
is started.
|
||||
|
||||
-d::
|
||||
\--site-path::
|
||||
Location of the gerrit.config file, and all other per-site
|
||||
configuration data, supporting libaries and log files.
|
||||
configuration data, supporting libraries and log files.
|
||||
|
||||
CONTEXT
|
||||
-------
|
||||
|
@ -21,7 +21,7 @@ OPTIONS
|
||||
-d::
|
||||
--site-path::
|
||||
Location of the gerrit.config file, and all other per-site
|
||||
configuration data, supporting libaries and log files.
|
||||
configuration data, supporting libraries and log files.
|
||||
|
||||
--all::
|
||||
Compile rules for all projects.
|
||||
|
@ -100,7 +100,7 @@ Changes where 'SHA1' is one of the patch sets of the change.
|
||||
[[project]]
|
||||
project:'PROJECT'::
|
||||
+
|
||||
Changes occuring in 'PROJECT'. If 'PROJECT' starts with `^` it
|
||||
Changes occurring in 'PROJECT'. If 'PROJECT' starts with `^` it
|
||||
matches project names by regular expression. The
|
||||
link:http://www.brics.dk/automaton/[dk.brics.automaton
|
||||
library] is used for evaluation of such patterns.
|
||||
|
Loading…
Reference in New Issue
Block a user