From 0a23018b8afced6a145d96efbe5bffe86f092cce Mon Sep 17 00:00:00 2001
From: Pjotr Prins
Date: Sat, 22 Aug 2020 09:49:11 +0100
Subject: Small text fixes

---
 doc/blog/using-covid-19-pubseq-part5.org | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'doc/blog')

diff --git a/doc/blog/using-covid-19-pubseq-part5.org b/doc/blog/using-covid-19-pubseq-part5.org
index 78eea66..99c8ebf 100644
--- a/doc/blog/using-covid-19-pubseq-part5.org
+++ b/doc/blog/using-covid-19-pubseq-part5.org
@@ -23,8 +23,8 @@ The public sequence resource uses multiple data formats listed on the
 for RDF and semantic web/linked data ontologies. This technology
 allows for querying data in unprescribed ways - that is, you can
 formulate your own queries without dealing with a preset model of that
-data (so typical of CSV files and SQL tables). Examples of exploring
-data are listed [[http://covid19.genenetwork.org/blog?id=using-covid-19-pubseq-part1][here]].
+data (which is how one has to approach CSV files and SQL
+tables). Examples of exploring data are listed [[http://covid19.genenetwork.org/blog?id=using-covid-19-pubseq-part1][here]].
 
 In this BLOG we are going to look at the metadata entered on the
 COVID-19 PubSeq website (or command line client). It is important to
-- 
cgit v1.2.3