Removing old warning, added xml update warning

pkg/yqlib/doc/usage/convert.md

@@ -5,12 +5,6 @@ Encode and decode to and from JSON. Supports multiple JSON documents in a single
 Note that YAML is a superset of (single document) JSON - so you don't have to use the JSON parser to read JSON when there is only one JSON document in the input. You will probably want to pretty print the result in this case, to get idiomatic YAML styling.
 
 
-{% hint style="warning" %}
-Note that versions prior to 4.18 require the 'eval/e' command to be specified. 
-
-`yq e <exp> <file>`
-{% endhint %}
-
 ## Parse json: simple
 JSON is a subset of yaml, so all you need to do is prettify the output
 

pkg/yqlib/doc/usage/csv-tsv.md

@@ -29,12 +29,6 @@ Fifi,cat
 ```
 
 
-{% hint style="warning" %}
-Note that versions prior to 4.18 require the 'eval/e' command to be specified. 
-
-`yq e <exp> <file>`
-{% endhint %}
-
 ## Encode CSV simple
 Given a sample.yml file of:
 ```yaml

pkg/yqlib/doc/usage/properties.md

@@ -4,12 +4,6 @@ Encode/Decode/Roundtrip to/from a property file. Line comments on value nodes wi
 
 By default, empty maps and arrays are not encoded - see below for an example on how to encode a value for these.
 
-{% hint style="warning" %}
-Note that versions prior to 4.18 require the 'eval/e' command to be specified. 
-
-`yq e <exp> <file>`
-{% endhint %}
-
 ## Encode properties
 Note that empty arrays and maps are not encoded by default.
 

pkg/yqlib/doc/usage/xml.md

@@ -16,6 +16,14 @@ This can be controlled by:
  | `--xml-proc-inst-prefix` | `+p_` |  ```<?xml version="1"?>``` |
 
 
+{% hint style="warning" %}
+Default Attribute Prefix will be changing in v4.30!
+In order to avoid name conflicts (e.g. having an attribute named "content" will create a field that clashes with the default content name of "+content") the attribute prefix will be changing to "+@".
+
+This will affect users that have not set their own prefix and are not roundtripping XML changes.
+
+{% endhint %}
+
 ## Encoder / Decoder flag options
 
 In addition to the above flags, there are the following xml encoder/decoder options controlled by flags:
@@ -31,12 +39,6 @@ In addition to the above flags, there are the following xml encoder/decoder opti
 
 See below for examples
 
-{% hint style="warning" %}
-Note that versions prior to 4.18 require the 'eval/e' command to be specified.&#x20;
-
-`yq e <exp> <file>`
-{% endhint %}
-
 ## Parse xml: simple
 Notice how all the values are strings, see the next example on how you can fix that.