fix(docs): LHOL - minor changes around typo and space (#70)

* fix: typo

* fix: missing space

Author: halchester

content/hands-on-labs/explore-cli/cli-gsi.en.md

@@ -20,7 +20,7 @@ aws dynamodb scan \
     --return-consumed-capacity TOTAL
 ```
 
-When running that scan operaton we could see that the *Count* returned was different than the *ScannedCount*.  If there had been a billion Reply items but only three of them were posted by User A, we would have to pay (both in time and money) to scan through a billion items just to find the three we wanted.
+When running that scan operation we could see that the *Count* returned was different than the *ScannedCount*.  If there had been a billion Reply items but only three of them were posted by User A, we would have to pay (both in time and money) to scan through a billion items just to find the three we wanted.
 
 Armed with this knowledge of GSIs, we can now create a GSI on the **Reply** table to service this new access pattern.  GSIs can be created and removed at any time, even if the table has data in it already! This new GSI will use the *PostedBy* attribute as the Partition (HASH) key and we will still keep the messages sorted by *ReplyDateTime* as the Sort (RANGE) key.  We want all the attributes from the table copied (projected) into the GSI so we will use the ALL ProjectionType.  Note that the name of the index we create is `PostedBy-ReplyDateTime-gsi`.
 

content/hands-on-labs/explore-console/console-read-item-collection.en.md

@@ -9,7 +9,7 @@ Item Collections are groups of Items that share a Partition Key.  By definition,
 When we invoke the *Query* API we must specify a [Key Condition Expression](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Query.html#Query.KeyConditionExpressions). If we were comparing this to SQL, we would say "this is the part of the WHERE clause that acts on the Partition Key and Sort Key attributes".  This could take a couple of forms:
 
 * Just the Partition Key value of our Item Collection.  This indicates that we want to read ALL the items in the item collection.
-* The Partition Key value and some kind ofExplore the other options in the Item explorer and figure out how to get queries to return with Replies sorted from most recent to least recent.
+* The Partition Key value and some kind of Explore the other options in the Item explorer and figure out how to get queries to return with Replies sorted from most recent to least recent.
 , >=, BETWEEN, and BEGINS_WITH.
 
 The Key Condition Expression will define the number of RRUs or RCUs that are consumed by our Query.  DynamoDB will add up the size of all the rows matched by the Key Condition Expression, then divide that total size by 4KB to calculate the consumed capacity (and then it will divide that number in half if you're using an eventually consistent read).