# [PATCH] Documentation: fix typos for the reference in new-command.txt

1 messages from 2017-11-09 to 2017-11-09. Participants: Kazuo Yagi.
Thread: https://gitlist.dev/t/47143

## Kazuo Yagi, 2017-11-09 12:36

Subject: [PATCH] Documentation: fix typos for the reference in new-command.txt
Message-ID: <0102015fa0c804c4-7dc9e5b3-e34e-45e2-b92f-3f4183406020-000000@eu-west-1.amazonses.com>
URL: https://gitlist.dev/e/0102015fa0c804c4-7dc9e5b3-e34e-45e2-b92f-3f4183406020-000000%40eu-west-1.amazonses.com

```
---
 Documentation/howto/new-command.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/howto/new-command.txt b/Documentation/howto/new-command.txt
index 15a4c8031f1f3..ac73c98be72de 100644
--- a/Documentation/howto/new-command.txt
+++ b/Documentation/howto/new-command.txt
@@ -1,13 +1,13 @@
 From: Eric S. Raymond <esr@thyrsus.com>
 Abstract: This is how-to documentation for people who want to add extension
- commands to Git.  It should be read alongside api-builtin.txt.
+ commands to Git.  It should be read alongside builtin.h.
 Content-type: text/asciidoc
 
 How to integrate new subcommands
 ================================
 
 This is how-to documentation for people who want to add extension
-commands to Git.  It should be read alongside api-builtin.txt.
+commands to Git.  It should be read alongside builtin.h.
 
 Runtime environment
 -------------------
@@ -48,7 +48,7 @@ binary); this organization makes it easy for people reading the code
 to find things.
 
 See the CodingGuidelines document for other guidance on what we consider
-good practice in C and shell, and api-builtin.txt for the support
+good practice in C and shell, and builtin.h for the support
 functions available to built-in commands written in C.
 
 What every extension command needs

--
https://github.com/git/git/pull/430

```