5676b04a44 · matheusbsbs/matheus-bagliano

Documentation/config/advice.txt

+1 -1

@@ -87,7 +87,7 @@ advice.*::

87 detachedHead::

88 Advice shown when you used

89 linkgit:git-switch[1] or linkgit:git-checkout[1]

90 - to move to the detach HEAD state, to instruct how to

90 + to move to the detached HEAD state, to instruct how to

91 create a local branch after the fact.

92 suggestDetachingHead::

93 Advice shown when linkgit:git-switch[1] refuses to detach HEAD

Documentation/config/clone.txt

+1 -1

@@ -4,7 +4,7 @@ clone.defaultRemoteName::

4 option to linkgit:git-clone[1].

5

6 clone.rejectShallow::

7 - Reject to clone a repository if it is a shallow one; this can be overridden by

7 + Reject cloning a repository if it is a shallow one; this can be overridden by

8 passing the `--reject-shallow` option on the command line. See linkgit:git-clone[1]

9

10 clone.filterSubmodules::

Documentation/config/column.txt

+1 -1

@@ -43,7 +43,7 @@ column.branch::

43 See `column.ui` for details.

44

45 column.clean::

46 - Specify the layout when list items in `git clean -i`, which always

46 + Specify the layout when listing items in `git clean -i`, which always

47 shows files and directories in columns. See `column.ui` for details.

48

49 column.status::

Documentation/git-clean.txt

+1 -1

@@ -103,7 +103,7 @@ filter by pattern::

103 This shows the files and directories to be deleted and issues an

104 "Input ignore patterns>>" prompt. You can input space-separated

105 patterns to exclude files and directories from deletion.

106 - E.g. "*.c *.h" will excludes files end with ".c" and ".h" from

106 + E.g. "*.c *.h" will exclude files ending with ".c" and ".h" from

107 deletion. When you are satisfied with the filtered result, press

108 ENTER (empty) back to the main menu.

109

Documentation/git-help.txt

+3 -3

@@ -48,7 +48,7 @@ OPTIONS

48 -------

49 -a::

50 --all::

51 - Prints all the available commands on the standard output.

51 + Print all the available commands on the standard output.

52

53 --no-external-commands::

54 When used with `--all`, exclude the listing of external "git-*"

@@ -69,10 +69,10 @@ OPTIONS

69

70 -g::

71 --guides::

72 - Prints a list of the Git concept guides on the standard output.

72 + Print a list of the Git concept guides on the standard output.

73

74 --user-interfaces::

75 - Prints a list of the repository, command and file interfaces

75 + Print a list of the repository, command and file interfaces

76 documentation on the standard output.

77 +

78 In-repository file interfaces such as `.git/info/exclude` are

Documentation/git-whatchanged.txt

+1 -1

@@ -18,7 +18,7 @@ Shows commit logs and diff output each commit introduces.

18

19 New users are encouraged to use linkgit:git-log[1] instead. The

20 `whatchanged` command is essentially the same as linkgit:git-log[1]

21 -but defaults to show the raw format diff output and to skip merges.

21 +but defaults to showing the raw format diff output and skipping merges.

22

23 The command is primarily kept for historical reasons; fingers of

24 many people who learned Git long before `git log` was invented by

Documentation/gitcli.txt

+2 -2

@@ -23,7 +23,7 @@ arguments. Here are the rules:

23 A subcommand may take dashed options (which may take their own

24 arguments, e.g. "--max-parents 2") and arguments. You SHOULD

25 give dashed options first and then arguments. Some commands may

26 - accept dashed options after you have already gave non-option

26 + accept dashed options after you have already given non-option

27 arguments (which may make the command ambiguous), but you should

28 not rely on it (because eventually we may find a way to fix

29 these ambiguity by enforcing the "options then args" rule).

@@ -42,7 +42,7 @@ arguments. Here are the rules:

42 `git diff HEAD --` to ask for the latter.

43

44 * Without disambiguating `--`, Git makes a reasonable guess, but errors

45 - out and asking you to disambiguate when ambiguous. E.g. if you have a

45 + out and asks you to disambiguate when ambiguous. E.g. if you have a

46 file called HEAD in your work tree, `git diff HEAD` is ambiguous, and

47 you have to say either `git diff HEAD --` or `git diff -- HEAD` to

48 disambiguate.

Documentation/gitformat-chunk.txt

+1 -1

@@ -67,7 +67,7 @@ caller is responsible for opening the `hashfile` and writing header

67 information so the file format is identifiable before the chunk-based

68 format begins.

69

70 -Then, call `add_chunk()` for each chunk that is intended for write. This

70 +Then, call `add_chunk()` for each chunk that is intended for writing. This

71 populates the `chunkfile` with information about the order and size of

72 each chunk to write. Provide a `chunk_write_fn` function pointer to

73 perform the write of the chunk data upon request.

Documentation/gitformat-pack.txt

+3 -3

@@ -117,7 +117,7 @@ the delta data is a sequence of instructions to reconstruct the object

117 from the base object. If the base object is deltified, it must be

118 converted to canonical form first. Each instruction appends more and

119 more data to the target object until it's complete. There are two

120 -supported instructions so far: one for copy a byte range from the

120 +supported instructions so far: one for copying a byte range from the

121 source object and one for inserting new data embedded in the

122 instruction itself.

123

@@ -137,7 +137,7 @@ copy. Offset and size are in little-endian order.

137

138 All offset and size bytes are optional. This is to reduce the

139 instruction size when encoding small offsets or sizes. The first seven

140 -bits in the first octet determines which of the next seven octets is

140 +bits in the first octet determine which of the next seven octets is

141 present. If bit zero is set, offset1 is present. If bit one is set

142 offset2 is present and so on.

143

@@ -163,7 +163,7 @@ converted to 0x10000.

163

164 This is the instruction to construct target object without the base

165 object. The following data is appended to the target object. The first

166 -seven bits of the first octet determines the size of data in

166 +seven bits of the first octet determine the size of data in

167 bytes. The size must be non-zero.

168

169 ==== Reserved instruction

Documentation/gitsubmodules.txt

+2 -2

@@ -78,7 +78,7 @@ Submodule operations can be configured using the following mechanisms

78

79 * The command line for those commands that support taking submodules

80 as part of their pathspecs. Most commands have a boolean flag

81 - `--recurse-submodules` which specify whether to recurse into submodules.

81 + `--recurse-submodules` which specifies whether to recurse into submodules.

82 Examples are `grep` and `checkout`.

83 Some commands take enums, such as `fetch` and `push`, where you can

84 specify how submodules are affected.

@@ -274,7 +274,7 @@ will not be checked out by default; you can instruct `clone` to recurse

274 into submodules. The `init` and `update` subcommands of `git submodule`

275 will maintain submodules checked out and at an appropriate revision in

276 your working tree. Alternatively you can set `submodule.recurse` to have

277 -`checkout` recursing into submodules (note that `submodule.recurse` also

277 +`checkout` recurse into submodules (note that `submodule.recurse` also

278 affects other Git commands, see linkgit:git-config[1] for a complete list).

279

280

Documentation/gitweb.conf.txt

+1 -1

@@ -53,7 +53,7 @@ following order:

53 `/etc/gitweb-common.conf`),

54

55 * either per-instance configuration file (defaults to 'gitweb_config.perl'

56 - in the same directory as the installed gitweb), or if it does not exists

56 + in the same directory as the installed gitweb), or if it does not exist

57 then fallback system-wide configuration file (defaults to `/etc/gitweb.conf`).

58

59 Values obtained in later configuration files override values obtained earlier

Documentation/gitweb.txt

+2 -2

@@ -8,7 +8,7 @@ gitweb - Git web interface (web frontend to Git repositories)

8 SYNOPSIS

9 --------

10 To get started with gitweb, run linkgit:git-instaweb[1] from a Git repository.

11 -This would configure and start your web server, and run web browser pointing to

11 +This will configure and start your web server, and run a web browser pointing to

12 gitweb.

13

14

@@ -24,7 +24,7 @@ Gitweb provides a web interface to Git repositories. Its features include:

24 * Viewing the blame/annotation details of any file (if enabled).

25 * Generating RSS and Atom feeds of commits, for any branch.

26 The feeds are auto-discoverable in modern web browsers.

27 -* Viewing everything that was changed in a revision, and step through

27 +* Viewing everything that was changed in a revision, and stepping through

28 revisions one at a time, viewing the history of the repository.

29 * Finding commits whose commit messages match a given search term.

30

Documentation/technical/reftable.txt

+1 -1

@@ -247,7 +247,7 @@ uint32( hash_id )

247 ....

248

249 The header is identical to `version_number=1`, with the 4-byte hash ID

250 -("sha1" for SHA1 and "s256" for SHA-256) append to the header.

250 +("sha1" for SHA1 and "s256" for SHA-256) appended to the header.

251

252 For maximum backward compatibility, it is recommended to use version 1 when

253 writing SHA1 reftables.

documentation: fix verb tense