diff --git a/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/feature.md b/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/feature.md
index f7b7cf9501..34232b2b8d 100644
--- a/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/feature.md
+++ b/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/feature.md
@@ -65,7 +65,7 @@ The request includes the following parameters:
 | `Field`   | Type    | Description                                            |
 |:----------|:--------|:-------------------------------------------------------|
 | `feature` | String  | _(Optional)_ The unique ID of an amendment, as hexadecimal; or the short name of the amendment. If provided, limits the response to one amendment. Otherwise, the response lists all amendments. |
-| `vetoed`  | Boolean | (Optional; ignored unless `feature` also specified) If true, instructs the server to vote against the amendment specified by `feature`. If false, instructs the server to vote in favor of the amendment. Use 'accept' or 'reject rather than 'true' or 'false' when using the commandline. |
+| `vetoed`  | Boolean | (Optional; ignored unless `feature` also specified) If true, instructs the server to vote against the amendment specified by `feature`. If false, instructs the server to vote in favor of the amendment. On the commandline, use 'accept' or 'reject rather than 'true' or 'false'. |
 
 **Note:** You can configure your server to vote in favor of a new amendment, even if the server does not currently know how to apply that amendment, by specifying the amendment ID in the `feature` field. For example, you might want to do this if you plan to upgrade soon to a new `rippled` version that _does_ support the amendment.