Docs: Update PHP_CodeSniffer repository link

src/pages/best-practices/extensions/architecture.md

@@ -51,4 +51,4 @@ Some important things to check in your extensions:
 
 ## Use the PHP_CodeSniffer tool
 
-[PHP_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer) is a set of PHP scripts that checks your code for violations of a particular coding standard. It can be used in conjunction with the [Coding Standard](https://github.com/magento/magento-coding-standard) to check your code for some of the more common application and PHP problems. Using these two tools will ensure that your extension code meets many of [coding standards](../../coding-standards/index.md). It also has the added benefits of keeping your code clean and maintainable.
+[PHP_CodeSniffer](https://github.com/PHPCSStandards/PHP_CodeSniffer) is a set of PHP scripts that checks your code for violations of a particular coding standard. It can be used in conjunction with the [Coding Standard](https://github.com/magento/magento-coding-standard) to check your code for some of the more common application and PHP problems. Using these two tools will ensure that your extension code meets many of [coding standards](../../coding-standards/index.md). It also has the added benefits of keeping your code clean and maintainable.

src/pages/best-practices/extensions/index.md

@@ -25,7 +25,7 @@ Coding standards are a set of guidelines that describe how code should be writte
 *  [PSR2](https://www.php-fig.org/psr/psr-2/)
 *  [PSR4](https://www.php-fig.org/psr/psr-4/)
 
-To help you stick to coding standards, we recommend using the [PHP_CodeSniffer tool](https://github.com/squizlabs/PHP_CodeSniffer).
+To help you stick to coding standards, we recommend using the [PHP_CodeSniffer tool](https://github.com/PHPCSStandards/PHP_CodeSniffer).
 
 ## Write and utilize reusable code
 

src/pages/coding-standards/contributing.md

@@ -23,7 +23,7 @@ To start your contribution:
 
 PHPCS rules are called sniffs. A sniff is just a static code analyzer that will process our custom logic every time it finds an occurrence or any tokens we choose. This custom logic is in charge of identifying if there's a violation of a certain rule in an specific code, and will return an **error** or **warning** depending on the severity of that issue.
 
-Follow the [official PHPCS guide](https://github.com/squizlabs/PHP_CodeSniffer/wiki/Coding-Standard-Tutorial) steps to write a sniff.
+Follow the [official PHPCS guide](https://github.com/PHPCSStandards/PHP_CodeSniffer/wiki/Coding-Standard-Tutorial) steps to write a sniff.
 
 <InlineAlert variant="info" slots="text"/>
 

src/pages/development/validate/test-component.md

@@ -59,4 +59,4 @@ See these resources for testing in PHP and validating components:
 [Install your component]: https://experienceleague.adobe.com/en/docs/commerce-operations/upgrade-guide/overview
 [Install using Composer]: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/next-steps/sample-data/composer-packages
 [Coding Standard]: https://github.com/magento/magento-coding-standard
-[PHP_CodeSniffer]: https://github.com/squizlabs/PHP_CodeSniffer
+[PHP_CodeSniffer]: https://github.com/PHPCSStandards/PHP_CodeSniffer