PharoTour - fix typo

Author: dmitrizagidulin

PharoTour/PharoTour.pillar

@@ -18,17 +18,17 @@ described here, do not be surprised.
 
 !!Pharo components
 
-Like many Smalltalk-derived systems, Pharo consists of four main component files. 
+Like many Smalltalk-derived systems, Pharo consists of four main component files.
 Although you do not need to deal with them directly for the purposes
 of this book, it is useful to understand the roles they play.
 
 ""1."" The ""virtual machine"" (VM) is the only component that is
 different for each operating system. The VM executable is named:
-- ==Pharo.exe== for Windows; 
+- ==Pharo.exe== for Windows;
 - ==pharo== for Linux ; and
 - ==Pharo== for OSX (inside a package also named ==Pharo==).
 
-The other components below are portable across operating systems, 
+The other components below are portable across operating systems,
 and can be copied and run on any appropriate virtual machine.
 
 ""2."" The ""sources"" file contains source code for parts of
@@ -37,33 +37,33 @@ file is generated once per major release of Pharo.
 For Pharo 4.0, this file is named ==PharoV40.sources==.
 
 
-""3."" The ""changes"" file logs of all source code 
+""3."" The ""changes"" file logs of all source code
 modifications since the ==.sources== file was generated.
 This facilitates a per method history for diffs or reverting.
 Each release provides a near empty file named for the release,
 for example ==Pharo4.0.changes==.
 
-""4."" The ""image"" file provides a frozen in time snapshot 
-of a running Pharo system. This is the heart of Pharo, 
-containing the live state of all objects in the system 
+""4."" The ""image"" file provides a frozen in time snapshot
+of a running Pharo system. This is the heart of Pharo,
+containing the live state of all objects in the system
 (including classes and methods, since they are objects too).
-The file is named for the release like ==Pharo4.0.image==.
+The file is named for the release (like ==Pharo4.0.image==).
 
-The ==.image== and ==.changes== files provided by a Pharo release 
-are the starting point for a live environment that you adapt to your needs. 
-As you work in Pharo, these files are modified, 
-so you need to make sure that they are writable. 
-The ==.image== and ==.changes== files are intimately linked 
+The ==.image== and ==.changes== files provided by a Pharo release
+are the starting point for a live environment that you adapt to your needs.
+As you work in Pharo, these files are modified,
+so you need to make sure that they are writable.
+The ==.image== and ==.changes== files are intimately linked
 and should always be kept together, with matching base filenames.
-Never edit them directly with a text editor, as ==.images== holds your 
-live object runtime memory,which indexes into the ==.changes== files 
-for the source. 
+Never edit them directly with a text editor, as ==.images== holds your
+live object runtime memory, which indexes into the ==.changes== files
+for the source.
 It is a good idea to keep a backup copy of the downloaded ==.image== and ==.changes==
 files so you can always start from a fresh image and reload your code.
 
-The four main component files above can be placed in the same directory, 
-but its also possible to put the Virtual Machine and sources file in separate
-directory where everyone has read-only access to them. 
+The four main component files above can be placed in the same directory,
+although it's also possible to put the Virtual Machine and sources file in
+separate directory where everyone has read-only access to them.
 Do whatever works best for your style of working and your operating system.
 
 !!Getting started