about summary refs log tree commit diff stats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/ir/lift.ipynb2
-rw-r--r--doc/locationdb/locationdb.ipynb4
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/ir/lift.ipynb b/doc/ir/lift.ipynb
index aaa20a0b..56ce6fbd 100644
--- a/doc/ir/lift.ipynb
+++ b/doc/ir/lift.ipynb
@@ -1729,7 +1729,7 @@
     "\n",
     "```\n",
     "\n",
-    "This is the generic code used in `x86_64` to model function calls. But you can finely model functions. For example, suppose you are analysing code on `x86_32` with `stdcall` convention. Suppose you know the callee clean its stack arguments. Supppose as well you know for each function how many arguments it has. You can then customize the model to match the callee and compute the correct stack modification, as well as getting the arguments from stack:\n",
+    "This is the generic code used in `x86_64` to model function calls. But you can finely model functions. For example, suppose you are analysing code on `x86_32` with `stdcall` convention. Suppose you know the callee clean its stack arguments. Suppose as well you know for each function how many arguments it has. You can then customize the model to match the callee and compute the correct stack modification, as well as getting the arguments from stack:\n",
     "\n",
     "\n",
     "\n"
diff --git a/doc/locationdb/locationdb.ipynb b/doc/locationdb/locationdb.ipynb
index 33a18930..09e47ca6 100644
--- a/doc/locationdb/locationdb.ipynb
+++ b/doc/locationdb/locationdb.ipynb
@@ -5,13 +5,13 @@
    "metadata": {},
    "source": [
     "# LocationDB object \n",
-    "The `LocationDB` is the Miasm object responsible of the symbols' management. A `Location` is an object representing a code or data (or anywhere else) position. As the name explicits it, the `LocationDB` is a database of locations. Here are some rules:\n",
+    "The `LocationDB` is the Miasm object responsible of the symbols' management. A `Location` is an object representing a code or data (or anywhere else) position. As the name says, the `LocationDB` is a database of locations. Here are some rules:\n",
     "- each location has exactly *one* associated `LocKey`\n",
     "- a `LocKey` is linked to a unique `LocationDB` (and must not be used in another `LocationDB`)\n",
     "- a `LocKey` is very similar to primary key object in a database.\n",
     "- a `LocKey` can have an optional *offset*.\n",
     "- a `LocKey` can have multiple symbol names\n",
-    "- two `Lockey`s cannot share an identic offset\n",
+    "- two `Lockey`s cannot share an identical offset\n",
     "- two `LocKey`s cannot share a symbol name\n",
     "\n",
     "Below are manipulations of the `LocationDB`"