Fixed: typo 'compatability' to 'compatibility'

[dhruvang21]

Trac ticket: https://core.trac.wordpress.org/ticket/63391

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props dhruvang21, abcd95, getsyash.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[himanshupathak95]

@dhruvang21 I think there are a lot more instances where the word compatability is used throughout the codebase.
For instance -

wordpress-develop/src/wp-includes/html-api/class-wp-html-doctype-info.php

Lines 129 to 136 in 4dd067f

	* Which document compatability mode this DOCTYPE declaration indicates.
	*
	* This value should be considered "read only" and not modified.
	*
	* When an HTML parser has not already set the document compatability mode,
	* (e.g. "quirks" or "no-quirks" mode), it will infer if from the properties
	* of the appropriate DOCTYPE declaration, if one exists. The DOCTYPE can
	* indicate one of three possible document compatability modes:

[getsyash]

I noticed the typo is also present in variable names like $this->indicated_compatability_mode. I’d like to fix those too, but since it affects functionality, I’ll ensure all references are updated. Please let me know if there are any backward compatibility concerns I should be aware of.

[dhruvang21]

@himanshupathak95 I also noticed that there are additional instances where typos need to be fixed. However, I agree with @getsyash — I think it’s best to wait for input from the reviewers, as they’ll definitely help guide us and suggest the appropriate solutions.