From c80b55b8e8443af0fc1f9563b32ff279e2aa3262 Mon Sep 17 00:00:00 2001
From: Evgeny Gavrin <e.gavrin@samsung.com>
Date: Sun, 14 Jun 2015 19:00:48 +0300
Subject: [PATCH] Fix Internals and remove favicon

---
 04.internals.md |   6 +++---
 favicon.ico     | Bin 318 -> 0 bytes
 2 files changed, 3 insertions(+), 3 deletions(-)
 delete mode 100644 favicon.ico

diff --git a/04.internals.md b/04.internals.md
index f6415f7d9..49540d9af 100644
--- a/04.internals.md
+++ b/04.internals.md
@@ -5,7 +5,7 @@ permalink: /internals/
 ---
 
 * toc
-{TOC}
+{:toc}
 
 # High-Level Design
 ![High-Level Design]({{ site.baseurl }}/img/engines_high_level_design.jpg)
@@ -416,7 +416,7 @@ Otherwise, object's property set is iterated fully and corresponding record is r
 
 ECMA-defined runtime operations are implemented mostly with routine having the following signature:
 
-`ecma_completion_value_t ecma_op_* ([ecma_value_t argumants])`  
+`ecma_completion_value_t ecma_op_* ([ecma_value_t arguments])`  
 or  
 `ecma_property_t * ecma_op_[find/get]*_property (objs, name string, ...)`  
 
@@ -453,7 +453,7 @@ Rules for completion value are the same as rules for values, contained in them.
 ## Opcode handler structure
 
 Most opcode handlers consists of the following steps:
-1. Decode instruction (i.e. extract "idx"-s)
+1. Decode instruction (i.e. extract `idx`-s)
 2. Read input values from variables/registers
 3. Perform necessary type conversions
 4. Perform calls to runtime
diff --git a/favicon.ico b/favicon.ico
deleted file mode 100644
index c2d199a5a9c9b0a92678a29e16e0dc9eea8f6fd4..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001

literal 318
zcmb7=F$w}P5Jg{zU}-8_Ew>DgH*g`>3U~}JBB`|U8iJ*brCoL=vb!KQ&gcK1{7Hro
zaEcIu>VnR}8t9Zkxm8+jm79LVdSjhWPin1{Qb;L{@t^KRqFs^bMa_!~7EEsIwwHF$
tM}uZN#hlxe#{K~NKKd`$@iudM+j|4A72KC_@xPh%Ppn*?dA!2y0Rx^kA*28R