List for cgit developers and users
 help / color / mirror / Atom feed
Subject: [PATCH 1/5] Fix some spelling errors
Date: Wed, 11 Sep 2013 20:10:10 +0200	[thread overview]
Message-ID: <1378923014-902-2-git-send-email-p.janouch@gmail.com> (raw)
In-Reply-To: <1378923014-902-1-git-send-email-p.janouch@gmail.com>

Signed-off-by: P?emysl Janouch <p.janouch at gmail.com>
---
 cgitrc.5.txt |   10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/cgitrc.5.txt b/cgitrc.5.txt
index 633cb00..07584ff 100644
--- a/cgitrc.5.txt
+++ b/cgitrc.5.txt
@@ -176,7 +176,7 @@ enable-git-config::
 	"scan-path", and must be defined prior, to augment repo-specific
 	settings. The keys gitweb.owner, gitweb.category, and gitweb.description
 	will map to the cgit keys repo.owner, repo.section, and repo.desc,
-	respectivly. All git config keys that begin with "cgit." will be mapped
+	respectively. All git config keys that begin with "cgit." will be mapped
 	to the corresponding "repo." key in cgit. Default value: "0". See also:
 	scan-path, section-from-path.
 
@@ -592,8 +592,8 @@ environment variable will be unset.
 
 MACRO EXPANSION
 ---------------
-The following cgitrc options supports a simple macro expansion feature,
-where tokens prefixed with "$" are replaced with the value of a similary
+The following cgitrc options support a simple macro expansion feature,
+where tokens prefixed with "$" are replaced with the value of a similarly
 named environment variable:
 
 - cache-root
@@ -620,7 +620,7 @@ EXAMPLE CGITRC FILE
 -------------------
 
 ....
-# Enable caching of up to 1000 output entriess
+# Enable caching of up to 1000 output entries
 cache-size=1000
 
 
@@ -700,7 +700,7 @@ mimetype.png=image/png
 mimetype.svg=image/svg+xml
 
 
-# Highlight source code with python pygments-based highligher
+# Highlight source code with python pygments-based highlighter
 source-filter=/var/www/cgit/filters/syntax-highlighting.py
 
 # Format markdown, restructuredtext, manpages, text files, and html files
-- 
1.7.10.4



  reply	other threads:[~2013-09-11 18:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 18:10 [PATCH 0/5] Miscellaneous fixes 
2013-09-11 18:10 `  [this message]
2014-01-08 15:46   ` [PATCH 1/5] Fix some spelling errors Jason
2013-09-11 18:10 ` [PATCH 2/5] Fix about-formatting.sh 
2014-01-08 15:47   ` Jason
2013-09-11 18:10 ` [PATCH 3/5] Fix UTF-8 with syntax-highlighting.py 
2013-09-13  6:14   ` 
2014-01-08 15:49     ` Jason
2013-09-11 18:10 ` [PATCH 4/5] Fix the example configuration 
2014-01-08 15:47   ` Jason
2013-09-11 18:10 ` [PATCH 5/5] Add a suggestion to the manpage 
2014-01-08 15:48   ` Jason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1378923014-902-2-git-send-email-p.janouch@gmail.com \
    --to=cgit@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).