another typo

[web/gag.com] / bdale / blog / posts / Digital_Photo_Creation_Dates.mdwn

diff --git a/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn b/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn
index beaaf0679efd9349ebc00e5421df332c49eabe04..3fe98a00b3b03eab3fbde069c798d6d9a09e37f6 100644 (file)
--- a/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn
+++ b/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn
@@ -98,7 +98,7 @@ Compounding my problem was that my wife had already spent many hours tagging
 her photos in the Piwigo web GUI, so it really seemed necessary to fix the
 images "in place" on the Piwigo server.  The first problem with that is that
 as you upload photos to the server, they are assigned unique filenames on
-disk based on the upload date and time plus a random has, and the original
+disk based on the upload date and time plus a random hash, and the original
 filename becomes just an element of metadata in the Piwigo database.  Piwigo
 scans the Exif data at image import time and stuffs the database with a 
 number of useful values from there, including the image creation time that is
@@ -107,7 +107,7 @@ fundamental to aligning images taken by different cameras on a timeline.
 I could find no Piwigo interface to easily extract the on-disk filenames for
 a given set of photos, so I ended up playing with the underlying database
 directly.  The Piwigo source tree contains a fle piwigo_structure-mysql.sql
-used in the installation process to set up the database tables tha served as
+used in the installation process to set up the database tables that served as
 a handy reference for figuring out the database schema.  Looking at the
 piwigo_categories table, I learned that the "folder" I had uploaded all of
 the raw photos from my wife's camera to was category 109.  After a couple