Skip to content

Fix typos in Rule Validator doc #9249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 4.5.0
Choose a base branch
from
Open

Fix typos in Rule Validator doc #9249

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions en/docs/governance/rule-validator/rule-validator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
- Any valid JSON or YAML file can be validated by providing a valid Spectral ruleset.

## Features and Limitations
WSO2 Rule validator supports most features that Spectral itself does. With the exception of a few listed below.
WSO2 Rule Validator supports most features that Spectral itself does. With the exception of a few listed below.

1. [_**given**_](https://docs.stoplight.io/docs/spectral/d3482ff0ccae9-rules#rules-properties) path is a JSON Path. But currently WSO2 Rule Validator does not support [JSON Path Plus](https://github.com/JSONPath-Plus/JSONPath) features, even though Spectral does.
- Object access should always be done inside single quotes \(`['paths']['order']\`)
Expand Down Expand Up @@ -214,7 +214,7 @@ paths:
```

### 3. Core functions
Below is a list of core functions that are supported by the rule validator, with a summary of each of its options.
Below is a list of core functions that are supported by the Rule Validator, with a summary of each of its options.

<table><thead>
<tr>
Expand Down