update guide clarifications with suggestions from @paulyoung

Author: oslego

guides/_posts/2014-01-11-ifelse.html

@@ -18,7 +18,7 @@
 W3C members have received an [onslaught](http://www.xanthir.com/b4PR0) of requests for "Element Queries" - because web designers
 are desperate to achieve higher levels of adaptiveness with their layouts.  The idea with Element Queries is simple - individual elements
 can be responsive to their own size, which would allow for richer designs & more modular Style Sheets. W3C have
-[started a discussion](http://responsiveimagescg.github.io/eq-usecases/) about element queries but as this point they still don't have official endorsement of element queries.
+[started a discussion](http://responsiveimagescg.github.io/eq-usecases/) about element queries but at this point they still don't have official endorsement of element queries.
 
 Yet, even with the hypothetical Element Query, elements could only be adaptive to their size.  Why not allow elements to be adaptive to any property
 like `col-count` or even to a custom variable?

guides/_posts/2015-02-05-layout.html

@@ -205,13 +205,13 @@
 
 ## Intrinsic values
 
-Positioning elements with `top` and `left` properties doesn't require GSS to know the dimensions of those elements. But `right` and `bottom` properties need to know about `width` and `height` of the element respectively. Properly constrained systems will provide those values indirectly with no regard to element contents.
+Positioning elements with `top` and `left` properties doesn't require GSS to know the dimensions of those elements. But `right` and `bottom` properties need to know about `width` and `height` of the element respectively. Properly constrained systems will provide those values indirectly with no regard to an element's contents.
 
 However, it's often desirable to know the computed dimensions of specific elements which GSS has no control over - be it text, images or blocks styled with CSS. Measurements provide dynamic "islands" to the layout, which can be automatically recomputed, whenever measured things are updated from the outside. It also may act as a feedback to the solver, disallowing content to shrink too much or helping to decide if things fit.
 
-Prepending a property with `intrinsic-` or `computed-` prefix makes GSS measure the values.
+Prefixing a property with `intrinsic-` or `computed-` prefix makes GSS measure the value.
 
-Prefixing a property with `intrinsic-` makes it *read-only* and it won't apply on the element. Declaring `intrinsic-width` property will ensure that `width` style is never applied to that element. This allows dimensions to change and update naturally. Otherwise, the width would be computed and applied only the first time, making it static.
+Prefixing a property with `intrinsic-` makes it *read-only* and it won't apply on the element. For example, declaring `intrinsic-width` will ensure that the `width` style is never applied to that element. This allows dimensions to change and update naturally. Otherwise, the width would be computed and applied only the first time, making it static.
 
 `computed`-prefixed properties can be used to measure styles regardless of their origin - either GSS constraints or CSS styles. Computed properties will not make styles *read-only*, unlike `intrinsic`-prefixed properties.