Autogenerated man pages for v1.2.4-gf61c2

[git.git] / man1 / git-check-ref-format.1

diff --git a/man1/git-check-ref-format.1 b/man1/git-check-ref-format.1
index 3b7ee77..831eda2 100755 (executable)
--- a/man1/git-check-ref-format.1
+++ b/man1/git-check-ref-format.1
@@ -19,16 +19,16 @@
 ..
 .TH "GIT-CHECK-REF-FORM" 1 "" "" ""
 .SH NAME
-git-check-ref-format \- Make sure ref name is well formed.
+git-check-ref-format \- Make sure ref name is well formed
 .SH "SYNOPSIS"
 
 
-git\-check\-ref\-format <refname>
+\fIgit\-check\-ref\-format\fR <refname>
 
 .SH "DESCRIPTION"
 
 
-Checks if a given refname is acceptable, and exits non\-zero if it is not\&.
+Checks if a given \fIrefname\fR is acceptable, and exits non\-zero if it is not\&.
 
 
 A reference is used in git to specify branches and tags\&. A branch head is stored under $GIT_DIR/refs/heads directory, and a tag is stored under $GIT_DIR/refs/tags directory\&. git imposes the following rules on how refs are named:
@@ -55,7 +55,7 @@ These rules makes it easy for shell script based tools to parse refnames, pathna
 double\-dot \&.\&. are often used as in ref1\&.\&.ref2, and in some context this notation means ^ref1 ref2 (i\&.e\&. not in ref1 and in ref2)\&.
 .TP
 2.
-tilde ~ and caret ^ are used to introduce postfix nth parent and peel onion operation\&.
+tilde ~ and caret ^ are used to introduce postfix \fInth parent\fR and \fIpeel onion\fR operation\&.
 .TP
 3.
 colon : is used as in srcref:dstref to mean "use srcref's value and store it in dstref" in fetch and push operations\&.