more explanation

docs/1.0.md

@@ -1076,6 +1076,11 @@ data that the other feed or feed item has.  This allows a podcast app to know wh
 requested.  What data is being requested is determined by the parent item.  For instance, if the parent item is a 
 `<podcast:podroll>` element, then the remote feed's `<channel>` metadata is needed.
 
+Using the `feedGuid` attribute is the preferred way to address a remote feed since, but there are times when an app may
+not have access to a list of resolvable `<podcast:guid>`'s.  In that case, it can be beneficial to include the `feedUrl`
+attribute for those cases as a fallback.  If both are present and the app is capable the `feedGuid` should be resolved
+and used.
+
 ### Parent
 &nbsp; `<channel>` or `<podcast:podroll>` or `<podcast:valueTimeSplit>`
 
@@ -1088,7 +1093,9 @@ requested.  What data is being requested is determined by the parent item.  For
 - **itemGuid** (optional) If this remote item element is intended to point to an `<item>` in the remote feed, this 
                           attribute should contain the value of the `<guid>` of that `<item>`. 
 - **medium** (optional) If the feed being pointed to is not of medium type 'podcast', this attribute should contain it's
-                        `<podcast:medium>` type from the [list](#medium) of types available in this document. 
+                        `<podcast:medium>` type from the [list](#medium) of types available in this document.  The
+                        reason this is helpful is to give the app a heads up on what type of data this is expected to be
+                        since that may affect the way it approaches fetch and display.
 
 ### Examples
 ```xml