Remove or fix dead-link

public/md-articles/best-practice/basic-security-in-dotkernel-headless-platform.md

@@ -151,7 +151,7 @@ The GitHub Action [Laminas Continuous Integration](https://github.com/laminas/la
 - [Content Negotiation in Dotkernel REST API](https://www.dotkernel.com/dotkernel-api/content-negotiation-in-dotkernel-rest-api/)
 - [laminas-form Documentation](https://docs.laminas.dev/laminas-form/v3/intro/)
 - [CORS in Dotkernel API](https://docs.dotkernel.org/api-documentation/v6/tutorials/cors/)
-- [CORS Policy Setup in Dotkernel](https://www.dotkernel.com/how-to/mezzio-cors-implementation-in-dotkernel/)
+- [CORS Policy Setup in Dotkernel](https://www.dotkernel.com/how-to/cors-policy-setup-in-dotkernel-using-mezzio-cors/)
 - [Error Reporting Endpoint](https://docs.dotkernel.org/api-documentation/v6/core-features/error-reporting/)
 - [OpenAPI Documentation](https://docs.dotkernel.org/api-documentation/v6/openapi/introduction/)
 - [mezzio/mezzio-authentication-oauth2 Configuration](https://docs.mezzio.dev/mezzio-authentication-oauth2/v1/intro/#configuration)

public/md-articles/best-practice/using-like-wildcards-with-zend-db.md

@@ -16,7 +16,7 @@ The LIKE condition allows pattern matching in the WHERE clause of SELECT, INSERT
 The `_` wildcard matches a single character, and `%` matches any string of any length (including zero).
 This article shows how to use LIKE and NOT LIKE with both wildcards in Zend_Db.
 
-Continuing the Zend_Db article [series](http://www.dotkernel.com/dotkernel/sql-queries-using-zend-db-select/), let's discuss the LIKE condition.
+Continuing the Zend_Db article series (http://www.dotkernel.com/dotkernel/sql-queries-using-zend-db-select/), let's discuss the LIKE condition.
 
 The **LIKE** condition allows you to use wildcards in the *WHERE* clause of an SQL statement. This allows pattern matching. It can be used in any valid SQL statement (*SELECT*, *INSERT*, *UPDATE* or *DELETE*).
 

public/md-articles/dotkernel/autologin-using-cookie-remember-me-in-dotkernel.md

@@ -84,7 +84,7 @@ npm run prod
    ```shell
    vendor/bin/phinx create --configuration=config/migrations.php  RememberUserSchema
    ```
-3. Modify the generated migration file as in [user_remember_schema](https://www.dotkernel.com/dotkernel/autologin-cookie-remember-me-feature/), then run it against the database:
+3. Modify the generated migration file as in [user_remember_schema](https://github.com/dotkernel/frontend/blob/b736eeaa7092c1c50d57db9242c938d8d5f83bd0/data/database/migrations/20220621062142_remember_user_schema.php), then run it against the database:
    ```shell
    vendor/bin/phinx migrate --configuration=config/migrations.php
    ```

public/md-articles/zend-framework/sunsetting-pear-channel-for-zend-framework-1.md

@@ -16,7 +16,7 @@ Dotkernel is sunsetting its unofficial PEAR channel for Zend Framework 1, which
 The main reasons are that upgrading PEAR to work with PHP 8 is too painful, and the channel currently runs on an LXC container with CentOS 7, which doesn't work on the latest Proxmox version, making the upgrade to AlmaLinux not worth the effort.
 The post closes by thanking PEAR for its historical contribution to the PHP ecosystem.
 
-The unofficial PEAR channel for Zend Framework 1 was created in [2016](https://www.dotkernel.com/dotkernel/migration-of-zend-framework-1-pear-channel/), at the time when [PEAR](https://pear.php.net/) was still used a lot.
+The unofficial PEAR channel for Zend Framework 1 was created in 2016, at the time when [PEAR](https://pear.php.net/) was still used a lot.
 
 Due to the fact that it is a pain to upgrade PEAR to work with PHP 8, we must sunset the channel.