> For the complete documentation index, see [llms.txt](https://docs.wproofreader.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wproofreader.com/v6.11.0/deployment/configuration/grammar-check-engine-setup/disabling-rules-and-categories.md).

# Disabling rules and categories

Disable individual **rules** or whole **categories** for any checking type.

This includes grammar rules, AI corrections and style rules.

### How it works

You create one or more JSON files with rule/category IDs.

You then reference these files in `AppServerX.xml` under the target `<Language ...>` block.

### File location

Disabled rules files live in the AppServer resources directory:

* Default: `<WebSpellChecker_Installation_Path>/AppServer/Resources/`
* Configurable via `ResourcesDir` in `AppServerX.xml`. See [AppServer parameters](/v6.11.0/deployment/configuration/application-server/appserver-parameters.md#resourcesdir).

Place files under the language group folder:

* `Resources/<lang_group>/`
* Example: `Resources/en/en_US_disabled_rules.json`

### Use a predefined file (or create your own)

You can start from a predefined `*_disabled_rules.json` file shipped in `Resources/<lang_group>/`.

Edit it to add or remove entries.

You can also create a new JSON file from scratch.

### Disabled rules JSON format

Example: `en_US_disabled_rules.json`

```json
{
  "categories": [
  ],
  "rules": [
    "DIFFERENT_THAN"
  ]
}
```

* `rules` contains rule IDs.
* `categories` contains category IDs.

### Configure AppServerX.xml

You can use:

* multiple disabled rules files per language.
* one shared file reused across several languages.

Add one `<DisabledRules .../>` entry per file inside the `<Language ...>` block.

Example:

```xml
<Language Id="en_US" Enabled="true">
  ...
  <DisabledRules Path="en/en_disabled_rules.json"/>
  <DisabledRules Path="en/en_US_disabled_rules.json"/>
  ...
</Language>
```

`Path` is resolved relative to `ResourcesDir`.

### Apply changes

{% hint style="warning" %}
Back up `AppServerX.xml` before you change it.
{% endhint %}

Restart AppServer to apply changes in `AppServerX.xml`.

To restart: [stop](https://docs.wproofreader.com/v6.11.0/deployment/configuration/grammar-check-engine-setup/pages/IA2KNQLXDh85TwDivL4y#mainappservercommands-stopappserverwindowslinux2.stopappserver) the application, then [start](https://docs.wproofreader.com/v6.11.0/deployment/configuration/grammar-check-engine-setup/pages/IA2KNQLXDh85TwDivL4y#mainappservercommands-startappserverwindowslinux1.startappserver) it again.

Use [Main AppServer commands](/v6.11.0/deployment/configuration/application-server/main-appserver-commands.md).

Changes in `*_disabled_rules.json` files are applied without the restart.

See [Main AppServer commands](/v6.11.0/deployment/configuration/application-server/main-appserver-commands.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wproofreader.com/v6.11.0/deployment/configuration/grammar-check-engine-setup/disabling-rules-and-categories.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.