Copy edits

cstack · cstack · commit 3519c11bde74 · 2017-08-31T18:41:20.000-07:00
diff --git a/index.md b/index.md
@@ -5,7 +5,7 @@
 - How does rolling back a transaction work?
 - How are indexes formatted?
 - When and how does a full table scan happen?
-- What format is a prepared statement save in?
+- What format is a prepared statement saved in?
 
 In short, how does a database **work**?
 
diff --git a/part1.md b/part1.md
@@ -1,25 +1,25 @@
 # Part 1 - Introduction and Setting up the REPL
 
-As a web developer, I use relational databases every day at my job, but they were always a black box to me. Some questions I had:
+As a web developer, I use relational databases every day at my job, but they're a black box to me. Some questions I have:
 - What format is data saved in? (in memory and on disk)
 - When does it move from memory to disk?
 - Why can there only be one primary key per table?
 - How does rolling back a transaction work?
 - How are indexes formatted?
 - When and how does a full table scan happen?
-- What format is a prepared statement save in?
+- What format is a prepared statement saved in?
 
-In other words, how does a database _work_?
+In other words, how does a database **work**?
 
-To figure things out, I started writing a database from scratch. It's modeled off sqlite because it is designed to be small with fewer features than MySQL or PostgreSQL, so I have a better hope of understanding it. The entire database is stored in a single file!
+To figure things out, I'm writing a database from scratch. It's modeled off sqlite because it is designed to be small with fewer features than MySQL or PostgreSQL, so I have a better hope of understanding it. The entire database is stored in a single file!
 
 # Sqlite
 
-There's lots of documentation of [sqlite internals on their website](https://www.sqlite.org/arch.html), plus I've got a copy of [SQLite Database System: Design and Implementation](https://play.google.com/store/books/details?id=9Z6IQQnX1JEC).
+There's lots of [documentation of sqlite internals](https://www.sqlite.org/arch.html) on their website, plus I've got a copy of [SQLite Database System: Design and Implementation](https://play.google.com/store/books/details?id=9Z6IQQnX1JEC).
 
 {% include image.html url="assets/images/arch1.gif" description="sqlite architecture (https://www.sqlite.org/zipvfs/doc/trunk/www/howitworks.wiki)" %}
 
-A query goes through a chain of components in order to retrieve or modify data. The _front-end_ consists of the:
+A query goes through a chain of components in order to retrieve or modify data. The **front-end** consists of the:
 - tokenizer
 - parser
 - code generator
@@ -32,7 +32,7 @@ The _back-end_ consists of the:
 - pager
 - os interface
 
-The **virtual machine** takes bytecode generated by the front-end as instructions. It can then issue operations on one or more tables or indexes, each of which is stored in a data structure called a B-tree. The VM is essentially a big switch statement on the type the bytecode instruction.
+The **virtual machine** takes bytecode generated by the front-end as instructions. It can then perform operations on one or more tables or indexes, each of which is stored in a data structure called a B-tree. The VM is essentially a big switch statement on the type the bytecode instruction.
 
 Each **B-tree** consists of many nodes. Each node is one page in length. The B-tree can retrieve a page from disk or save it back to disk by issuing commands to the pager.
 
@@ -153,7 +153,7 @@ db > .exit
 ~
 ```
 
-Alright, we've got a working REPL. In the [next part](/part2) we'll start developing our command language. Meanwhile, here's the entire program from this part:
+Alright, we've got a working REPL. In [Part 2](/part2) we'll start developing our command language. Meanwhile, here's the entire program from this part:
 
 ```c
 #include <stdbool.h>
diff --git a/part2.md b/part2.md
@@ -53,7 +53,7 @@ Non-SQL statements like `.exit` are called "meta-commands". They all start with
 
 Next, we add a step that converts the line of input into our internal representation of a statement. This is our hacky version of the sqlite front-end.
 
-Lastly, we pass the prepared statement to `execute_statement`. This will eventually become our virtual machine.
+Lastly, we pass the prepared statement to `execute_statement`. This function will eventually become our virtual machine.
 
 Notice that two of our new functions return enums indicating success or failure:
 
