-After edits to a file or group of files are completed, the differences between the local working copy and the version on the FreeBSD repository must be collected into a single file for submission.
-These _diff_ files are produced by redirecting the output of `git diff` into a file:
+After edits to a file or group of files are completed, the differences between the local working copy and the version on the FreeBSD repository must be collected into a logical change called a commit, and submitted as a patch.
[source,shell]
....
% cd ~/doc
-% git diff > doc-fix-spelling.diff
+% vi README.md
+% git commit -a
....
-Give the file a meaningful name that identifies the contents.
-The example above is for spelling fixes to the whole documentation tree.
+They should be organized as one logical change per commit, with properly set authorship, and a message according to extref:{committers-guide}[project guidelines, commit-log-messages].
-If the diff file is to be submitted with the web "link:https://bugs.FreeBSD.org/bugzilla/enter_bug.cgi[Submit a FreeBSD problem report]" interface, add a [.filename]#.txt# extension to give the earnest and simple-minded web form a clue that the contents are plain text.
-
-Be careful: `git diff` includes all changes made in the current directory and any subdirectories.
-If there are files in the working copy with edits that are not ready to be submitted yet, provide a list of only the files that are to be included:
+Be careful: `git commit -a` includes all changes made in the current directory and any subdirectories, except deleted files.
+If there are files in the working copy with edits that are not ready to be submitted yet, add a list of only the files that are to be included: