1 files changed, 17 insertions, 17 deletions
diff --git a/doc/markdown/architecture/index.md b/doc/markdown/architecture/index.md
index 324c5260a..45e52fa8e 100644
--- a/doc/markdown/architecture/index.md
+++ b/doc/markdown/architecture/index.md
@@ -2,7 +2,7 @@
 
 ## Introduction
 
-Rspamd is a universal spam filtering system based on event-driven processing 
+Rspamd is a universal spam filtering system based on event-driven processing
 model. It means that rspamd is intended not to block anywhere in the code. To
 process messages rspamd uses a set of so called `rules`. Each `rule` is a symbolic
 name associated with some message property. For example, we can define the following
@@ -24,7 +24,7 @@ written in Lua. There is no real difference between these two types with the exc
 that C modules are embeded all the time and can be enabled in `filters` attribute
 in the `options` section of the config:
 
-~~~nginx
+~~~ucl
 options {
  filters = "regexp,surbl,spf,dkim,fuzzy_check,chartable,email";
  ...
@@ -83,7 +83,7 @@ Rspamd defines the following actions:
 These actions are just recommendations for MTA and are not to be strictly followed.
 For all actions that are greater or equal than `greylist` it is recommended to
 perform explicit greylisting. `Add header` and `rewrite subject` actions are very
-close in semantics and are both considered as `probable spam`. `Reject` is a 
+close in semantics and are both considered as `probable spam`. `Reject` is a
 strong rule that usually means that a message should be really rejected by MTA.
 The triggering score for these actions should be specified according to their logic
 priorities. If two actions have the same weight, the result is unspecified.
@@ -106,7 +106,7 @@ Rspamd uses statistic algorithms to precise the final score of a message. Curren
 the only algorithm defined is OSB-Bayes. You may find the concrete details of this
 algorithm in the following [paper](http://osbf-lua.luaforge.net/papers/osbf-eddc.pdf).
 Rspamd uses window size of 5 words in its classification. During classification procedure,
-rspamd split a message to a set of tokens. 
+rspamd split a message to a set of tokens.
 
 Tokens are separated by punctiation or space characters. Short tokens (less than 3 symbols) are ignored. For each token rspamd
 calculates two non-cryptographic hashes used subsequently as indices. All these tokens
@@ -115,7 +115,7 @@ is a set of token chains, indexed by the first hash. A new token may be inserted
 chain, and if this chain is full then rspamd tries to expire less significant tokens to
 insert a new one. It is possible to obtain the current state of tokens by running
 
-	rspamc stat 
+	rspamc stat
 
 command that asks controller for free and used tokens in each statfile.
 Please note that if a statfile is close to be completely filled then during subsequent
@@ -123,23 +123,23 @@ learning you will loose existing data. Therefore, it is recommended to increase
 such statfiles.
 
 ## Running rspamd
- 
-There are several command-line options that can be passed to rspamd. All of them can be displayed by passing `--help` argument: 
 
-All options are optional: by default rspamd would try to read `etc/rspamd.conf` config file and run as daemon. Also there is test mode that can be turned on by passing `-t` argument. In test mode, rspamd reads config file and checks its syntax. If a configuration file is OK, then exit code is zero. Test mode is useful for testing new config file withou rspamd restart. `--convert-config` option can be used to convert old style (pre 0.6.0) config to [ucl](../configuration/ucl.md) one: 
+There are several command-line options that can be passed to rspamd. All of them can be displayed by passing `--help` argument:
+
+All options are optional: by default rspamd would try to read `etc/rspamd.conf` config file and run as daemon. Also there is test mode that can be turned on by passing `-t` argument. In test mode, rspamd reads config file and checks its syntax. If a configuration file is OK, then exit code is zero. Test mode is useful for testing new config file withou rspamd restart. `--convert-config` option can be used to convert old style (pre 0.6.0) config to [ucl](../configuration/ucl.md) one:
 
 	$ rspamd -c ./rspamd.xml --convert-conf ./rspamd.conf
 
- 
+
 ## Managing rspamd using signals
 
-First of all, it is important to note that all user's signals should be sent to rspamd main process and not to its children (as for child processes these signals can have other meanings). To determine which process is main you can use two ways: 
+First of all, it is important to note that all user's signals should be sent to rspamd main process and not to its children (as for child processes these signals can have other meanings). To determine which process is main you can use two ways:
 
-- by reading pidfile: 
+- by reading pidfile:
 
 		$ cat pidfile
 
-- by getting process info: 
+- by getting process info:
 
 		$ ps auxwww | grep rspamd
 		nobody 28378  0.0  0.2 49744  9424   rspamd: main process
@@ -147,14 +147,14 @@ First of all, it is important to note that all user's signals should be sent to
 		nobody 64083  0.0  0.3 51792 11036   rspamd: worker process
 		nobody 64084  0.0  2.7 158288 114200 rspamd: controller process
 		nobody 64085  0.0  1.8 116304 75228  rspamd: fuzzy storage
-	
+
 		$ ps auxwww | grep rspamd | grep main
 		nobody 28378  0.0  0.2 49744  9424   rspamd: main process
 
 After getting the pid of main process it is possible to manage rspamd with signals:
- 
-- `SIGHUP` - restart rspamd: reread config file, start new workers (as well as controller and other processes), stop accepting connections by old workers, reopen all log files. Note that old workers would be terminated after one minute that should allow to process all pending requests. All new requests to rspamd will be processed by newly started workers. 
+
+- `SIGHUP` - restart rspamd: reread config file, start new workers (as well as controller and other processes), stop accepting connections by old workers, reopen all log files. Note that old workers would be terminated after one minute that should allow to process all pending requests. All new requests to rspamd will be processed by newly started workers.
 - `SIGTERM` - terminate rspamd system.
-- `SIGUSR1` - reopen log files (useful for log files rotation). 
+- `SIGUSR1` - reopen log files (useful for log files rotation).
 
-These signals may be used in start scripts as it is done in `FreeBSD` start script. Restarting of rspamd is performed softly: no connections are dropped and if a new config is incorrect then the old config is used. 
-\ No newline at end of file
+These signals may be used in start scripts as it is done in `FreeBSD` start script. Restarting of rspamd is performed softly: no connections are dropped and if a new config is incorrect then the old config is used.