Add a reminder comment for table formatting

The formatting of the tables in the book follow the rule of column seperations
by tab characters. Remind the translators to follow this rule where it is applied
in the original text.

Author: jnavila

en/02-git-basics/01-chapter2.markdown

@@ -561,6 +561,11 @@ The most interesting option is `format`, which allows you to specify your own lo
 
 Table 2-1 lists some of the more useful options that format takes.
 
+<!-- Attention to translators: this is a table declaration.
+The lines must be formatted as follows
+<TAB><First column text><TAB><Second column text>
+-->
+
 	Option	Description of Output
 	%H	Commit hash
 	%h	Abbreviated commit hash
@@ -596,6 +601,11 @@ The `oneline` and `format` options are particularly useful with another `log` op
 
 Those are only some simple output-formatting options to `git log` — there are many more. Table 2-2 lists the options we’ve covered so far and some other common formatting options that may be useful, along with how they change the output of the `log` command.
 
+<!-- Attention to translators: this is a table declaration.
+The lines must be formatted as follows
+<TAB><First column text><TAB><Second column text>
+-->
+
 	Option	Description
 	-p	Show the patch introduced with each commit.
 	--word-diff	Show the patch in a word diff format.
@@ -625,6 +635,11 @@ The last really useful option to pass to `git log` as a filter is a path. If you
 
 In Table 2-3 we’ll list these and a few other common options for your reference.
 
+<!-- Attention to translators: this is a table declaration.
+The lines must be formatted as follows
+<TAB><First column text><TAB><Second column text>
+-->
+
 	Option	Description
 	-(n)	Show only the last n commits
 	--since, --after	Limit the commits to those made after the specified date.