From 8ee93ae26786c11f5169aedceb5b2670ff53568a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonathan=20Neusch=C3=A4fer?= Date: Mon, 9 Apr 2018 13:05:29 +0200 Subject: Documentation: Fix a bunch of typos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: I25dca2e231343cfdad61a638f0302726a6aa3f8b Signed-off-by: Jonathan Neuschäfer Reviewed-on: https://review.coreboot.org/25571 Tested-by: build bot (Jenkins) Reviewed-by: Arthur Heymans Reviewed-by: Patrick Georgi --- Documentation/corebootBuildingGuide.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'Documentation/corebootBuildingGuide.tex') diff --git a/Documentation/corebootBuildingGuide.tex b/Documentation/corebootBuildingGuide.tex index 867891b431..e451ad4fd6 100644 --- a/Documentation/corebootBuildingGuide.tex +++ b/Documentation/corebootBuildingGuide.tex @@ -413,8 +413,8 @@ $ git commit -m "my first change." \end{verbatim} } -% Does anyone have a better word to describe the phylosophy of spliting changes to patches? -You need to realize that the changes you have made should be well devided into +% Does anyone have a better word to describe the philosophy of splitting changes to patches? +You need to realize that the changes you have made should be well divided into several commits. Each of them has one and only one meaning. You could use git rebase -i to split, squash, remove, rewrite you comment. -- cgit v1.2.3