Cleanup of redundant README files

internal/README.md

-# `/internal`
-
-Private application and library code. This is the code you don't want others importing in their applications or libraries. Note that this layout pattern is enforced by the Go compiler itself. See the Go 1.4 [`release notes`](https://golang.org/doc/go1.4#internalpackages) for more details. Note that you are not limited to the top level `internal` directory. You can have more than one `internal` directory at any level of your project tree.

internal/data/jsonQuery.json

-{
-  "Return": {
-    "Entities": [
-      0,
-      1
-    ],
-    "Relations": []
-  },
-  "Entities": [
-    {
-      "Type": "airports",
-      "Constraints": [
-        {
-          "Attribute": "city",
-          "Value": "New York",
-          "DataType": "text",
-          "MatchType": "exact"
-        }
-      ]
-    },
-    {
-      "Type": "airports",
-      "Constraints": [
-        {
-          "Attribute": "city",
-          "Value": "Hilliard",
-          "DataType": "text",
-          "MatchType": "exact"
-        }
-      ]
-    }
-  ],
-  "Relations": []
-}
\ No newline at end of file

pkg/README.md

-# `/pkg`
-
-Library code that's ok to use by external applications (e.g., /pkg/mypubliclib). Other projects will import these libraries expecting them to work, so think twice before you put something here :-) Note that the internal directory is a better way to ensure your private packages are not importable because it's enforced by Go. The /pkg directory is still a good way to explicitly communicate that the code in that directory is safe for use by others. The I'll take pkg over internal blog post by Travis Jeffery provides a good overview of the pkg and internal directories and when it might make sense to use them.
\ No newline at end of file