Skip to content
Browse files

Copy edits to PuppetDB spec_q_nodes.

  • Loading branch information...
1 parent 450c382 commit f8e344c9f89c925f94bd619cd08a4c4564ccfe04 Fred Lifton committed Oct 12, 2012
Showing with 4 additions and 4 deletions.
  1. +4 −4 source/puppetdb/1/spec_q_nodes.markdown
View
8 source/puppetdb/1/spec_q_nodes.markdown
@@ -5,20 +5,20 @@ layout: default
[resource]: ./spec_q_resources.html
-Querying nodes is accomplished by making an HTTP request to the `/nodes` REST
+Nodes can be queried by making an HTTP request to the `/nodes` REST
endpoint with a JSON-formatted parameter called `query`.
## Query format
* The HTTP method must be `GET`.
* There must be an `Accept` header specifying `application/json`.
-The `query` parameter is a similar format to [resource queries][resource].
+The `query` parameter uses a format similar to [resource queries][resource].
Only queries against facts and filters based on node activeness are currently
supported.
-These terms must be of the form `["fact", "<fact name>"]` or `["node", "active"]`,
+These query terms must be of the form `["fact", "<fact name>"]` or `["node", "active"]`,
respectively.
Accepted operators are: `[= > < >= <= and or not]`
@@ -29,7 +29,7 @@ which are not numeric.
Note that nodes which are missing a fact referenced by a `not` query will match
the query.
-This query will return active nodes whose kernel is Linux and whose uptime is less
+In this example, the query will return active nodes whose kernel is Linux and whose uptime is less
than 30 days:
["and",

0 comments on commit f8e344c

Please sign in to comment.
Something went wrong with that request. Please try again.