Merge pull request MicrosoftDocs#4955 from MicrosoftDocs/2371777-2

portal checker new rules - follow up - 2371777

Author: tapanm-MSFT

powerapps-docs/maker/portals/admin/portal-checker-analysis.md

@@ -66,13 +66,13 @@ To find anonymous OData feeds enabled on your portal:
     ![Enabled OData feeds](media/portal-checker-analysis/enabled-odata-feeds.png "Enabled OData feeds")
 
     > [!NOTE]
-    > List of all OData feeds enabled doesn't mean all of them are available anonymously.
+    > The list of OData feeds on this page might be available anonymously depending on your security configuration. The next steps will help you verify the anonymous access of these feeds.
 
-1. Go to each of OData feed by browsing to the URL format {Portal URL}/_odata/{collection href value} where collection href value is highlighted below.
+1. Go to each of OData feed by browsing to the URL format {Portal URL}/_odata/{collection href value} (for example, `https://contoso.powerappsportals.com/_odata/accounts`) where collection href value is highlighted below.
 
     ![Browse to OData feed](media/portal-checker-analysis/browse-to-enabled-odata-feeds.png "Browse to OData feed")
 
-1. If the OData field is available anonymously, it will return the data with HTTP 200 response. If the feed isn't enabled anonymously, it will return HTTP 403 response with a message “Access to oData, with the entity set name of '{entity set name}', has been denied.”
+1. If the OData field is available anonymously, it will return the data with HTTP 200 response. If the feed isn't enabled anonymously, it will return HTTP 403 response with a message “Access to OData, with the entity set name of '{table set name}', has been denied.”
 
 If you've unintended OData feed enabled on your portal anonymous, it could be because of one of these possibilities: