Skip to content

Commit 8160e62

Browse files
authored
Fixed typos on spec2.md
Fixed some typos.
1 parent a2598aa commit 8160e62

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

spec2.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -36,10 +36,10 @@
3636
- [A (simple) sample presenter](#SpSimpleExamplePresenter)
3737
# Spec Applications
3838

39-
A SpApplication is a class that handles many aspects of a Spec Application (hence it's name) in a convenient fashion.
40-
SpApplication handles your application initialisation, configuration and resources. It also keeps the windows you have currently opened.
41-
## Initialisation
42-
Initialisation of an application includes (non mandatory): configure the backend you want to use, add useful resources and define a start method that will call your initial window.
39+
A SpApplication is a class that handles many aspects of an Spec Application (hence it's name) in a convenient fashion.
40+
SpApplication handles your application initialization, configuration and resources. It also keeps the windows you have currently opened.
41+
## Initialization
42+
Initialization of an application includes (non mandatory): configure the backend you want to use, add useful resources and define a start method that will call your initial window.
4343
### Configure backend
4444
Spec2 includes several backends (for the moment, Morphic and Gtk). A SpApplication configures a Morphic backend by default, but you can change it using `#useBackend:` or `#useBackend:with:` and sending the backend identifier and optionally a configuration (you may want to do specific backend things to configure your application behavior).
4545

@@ -56,7 +56,7 @@ app run
5656

5757
see also: [SpApplicationConfiguration](#SpApplicationConfiguration)
5858
### Add resources
59-
During initialisation, you may want to add special resources (like icons, themes, etc.).
59+
During initialization, you may want to add special resources (like icons, themes, etc.).
6060
While you can add your own way to access resources, SpApplication provides a property registration mechanism (a simple Dictionary and accessors), you may find useful to search at `accessing properties` protocol.
6161
### Defining a start method.
6262
This is useful to give your application a starting window (in general, this is what you want).
@@ -69,7 +69,7 @@ MyApplication>>start
6969

7070
# Application Configurations
7171

72-
Tipically, each Spec application will implement one or several configurations (for example, to run on Morphic or Gtk) by extending this class or one of its children.
72+
Typically, each Spec application will implement one or several configurations (for example, to run on Morphic or Gtk) by extending this class or one of its children.
7373
A configuration takes the responsibility to prepare an application to run properly. This preparation can be different depending on the platform where it is running, that's why you have several extension points you can extend/override:
7474

7575
- `configure:` a generic configuration point that normally will dispatch the configuration to a plarform specific method.
@@ -79,7 +79,7 @@ A configuration takes the responsibility to prepare an application to run proper
7979
see also: [SpMorphicConfiguration](#SpMorphicConfiguration), [SpGtkConfiguration](#SpGtkConfiguration)
8080
# Morphic configurations
8181

82-
Morphic configurations will prepare your application to run in a Morphic backend. Tipically, you will not change much of what is already provided on a Pharo system, but there are several entry points you may want to extend/override:
82+
Morphic configurations will prepare your application to run in a Morphic backend. Typically, you will not change much of what is already provided on a Pharo system, but there are several entry points you may want to extend/override:
8383

8484
- [SpMorphicConfiguration>>#styleSheet](#SpMorphicConfiguration_styleSheet)
8585

@@ -108,7 +108,7 @@ SpStyleSTONReader fromString: '
108108
]'
109109
```
110110

111-
As a more complex example, see [SpStyle class>>#createDefaultStyleSheet](#SpStyle class_createDefaultStyleSheet) who defines the default behaviour of all elements of a Morphic Spec backend.
111+
As a more complex example, see [SpStyle class>>#createDefaultStyleSheet](#SpStyle class_createDefaultStyleSheet) which defines the default behaviour of all elements of a Morphic Spec backend.
112112
## Referencing style elements in your presenters
113113
You can add styles to your presenters easily by using [class:SpAbstractWidgetPresenter](>#addStyle:)
114114
**TODO**: more examples
@@ -506,4 +506,4 @@ aWindowPresenter
506506
title: 'Simple Application';
507507
initialExtent: 400@400
508508
```
509-
509+

0 commit comments

Comments
 (0)