From a0dc30263d6a8effa747d4e9a7430420f901cc2f Mon Sep 17 00:00:00 2001
From: Ze Libertine Gamer <zlg@zlg.space>
Date: Wed, 12 Oct 2016 02:51:22 -0700
Subject: Clarify a method to move between platforms

Also correct a typo.
---
 README.mdown | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/README.mdown b/README.mdown
index b733efc..c57717e 100644
--- a/README.mdown
+++ b/README.mdown
@@ -11,7 +11,7 @@ Nothing fancy like box art or finding games in a massive dropdown box. There are
 easy flags to track common searches, like "All games that are owned and haven't
 been beaten", making vgstash convenient.
 
-Since vgstash itself is just a front-end to an SQLite dataabase, other
+Since vgstash itself is just a front-end to an SQLite database, other
 interfaces to this basic database format can be built to extend the basic
 concept. SQLite is supported across tons of languages and platforms, so it's
 rather trivial to build another frontend to it. If that's not enough, vgstash 
@@ -37,7 +37,10 @@ with its data format:
 
 There isn't a hard limit on the length of the Name or System strings. SQLite 
 itself, however, has internal limits. Those limits may differ between platforms, 
-so there's no guarantee that vgstash databases will work across them.
+so there's no guarantee that vgstash databases will work across them. The 
+`import` and `export` functions should be used to transport vgstash databases 
+from one platform to another, as YAML is better-standardized and easily 
+modifiable.
 
 # Usage
 
-- 
cgit v1.2.3-54-g00ecf