typos

yegor256 · yegor256 · commit 39672e9fc25d · 2025-04-17T16:46:18.000+03:00
diff --git a/Gemfile b/Gemfile
@@ -1,3 +1,6 @@
+# SPDX-FileCopyrightText: Copyright (c) 2022-2025 Objectionary.com
+# SPDX-License-Identifier: MIT
+
 source 'https://rubygems.org'
 
 gem 'jekyll', '~>4.3'
diff --git a/_layouts/default.html b/_layouts/default.html
@@ -1,4 +1,7 @@
 ---
+# SPDX-FileCopyrightText: Copyright (c) 2022-2025 Objectionary.com
+# SPDX-License-Identifier: MIT
+
 layout: default
 ---
 <!DOCTYPE html>
diff --git a/_layouts/post.html b/_layouts/post.html
@@ -1,4 +1,7 @@
 ---
+# SPDX-FileCopyrightText: Copyright (c) 2022-2025 Objectionary.com
+# SPDX-License-Identifier: MIT
+
 layout: default
 ---
 
diff --git a/_layouts/static.html b/_layouts/static.html
@@ -1,4 +1,7 @@
 ---
+# SPDX-FileCopyrightText: Copyright (c) 2022-2025 Objectionary.com
+# SPDX-License-Identifier: MIT
+
 layout: default
 ---
 
diff --git a/_posts/2022/08/2022-08-31-new-while-dataization-result.md b/_posts/2022/08/2022-08-31-new-while-dataization-result.md
@@ -18,7 +18,7 @@ is `FALSE`.
 
 When the condition is `TRUE` we get the result of the last dataization object in the `while` loop.
 
-When the condition is `FALSE` such dataization result become `FALSE`.
+When the condition is `FALSE` such dataization result becomes `FALSE`.
 
 Let's check it out with examples. In this case, the result of condition `x.lt 6`
 is `TRUE` for at least one iteration. So the result of dataization `when-true` object is `6`:
diff --git a/_posts/2022/11/2022-11-25-xmir-guide.md b/_posts/2022/11/2022-11-25-xmir-guide.md
@@ -11,7 +11,7 @@ XMIR is a dialect of [XML](https://en.wikipedia.org/wiki/XML),
 which we use to represent a parsed
 [EO](https://www.eolang.org) object. It is a pretty simple format,
 which has a few
-important tricks, which I share below in this blog post. You may
+important tricks that I share below in this blog post. You may
 also want to check our [schema](https://en.wikipedia.org/wiki/XML_schema):
 [`XMIR.xsd`][xsd]
 (it is also [rendered in HTML](https://www.eolang.org/XMIR.html),
@@ -33,16 +33,16 @@ Consider this simple EO object that prints `"Hello, world!"`:
     "world!"
 ```
 
-If we parse it using `EoSyntax` class from [eo-parser],
+If we parse it using the `EoSyntax` class from [eo-parser],
 we will get this XMIR (or very similar):
 
 ```xml
-<object 
+<object
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- dob="2024-12-27T11:00:08" 
- ms="98" 
+ dob="2024-12-27T11:00:08"
+ ms="98"
  revision="27abe8b"
- time="2025-04-17T09:32:04.455112Z" 
+ time="2025-04-17T09:32:04.455112Z"
  version="0.56.0"
  xsi:noNamespaceSchemaLocation="https://www.eolang.org/xsd/XMIR-0.56.0.xsd">
  <listing># App.
@@ -180,7 +180,7 @@ of the `<tail>` separated by spaces.
 
 ## Objects
 
-The `<object>` element must contain only one `<o/>` element which represents an 
+The `<object>` element must contain only one `<o/>` element which represents an
 object being parsed. The `<o/>` element may have a few optional attributes:
 
 * `line` and `pos` are the number of the line where the object
@@ -194,7 +194,7 @@ There could be no other attributes.
 
 ## Special cases
 
-1. The `<o/>` elements that have nested `<o>` element with `name` which 
+1. The `<o/>` elements that have nested `<o>` element with `name` which
 value is `λ` are **atoms**. Atoms must not have `base` attribute:
 ```xml
 <o name="try">
@@ -220,7 +220,7 @@ nested `<o>` element with text.
 </o>
 ```
 
-4. The `name` attribute of `<o/>` element may be **auto generated** by EO parser. 
+4. The `name` attribute of `<o/>` element may be **auto generated** by EO parser.
 In such case it's look like:
 ```xml
 <o name="a🌵104"/>
@@ -229,7 +229,7 @@ In such case it's look like:
 Such `name` consists of several parts:
 - char `a` (ascii 97) that stands for "auto-generated"
 - char `🌵` that is just a pretty character prohibited by EO grammar
-- number `104` which is joined line and position of the place where 
+- number `104` which is joined line and position of the place where
 the object is found.
 
 Such names are unique through entire XMIR.
@@ -239,7 +239,7 @@ Such names are unique through entire XMIR.
 ```xml
 <o base="Q.org.eolang.number" as="α2"/>
 ```
-Here the first character is `α` (alpha), the number `2` is the position of the 
+Here the first character is `α` (alpha), the number `2` is the position of the
 attribute.
 
 <hr/>
diff --git a/_posts/2023/08/2023-08-05-storing-objects-formed-differently-into-cage.md b/_posts/2023/08/2023-08-05-storing-objects-formed-differently-into-cage.md
@@ -35,7 +35,7 @@ object `lisa` "was formed by" object `cat` and has the same "form"—"cat."
 Let's get back to the object `cage`. The object is used as temporary storage of objects in memory.
 It should be remembered that `cage` does not dataize a stored object.
 
-Here is the typical example how `cage` was used before:
+Here is the typical example of how `cage` was used before:
 
 ```
 cage 0 > cg
@@ -47,7 +47,7 @@ seq > @
 Here we copy object `cage` and store the object `0` (which is "formed by" object `int`) in it, and
 then we write an object `lisa` to it.
 
-Such behavior is prohibited now and will lead to exception throwing.
+Such behavior is prohibited now and will lead to an exception being thrown.
 Object `cage` can store inside only objects of the same "form."
 
 The next code will work since object `cat` and `lisa` have the same "form"–"cat":
diff --git a/_posts/2024/05/2024-05-02-rho-sigma-delta-lambda.md b/_posts/2024/05/2024-05-02-rho-sigma-delta-lambda.md
@@ -195,12 +195,12 @@ The last special thing we're observing is `λ` (Lambda) asset. Let's look at it
 - The `λ` asset, as well as the `φ` attribute, also allows reusing the attributes:
 
 ```
-[] > mars-termerature /float # measures the temperature on Mars and returns float
+[] > mars-temperature /float # measures the temperature on Mars and returns float
 
 mars-temperature.div 10 > divided
 ```
 
-Here, as you may see, `mars-termerature` is the atom that does not have an attribute `div` and
+Here, as you may see, `mars-temperature` is the atom that does not have an attribute `div` and
 returns `float`. However, we can still retrieve the attribute `div` from it. It will go to the
 `λ` asset, execute it, do some calculations, return us some `float`, and the `div` attribute will
 be taken from this `float`.
diff --git a/css/main.scss b/css/main.scss
@@ -1,5 +1,10 @@
 ---
 ---
+/**
+ * SPDX-FileCopyrightText: Copyright (c) 2022-2025 Objectionary.com
+ * SPDX-License-Identifier: MIT
+ */
+
 @charset 'utf-8';
 
 body {
diff --git a/index.html b/index.html
@@ -1,4 +1,7 @@
 ---
+# SPDX-FileCopyrightText: Copyright (c) 2022-2025 Objectionary.com
+# SPDX-License-Identifier: MIT
+
 layout: default
 title: "News About EO Programming Language"
 description: |
