Rewrite summary of build history in introduction

[hubacji1/oneflow.git] / intro.md

diff --git a/intro.md b/intro.md
index 4050b82bab6d104c776b54ec11822481877ebd1d..16202cb5e0d4fdf76b0228aaf165831fd414a253 100644 (file)
--- a/intro.md
+++ b/intro.md
@@ -104,15 +104,10 @@ And staged patches by:
 git diff --cached
 ```
 
-# Commit - build repository history
-You get ready the files to be commited to the history by `git add FILE`
-command. If you change your mind, you may `git reset FILE` that file.
-
-If only huks of lines in file should be prepared for commiting to the history
-`git add -p FILE` and `git reset -p FILE` can be used respectively.
-
-Before commiting to the history log check twice `git diff --cached` and `git
-diff`.
+# Build repository history
+Use `git commit` to store staged patches to git history. Moving patches and
+files between states described above is done by `git add` and `git reset`
+commands.
 
 When sure that staged changes should be commited to the history, use `git
 commit -m'COMMIT MSG'`. For commit messages, some rules are good to keep in