fix dead link

Author: OStefan2001

public/md-articles/best-practice/insert-update-delete-statements-with-zend-db.md

@@ -15,7 +15,7 @@ language: "en"
 DML (Data Manipulation Language) statements change data values in database tables.
 This article, continuing the Zend_Db series, shows how the three primary DML statements - INSERT, UPDATE, and DELETE - are written in raw SQL and translated into Zend_Db method calls.
 
-Continuing the Zend_DB article [series](http://www.dotkernel.com/dotkernel/sql-queries-using-zend-db-select/), we are stopping now at DML statements. DML (Data Manipulation Language) statements are statements that change data values in database tables. There are 3 primary DML statements:
+Continuing the Zend_DB article [series](http://www.dotkernel.com/best-practice/sql-queries-using-zend-db-select/), we are stopping now at DML statements. DML (Data Manipulation Language) statements are statements that change data values in database tables. There are 3 primary DML statements:
 
 - INSERT - Inserting new rows into database tables.
 - UPDATE - Updating existing rows in database tables.

public/md-articles/best-practice/subqueries-with-zend-db.md

@@ -14,7 +14,7 @@ language: "en"
 
 Continuing the Zend_Db series, this article shows a more complex query - combining COUNT(), LEFT JOIN, and GROUP BY across 3 tables, with a count taken from 2 different tables - and how to build it, including a nested subquery, using Zend_Db.
 
-Continuing the Zend_DB article [series](http://www.dotkernel.com/dotkernel/sql-queries-using-zend-db-select/), we are stopping now at subqueries.
+Continuing the Zend_DB article [series](http://www.dotkernel.com/best-practice/sql-queries-using-zend-db-select/), we are stopping now at subqueries.
 
 As you note, the below is a complicate query, with *COUNT()*, *LEFT JOIN()*, *GROUP BY* - select from 3 tables, and make a count from 2 different tables:
 

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](https://www.dotkernel.com/best-practice/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/best-practice/what-are-returning-the-fetch-functions-from-zend-db.md

@@ -15,7 +15,7 @@ language: "en"
 Continuing the Zend_Db article series, this article walks through the FETCH methods available on Zend_Db_Adapter_Abstract: fetchAll, fetchAssoc, fetchCol, fetchOne, fetchPairs, and fetchRow.
 Each method is shown next to the equivalent old-style code built on query(), next_record(), and f(), so the two approaches can be compared side by side.
 
-Continuing the Zend_DB article [series](http://www.dotkernel.com/dotkernel/sql-queries-using-zend-db-select/), we are stopping now at *FETCH* methods that are in [Zend_Db_Adapter_Abstract](https://docs.laminas.dev/laminas-db/adapter/):
+Continuing the Zend_DB article [series](http://www.dotkernel.com/best-practice/sql-queries-using-zend-db-select/), we are stopping now at *FETCH* methods that are in [Zend_Db_Adapter_Abstract](https://docs.laminas.dev/laminas-db/adapter/):
 
 ```php
 array  fetchAll   (string|Zend_Db_Select $sql, [mixed $bind = array()])