diff --git a/src/Blog/templates/page/JSON-LD/dotkernel-api/dotkernel-api-1-0-0-released.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel-api/dotkernel-api-1-0-0-released.jsonld.twig
index 5df32311..e0aabacf 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel-api/dotkernel-api-1-0-0-released.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel-api/dotkernel-api-1-0-0-released.jsonld.twig
@@ -43,7 +43,7 @@
                 "mainEntity": [
                     {
                         "@type": "Question",
-                        "name": "What is DotKernel API?",
+                        "name": "What is Dotkernel API?",
                         "acceptedAnswer": {
                             "@type": "Answer",
                             "text": "It is a Zend Expressive 3 application aiming to help developers quickly and efficiently develop an API."
@@ -51,7 +51,7 @@
                     },
                     {
                         "@type": "Question",
-                        "name": "What key libraries does DotKernel API 1.0.0 use?",
+                        "name": "What key libraries does Dotkernel API 1.0.0 use?",
                         "acceptedAnswer": {
                             "@type": "Answer",
                             "text": "Among others, it's built on the ezimuel/zend-expressive-api skeleton, and uses dotkernel/dot-annotated-services for dependency injection, dotkernel/dot-console for console applications, dotkernel/dot-errorhandler for error logging, dotkernel/dot-mail for SMTP email, zend-expressive-authentication-oauth2 for OAuth2 authentication, zend-expressive-authorization-rbac for role-based permissions, and swagger-api/swagger-ui for OpenAPI 3 documentation."
@@ -59,7 +59,7 @@
                     },
                     {
                         "@type": "Question",
-                        "name": "What features does DotKernel API 1.0.0 offer out of the box?",
+                        "name": "What features does Dotkernel API 1.0.0 offer out of the box?",
                         "acceptedAnswer": {
                             "@type": "Answer",
                             "text": "Secure authentication via OAuth2, two user roles (admin and member), where admins can manage any user account and members can manage only their own, plus OpenAPI 3 documentation with an interactive interface developers can use to integrate the API."
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/adding-composer-support-in-your-dotkernel-project.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/adding-composer-support-in-your-dotkernel-project.jsonld.twig
index c4c8dd80..985fb763 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/adding-composer-support-in-your-dotkernel-project.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/adding-composer-support-in-your-dotkernel-project.jsonld.twig
@@ -42,10 +42,10 @@
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
                     { "@type": "Question", "name": "What does Composer do?", "acceptedAnswer": { "@type": "Answer", "text": "Composer is an application-level package manager. It auto-loads dependencies on demand and can also auto-load custom classes." } },
-                    { "@type": "Question", "name": "What must a DotKernel project have before Composer can be used?", "acceptedAnswer": { "@type": "Answer", "text": "A composer.json file, for example requiring zendframework/zendframework1 at 1.12.* and mobiledetect/mobiledetectlib at 2.8.*, plus PHP >=5.4.0 listed under require-dev." } },
+                    { "@type": "Question", "name": "What must a Dotkernel project have before Composer can be used?", "acceptedAnswer": { "@type": "Answer", "text": "A composer.json file, for example requiring zendframework/zendframework1 at 1.12.* and mobiledetect/mobiledetectlib at 2.8.*, plus PHP >=5.4.0 listed under require-dev." } },
                     { "@type": "Question", "name": "What happens when you run composer update?", "acceptedAnswer": { "@type": "Answer", "text": "If the vendor folder already exists, composer checks for and applies updates to the packages. If it doesn't exist, composer creates the vendor folder containing all requested packages, along with an autoload file." } },
                     { "@type": "Question", "name": "How do you safely load the Composer autoloader in case Composer isn't present?", "acceptedAnswer": { "@type": "Answer", "text": "Check whether vendor/autoload.php exists using file_exists() before calling require_once() on it, and handle the case gracefully (for example by loading fallbacks) if the path is missing." } },
-                    { "@type": "Question", "name": "Which DotKernel versions does this apply to?", "acceptedAnswer": { "@type": "Answer", "text": "The article states it works for any DotKernel 1.x version, as long as the server is running PHP greater than 5.4.0." } }
+                    { "@type": "Question", "name": "Which Dotkernel versions does this apply to?", "acceptedAnswer": { "@type": "Answer", "text": "The article states it works for any Dotkernel 1.x version, as long as the server is running PHP greater than 5.4.0." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/adding-windows-10-os-and-browser-detection-in-dotkernel-projects.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/adding-windows-10-os-and-browser-detection-in-dotkernel-projects.jsonld.twig
index e7863c27..59c40140 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/adding-windows-10-os-and-browser-detection-in-dotkernel-projects.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/adding-windows-10-os-and-browser-detection-in-dotkernel-projects.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What DotKernel version is required before applying this patch?", "acceptedAnswer": { "@type": "Answer", "text": "Your project must be running version 1.5.0 or newer." } },
+                    { "@type": "Question", "name": "What Dotkernel version is required before applying this patch?", "acceptedAnswer": { "@type": "Answer", "text": "Your project must be running version 1.5.0 or newer." } },
                     { "@type": "Question", "name": "Which files does the patch modify or add?", "acceptedAnswer": { "@type": "Answer", "text": "It modifies configs/useragent/browser.xml and configs/useragent/os.xml, and adds images/browsers/edge.png and images/os/windows_metro.png." } },
                     { "@type": "Question", "name": "Why do you need to clear the cache after applying the patch?", "acceptedAnswer": { "@type": "Answer", "text": "Because the OS and browser XML files are cached, so the new icons won't show up until the cache is cleared." } },
                     { "@type": "Question", "name": "Will applying the patch overwrite existing files?", "acceptedAnswer": { "@type": "Answer", "text": "You'll be prompted to replace 2 files (browser.xml and os.xml) and should agree, and also agree to merge the folders' contents since the other files listed are added rather than replaced." } }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/caching-in-dotkernel-using-zend-framework.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/caching-in-dotkernel-using-zend-framework.jsonld.twig
index 49657cd5..691e03d4 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/caching-in-dotkernel-using-zend-framework.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/caching-in-dotkernel-using-zend-framework.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What data does DotKernel's cache layer store?", "acceptedAnswer": { "@type": "Answer", "text": "Router, acl_role, menu, options (including seo_xml), browser_xml, os_xml, and test data between requests." } },
+                    { "@type": "Question", "name": "What data does Dotkernel's cache layer store?", "acceptedAnswer": { "@type": "Answer", "text": "Router, acl_role, menu, options (including seo_xml), browser_xml, os_xml, and test data between requests." } },
                     { "@type": "Question", "name": "What storage providers are available for the cache?", "acceptedAnswer": { "@type": "Answer", "text": "Two cache factories to choose from: APC (or APCU for newer PHP installations) and File." } },
                     { "@type": "Question", "name": "Where is the cache configured?", "acceptedAnswer": { "@type": "Answer", "text": "In /configs/application.ini, where you can enable or disable caching, set how long the cache stays valid, choose the cache namespace, and pick the storage provider (File or APC). The article recommends disabling the cache in development mode." } },
                     { "@type": "Question", "name": "Do you need to manually load the cache engine?", "acceptedAnswer": { "@type": "Answer", "text": "No, it's automatically loaded during kernel initialization (Dot_Kernel::initialize()). Manually calling Dot_Cache::loadCache() is only needed if you want to use caching outside of that normal initialization." } },
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/configuring-the-cache-in-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/configuring-the-cache-in-dotkernel.jsonld.twig
index 3f59dd8d..81e05aa3 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/configuring-the-cache-in-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/configuring-the-cache-in-dotkernel.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What is DotKernel's caching layer based on?", "acceptedAnswer": { "@type": "Answer", "text": "It's based on Zend Framework Cache, configured through settings in application.ini, with more configuration options available at the Zend Framework Cache Frontends and Backends documentation links given in the article." } },
+                    { "@type": "Question", "name": "What is Dotkernel's caching layer based on?", "acceptedAnswer": { "@type": "Answer", "text": "It's based on Zend Framework Cache, configured through settings in application.ini, with more configuration options available at the Zend Framework Cache Frontends and Backends documentation links given in the article." } },
                     { "@type": "Question", "name": "What does the cache.enable setting do?", "acceptedAnswer": { "@type": "Answer", "text": "It can be used to disable caching, which is mostly useful during the development stage." } },
                     { "@type": "Question", "name": "What values can cache.factory take?", "acceptedAnswer": { "@type": "Answer", "text": "The cache.factory value is the cache service to use, and the article lists two options: file or apc." } },
                     { "@type": "Question", "name": "Why bother setting the individual/backend cache settings like cache.file.cache_dir?", "acceptedAnswer": { "@type": "Answer", "text": "These settings are optional, but the article highly recommends setting them, otherwise other projects might end up using the same cache." } }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/detecting-mobile-devices-in-dotkernel-1-6-0.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/detecting-mobile-devices-in-dotkernel-1-6-0.jsonld.twig
index 2fe973cc..5ecd4341 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/detecting-mobile-devices-in-dotkernel-1-6-0.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/detecting-mobile-devices-in-dotkernel-1-6-0.jsonld.twig
@@ -41,9 +41,9 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Why did mobile detection change in DotKernel 1.6.0?", "acceptedAnswer": { "@type": "Answer", "text": "Because of the new Wurfl Cloud integration. This version no longer ships with a working built-in method for mobile detection, so it must be configured first." } },
+                    { "@type": "Question", "name": "Why did mobile detection change in Dotkernel 1.6.0?", "acceptedAnswer": { "@type": "Answer", "text": "Because of the new Wurfl Cloud integration. This version no longer ships with a working built-in method for mobile detection, so it must be configured first." } },
                     { "@type": "Question", "name": "What are the steps to configure Wurfl Cloud detection?", "acceptedAnswer": { "@type": "Answer", "text": "Go to the scientiamobile website and register for a Wurfl Cloud account, choose the device_os and mobile_browser capabilities for the account and save, then go to API Keys and copy the key into application.ini." } },
-                    { "@type": "Question", "name": "Why choose the device_os and mobile_browser capabilities specifically?", "acceptedAnswer": { "@type": "Answer", "text": "With these two capabilities, DotKernel's built-in methods can also derive extra capabilities such as isMobile, isSmartPhone, isIphone, isAndroid, isBlackberry, isSymbian, and isWindowsMobile. Choosing other capabilities from scientiamobile results in wrong detection of these extra capabilities." } },
+                    { "@type": "Question", "name": "Why choose the device_os and mobile_browser capabilities specifically?", "acceptedAnswer": { "@type": "Answer", "text": "With these two capabilities, Dotkernel's built-in methods can also derive extra capabilities such as isMobile, isSmartPhone, isIphone, isAndroid, isBlackberry, isSymbian, and isWindowsMobile. Choosing other capabilities from scientiamobile results in wrong detection of these extra capabilities." } },
                     { "@type": "Question", "name": "What happened to the old Dot_UserAgent_Wurfl class?", "acceptedAnswer": { "@type": "Answer", "text": "It was removed and replaced with the new Dot_UserAgent_WurflCloud class, which uses the Wurfl Cloud API adapter." } },
                     { "@type": "Question", "name": "What does the redirect setting in application.ini control?", "acceptedAnswer": { "@type": "Answer", "text": "When resources.useragent.wurflcloud.redirect is TRUE (the default), visitors from the frontend are redirected to the mobile module the first time a mobile device is detected." } }
                 ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/disable-wurfl-redirect-for-mobile-browsers.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/disable-wurfl-redirect-for-mobile-browsers.jsonld.twig
index 50a65522..84fd7f73 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/disable-wurfl-redirect-for-mobile-browsers.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/disable-wurfl-redirect-for-mobile-browsers.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "How do you disable the automatic mobile redirect in DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "Starting with revision 408, set resources.useragent.wurflapi.redirect = false in application.ini. Per the article, this is also the default state of the redirect option." } },
+                    { "@type": "Question", "name": "How do you disable the automatic mobile redirect in Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "Starting with revision 408, set resources.useragent.wurflapi.redirect = false in application.ini. Per the article, this is also the default state of the redirect option." } },
                     { "@type": "Question", "name": "Where in the code is this configuration option checked?", "acceptedAnswer": { "@type": "Answer", "text": "In Controllers/frontend/IndexController.php (around line 19), a condition checks whether the redirect is enabled in application.ini, whether the visiting browser is mobile, and whether session->mobileHit isn't already set, before registering and redirecting the visit." } }
                 ]
             }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/disambiguation-dotkernel-1-and-dotkernel-3.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/disambiguation-dotkernel-1-and-dotkernel-3.jsonld.twig
index feff2e26..ccecc961 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/disambiguation-dotkernel-1-and-dotkernel-3.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/disambiguation-dotkernel-1-and-dotkernel-3.jsonld.twig
@@ -41,11 +41,11 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What does the name \"DotKernel\" mean?", "acceptedAnswer": { "@type": "Answer", "text": "It combines \"Dot\", as a representation of the Internet, with \"Kernel\", the quintessence of any IT application, reflecting the aim of being a central part of Internet development." } },
-                    { "@type": "Question", "name": "What is DotKernel 1?", "acceptedAnswer": { "@type": "Answer", "text": "A PHP Application Framework built on top of Zend Framework 1, first publicly released in July 2010, with an architecture based on MVC. Its latest version is 1.8 Long Term Support, which per the article will not be followed by a new version, only bugfixes." } },
-                    { "@type": "Question", "name": "What is DotKernel 3?", "acceptedAnswer": { "@type": "Answer", "text": "A collection of PSR-7 Middleware applications built on top of the Zend Expressive microframework, composed of a set of custom and extended Zend Framework 3 components, with an architecture based on Middleware. It implements PSR-1, PSR-2, PSR-4, PSR-7, and PSR-11." } },
-                    { "@type": "Question", "name": "How many applications make up DotKernel 3?", "acceptedAnswer": { "@type": "Answer", "text": "At the time of the article, there were two available applications, Frontend and Admin, with a third one, API, under development." } },
-                    { "@type": "Question", "name": "When someone writes just \"DotKernel\", which version is meant?", "acceptedAnswer": { "@type": "Answer", "text": "In posts older than 2017, \"DotKernel\" referred to DotKernel 1, since it was the only version. Since the release of DotKernel 3, \"DotKernel\" refers to DotKernel 3, and all future references to DotKernel 1 are made explicitly." } }
+                    { "@type": "Question", "name": "What does the name \"Dotkernel\" mean?", "acceptedAnswer": { "@type": "Answer", "text": "It combines \"Dot\", as a representation of the Internet, with \"Kernel\", the quintessence of any IT application, reflecting the aim of being a central part of Internet development." } },
+                    { "@type": "Question", "name": "What is Dotkernel 1?", "acceptedAnswer": { "@type": "Answer", "text": "A PHP Application Framework built on top of Zend Framework 1, first publicly released in July 2010, with an architecture based on MVC. Its latest version is 1.8 Long Term Support, which per the article will not be followed by a new version, only bugfixes." } },
+                    { "@type": "Question", "name": "What is Dotkernel 3?", "acceptedAnswer": { "@type": "Answer", "text": "A collection of PSR-7 Middleware applications built on top of the Zend Expressive microframework, composed of a set of custom and extended Zend Framework 3 components, with an architecture based on Middleware. It implements PSR-1, PSR-2, PSR-4, PSR-7, and PSR-11." } },
+                    { "@type": "Question", "name": "How many applications make up Dotkernel 3?", "acceptedAnswer": { "@type": "Answer", "text": "At the time of the article, there were two available applications, Frontend and Admin, with a third one, API, under development." } },
+                    { "@type": "Question", "name": "When someone writes just \"Dotkernel\", which version is meant?", "acceptedAnswer": { "@type": "Answer", "text": "In posts older than 2017, \"Dotkernel\" referred to Dotkernel 1, since it was the only version. Since the release of Dotkernel 3, \"Dotkernel\" refers to Dotkernel 3, and all future references to Dotkernel 1 are made explicitly." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotboost-technologies-products-and-services-north-american-relaunch.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotboost-technologies-products-and-services-north-american-relaunch.jsonld.twig
index d6253dce..0d5d2a5b 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotboost-technologies-products-and-services-north-american-relaunch.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotboost-technologies-products-and-services-north-american-relaunch.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What is at the heart of Dotboost's North American relaunch?", "acceptedAnswer": { "@type": "Answer", "text": "The source release of Dotboost's exclusive, in-house developed DotKernel framework, along with added business IT integration and increased clarity around existing consulting services." } },
+                    { "@type": "Question", "name": "What is at the heart of Dotboost's North American relaunch?", "acceptedAnswer": { "@type": "Answer", "text": "The source release of Dotboost's exclusive, in-house developed Dotkernel framework, along with added business IT integration and increased clarity around existing consulting services." } },
                     { "@type": "Question", "name": "When was Dotboost founded, and at what stages can it join a project?", "acceptedAnswer": { "@type": "Answer", "text": "Dotboost was founded in 2005. Per the article, its process can incorporate anywhere into a project's life-cycle, including concept development, architecture and design, development and integration, and implementation and support." } }
                 ]
             }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-2-0-release.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-2-0-release.jsonld.twig
index 7ab10366..b67c1f7f 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-2-0-release.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-2-0-release.jsonld.twig
@@ -41,11 +41,11 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What is a \"dots\" in DotKernel, a term introduced in this release?", "acceptedAnswer": { "@type": "Answer", "text": "A term for a submodule and all its component files. For example, \"user\" is a dots of the frontend module, and one dots can belong to multiple modules, such as \"user\" belonging to both frontend and admin." } },
+                    { "@type": "Question", "name": "What is a \"dots\" in Dotkernel, a term introduced in this release?", "acceptedAnswer": { "@type": "Answer", "text": "A term for a submodule and all its component files. For example, \"user\" is a dots of the frontend module, and one dots can belong to multiple modules, such as \"user\" belonging to both frontend and admin." } },
                     { "@type": "Question", "name": "Where are dots configuration values stored, compared to earlier versions?", "acceptedAnswer": { "@type": "Answer", "text": "They're stored in XML files inside the configs/dots folder. In previous versions, these values were hard-coded in the PHP files." } },
-                    { "@type": "Question", "name": "What dots does the admin module include by default?", "acceptedAnswer": { "@type": "Answer", "text": "admin, user, and system, to make it easier to start an application from DotKernel." } },
+                    { "@type": "Question", "name": "What dots does the admin module include by default?", "acceptedAnswer": { "@type": "Answer", "text": "admin, user, and system, to make it easier to start an application from Dotkernel." } },
                     { "@type": "Question", "name": "What library classes were added or updated in 1.2.0?", "acceptedAnswer": { "@type": "Answer", "text": "Dot_Geoip and Dot_Seo were newly implemented, while Dot_Curl and Dot_Session were updated, with each module now having its own session." } },
-                    { "@type": "Question", "name": "How are SQL queries written in DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "All SQL queries are written as prepared statements, a practice the article strongly encourages." } }
+                    { "@type": "Question", "name": "How are SQL queries written in Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "All SQL queries are written as prepared statements, a practice the article strongly encourages." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-2-2-release.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-2-2-release.jsonld.twig
index 07b053e5..04bdc6dc 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-2-2-release.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-2-2-release.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What does the DotKernel 1.2.2 release include?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel 1.2.2 is a bug-fix release that closes five issues: captcha error handling (try/catch), a pagination issue, a wrong admin link, notices and a fatal error found by an Acunetix scan, and an update to the copyright line in files." } },
+                    { "@type": "Question", "name": "What does the Dotkernel 1.2.2 release include?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel 1.2.2 is a bug-fix release that closes five issues: captcha error handling (try/catch), a pagination issue, a wrong admin link, notices and a fatal error found by an Acunetix scan, and an update to the copyright line in files." } },
                     { "@type": "Question", "name": "Why did all PHP files change in the 1.2.2 release?", "acceptedAnswer": { "@type": "Answer", "text": "Because of the fix for bug 35, which updated the copyright line, every PHP file in the codebase was touched, which is why the note in the post warns that all PHP files have changed." } },
                     { "@type": "Question", "name": "How can I upgrade from a previous version to 1.2.2?", "acceptedAnswer": { "@type": "Answer", "text": "You can download just the changed files from 1.2.1 to 1.2.2 using the upgrade package linked in the post, or check the ChangeLog 1.2.2 for full details of what changed." } }
                 ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-3-0-release.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-3-0-release.jsonld.twig
index ddba7ec5..bb6c1a9d 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-3-0-release.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-3-0-release.jsonld.twig
@@ -41,10 +41,10 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What is new in the admin interface in DotKernel 1.3.0?", "acceptedAnswer": { "@type": "Answer", "text": "1.3.0 adds a skin switcher for the admin, with several ready-made skins (blue, brown, gray, green) that can be set via the settings.admin.skin configuration value." } },
+                    { "@type": "Question", "name": "What is new in the admin interface in Dotkernel 1.3.0?", "acceptedAnswer": { "@type": "Answer", "text": "1.3.0 adds a skin switcher for the admin, with several ready-made skins (blue, brown, gray, green) that can be set via the settings.admin.skin configuration value." } },
                     { "@type": "Question", "name": "How do I protect a page so only logged-in members can access it?", "acceptedAnswer": { "@type": "Answer", "text": "Add the line Dot_Auth::checkIdentity(); in the controller file above the code you want to protect - everything below that line requires the visitor to be logged in." } },
                     { "@type": "Question", "name": "What happened to resource.xml in this release?", "acceptedAnswer": { "@type": "Answer", "text": "resource.xml was deleted and its content split between two new files, route.xml and dots.xml." } },
-                    { "@type": "Question", "name": "Is DotKernel 1.3.0 backward compatible with earlier versions?", "acceptedAnswer": { "@type": "Answer", "text": "No. Because of the XML file reorganization (bug 69), 1.3.0 is not compatible with previous versions." } }
+                    { "@type": "Question", "name": "Is Dotkernel 1.3.0 backward compatible with earlier versions?", "acceptedAnswer": { "@type": "Answer", "text": "No. Because of the XML file reorganization (bug 69), 1.3.0 is not compatible with previous versions." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-3-2-release.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-3-2-release.jsonld.twig
index d09746f0..22072618 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-3-2-release.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-3-2-release.jsonld.twig
@@ -41,9 +41,9 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What kind of release is DotKernel 1.3.2?", "acceptedAnswer": { "@type": "Answer", "text": "It's mainly a maintenance release, containing many bug fixes, some refactoring, and a few minor features." } },
+                    { "@type": "Question", "name": "What kind of release is Dotkernel 1.3.2?", "acceptedAnswer": { "@type": "Answer", "text": "It's mainly a maintenance release, containing many bug fixes, some refactoring, and a few minor features." } },
                     { "@type": "Question", "name": "What bugs were fixed in 1.3.2?", "acceptedAnswer": { "@type": "Answer", "text": "Fixes include a CSS issue on the admin phpinfo page, a warning in the admin dashboard, a WURFL cache issue and WURFL version issue in admin, a Dot_Paginator bug, a Zend Paginator double-query issue, and a database naming convention issue." } },
-                    { "@type": "Question", "name": "What minor features and refactoring were included?", "acceptedAnswer": { "@type": "Answer", "text": "Minor features include a refactor of validIP in Dot_Kernel and showing the WURFL date and API version in admin. Refactoring covered Zend_Paginator and added a dojo dijit theme to DotKernel." } }
+                    { "@type": "Question", "name": "What minor features and refactoring were included?", "acceptedAnswer": { "@type": "Answer", "text": "Minor features include a refactor of validIP in Dot_Kernel and showing the WURFL date and API version in admin. Refactoring covered Zend_Paginator and added a dojo dijit theme to Dotkernel." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-5-0-released.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-5-0-released.jsonld.twig
index 71f2e4fb..d20d6078 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-5-0-released.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-5-0-released.jsonld.twig
@@ -41,11 +41,11 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Why did DotKernel jump from 1.3 straight to 1.5.0?", "acceptedAnswer": { "@type": "Answer", "text": "Because of the large amount of changes and the long time spent in development, the team chose to skip version 1.4 and go straight to 1.5.0." } },
-                    { "@type": "Question", "name": "Did DotKernel switch from Dojo to jQuery in 1.5.0?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Starting with 1.5.0, DotKernel switched from Dojo to jQuery for its own distribution, though Dojo can still be used in your own projects." } },
+                    { "@type": "Question", "name": "Why did Dotkernel jump from 1.3 straight to 1.5.0?", "acceptedAnswer": { "@type": "Answer", "text": "Because of the large amount of changes and the long time spent in development, the team chose to skip version 1.4 and go straight to 1.5.0." } },
+                    { "@type": "Question", "name": "Did Dotkernel switch from Dojo to jQuery in 1.5.0?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Starting with 1.5.0, Dotkernel switched from Dojo to jQuery for its own distribution, though Dojo can still be used in your own projects." } },
                     { "@type": "Question", "name": "What is Dot_Model and why was it introduced?", "acceptedAnswer": { "@type": "Answer", "text": "Dot_Model is a base class introduced to reduce code duplication between admin and frontend models. Both admin- and frontend-specific model classes (such as User) inherit from a shared Dot_Model_User class that holds the common code." } },
                     { "@type": "Question", "name": "How does the \"dashed controllers\" feature work?", "acceptedAnswer": { "@type": "Answer", "text": "The controller name parsing was changed so a URL like www.example.com/search-article correctly calls SearchArticleController.php, allowing multi-word controller names split with dashes without breaking the coding standard." } },
-                    { "@type": "Question", "name": "How much changed in the 1.5.0 release?", "acceptedAnswer": { "@type": "Answer", "text": "About 250 commits went into the SVN repository since the previous release, so the blog post only covers the highlights - the full DotKernel 1.5.0 download is available to try out." } }
+                    { "@type": "Question", "name": "How much changed in the 1.5.0 release?", "acceptedAnswer": { "@type": "Answer", "text": "About 250 commits went into the SVN repository since the previous release, so the blog post only covers the highlights - the full Dotkernel 1.5.0 download is available to try out." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-8-0-lts-released.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-8-0-lts-released.jsonld.twig
index 5e99feb4..4963912e 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-8-0-lts-released.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-8-0-lts-released.jsonld.twig
@@ -41,11 +41,11 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What does LTS mean for DotKernel 1.8.0?", "acceptedAnswer": { "@type": "Answer", "text": "LTS stands for Long-term support, a type of special version designed to be supported for longer than normal, which is particularly common for open-source software projects." } },
-                    { "@type": "Question", "name": "What is the Plugin Architecture introduced in 1.8.0?", "acceptedAnswer": { "@type": "Answer", "text": "Starting with 1.8.0, DotKernel uses Plugins to make extending the framework easier." } },
+                    { "@type": "Question", "name": "What does LTS mean for Dotkernel 1.8.0?", "acceptedAnswer": { "@type": "Answer", "text": "LTS stands for Long-term support, a type of special version designed to be supported for longer than normal, which is particularly common for open-source software projects." } },
+                    { "@type": "Question", "name": "What is the Plugin Architecture introduced in 1.8.0?", "acceptedAnswer": { "@type": "Answer", "text": "Starting with 1.8.0, Dotkernel uses Plugins to make extending the framework easier." } },
                     { "@type": "Question", "name": "How does 1.8.0 load faster than previous versions?", "acceptedAnswer": { "@type": "Answer", "text": "It supports APC and File Caching within the framework, so XML files and config files are cached to maximize response speed." } },
                     { "@type": "Question", "name": "What is Dot_Request?", "acceptedAnswer": { "@type": "Answer", "text": "Dot_Request is a new class that gives you control over the request data before you use it, so that the variables $_SERVER, $_GET and $_POST are only accessed within controllers." } },
-                    { "@type": "Question", "name": "What was removed from DotKernel in 1.8.0?", "acceptedAnswer": { "@type": "Answer", "text": "WURFL integration was removed (mobile device detection is now handled separately, and WURFL can be added as a plugin), and support for multiple SMTP transporters was removed (it can also be added as a plugin)." } },
+                    { "@type": "Question", "name": "What was removed from Dotkernel in 1.8.0?", "acceptedAnswer": { "@type": "Answer", "text": "WURFL integration was removed (mobile device detection is now handled separately, and WURFL can be added as a plugin), and support for multiple SMTP transporters was removed (it can also be added as a plugin)." } },
                     { "@type": "Question", "name": "What security-related additions does 1.8.0 include?", "acceptedAnswer": { "@type": "Answer", "text": "A security scan in the Admin Dashboard shows recommended settings, admin failed-login notifications are sent to all developers listed in devEmails (not just the first admin), and a new Alert System can notify developers if something goes wrong." } }
                 ]
             }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-8-1-upgrade-from-1-8-0-released.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-8-1-upgrade-from-1-8-0-released.jsonld.twig
index 428d4a79..0d8217ae 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-8-1-upgrade-from-1-8-0-released.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-1-8-1-upgrade-from-1-8-0-released.jsonld.twig
@@ -41,8 +41,8 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What's new in DotKernel 1.8.1?", "acceptedAnswer": { "@type": "Answer", "text": "The main change is Enhanced Cache Support, which means you can use tags in your cache system if the host supports it." } },
-                    { "@type": "Question", "name": "How do I upgrade from 1.8.0 to 1.8.1?", "acceptedAnswer": { "@type": "Answer", "text": "The post provides a dedicated \"Upgrade from DotKernel 1.8.0\" download link, separate from the full DotKernel 1.8.1 package and the original DotKernel 1.8.0 (LTS) download." } }
+                    { "@type": "Question", "name": "What's new in Dotkernel 1.8.1?", "acceptedAnswer": { "@type": "Answer", "text": "The main change is Enhanced Cache Support, which means you can use tags in your cache system if the host supports it." } },
+                    { "@type": "Question", "name": "How do I upgrade from 1.8.0 to 1.8.1?", "acceptedAnswer": { "@type": "Answer", "text": "The post provides a dedicated \"Upgrade from Dotkernel 1.8.0\" download link, separate from the full Dotkernel 1.8.1 package and the original Dotkernel 1.8.0 (LTS) download." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-coding-standard.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-coding-standard.jsonld.twig
index a744744e..6ee687fb 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-coding-standard.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-coding-standard.jsonld.twig
@@ -41,8 +41,8 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What coding standard does DotKernel follow?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel borrows its coding standard from the Zend Framework Coding Standard, with some exceptions described in this article." } },
-                    { "@type": "Question", "name": "Tabs or spaces for indentation?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel indents with tabs, not spaces." } },
+                    { "@type": "Question", "name": "What coding standard does Dotkernel follow?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel borrows its coding standard from the Zend Framework Coding Standard, with some exceptions described in this article." } },
+                    { "@type": "Question", "name": "Tabs or spaces for indentation?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel indents with tabs, not spaces." } },
                     { "@type": "Question", "name": "How should classes, interfaces, and filenames be named?", "acceptedAnswer": { "@type": "Answer", "text": "Classes start with the prefix Dot_ (e.g. Dot_Templates), interfaces end with the string \"Interface\" (e.g. Dot_Db_Interface), and all PHP files use the \".php\" extension, with no fancy extensions like \".inc\"." } },
                     { "@type": "Question", "name": "How should curly braces be placed for control statements?", "acceptedAnswer": { "@type": "Answer", "text": "Every opening curly brace starts on its own new line after the statement, and its matching closing brace also goes on a new line, aligned in the same column as the opening brace, for better indentation of the code." } }
                 ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-database-naming-conventions-for-mysql.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-database-naming-conventions-for-mysql.jsonld.twig
index 313b3171..ab6f0420 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-database-naming-conventions-for-mysql.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-database-naming-conventions-for-mysql.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Where do DotKernel's database naming conventions come from?", "acceptedAnswer": { "@type": "Answer", "text": "They are borrowed from FaZend's \"Rules of naming of database tables and columns,\" an open-source PHP framework based on Zend Framework." } },
+                    { "@type": "Question", "name": "Where do Dotkernel's database naming conventions come from?", "acceptedAnswer": { "@type": "Answer", "text": "They are borrowed from FaZend's \"Rules of naming of database tables and columns,\" an open-source PHP framework based on Zend Framework." } },
                     { "@type": "Question", "name": "Should table names be singular or plural?", "acceptedAnswer": { "@type": "Answer", "text": "Singular table names only, for example user, category, product, order, orderProduct." } },
                     { "@type": "Question", "name": "How should foreign key columns be named?", "acceptedAnswer": { "@type": "Answer", "text": "A foreign key column takes the name of the referenced table plus the name of the referenced column. For example, referencing table admin's Id column produces a column named adminId." } },
                     { "@type": "Question", "name": "What naming pattern is used for CONSTRAINT names?", "acceptedAnswer": { "@type": "Answer", "text": "The pattern is FK_referencedTableName_tableName, for example CONSTRAINT `FK_admin_adminLogin`." } },
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-on-nginx.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-on-nginx.jsonld.twig
index 62b7551b..3ed2bf9c 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-on-nginx.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-on-nginx.jsonld.twig
@@ -44,7 +44,7 @@
                     { "@type": "Question", "name": "What server stack was used to test Dotkernel on Nginx?", "acceptedAnswer": { "@type": "Answer", "text": "A clean CentOS 6.3 VPS running Nginx 1.4.1, PHP 5.4.16, and PHP-FPM, with the APC and GeoIP PHP modules installed." } },
                     { "@type": "Question", "name": "What is the Nginx equivalent of the main .htaccess file?", "acceptedAnswer": { "@type": "Answer", "text": "The directive try_files $uri $uri/ /index.php;, which sends all requests to the index.php file." } },
                     { "@type": "Question", "name": "How is the configs folder protected from web access in Nginx?", "acceptedAnswer": { "@type": "Answer", "text": "By adding a location block matching ^/configs/ that returns deny all;." } },
-                    { "@type": "Question", "name": "How was the DotKernel codebase deployed onto the server?", "acceptedAnswer": { "@type": "Answer", "text": "It was exported directly from SVN using svn export --force http://v1.dotkernel.net/svn/trunk/ /var/www/html." } }
+                    { "@type": "Question", "name": "How was the Dotkernel codebase deployed onto the server?", "acceptedAnswer": { "@type": "Answer", "text": "It was exported directly from SVN using svn export --force http://v1.dotkernel.net/svn/trunk/ /var/www/html." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-template-engine.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-template-engine.jsonld.twig
index 03511d51..41bc5818 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-template-engine.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-template-engine.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What is the DotKernel Template Engine based on?", "acceptedAnswer": { "@type": "Answer", "text": "It's an implementation of the PHPLib Template engine for PHP5." } },
+                    { "@type": "Question", "name": "What is the Dotkernel Template Engine based on?", "acceptedAnswer": { "@type": "Answer", "text": "It's an implementation of the PHPLib Template engine for PHP5." } },
                     { "@type": "Question", "name": "What is the main benefit of using it?", "acceptedAnswer": { "@type": "Answer", "text": "It separates application code from the presentation layer, and separates data manipulation from its final format (HTML, XML, or a formatted e-mail), letting you change a site's look and feel quickly without delving into a lot of PHP variable assignments and print statements." } }
                 ]
             }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-version-1-0-in-action.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-version-1-0-in-action.jsonld.twig
index 4e504144..b43df0db 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-version-1-0-in-action.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/dotkernel-version-1-0-in-action.jsonld.twig
@@ -41,9 +41,9 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Who developed DotKernel and what is it built on?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel is DotBoost's in-house developed framework, built on top of Zend Framework. At the time of this article it was at version 1.0, released under the Open Software License (OSL 3.0)." } },
-                    { "@type": "Question", "name": "What architecture does DotKernel use?", "acceptedAnswer": { "@type": "Answer", "text": "A simplified MVC (Model-View-Controller) architecture that's easy to learn for beginner and intermediate level programmers, achieved by eliminating much of Zend Framework's complexity through a different approach to handling web requests." } },
-                    { "@type": "Question", "name": "What does Zend_Config provide in DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "It provides multiple backends for configuration storage and a simple, intuitive, object-oriented interface for accessing it. DotKernel stores configuration as simple PHP arrays, which are then wrapped by Zend_Config." } },
+                    { "@type": "Question", "name": "Who developed Dotkernel and what is it built on?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel is DotBoost's in-house developed framework, built on top of Zend Framework. At the time of this article it was at version 1.0, released under the Open Software License (OSL 3.0)." } },
+                    { "@type": "Question", "name": "What architecture does Dotkernel use?", "acceptedAnswer": { "@type": "Answer", "text": "A simplified MVC (Model-View-Controller) architecture that's easy to learn for beginner and intermediate level programmers, achieved by eliminating much of Zend Framework's complexity through a different approach to handling web requests." } },
+                    { "@type": "Question", "name": "What does Zend_Config provide in Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "It provides multiple backends for configuration storage and a simple, intuitive, object-oriented interface for accessing it. Dotkernel stores configuration as simple PHP arrays, which are then wrapped by Zend_Config." } },
                     { "@type": "Question", "name": "What role do Zend_Db and Zend_Db_Table play?", "acceptedAnswer": { "@type": "Answer", "text": "Zend_Db_Table is a classic implementation of the Table Data Gateway and Row Data Gateway design patterns, allowing easy and intuitive access to database tables and rows, as well as an entry point for custom business logic surrounding the data." } },
                     { "@type": "Question", "name": "What are Zend_Mail and Zend_Registry used for?", "acceptedAnswer": { "@type": "Answer", "text": "Zend_Mail composes and sends both text and MIME-compliant multipart e-mail, via the default Zend_Mail_Transport_Sendmail transport or via Zend_Mail_Transport_Smtp. Zend_Registry is a container for storing objects and values in the application space, so the same object is always available throughout the application, as an alternative to using global storage." } }
                 ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/geoip-city-removed-from-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/geoip-city-removed-from-dotkernel.jsonld.twig
index b4b828c3..0111b617 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/geoip-city-removed-from-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/geoip-city-removed-from-dotkernel.jsonld.twig
@@ -41,10 +41,10 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Why was GeoIP City removed from DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "The City database on GeoIP extension version 1.1.0 and above was causing a segmentation fault, which resulted in crashing or outputting an error instead of executing the PHP code." } },
-                    { "@type": "Question", "name": "Who is affected by this error?", "acceptedAnswer": { "@type": "Answer", "text": "Users running an older DotKernel version together with GeoIP extension version 1.1.0 or newer, since the error comes from the extension's incompatibility with the database (dat) file." } },
+                    { "@type": "Question", "name": "Why was GeoIP City removed from Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "The City database on GeoIP extension version 1.1.0 and above was causing a segmentation fault, which resulted in crashing or outputting an error instead of executing the PHP code." } },
+                    { "@type": "Question", "name": "Who is affected by this error?", "acceptedAnswer": { "@type": "Answer", "text": "Users running an older Dotkernel version together with GeoIP extension version 1.1.0 or newer, since the error comes from the extension's incompatibility with the database (dat) file." } },
                     { "@type": "Question", "name": "How does the error show up to visitors?", "acceptedAnswer": { "@type": "Answer", "text": "On some operating systems, Apache still responds with HTTP Status Code 200 (OK) but with a page containing a generic \"internal error or misconfiguration\" message, and the error might not be logged since it's generated by the GeoIP extension rather than by the PHP code." } },
-                    { "@type": "Question", "name": "How can you get rid of the error if you don't need GeoIP City?", "acceptedAnswer": { "@type": "Answer", "text": "Comment out or remove the relevant lines in DotKernel/admin/System.php (the Admin/System model) and in library/Dot/GeoIp.php (the Dot_GeoIp class). These changes were also made in the latest version of DotKernel, but this fix should only be used if you don't intend to use GeoIP City." } },
+                    { "@type": "Question", "name": "How can you get rid of the error if you don't need GeoIP City?", "acceptedAnswer": { "@type": "Answer", "text": "Comment out or remove the relevant lines in Dotkernel/admin/System.php (the Admin/System model) and in library/Dot/GeoIp.php (the Dot_GeoIp class). These changes were also made in the latest version of Dotkernel, but this fix should only be used if you don't intend to use GeoIP City." } },
                     { "@type": "Question", "name": "What does the article recommend going forward?", "acceptedAnswer": { "@type": "Answer", "text": "It recommends special coding for GeoIP City and for the GeoIP extension in general, and notes that GeoIP is an obsolete extension, with Maxmind recommending GeoIP2 instead." } }
                 ]
             }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/geoip-ip-address-location-in-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/geoip-ip-address-location-in-dotkernel.jsonld.twig
index 8b4b68a6..c5b24521 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/geoip-ip-address-location-in-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/geoip-ip-address-location-in-dotkernel.jsonld.twig
@@ -41,9 +41,9 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What is GeoIP and what does it let DotKernel do?", "acceptedAnswer": { "@type": "Answer", "text": "GeoIP is MaxMind's proprietary technology for IP geolocation data. DotKernel uses it to get user statistics by country, determining a visitor's country, region, city, postal code, or area code in real time." } },
-                    { "@type": "Question", "name": "Where does the GeoIP logic live in DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "In library/Dot/Geoip.php, inside the getCountryByIp function." } },
-                    { "@type": "Question", "name": "What does getCountryByIp do when the mod_geoip PECL extension isn't installed?", "acceptedAnswer": { "@type": "Answer", "text": "It falls back to the existing externals/geoip/GeoIP.dat file bundled with DotKernel (downloadable from MaxMind if not present)." } },
+                    { "@type": "Question", "name": "What is GeoIP and what does it let Dotkernel do?", "acceptedAnswer": { "@type": "Answer", "text": "GeoIP is MaxMind's proprietary technology for IP geolocation data. Dotkernel uses it to get user statistics by country, determining a visitor's country, region, city, postal code, or area code in real time." } },
+                    { "@type": "Question", "name": "Where does the GeoIP logic live in Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "In library/Dot/Geoip.php, inside the getCountryByIp function." } },
+                    { "@type": "Question", "name": "What does getCountryByIp do when the mod_geoip PECL extension isn't installed?", "acceptedAnswer": { "@type": "Answer", "text": "It falls back to the existing externals/geoip/GeoIP.dat file bundled with Dotkernel (downloadable from MaxMind if not present)." } },
                     { "@type": "Question", "name": "What happens when mod_geoip is installed and GeoIP.dat exists?", "acceptedAnswer": { "@type": "Answer", "text": "It uses the built-in PHP functions geoip_country_code_by_name and geoip_country_name_by_name to get the country code and name." } },
                     { "@type": "Question", "name": "What if GeoIP.dat is missing but GeoIPCity.dat exists, or neither file exists?", "acceptedAnswer": { "@type": "Answer", "text": "If GeoIPCity.dat exists, it uses the PHP function geoip_record_by_name to get the country code and name. If neither .dat file exists, it behaves the same as when mod_geoip isn't installed, falling back to externals/geoip/GeoIP.dat." } }
                 ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/handling-and-logging-errors-with-dot-errorhandler-and-dot-log.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/handling-and-logging-errors-with-dot-errorhandler-and-dot-log.jsonld.twig
index 76ad4ecd..0546dac1 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/handling-and-logging-errors-with-dot-errorhandler-and-dot-log.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/handling-and-logging-errors-with-dot-errorhandler-and-dot-log.jsonld.twig
@@ -44,7 +44,7 @@
                     { "@type": "Question", "name": "What two kinds of error handlers does dot-errorhandler provide?", "acceptedAnswer": { "@type": "Answer", "text": "A plain ErrorHandler, which is a copy of Zend Expressive's Zend\\Stratigility\\Middleware\\ErrorHandler (copied because that class is final), and a logging LogErrorHandler, which is the same but with added logging support via the container. Both have factories registered for easier use with the Container." } },
                     { "@type": "Question", "name": "How do you install dot-errorhandler?", "acceptedAnswer": { "@type": "Answer", "text": "Run composer require dotkernel/dot-errorhandler." } },
                     { "@type": "Question", "name": "Which error handler is used by default?", "acceptedAnswer": { "@type": "Answer", "text": "The plain error handler is selected by default as a fallback, and this can be overwritten through the config file, which also registers factories for both handlers plus an alias to switch between them." } },
-                    { "@type": "Question", "name": "What must already be in place before configuring the logging error handler?", "acceptedAnswer": { "@type": "Answer", "text": "A configured logger as described in the \"Logging with dot-log in Zend Expressive and DotKernel\" article, with the logger named default_logger as used in the package's config example." } },
+                    { "@type": "Question", "name": "What must already be in place before configuring the logging error handler?", "acceptedAnswer": { "@type": "Answer", "text": "A configured logger as described in the \"Logging with dot-log in Zend Expressive and Dotkernel\" article, with the logger named default_logger as used in the package's config example." } },
                     { "@type": "Question", "name": "Why might whoops interfere when testing dot-errorhandler?", "acceptedAnswer": { "@type": "Answer", "text": "dot-errorhandler is meant to be a silent logger for staging and production environments. To actually test it, development mode should be disabled, otherwise whoops will catch the errors and show them to the developer instead." } },
                     { "@type": "Question", "name": "How were errors triggered to test the error handlers?", "acceptedAnswer": { "@type": "Answer", "text": "By throwing Exceptions, the most common case, and by raising warnings/errors such as dividing a number by zero (e.g. 16/0) or casting an array to a string." } }
                 ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/highcharts-integration-in-dotkernel-1-6-0.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/highcharts-integration-in-dotkernel-1-6-0.jsonld.twig
index cc66d280..914c3957 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/highcharts-integration-in-dotkernel-1-6-0.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/highcharts-integration-in-dotkernel-1-6-0.jsonld.twig
@@ -41,9 +41,9 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What charting library was integrated in DotKernel 1.6.0?", "acceptedAnswer": { "@type": "Answer", "text": "Highcharts was integrated in DotKernel 1.6.0, offering a new, intuitive and interactive charting experience." } },
+                    { "@type": "Question", "name": "What charting library was integrated in Dotkernel 1.6.0?", "acceptedAnswer": { "@type": "Answer", "text": "Highcharts was integrated in Dotkernel 1.6.0, offering a new, intuitive and interactive charting experience." } },
                     { "@type": "Question", "name": "What sample charts were added to the admin?", "acceptedAnswer": { "@type": "Answer", "text": "The admin includes samples made with Highcharts: a pie chart (with a small custom feature), a column chart, and a line chart." } },
-                    { "@type": "Question", "name": "Where can the Highcharts library be found in a DotKernel project?", "acceptedAnswer": { "@type": "Answer", "text": "The Highcharts library is located in the externals directory of the project." } }
+                    { "@type": "Question", "name": "Where can the Highcharts library be found in a Dotkernel project?", "acceptedAnswer": { "@type": "Answer", "text": "The Highcharts library is located in the externals directory of the project." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/how-to-group-log-files-by-date-using-dot-log.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/how-to-group-log-files-by-date-using-dot-log.jsonld.twig
index ff6099ab..34441168 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/how-to-group-log-files-by-date-using-dot-log.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/how-to-group-log-files-by-date-using-dot-log.jsonld.twig
@@ -44,9 +44,9 @@
                     { "@type": "Question", "name": "What does dot-log Version 3.1.1 add?", "acceptedAnswer": { "@type": "Answer", "text": "Version 3.1.1 adds the ability to use datetime formatter strings directly in the stream option of your log writer, and it fixes an issue where caching dot-log configs caused logs to be written to the same file instead of being grouped by date." } },
                     { "@type": "Question", "name": "How do I make sure I'm using the fix in Version 3.1.1?", "acceptedAnswer": { "@type": "Answer", "text": "Make sure you're using the latest version of dot-log by running composer update dotkernel/dot-log." } },
                     { "@type": "Question", "name": "Do I need to change anything if my logs are already written to a single static file?", "acceptedAnswer": { "@type": "Answer", "text": "No. If your application logs messages in a single file with a static name (e.g. log/dk.log), you can skip the rest of the article - logging will work as before." } },
-                    { "@type": "Question", "name": "How do I group log files by date when using DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "In config/autoload/error-handling.global.php, locate every log writer by navigating to dot_log->loggers->default_logger->writers and replace a stream value like sprintf('%s/../../log/error-log-%s.log', __DIR__, date('Y-m-d')) with __DIR__ . '/../../log/error-log-{Y}-{m}-{d}.log'." } },
-                    { "@type": "Question", "name": "How do I group log files by date without DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "In your dot-log config (e.g. /config/autoload/log.global.php), locate every writer under dot_log->loggers->my_logger->writers and replace a dynamic stream value such as sprintf('%s/../../log/dk-%s.log', __DIR__, date('Y-m-d')) with a formatter string like __DIR__ . '/../../log/error-log-{Y}-{m}-{d}.log'." } },
-                    { "@type": "Question", "name": "What must I do after changing the stream configuration?", "acceptedAnswer": { "@type": "Answer", "text": "Clear the config cache. In a DotKernel application, run php bin/clear-config-cache.php; in a non-DotKernel setup, make sure you clear your application's config before usage." } }
+                    { "@type": "Question", "name": "How do I group log files by date when using Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "In config/autoload/error-handling.global.php, locate every log writer by navigating to dot_log->loggers->default_logger->writers and replace a stream value like sprintf('%s/../../log/error-log-%s.log', __DIR__, date('Y-m-d')) with __DIR__ . '/../../log/error-log-{Y}-{m}-{d}.log'." } },
+                    { "@type": "Question", "name": "How do I group log files by date without Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "In your dot-log config (e.g. /config/autoload/log.global.php), locate every writer under dot_log->loggers->my_logger->writers and replace a dynamic stream value such as sprintf('%s/../../log/dk-%s.log', __DIR__, date('Y-m-d')) with a formatter string like __DIR__ . '/../../log/error-log-{Y}-{m}-{d}.log'." } },
+                    { "@type": "Question", "name": "What must I do after changing the stream configuration?", "acceptedAnswer": { "@type": "Answer", "text": "Clear the config cache. In a Dotkernel application, run php bin/clear-config-cache.php; in a non-Dotkernel setup, make sure you clear your application's config before usage." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/how-to-set-a-persistent-connection-to-database-with-zend-framework-zend-db-adapter.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/how-to-set-a-persistent-connection-to-database-with-zend-framework-zend-db-adapter.jsonld.twig
index ba4bae23..ba147527 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/how-to-set-a-persistent-connection-to-database-with-zend-framework-zend-db-adapter.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/how-to-set-a-persistent-connection-to-database-with-zend-framework-zend-db-adapter.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Where do you configure a persistent database connection in a DotKernel project?", "acceptedAnswer": { "@type": "Answer", "text": "The option should be added in application.ini, as shown in the DotKernel approach used as an example in the article." } },
+                    { "@type": "Question", "name": "Where do you configure a persistent database connection in a Dotkernel project?", "acceptedAnswer": { "@type": "Answer", "text": "The option should be added in application.ini, as shown in the Dotkernel approach used as an example in the article." } },
                     { "@type": "Question", "name": "What Zend_Db configuration line should NOT be used for a persistent connection?", "acceptedAnswer": { "@type": "Answer", "text": "database.params.options.PDO::ATTR_PERSISTENT = TRUE should not be used - the article states that it will not work." } },
                     { "@type": "Question", "name": "What's the correct line to enable a persistent connection?", "acceptedAnswer": { "@type": "Answer", "text": "Use database.params.persistent = TRUE instead." } }
                 ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/how-to-use-alerts-in-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/how-to-use-alerts-in-dotkernel.jsonld.twig
index efeefb82..615e3bdc 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/how-to-use-alerts-in-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/how-to-use-alerts-in-dotkernel.jsonld.twig
@@ -43,7 +43,7 @@
                 "mainEntity": [
                     { "@type": "Question", "name": "What is a Dot_Alert used for?", "acceptedAnswer": { "@type": "Answer", "text": "Alerts (Dot_Alert's) are e-mails usually sent to the site developers using PHP's mail() function. They shouldn't be used to send regular mail - they only notify the developer that something is wrong." } },
                     { "@type": "Question", "name": "What does the Dot_Alert class resemble, and what does an alert contain?", "acceptedAnswer": { "@type": "Answer", "text": "Dot_Alert resembles Dot_Email. Like a mail message, an alert has at least a sender, a subject, a destination and a message, and it can be sent." } },
-                    { "@type": "Question", "name": "What's an example use of Alerts in DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel uses Alerts to notify the developer when an email was not sent successfully, with the message kept in the dots.xml file under the alertMessages section." } },
+                    { "@type": "Question", "name": "What's an example use of Alerts in Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel uses Alerts to notify the developer when an email was not sent successfully, with the message kept in the dots.xml file under the alertMessages section." } },
                     { "@type": "Question", "name": "How are the {VARIABLES} in an alert message replaced with real data?", "acceptedAnswer": { "@type": "Answer", "text": "A $details array is prepared (e.g. e_class, site_name, site_url, e_message, to_email, from_email, date_now), and the alert's setDetails() method replaces the {VARIABLES} placeholders in the subject and message with that data." } },
                     { "@type": "Question", "name": "What are the steps to build and send an alert?", "acceptedAnswer": { "@type": "Answer", "text": "Create a new Dot_Alert(), add headers such as From, Reply-To and X-Mailer, then call setTo(), setSubject() and setContent(), then setDetails() to fill in the placeholders, and finally call send()." } }
                 ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/implementing-the-new-password-hashing-api-from-php-5-5-in-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/implementing-the-new-password-hashing-api-from-php-5-5-in-dotkernel.jsonld.twig
index 54f18b64..b995ca28 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/implementing-the-new-password-hashing-api-from-php-5-5-in-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/implementing-the-new-password-hashing-api-from-php-5-5-in-dotkernel.jsonld.twig
@@ -41,10 +41,10 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Why was DotKernel refactored to use the new PHP 5.5 Password Hashing API?", "acceptedAnswer": { "@type": "Answer", "text": "To use the new Password Hashing functions introduced in PHP 5.5 and unify all password related functions used for both admin and users, DotKernel's codebase was refactored in version 1.8.0, starting from revision 799." } },
-                    { "@type": "Question", "name": "How can PHP versions older than 5.5 use these new hashing functions?", "acceptedAnswer": { "@type": "Answer", "text": "Since the 4 new functions are only available since PHP 5.5, DotKernel used the Password Compatibility library (ircmaxell/password_compat)." } },
-                    { "@type": "Question", "name": "What is the minimum PHP version required after this change?", "acceptedAnswer": { "@type": "Answer", "text": "The minimum PHP version required to run DotKernel was raised to PHP 5.3.8." } },
-                    { "@type": "Question", "name": "What steps are needed to apply this refactor to an older DotKernel system?", "acceptedAnswer": { "@type": "Answer", "text": "Change the password column definition in the admin and user tables via ALTER TABLE, remove the settings.admin.salt entry from application.ini, apply the provided patch, and run the conversion script described in Console/Controller.php at line 47." } },
+                    { "@type": "Question", "name": "Why was Dotkernel refactored to use the new PHP 5.5 Password Hashing API?", "acceptedAnswer": { "@type": "Answer", "text": "To use the new Password Hashing functions introduced in PHP 5.5 and unify all password related functions used for both admin and users, Dotkernel's codebase was refactored in version 1.8.0, starting from revision 799." } },
+                    { "@type": "Question", "name": "How can PHP versions older than 5.5 use these new hashing functions?", "acceptedAnswer": { "@type": "Answer", "text": "Since the 4 new functions are only available since PHP 5.5, Dotkernel used the Password Compatibility library (ircmaxell/password_compat)." } },
+                    { "@type": "Question", "name": "What is the minimum PHP version required after this change?", "acceptedAnswer": { "@type": "Answer", "text": "The minimum PHP version required to run Dotkernel was raised to PHP 5.3.8." } },
+                    { "@type": "Question", "name": "What steps are needed to apply this refactor to an older Dotkernel system?", "acceptedAnswer": { "@type": "Answer", "text": "Change the password column definition in the admin and user tables via ALTER TABLE, remove the settings.admin.salt entry from application.ini, apply the provided patch, and run the conversion script described in Console/Controller.php at line 47." } },
                     { "@type": "Question", "name": "What happens to existing admin passwords during the upgrade?", "acceptedAnswer": { "@type": "Answer", "text": "Admin passwords cannot be converted automatically, so they need to be recreated manually." } }
                 ]
             }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/manual-upgrade-of-wurfl-xml-file-in-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/manual-upgrade-of-wurfl-xml-file-in-dotkernel.jsonld.twig
index 389bd588..036e0dd6 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/manual-upgrade-of-wurfl-xml-file-in-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/manual-upgrade-of-wurfl-xml-file-in-dotkernel.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Why does the WURFL xml file need to be manually upgraded in DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel bundles an old WURFL XML file (the latest GPL version, from June 2011). Because of a license change to that WURFL file, the bundled file will no longer be upgraded by DotKernel, so it must be upgraded manually if you still want to use it." } },
+                    { "@type": "Question", "name": "Why does the WURFL xml file need to be manually upgraded in Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel bundles an old WURFL XML file (the latest GPL version, from June 2011). Because of a license change to that WURFL file, the bundled file will no longer be upgraded by Dotkernel, so it must be upgraded manually if you still want to use it." } },
                     { "@type": "Question", "name": "What are the main steps to manually upgrade the WURFL file?", "acceptedAnswer": { "@type": "Answer", "text": "Download the wurfl-2.3.xml.zip file, rename it to wurfl.zip, rename the file inside the archive to wurfl.xml, and replace /externals/wurfl/wurfl.zip with this new wurfl.zip file." } },
                     { "@type": "Question", "name": "Is there anything else to replace besides wurfl.zip?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Download the web_browsers_patch.xml file and replace the /externals/wurfl/web_browsers_patch.xml file with the new one." } },
                     { "@type": "Question", "name": "What's the last step after replacing the files?", "acceptedAnswer": { "@type": "Answer", "text": "Go to the Admin panel, click on the \"empty\" wurfl cache link, then rebuild the cache." } }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/php-formatter-and-templates-for-zend-studio-10-1.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/php-formatter-and-templates-for-zend-studio-10-1.jsonld.twig
index cafb3028..53f9eea7 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/php-formatter-and-templates-for-zend-studio-10-1.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/php-formatter-and-templates-for-zend-studio-10-1.jsonld.twig
@@ -42,7 +42,7 @@
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
                     { "@type": "Question", "name": "Why does the PHP Formatter plugin for Zend Studio 10.1 need to be changed?", "acceptedAnswer": { "@type": "Answer", "text": "Because Zend donated the Zend Studio Formatter upstream to the PDT project, the Formatter plugin needs to be changed by replacing \"com.zend.php\" with \"org.eclipse.php\"." } },
-                    { "@type": "Question", "name": "Where can I get DotKernel's updated Formatter and Templates files for Zend Studio 10.1?", "acceptedAnswer": { "@type": "Answer", "text": "The updated PHP Formatter file for Zend Studio 10.1 and a templates file built according to the DotKernel coding standard are both available as downloads linked in the article." } }
+                    { "@type": "Question", "name": "Where can I get Dotkernel's updated Formatter and Templates files for Zend Studio 10.1?", "acceptedAnswer": { "@type": "Answer", "text": "The updated PHP Formatter file for Zend Studio 10.1 and a templates file built according to the Dotkernel coding standard are both available as downloads linked in the article." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/scientia-mobile-licensed-its-wurfl-cloud-php-library-to-dotkernel-1-6.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/scientia-mobile-licensed-its-wurfl-cloud-php-library-to-dotkernel-1-6.jsonld.twig
index 6e698b53..03d786d0 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/scientia-mobile-licensed-its-wurfl-cloud-php-library-to-dotkernel-1-6.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/scientia-mobile-licensed-its-wurfl-cloud-php-library-to-dotkernel-1-6.jsonld.twig
@@ -41,10 +41,10 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Why was the WURFL PHP library removed from DotKernel 1.6.0?", "acceptedAnswer": { "@type": "Answer", "text": "In DotKernel 1.6.0, released on May 16th, 2012, the GPL'ed WURFL PHP library was removed because the code was obsolete anyway and the structure of the XML file had changed." } },
-                    { "@type": "Question", "name": "What replaced the old WURFL PHP library?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel implemented Scientia Mobile's WURFL Cloud PHP library instead." } },
-                    { "@type": "Question", "name": "Where can I find instructions to set up the WURFL Cloud API key?", "acceptedAnswer": { "@type": "Answer", "text": "Instructions on how to sign up for a free account and set up your API key are linked in the article, pointing to the \"Detecting Mobile Devices in DotKernel 1.6\" article." } },
-                    { "@type": "Question", "name": "What are the terms of DotKernel's special WURFL Cloud license?", "acceptedAnswer": { "@type": "Answer", "text": "The license is non-transferable, conditioned, limited to the version received, and restricted to use and distribution only in connection with the Dotkernel software framework. It does not allow making derivative works, even when source code is provided or the code is not obfuscated." } }
+                    { "@type": "Question", "name": "Why was the WURFL PHP library removed from Dotkernel 1.6.0?", "acceptedAnswer": { "@type": "Answer", "text": "In Dotkernel 1.6.0, released on May 16th, 2012, the GPL'ed WURFL PHP library was removed because the code was obsolete anyway and the structure of the XML file had changed." } },
+                    { "@type": "Question", "name": "What replaced the old WURFL PHP library?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel implemented Scientia Mobile's WURFL Cloud PHP library instead." } },
+                    { "@type": "Question", "name": "Where can I find instructions to set up the WURFL Cloud API key?", "acceptedAnswer": { "@type": "Answer", "text": "Instructions on how to sign up for a free account and set up your API key are linked in the article, pointing to the \"Detecting Mobile Devices in Dotkernel 1.6\" article." } },
+                    { "@type": "Question", "name": "What are the terms of Dotkernel's special WURFL Cloud license?", "acceptedAnswer": { "@type": "Answer", "text": "The license is non-transferable, conditioned, limited to the version received, and restricted to use and distribution only in connection with the Dotkernel software framework. It does not allow making derivative works, even when source code is provided or the code is not obfuscated." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/templating-in-dotkernel3.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/templating-in-dotkernel3.jsonld.twig
index 0a6c952c..b886e249 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/templating-in-dotkernel3.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/templating-in-dotkernel3.jsonld.twig
@@ -41,10 +41,10 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Which templating engine does DotKernel3 use?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel3 moved to the popular Twig Templating Engine." } },
-                    { "@type": "Question", "name": "Why did DotKernel move away from the previous templating engine?", "acceptedAnswer": { "@type": "Answer", "text": "The previous templating engine, although solid and robust, was also 10 years old and used techniques that had become slightly outdated, and it was one of the pain points in the previous version of DotKernel." } },
-                    { "@type": "Question", "name": "What features does Twig bring to DotKernel3 templates?", "acceptedAnswer": { "@type": "Answer", "text": "Templates can now be written as HTML code with extra Twig tags, and Twig includes features such as layouts, loops, variables, and escaping, giving the familiarity of HTML with the overview and convenience of PHP." } },
-                    { "@type": "Question", "name": "Where can I read the official Twig templating documentation for DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "The official documentation is linked in the article at docs.dotkernel.com/Prerequisites/Templates." } }
+                    { "@type": "Question", "name": "Which templating engine does Dotkernel3 use?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel3 moved to the popular Twig Templating Engine." } },
+                    { "@type": "Question", "name": "Why did Dotkernel move away from the previous templating engine?", "acceptedAnswer": { "@type": "Answer", "text": "The previous templating engine, although solid and robust, was also 10 years old and used techniques that had become slightly outdated, and it was one of the pain points in the previous version of Dotkernel." } },
+                    { "@type": "Question", "name": "What features does Twig bring to Dotkernel3 templates?", "acceptedAnswer": { "@type": "Answer", "text": "Templates can now be written as HTML code with extra Twig tags, and Twig includes features such as layouts, loops, variables, and escaping, giving the familiarity of HTML with the overview and convenience of PHP." } },
+                    { "@type": "Question", "name": "Where can I read the official Twig templating documentation for Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "The official documentation is linked in the article at docs.dotkernel.com/Prerequisites/Templates." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/using-dotkernel-with-composer-dependencies.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/using-dotkernel-with-composer-dependencies.jsonld.twig
index c8d34275..71ae1cf0 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/using-dotkernel-with-composer-dependencies.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/using-dotkernel-with-composer-dependencies.jsonld.twig
@@ -41,12 +41,12 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Do I need to manually include or require Composer dependencies in DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "No. Composer automatically loads dependencies, so there is no need to include or require them yourself." } },
+                    { "@type": "Question", "name": "Do I need to manually include or require Composer dependencies in Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "No. Composer automatically loads dependencies, so there is no need to include or require them yourself." } },
                     { "@type": "Question", "name": "What example does the article use to demonstrate Composer dependencies?", "acceptedAnswer": { "@type": "Answer", "text": "The article renders a Barcode using Zend Framework 1 as the Non-Namespaced dependency (installed with composer require 'zendframework/zendframework1') and Zend Framework 2 as the Namespaced dependency (installed with composer require 'zendframework/zend-barcode')." } },
                     { "@type": "Question", "name": "When can these Composer dependencies be used in the application?", "acceptedAnswer": { "@type": "Answer", "text": "These dependencies can be used anywhere after the Dot_Kernel::initialize() function has been called." } },
                     { "@type": "Question", "name": "How are non-namespaced (Zend Framework 1) classes loaded compared to namespaced (Zend Framework 2) classes?", "acceptedAnswer": { "@type": "Answer", "text": "Non-namespaced ZF1 classes are loaded PSR-0 style, meaning the class name looks like VendorName_PackageName_ClassName (e.g. Zend_Barcode). Namespaced ZF2 classes are loaded PSR-4 style, meaning the class name looks like \\VendorName\\PackageName\\ClassName (e.g. Zend\\Barcode\\Barcode)." } },
                     { "@type": "Question", "name": "Can the same code work for both namespaced and non-namespaced barcode dependencies?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. If you add \"use Zend\\Barcode\\Barcode as Zend_Barcode;\" as the first line, the ZF1-style example will work for both, and you can then reference the module as Zend\\Barcode\\Barcode, Barcode, or Zend_Barcode." } },
-                    { "@type": "Question", "name": "What DotKernel and PHP versions does this article apply to?", "acceptedAnswer": { "@type": "Answer", "text": "This article works for any DotKernel 1.x version if your server is running PHP greater than 5.4.0." } }
+                    { "@type": "Question", "name": "What Dotkernel and PHP versions does this article apply to?", "acceptedAnswer": { "@type": "Answer", "text": "This article works for any Dotkernel 1.x version if your server is running PHP greater than 5.4.0." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/using-utf8-charset-in-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/using-utf8-charset-in-dotkernel.jsonld.twig
index 3dda6089..4a2b344b 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/using-utf8-charset-in-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/using-utf8-charset-in-dotkernel.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What needs to change to use UTF8 encoding in a DotKernel-based system?", "acceptedAnswer": { "@type": "Answer", "text": "Both the database structure and the application.ini file need changes: all tables and columns must have a proper UTF8 collation (utf8_general_ci or utf8_bin), and application.ini must load the utf8 charset." } },
+                    { "@type": "Question", "name": "What needs to change to use UTF8 encoding in a Dotkernel-based system?", "acceptedAnswer": { "@type": "Answer", "text": "Both the database structure and the application.ini file need changes: all tables and columns must have a proper UTF8 collation (utf8_general_ci or utf8_bin), and application.ini must load the utf8 charset." } },
                     { "@type": "Question", "name": "What line should I add to application.ini to enable UTF8?", "acceptedAnswer": { "@type": "Answer", "text": "Add the line database.params.charset = utf8 to your application.ini file." } },
                     { "@type": "Question", "name": "What is the difference between utf8_general_ci and utf8_bin collation?", "acceptedAnswer": { "@type": "Answer", "text": "utf8_bin compares strings by the binary value of each character, while utf8_general_ci compares strings using general language rules with case-insensitive comparisons. For example, A with umlaut equals A, O with umlaut equals O, and U with umlaut equals U evaluate as true under utf8_general_ci but not under utf8_bin." } },
                     { "@type": "Question", "name": "Does the collation choice affect PHP string functions too?", "acceptedAnswer": { "@type": "Answer", "text": "No. These collation differences only happen at the MySQL level, for instance in queries using the LIKE operator, and not at the PHP level, for instance in str_replace() calls." } }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-cloud-integration-in-dotkernel-1-6-0.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-cloud-integration-in-dotkernel-1-6-0.jsonld.twig
index 7f30e5d4..b4dfb6da 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-cloud-integration-in-dotkernel-1-6-0.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-cloud-integration-in-dotkernel-1-6-0.jsonld.twig
@@ -41,8 +41,8 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What is WURFL Cloud?", "acceptedAnswer": { "@type": "Answer", "text": "WURFL Cloud is a new way that WURFL (Wireless Universal Resource FiLe) delivers its device detection services. DotKernel integrated it as the default detection method for mobile devices starting with version 1.6.0." } },
-                    { "@type": "Question", "name": "How do I get a functional device detection setup with WURFL Cloud?", "acceptedAnswer": { "@type": "Answer", "text": "Register for a Wurfl Cloud account with Scientia Mobile, choose device_os and mobile_browser as your capabilities, then copy your API key into application.ini in DotKernel." } },
+                    { "@type": "Question", "name": "What is WURFL Cloud?", "acceptedAnswer": { "@type": "Answer", "text": "WURFL Cloud is a new way that WURFL (Wireless Universal Resource FiLe) delivers its device detection services. Dotkernel integrated it as the default detection method for mobile devices starting with version 1.6.0." } },
+                    { "@type": "Question", "name": "How do I get a functional device detection setup with WURFL Cloud?", "acceptedAnswer": { "@type": "Answer", "text": "Register for a Wurfl Cloud account with Scientia Mobile, choose device_os and mobile_browser as your capabilities, then copy your API key into application.ini in Dotkernel." } },
                     { "@type": "Question", "name": "What line do I add to application.ini for the API key?", "acceptedAnswer": { "@type": "Answer", "text": "Add a line such as resources.useragent.wurflcloud.api_key = 000000:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX, using your own API key." } },
                     { "@type": "Question", "name": "How can I test that mobile detection is working?", "acceptedAnswer": { "@type": "Answer", "text": "Change the user agent in your browser to a mobile device and access your project; you should be redirected to the mobile module." } }
                 ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-php-api-license-incompatible-with-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-php-api-license-incompatible-with-dotkernel.jsonld.twig
index 4fa77c43..1297b4e5 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-php-api-license-incompatible-with-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-php-api-license-incompatible-with-dotkernel.jsonld.twig
@@ -41,9 +41,9 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Why did the WURFL PHP API license become incompatible with DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "The WURFL PHP API used to be licensed under GNU/GPL, compatible with both Zend Framework's new BSD license and DotKernel's OSL 3.0 license. On June 6th, 2011, version 1.3.0 of the library changed its license to AGPL, turning it into a trial-only library for product evaluation, which is incompatible with keeping DotKernel free." } },
-                    { "@type": "Question", "name": "Which version introduced the license change, and when?", "acceptedAnswer": { "@type": "Answer", "text": "Version 1.3.0 of the WURFL PHP API, released June 6th, 2011, changed the license from GNU/GPL to AGPL. DotKernel had updated to this version in its 1.5.0 release candidate without noticing the license change." } },
-                    { "@type": "Question", "name": "What did DotKernel do in response to the license change?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel planned to remove WURFL PHP API version 1.3.0 from its codebase and reintegrate version 1.2.1, which was still GNU/GPL. It also intended to keep contributing to the free WURFL XML data, and considered forking the 1.2.1 library and renaming it to avoid trademark issues." } }
+                    { "@type": "Question", "name": "Why did the WURFL PHP API license become incompatible with Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "The WURFL PHP API used to be licensed under GNU/GPL, compatible with both Zend Framework's new BSD license and Dotkernel's OSL 3.0 license. On June 6th, 2011, version 1.3.0 of the library changed its license to AGPL, turning it into a trial-only library for product evaluation, which is incompatible with keeping Dotkernel free." } },
+                    { "@type": "Question", "name": "Which version introduced the license change, and when?", "acceptedAnswer": { "@type": "Answer", "text": "Version 1.3.0 of the WURFL PHP API, released June 6th, 2011, changed the license from GNU/GPL to AGPL. Dotkernel had updated to this version in its 1.5.0 release candidate without noticing the license change." } },
+                    { "@type": "Question", "name": "What did Dotkernel do in response to the license change?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel planned to remove WURFL PHP API version 1.3.0 from its codebase and reintegrate version 1.2.1, which was still GNU/GPL. It also intended to keep contributing to the free WURFL XML data, and considered forking the 1.2.1 library and renaming it to avoid trademark issues." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-zend-framework-integration-into-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-zend-framework-integration-into-dotkernel.jsonld.twig
index 48cccfa5..c91c58b5 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-zend-framework-integration-into-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/wurfl-zend-framework-integration-into-dotkernel.jsonld.twig
@@ -41,8 +41,8 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Which Zend Framework class is used to integrate WURFL into DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "WURFL is integrated using the Zend_Http_UserAgent class from Zend Framework 1.11.0rc1 (the beta release at the time of the post)." } },
-                    { "@type": "Question", "name": "What is the first step to integrate WURFL into DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "Download the WURFL PHP API and unzip it into a folder named wurfl-php-1.1." } },
+                    { "@type": "Question", "name": "Which Zend Framework class is used to integrate WURFL into Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "WURFL is integrated using the Zend_Http_UserAgent class from Zend Framework 1.11.0rc1 (the beta release at the time of the post)." } },
+                    { "@type": "Question", "name": "What is the first step to integrate WURFL into Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "Download the WURFL PHP API and unzip it into a folder named wurfl-php-1.1." } },
                     { "@type": "Question", "name": "Which folders need to be created and made writable?", "acceptedAnswer": { "@type": "Answer", "text": "Two folders must be created and made writable by the web server: cache/wurfl/FILE_CACHE_PROVIDER and cache/wurfl/FILE_PERSISTENCE_PROVIDER." } },
                     { "@type": "Question", "name": "What needs to be added to application.ini?", "acceptedAnswer": { "@type": "Answer", "text": "Three lines need to be added: resources.useragent.wurflapi.wurfl_api_version = 1.1, resources.useragent.wurflapi.wurfl_lib_dir pointing to APPLICATION_PATH /library/Wurfl/, and resources.useragent.wurflapi.wurfl_config_file pointing to APPLICATION_PATH /configs/wurfl.xml." } },
                     { "@type": "Question", "name": "How do you access WURFL configuration in code?", "acceptedAnswer": { "@type": "Answer", "text": "Instantiate a Zend_Http_UserAgent with the useragent config, then call getDevice() on it. getDevice() returns all the relevant information about the current user agent." } }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/zend-auth-and-zend-acl-integrated-in-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/zend-auth-and-zend-acl-integrated-in-dotkernel.jsonld.twig
index 9a26d2f1..0d9c1aea 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/zend-auth-and-zend-acl-integrated-in-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/zend-auth-and-zend-acl-integrated-in-dotkernel.jsonld.twig
@@ -41,9 +41,9 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "When were Zend_Auth and Zend_Acl integrated into DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "Zend_Auth and Zend_Acl were integrated starting with DotKernel version 1.5.0, as part of a refactor of the User and Admin models using the new Dot_Auth and Dot_Acl classes." } },
+                    { "@type": "Question", "name": "When were Zend_Auth and Zend_Acl integrated into Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "Zend_Auth and Zend_Acl were integrated starting with Dotkernel version 1.5.0, as part of a refactor of the User and Admin models using the new Dot_Auth and Dot_Acl classes." } },
                     { "@type": "Question", "name": "How does Dot_Auth authenticate a user?", "acceptedAnswer": { "@type": "Answer", "text": "Dot_Auth authenticates the user by checking the database using Zend_Auth_Adapter_DbTable, setting the table name, the identity column to username, and the credential column to password." } },
-                    { "@type": "Question", "name": "What roles exist for ACL in DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel defines 3 ACL roles (user types): guest, user, and admin. These roles and their permissions are configured in the configs/acl/role.xml file." } },
+                    { "@type": "Question", "name": "What roles exist for ACL in Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel defines 3 ACL roles (user types): guest, user, and admin. These roles and their permissions are configured in the configs/acl/role.xml file." } },
                     { "@type": "Question", "name": "Where do the ACL resources come from?", "acceptedAnswer": { "@type": "Answer", "text": "The resources for ACL are taken from configs/router.xml, specifically the controllers tag." } },
                     { "@type": "Question", "name": "What does the Dot_Acl class do?", "acceptedAnswer": { "@type": "Answer", "text": "Dot_Acl controls user access (Access Controller Layer), is used for setting and checking a user's permissions, and uses Zend_Acl to check whether a role has access to a resource. Dot_Auth calls the isAllowed method from Dot_Acl to authenticate the user." } }
                 ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/zend-console-implementation-in-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/zend-console-implementation-in-dotkernel.jsonld.twig
index 55cb2043..1715c049 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/zend-console-implementation-in-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/zend-console-implementation-in-dotkernel.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What is the purpose of the Console bootstrap in DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "Starting with version 1.5, DotKernel has a Console bootstrap to easily run PHP scripts from the command line, most commonly used to run cron jobs without using wget or going through Apache." } },
+                    { "@type": "Question", "name": "What is the purpose of the Console bootstrap in Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "Starting with version 1.5, Dotkernel has a Console bootstrap to easily run PHP scripts from the command line, most commonly used to run cron jobs without using wget or going through Apache." } },
                     { "@type": "Question", "name": "Where is the Console bootstrap located?", "acceptedAnswer": { "@type": "Answer", "text": "The bootstrap is found in Console/index.php, and it has one controller in Controller.php with two example actions." } },
                     { "@type": "Question", "name": "What command line arguments does the Console bootstrap support?", "acceptedAnswer": { "@type": "Answer", "text": "There are two arguments: -a, the name of the action to execute, and -e, the environment as defined in application.ini (development, staging, or production), which is optional and defaults to production." } },
                     { "@type": "Question", "name": "What happens to extra arguments passed to the script?", "acceptedAnswer": { "@type": "Answer", "text": "Any other arguments set when calling the script will be available in the controller in the registry's arguments array." } },
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/zend-framework-dropped-integration-of-wurfl-adapter.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/zend-framework-dropped-integration-of-wurfl-adapter.jsonld.twig
index 55784d3c..2bb15502 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/zend-framework-dropped-integration-of-wurfl-adapter.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/zend-framework-dropped-integration-of-wurfl-adapter.jsonld.twig
@@ -42,7 +42,7 @@
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
                     { "@type": "Question", "name": "Why did Zend Framework drop the WURFL adapter?", "acceptedAnswer": { "@type": "Answer", "text": "According to Matthew Weier O'Phinney, Zend Framework Project Leader, the WURFL adapter was dropped from Zend_Http_UserAgent in the upcoming 1.12.0 branch due to a change in licensing by the WURFL project: the free version became AGPL, which raised too many concerns for end users regarding how their products must be licensed to comply." } },
-                    { "@type": "Question", "name": "Does this change affect projects built with DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "No. DotKernel uses its own WURFL adapter, so the removal of the WURFL adapter from Zend_Http_UserAgent in ZF 1.12.0 will not affect projects built with DotKernel." } }
+                    { "@type": "Question", "name": "Does this change affect projects built with Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "No. Dotkernel uses its own WURFL adapter, so the removal of the WURFL adapter from Zend_Http_UserAgent in ZF 1.12.0 will not affect projects built with Dotkernel." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/zend-registry-usage-in-dotkernel.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/zend-registry-usage-in-dotkernel.jsonld.twig
index 2685508b..0284cd17 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/zend-registry-usage-in-dotkernel.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/zend-registry-usage-in-dotkernel.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What variables does Zend_Registry contain in DotKernel?", "acceptedAnswer": { "@type": "Answer", "text": "It contains startTime (the result of microtime() at the beginning of the request), configuration (loaded from configs/application.ini), router (loaded from configs/router.xml), database (the database adapter), settings (loaded from the database), requestModule/requestController/requestAction, request (additional request variables), seo (loaded from configs/dots/seo.xml), option (loaded from configs/dots/<moduleName>.xml), and session (the session object)." } },
+                    { "@type": "Question", "name": "What variables does Zend_Registry contain in Dotkernel?", "acceptedAnswer": { "@type": "Answer", "text": "It contains startTime (the result of microtime() at the beginning of the request), configuration (loaded from configs/application.ini), router (loaded from configs/router.xml), database (the database adapter), settings (loaded from the database), requestModule/requestController/requestAction, request (additional request variables), seo (loaded from configs/dots/seo.xml), option (loaded from configs/dots/<moduleName>.xml), and session (the session object)." } },
                     { "@type": "Question", "name": "How do you get an instance of the registry?", "acceptedAnswer": { "@type": "Answer", "text": "Use $registry = Zend_Registry::getInstance(); and then access variables such as $registry->startTime or $registry->requestAction." } },
                     { "@type": "Question", "name": "How do you retrieve just one variable from the registry?", "acceptedAnswer": { "@type": "Answer", "text": "If you only need one variable, you can get it directly using $action = Zend_Registry::get('requestAction');." } },
                     { "@type": "Question", "name": "What does the seo entry in the registry contain?", "acceptedAnswer": { "@type": "Answer", "text": "It contains seo information loaded from configs/dots/seo.xml, such as site name, default description, and keywords." } }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/zend-session-usage-in-dotkernel-refactor-of-dot-session-class.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/zend-session-usage-in-dotkernel-refactor-of-dot-session-class.jsonld.twig
index 85a84972..aa95dc74 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/zend-session-usage-in-dotkernel-refactor-of-dot-session-class.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/zend-session-usage-in-dotkernel-refactor-of-dot-session-class.jsonld.twig
@@ -41,9 +41,9 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What session bug was found in DotKernel 1.5.0?", "acceptedAnswer": { "@type": "Answer", "text": "In unknown circumstances, and only in IE8 and IE9, the session cookie was not saved on the client machine, forcing the user to log in over and over again. The only workaround found was to open a new tab with the same page." } },
+                    { "@type": "Question", "name": "What session bug was found in Dotkernel 1.5.0?", "acceptedAnswer": { "@type": "Answer", "text": "In unknown circumstances, and only in IE8 and IE9, the session cookie was not saved on the client machine, forcing the user to log in over and over again. The only workaround found was to open a new tab with the same page." } },
                     { "@type": "Question", "name": "What caused the session cookie to be generated multiple times?", "acceptedAnswer": { "@type": "Answer", "text": "Investigation of the Dot_Session class showed the session cookie was generated 3 times, because the code called both regenerateID() and rememberMe() methods of Zend_Session. According to the Zend Framework documentation, this is unnecessary: if you call rememberMe(), you should not also call regenerateId(), since rememberMe() already calls it internally." } },
-                    { "@type": "Question", "name": "What was the fix, and where was it released?", "acceptedAnswer": { "@type": "Answer", "text": "The regenerateID() call was removed, and two new application.ini settings were added: use_only_cookies, which must be ON at all times to avoid session fixation, and remember_me_seconds. These fixes were included in DotKernel version 1.5.1." } },
+                    { "@type": "Question", "name": "What was the fix, and where was it released?", "acceptedAnswer": { "@type": "Answer", "text": "The regenerateID() call was removed, and two new application.ini settings were added: use_only_cookies, which must be ON at all times to avoid session fixation, and remember_me_seconds. These fixes were included in Dotkernel version 1.5.1." } },
                     { "@type": "Question", "name": "What should I do if I still see this issue in IE8/IE9?", "acceptedAnswer": { "@type": "Answer", "text": "If you encounter the same issue in IE8 and IE9, the tip given is to deactivate the rememberMe() and regenerateId() method calls." } }
                 ]
             }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel/zend-studio-php-formatter-file-for-dotkernel-coding-standard.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel/zend-studio-php-formatter-file-for-dotkernel-coding-standard.jsonld.twig
index 6685d697..056df031 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel/zend-studio-php-formatter-file-for-dotkernel-coding-standard.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel/zend-studio-php-formatter-file-for-dotkernel-coding-standard.jsonld.twig
@@ -46,7 +46,7 @@
                         "name": "What is this file for?",
                         "acceptedAnswer": {
                             "@type": "Answer",
-                            "text": "It is an XML file, downloadable from the linked page, that can be imported into Zend Studio (version 9.x) to set up the PHP code formatter so it follows DotKernel's coding standard."
+                            "text": "It is an XML file, downloadable from the linked page, that can be imported into Zend Studio (version 9.x) to set up the PHP code formatter so it follows Dotkernel's coding standard."
                         }
                     },
                     {
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel3/development-report-december-11-2017.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel3/development-report-december-11-2017.jsonld.twig
index 594785ff..d4bcdc17 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel3/development-report-december-11-2017.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel3/development-report-december-11-2017.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What documentation updates does this report cover?", "acceptedAnswer": { "@type": "Answer", "text": "Release notes were added for DotKernel3 frontend and admin, a Webpack tutorial was added to the Prerequisites section, and the Api Endpoint Documentation Guidelines were updated with a slightly different layout and some corrections." } },
+                    { "@type": "Question", "name": "What documentation updates does this report cover?", "acceptedAnswer": { "@type": "Answer", "text": "Release notes were added for Dotkernel3 frontend and admin, a Webpack tutorial was added to the Prerequisites section, and the Api Endpoint Documentation Guidelines were updated with a slightly different layout and some corrections." } },
                     { "@type": "Question", "name": "Who was credited as a contributor in this report?", "acceptedAnswer": { "@type": "Answer", "text": "JapSeyz was thanked as a contributor." } }
                 ]
             }
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel3/dotkernel-admin-v4.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel3/dotkernel-admin-v4.jsonld.twig
index b99e1452..92cc8ea6 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel3/dotkernel-admin-v4.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel3/dotkernel-admin-v4.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "When was Dotkernel Admin V4 released, and what is it built on?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel Admin V4 was officially released on 19 July 2022. It's DotKernel's PSR-7 Admin, an application based on Mezzio, mainly for managing and displaying tabular data from one or more database components." } },
+                    { "@type": "Question", "name": "When was Dotkernel Admin V4 released, and what is it built on?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel Admin V4 was officially released on 19 July 2022. It's Dotkernel's PSR-7 Admin, an application based on Mezzio, mainly for managing and displaying tabular data from one or more database components." } },
                     { "@type": "Question", "name": "What are the demo credentials for trying out Dotkernel Admin V4?", "acceptedAnswer": { "@type": "Answer", "text": "Username admin and password dotadmin, on the demo at https://admin4.dotkernel.net/." } },
                     { "@type": "Question", "name": "What PHP version does Dotkernel Admin V4 support?", "acceptedAnswer": { "@type": "Answer", "text": "Full support for PHP 8.1, with a minimum requirement of PHP 7.4." } },
                     { "@type": "Question", "name": "How do you register a new module or middleware?", "acceptedAnswer": { "@type": "Answer", "text": "Register a module by adding its ConfigProvider.php in config.php. New middleware goes into pipeline.php, where you can also edit the order in which middleware runs." } },
diff --git a/src/Blog/templates/page/JSON-LD/dotkernel3/php-8-3-support-in-dotkernel-frontend.jsonld.twig b/src/Blog/templates/page/JSON-LD/dotkernel3/php-8-3-support-in-dotkernel-frontend.jsonld.twig
index 1497679d..93cca3a2 100644
--- a/src/Blog/templates/page/JSON-LD/dotkernel3/php-8-3-support-in-dotkernel-frontend.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/dotkernel3/php-8-3-support-in-dotkernel-frontend.jsonld.twig
@@ -60,7 +60,7 @@
                         "name": "What update adds PHP 8.3 support to Dotkernel Frontend?",
                         "acceptedAnswer": {
                             "@type": "Answer",
-                            "text": "The DotKernel team updated the Frontend application to version 4.2.0 so it can take advantage of PHP 8.3 support in the newest packages."
+                            "text": "The Dotkernel team updated the Frontend application to version 4.2.0 so it can take advantage of PHP 8.3 support in the newest packages."
                         }
                     },
                     {
diff --git a/src/Blog/templates/page/JSON-LD/how-to/creating-admin-accounts-in-dotkernel-api.jsonld.twig b/src/Blog/templates/page/JSON-LD/how-to/creating-admin-accounts-in-dotkernel-api.jsonld.twig
index d7176b3d..0183f1c5 100644
--- a/src/Blog/templates/page/JSON-LD/how-to/creating-admin-accounts-in-dotkernel-api.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/how-to/creating-admin-accounts-in-dotkernel-api.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What are the two ways to create an admin account in DotKernel API?", "acceptedAnswer": { "@type": "Answer", "text": "You can either call the protected API endpoint POST /admin with a JSON body, or run the terminal command php ./bin/cli.php admin:create." } },
+                    { "@type": "Question", "name": "What are the two ways to create an admin account in Dotkernel API?", "acceptedAnswer": { "@type": "Answer", "text": "You can either call the protected API endpoint POST /admin with a JSON body, or run the terminal command php ./bin/cli.php admin:create." } },
                     { "@type": "Question", "name": "Who can create an admin account via the API endpoint?", "acceptedAnswer": { "@type": "Answer", "text": "This action can be performed only by an authenticated admin/superuser, calling the protected POST /admin endpoint." } },
                     { "@type": "Question", "name": "What data does the POST /admin request body need?", "acceptedAnswer": { "@type": "Answer", "text": "identity, password, passwordConfirm, and roles (one or more valid admin role UUIDs, obtainable via the protected GET /admin/role endpoint). firstname and lastname are optional." } },
                     { "@type": "Question", "name": "What role does an admin get when created via the terminal command?", "acceptedAnswer": { "@type": "Answer", "text": "The terminal command doesn't allow specifying an admin role, so newly created accounts are given the role of admin." } },
diff --git a/src/Blog/templates/page/JSON-LD/how-to/database-migrations-and-how-to-use-them.jsonld.twig b/src/Blog/templates/page/JSON-LD/how-to/database-migrations-and-how-to-use-them.jsonld.twig
index 2313c421..784c7b01 100644
--- a/src/Blog/templates/page/JSON-LD/how-to/database-migrations-and-how-to-use-them.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/how-to/database-migrations-and-how-to-use-them.jsonld.twig
@@ -41,7 +41,7 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What is a database migration?", "acceptedAnswer": { "@type": "Answer", "text": "A database migration is a change to the database schema. The DotKernel stack integrates migrations (and seeders) via a package that adds the php dot command to the application." } },
+                    { "@type": "Question", "name": "What is a database migration?", "acceptedAnswer": { "@type": "Answer", "text": "A database migration is a change to the database schema. The Dotkernel stack integrates migrations (and seeders) via a package that adds the php dot command to the application." } },
                     { "@type": "Question", "name": "What are the benefits of using migrations and seeders?", "acceptedAnswer": { "@type": "Answer", "text": "They keep the database synchronised across the team with minimal effort, so column types and limits stay consistent instead of drifting (e.g. one dev using VARCHAR(50) and another VARCHAR(150)). Deployment scripts can also run migrations automatically in production, avoiding manual SSH access and risky manual database changes." } },
                     { "@type": "Question", "name": "How do I create a new migration?", "acceptedAnswer": { "@type": "Answer", "text": "Run php dot make:migration <name>, giving the migration a reasonable name so its action and the database's progression are easy to follow in the project tree." } },
                     { "@type": "Question", "name": "What's the difference between migrations and seeders?", "acceptedAnswer": { "@type": "Answer", "text": "Migrations manage the database layout/schema, while seeders add data to the database, such as adding a default admin profile on a fresh installation." } },
diff --git a/src/Blog/templates/page/JSON-LD/licensing/mit-versus-lgpl-in-practice-dotkernel-case.jsonld.twig b/src/Blog/templates/page/JSON-LD/licensing/mit-versus-lgpl-in-practice-dotkernel-case.jsonld.twig
index 31cc5356..f498b6f9 100644
--- a/src/Blog/templates/page/JSON-LD/licensing/mit-versus-lgpl-in-practice-dotkernel-case.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/licensing/mit-versus-lgpl-in-practice-dotkernel-case.jsonld.twig
@@ -41,11 +41,11 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "Why did DotKernel need a workaround for this package?", "acceptedAnswer": { "@type": "Answer", "text": "An analysis found that an upstream package, matomo/device-detector, was licensed under LGPL v3, which requires developers to share their derivative code publicly. Since DotKernel's own projects use the MIT license, and the more restrictive license would have to apply to the whole application, this conflicted with contractual obligations to keep client code business and enterprise friendly." } },
-                    { "@type": "Question", "name": "Where was the LGPL v3 package being used?", "acceptedAnswer": { "@type": "Answer", "text": "The matomo/device-detector package was used in DotKernel's dot-user-agent-sniffer package to identify the user agent and use the results in internal reports." } },
-                    { "@type": "Question", "name": "What solution did DotKernel adopt?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel decided to discard the use of third-party packages licensed under LGPL v3. All of DotKernel's own packages are licensed under MIT, which has no restrictions on the source code other than keeping the license and copyright notice in a file within each package. Other non-restrictive licenses considered acceptable include Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0 and OSL-3.0." } },
+                    { "@type": "Question", "name": "Why did Dotkernel need a workaround for this package?", "acceptedAnswer": { "@type": "Answer", "text": "An analysis found that an upstream package, matomo/device-detector, was licensed under LGPL v3, which requires developers to share their derivative code publicly. Since Dotkernel's own projects use the MIT license, and the more restrictive license would have to apply to the whole application, this conflicted with contractual obligations to keep client code business and enterprise friendly." } },
+                    { "@type": "Question", "name": "Where was the LGPL v3 package being used?", "acceptedAnswer": { "@type": "Answer", "text": "The matomo/device-detector package was used in Dotkernel's dot-user-agent-sniffer package to identify the user agent and use the results in internal reports." } },
+                    { "@type": "Question", "name": "What solution did Dotkernel adopt?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel decided to discard the use of third-party packages licensed under LGPL v3. All of Dotkernel's own packages are licensed under MIT, which has no restrictions on the source code other than keeping the license and copyright notice in a file within each package. Other non-restrictive licenses considered acceptable include Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0 and OSL-3.0." } },
                     { "@type": "Question", "name": "What changed in dot-user-agent-sniffer as a result?", "acceptedAnswer": { "@type": "Answer", "text": "Starting with version 3.4.0, the dotkernel/dot-user-agent-sniffer package must follow the LGPL v3 license. The admin application will not use the features from matomo/device-detector, but will contain instructions for developers who intend to add the package themselves." } },
-                    { "@type": "Question", "name": "Is it still risky to use an older version of dot-user-agent-sniffer?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Any application using dotkernel/dot-user-agent-sniffer with a version lower than 3.4.0 is still a legal liability. DotKernel will not include dot-user-agent-sniffer in any of its applications by default for now, while it looks into bringing back the device detector functionality under a less restrictive license in the future." } }
+                    { "@type": "Question", "name": "Is it still risky to use an older version of dot-user-agent-sniffer?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Any application using dotkernel/dot-user-agent-sniffer with a version lower than 3.4.0 is still a legal liability. Dotkernel will not include dot-user-agent-sniffer in any of its applications by default for now, while it looks into bringing back the device detector functionality under a less restrictive license in the future." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/JSON-LD/php-development/mezzio-app-development-in-wsl2.jsonld.twig b/src/Blog/templates/page/JSON-LD/php-development/mezzio-app-development-in-wsl2.jsonld.twig
index bd0789d6..30baf108 100644
--- a/src/Blog/templates/page/JSON-LD/php-development/mezzio-app-development-in-wsl2.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/php-development/mezzio-app-development-in-wsl2.jsonld.twig
@@ -41,10 +41,10 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What does this guide help you accomplish?", "acceptedAnswer": { "@type": "Answer", "text": "It walks you through installing a Mezzio application (DotKernel API) using WSL2 and running it on Ubuntu 20.04 LTS." } },
+                    { "@type": "Question", "name": "What does this guide help you accomplish?", "acceptedAnswer": { "@type": "Answer", "text": "It walks you through installing a Mezzio application (Dotkernel API) using WSL2 and running it on Ubuntu 20.04 LTS." } },
                     { "@type": "Question", "name": "What do you need before installing Ubuntu inside WSL2?", "acceptedAnswer": { "@type": "Answer", "text": "You first need WSL2 installed on your machine, which you can set up by following the linked WSL2 installation guide, before installing Ubuntu inside it." } },
                     { "@type": "Question", "name": "How do you set up a virtual host for the project?", "acceptedAnswer": { "@type": "Answer", "text": "After Ubuntu is installed inside WSL2, you create a virtual host for your project by following the linked virtual-host creation guide." } },
-                    { "@type": "Question", "name": "How do you install DotKernel API once the virtual host is ready?", "acceptedAnswer": { "@type": "Answer", "text": "Using your terminal, move into the virtual host directory you created (for example, cd /home/your-username/projects/your-virtualhost), then install DotKernel API by following its guide. Afterward, make sure the data and log directories are writable by changing their permissions, as described in the linked permission-fix guide." } },
+                    { "@type": "Question", "name": "How do you install Dotkernel API once the virtual host is ready?", "acceptedAnswer": { "@type": "Answer", "text": "Using your terminal, move into the virtual host directory you created (for example, cd /home/your-username/projects/your-virtualhost), then install Dotkernel API by following its guide. Afterward, make sure the data and log directories are writable by changing their permissions, as described in the linked permission-fix guide." } },
                     { "@type": "Question", "name": "How do you get PHPStorm to work with the WSL2 project files?", "acceptedAnswer": { "@type": "Answer", "text": "You set up PHPStorm to work with WSL2 files by following the linked JetBrains article on using a WSL development environment in the product." } },
                     { "@type": "Question", "name": "Does this guide also work for AlmaLinux instead of Ubuntu?", "acceptedAnswer": { "@type": "Answer", "text": "There is a guide for AlmaLinux 8 as well, but it is not fully functional because of a well-known issue regarding running systemd inside WSL2." } }
                 ]
diff --git a/src/Blog/templates/page/JSON-LD/php-development/using-aptana-to-connect-to-dotkernel-tracker-mantis.jsonld.twig b/src/Blog/templates/page/JSON-LD/php-development/using-aptana-to-connect-to-dotkernel-tracker-mantis.jsonld.twig
index edc5e3ac..4ce502b1 100644
--- a/src/Blog/templates/page/JSON-LD/php-development/using-aptana-to-connect-to-dotkernel-tracker-mantis.jsonld.twig
+++ b/src/Blog/templates/page/JSON-LD/php-development/using-aptana-to-connect-to-dotkernel-tracker-mantis.jsonld.twig
@@ -41,10 +41,10 @@
                 "@type": "FAQPage",
                 "@id": "{{ absolute_url(path('page::blog-resource', {categorySlug: article.category.slug, slug: article.slug})) }}#faq",
                 "mainEntity": [
-                    { "@type": "Question", "name": "What is DotKernel Tracker?", "acceptedAnswer": { "@type": "Answer", "text": "DotKernel Tracker is a Mantis-based, web-based bugtracking system used by the DotKernel application framework, where bugs are reported, new features are announced, and other general tickets are added." } },
-                    { "@type": "Question", "name": "How is Aptana integrated with DotKernel Tracker?", "acceptedAnswer": { "@type": "Answer", "text": "Aptana, the web development IDE used for DotKernel development, is integrated with DotKernel Tracker via the Mylyn plugin's Mantis connector, so tickets can be managed directly from within the IDE." } },
+                    { "@type": "Question", "name": "What is Dotkernel Tracker?", "acceptedAnswer": { "@type": "Answer", "text": "Dotkernel Tracker is a Mantis-based, web-based bugtracking system used by the Dotkernel application framework, where bugs are reported, new features are announced, and other general tickets are added." } },
+                    { "@type": "Question", "name": "How is Aptana integrated with Dotkernel Tracker?", "acceptedAnswer": { "@type": "Answer", "text": "Aptana, the web development IDE used for Dotkernel development, is integrated with Dotkernel Tracker via the Mylyn plugin's Mantis connector, so tickets can be managed directly from within the IDE." } },
                     { "@type": "Question", "name": "What plugin do you need to install in Aptana before connecting to Mantis?", "acceptedAnswer": { "@type": "Answer", "text": "You need to install the Mylyn plugin via Aptana -> Help -> Software Update, adding the update site http://download.eclipse.org/tools/mylyn/update/e3.4/, and then install the Mylyn Connector for Mantis." } },
-                    { "@type": "Question", "name": "What information is needed to add DotKernel Tracker as a task repository?", "acceptedAnswer": { "@type": "Answer", "text": "You need the server URL (http://www.dotkernel.net/api/soap/mantisconnect.php), a label of your choosing (e.g. \"DotKernel Tracker\"), and your User ID, which is your username from dotkernel.net (you can sign up if you don't already have an account)." } }
+                    { "@type": "Question", "name": "What information is needed to add Dotkernel Tracker as a task repository?", "acceptedAnswer": { "@type": "Answer", "text": "You need the server URL (http://www.dotkernel.net/api/soap/mantisconnect.php), a label of your choosing (e.g. \"Dotkernel Tracker\"), and your User ID, which is your username from dotkernel.net (you can sign up if you don't already have an account)." } }
                 ]
             }
         ]
diff --git a/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-1-0-0-released.html.twig b/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-1-0-0-released.html.twig
index ec0b889f..11acc3aa 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-1-0-0-released.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-1-0-0-released.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel-api/dotkernel-api-1-0-0-released.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel API 1.0.0 Released{% endblock %}
+{% block title %}Dotkernel API 1.0.0 Released{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -23,9 +23,9 @@
 <blockquote><p class="mb-3">Dotkernel API has come a long way since this post was created. <a href="https://www.dotkernel.com/headless-platform/version-7-adds-postgresql-native-uuid-and-php-8-5/" data-type="link" data-id="https://www.dotkernel.com/headless-platform/version-7-adds-postgresql-native-uuid-and-php-8-5/">Check out the newest version of Dotkernel API</a> to stay up to date with the latest functional and security features.</p>
 </blockquote>
 
-<h2><a href="https://github.com/dotkernel/api/releases/tag/v1.0.0">DotKernel API 1.0.0</a> was just released!</h2>
+<h2><a href="https://github.com/dotkernel/api/releases/tag/v1.0.0">Dotkernel API 1.0.0</a> was just released!</h2>
 <p class="mb-3"> </p>
-<h3>What is DotKernel API?</h3>
+<h3>What is Dotkernel API?</h3>
 <p class="mb-3">It is a <a href="https://github.com/zendframework/zend-expressive">Zend Expressive 3</a> application aiming to help developers quickly and efficiently develop an API.</p>
 <p class="mb-3"> </p>
 <h3>How does it work?</h3>
@@ -45,7 +45,7 @@
 </ul>
 <p class="mb-3"> </p>
 <h3>What does it offer?</h3>
-<p class="mb-3">Out-of-the-box, DotKernel API provides the following features:</p>
+<p class="mb-3">Out-of-the-box, Dotkernel API provides the following features:</p>
 <ul>
 <li>Secure authentication via OAuth2</li>
 <li>Two user roles: admin and member</li>
@@ -58,19 +58,19 @@
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What is DotKernel API? <span class="chev">+</span></summary>
+        <summary>What is Dotkernel API? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">It is a Zend Expressive 3 application aiming to help developers quickly and efficiently develop an API.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What key libraries does DotKernel API 1.0.0 use? <span class="chev">+</span></summary>
+        <summary>What key libraries does Dotkernel API 1.0.0 use? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Among others, it's built on the ezimuel/zend-expressive-api skeleton, and uses dotkernel/dot-annotated-services for dependency injection, dotkernel/dot-console for console applications, dotkernel/dot-errorhandler for error logging, dotkernel/dot-mail for SMTP email, zend-expressive-authentication-oauth2 for OAuth2 authentication, zend-expressive-authorization-rbac for role-based permissions, and swagger-api/swagger-ui for OpenAPI 3 documentation.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What features does DotKernel API 1.0.0 offer out of the box? <span class="chev">+</span></summary>
+        <summary>What features does Dotkernel API 1.0.0 offer out of the box? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Secure authentication via OAuth2, two user roles (admin and member), where admins can manage any user account and members can manage only their own, plus OpenAPI 3 documentation with an interactive interface developers can use to integrate the API.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-client-side-authorization.html.twig b/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-client-side-authorization.html.twig
index 23beec06..401769c1 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-client-side-authorization.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-client-side-authorization.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel-api/dotkernel-api-client-side-authorization.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel API Client Side  Authorization{% endblock %}
+{% block title %}Dotkernel API Client Side  Authorization{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-<strong>This article covers the basic authorization of a Client application which use a backend built using </strong><a href="https://github.com/dotkernel/api" target="_blank" rel="noopener noreferrer"><strong>DotKernel API</strong></a>
+<strong>This article covers the basic authorization of a Client application which use a backend built using </strong><a href="https://github.com/dotkernel/api" target="_blank" rel="noopener noreferrer"><strong>Dotkernel API</strong></a>
 
 <h2>Authorization Request</h2>
 Client application users send a <strong>POST</strong> request to the backend containing the following JSON object:
diff --git a/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-server-side-authorization.html.twig b/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-server-side-authorization.html.twig
index b6adfadd..64c6ddd5 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-server-side-authorization.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-server-side-authorization.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel-api/dotkernel-api-server-side-authorization.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel API Server Side Authorization{% endblock %}
+{% block title %}Dotkernel API Server Side Authorization{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-<strong>This article covers the basic authorization of a Server Side application  built using <a href="https://github.com/dotkernel/api" target="_blank" rel="noopener noreferrer">DotKernel API</a></strong>
+<strong>This article covers the basic authorization of a Server Side application  built using <a href="https://github.com/dotkernel/api" target="_blank" rel="noopener noreferrer">Dotkernel API</a></strong>
 <h2>Protecting an endpoint</h2>
 <ul>
      <li><strong>no-auth:</strong> the resource can be accessed without the need of authentication/authorization</li>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-versus-laminas-api-tools.html.twig b/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-versus-laminas-api-tools.html.twig
index 2c59b7a6..8c3a257c 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-versus-laminas-api-tools.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-versus-laminas-api-tools.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel-api/dotkernel-api-versus-laminas-api-tools.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel API versus Laminas API Tools{% endblock %}
+{% block title %}Dotkernel API versus Laminas API Tools{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-<p class="mb-3">Below we have created an analysis of the basic features available in <strong>Laminas Api Tools </strong>and <strong>DotKernel API</strong>. It's intended to highlight the differences between the two and also to showcase why DotKernel API is a good alternative for Laminas API Tools, especially considering the latter's archived status.</p>
+<p class="mb-3">Below we have created an analysis of the basic features available in <strong>Laminas Api Tools </strong>and <strong>Dotkernel API</strong>. It's intended to highlight the differences between the two and also to showcase why Dotkernel API is a good alternative for Laminas API Tools, especially considering the latter's archived status.</p>
 
 <blockquote><p class="mb-3">The table below refers to <a href="https://github.com/dotkernel/api/tree/7.0" data-type="link" data-id="https://github.com/dotkernel/api/tree/7.0" target="_blank" rel="noreferrer noopener">Dotkernel API V7</a></p>
 </blockquote>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel-api/how-to-implement-mailchimp-in-dotkernel-api.html.twig b/src/Blog/templates/page/blog-resource/dotkernel-api/how-to-implement-mailchimp-in-dotkernel-api.html.twig
index 26dd02dc..a11ea650 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel-api/how-to-implement-mailchimp-in-dotkernel-api.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel-api/how-to-implement-mailchimp-in-dotkernel-api.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel-api/how-to-implement-mailchimp-in-dotkernel-api.jsonld.twig') }} {% endblock %}
 
-{% block title %}How to implement MailChimp in DotKernel API{% endblock %}
+{% block title %}How to implement MailChimp in Dotkernel API{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-<h2>This article will walk you through the process of implementing MailChimp into your instance of <a href="https://github.com/dotkernel/api">DotKernel API</a> using <a href="https://github.com/drewm/mailchimp-api">drewm/mailchimp-api</a></h2>
+<h2>This article will walk you through the process of implementing MailChimp into your instance of <a href="https://github.com/dotkernel/api">Dotkernel API</a> using <a href="https://github.com/drewm/mailchimp-api">drewm/mailchimp-api</a></h2>
 &nbsp;
 
 <strong>Step 1</strong>: Add the library to your application using the following command:
diff --git a/src/Blog/templates/page/blog-resource/dotkernel-api/openapi-implementation-in-dotkernel-api.html.twig b/src/Blog/templates/page/blog-resource/dotkernel-api/openapi-implementation-in-dotkernel-api.html.twig
index c817a4e1..7bfdfb5a 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel-api/openapi-implementation-in-dotkernel-api.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel-api/openapi-implementation-in-dotkernel-api.html.twig
@@ -61,11 +61,11 @@
 <li><strong>Helps troubleshooting</strong>: It defines the correct functionality that helps developers and maintainers find and fix bugs more effectively.</li>
 </ul>
 
-<h2>OpenAPI in DotKernel API</h2>
+<h2>OpenAPI in Dotkernel API</h2>
 
-<p class="mb-3"><strong>DotKernel API </strong>has full support for OpenAPI, from describing the endpoints and generating the documentation, to rendering and testing the endpoints.</p>
+<p class="mb-3"><strong>Dotkernel API </strong>has full support for OpenAPI, from describing the endpoints and generating the documentation, to rendering and testing the endpoints.</p>
 
-<p class="mb-3">Each <strong>module </strong>(Admin, App, User) in DotKernel API contains a file named <strong>OpenAPI.php</strong>. In this file you must document <strong>all of the endpoints from RoutesDelegator.php</strong>. The entries in OpenAPI.php have several descriptive items, the most important being method, request and response. These are used to generate a documentation file from the command line. The static documentation file is rendered using Swagger UI or Redoc in a user-friendly way. You can read more about this <a href="https://docs.dotkernel.org/api-documentation/v5/openapi/introduction/" data-type="link" data-id="https://docs.dotkernel.org/api-documentation/v5/openapi/introduction/" target="_blank" rel="noreferrer noopener">starting here</a> and its subsequent pages.</p>
+<p class="mb-3">Each <strong>module </strong>(Admin, App, User) in Dotkernel API contains a file named <strong>OpenAPI.php</strong>. In this file you must document <strong>all of the endpoints from RoutesDelegator.php</strong>. The entries in OpenAPI.php have several descriptive items, the most important being method, request and response. These are used to generate a documentation file from the command line. The static documentation file is rendered using Swagger UI or Redoc in a user-friendly way. You can read more about this <a href="https://docs.dotkernel.org/api-documentation/v5/openapi/introduction/" data-type="link" data-id="https://docs.dotkernel.org/api-documentation/v5/openapi/introduction/" target="_blank" rel="noreferrer noopener">starting here</a> and its subsequent pages.</p>
 
 <h3>Describing OpenAPI components</h3>
 
@@ -84,7 +84,7 @@
 
 <p class="mb-3">Read more details about the above <a href="https://docs.dotkernel.org/api-documentation/v5/openapi/initialized-components/" data-type="link" data-id="https://docs.dotkernel.org/api-documentation/v5/openapi/initialized-components/" target="_blank" rel="noreferrer noopener">here</a>.</p>
 
-<p class="mb-3">Once you have your basic components defined, you can begin work on the endpoints. The endpoints already made available in DotKernel API are documented, so you must do the same for the new endpoints you create in your project. This is done by defining these items:</p>
+<p class="mb-3">Once you have your basic components defined, you can begin work on the endpoints. The endpoints already made available in Dotkernel API are documented, so you must do the same for the new endpoints you create in your project. This is done by defining these items:</p>
 
 <ul><li>the <strong>request </strong>object (Get, Post, Patch, Put, Delete)</li>
 
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/adding-a-cors-implementation-to-zend-expressive.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/adding-a-cors-implementation-to-zend-expressive.html.twig
index 212f50af..c2f70467 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/adding-a-cors-implementation-to-zend-expressive.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/adding-a-cors-implementation-to-zend-expressive.html.twig
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-                    <p>This article is a guide on how to add a CORS implementation on an existing DotKernel3 project.</p>
+                    <p>This article is a guide on how to add a CORS implementation on an existing Dotkernel3 project.</p>
 
                     <h2>The issue</h2>
                     <p>If you're facing this message:</p>
@@ -41,7 +41,7 @@
                     <p>Run the following command in your project:</p>
                     <pre><code>composer require tuupola/cors-middleware</code></pre>
                     <p>At the time writing this article the current package version is: 0.9.4.</p>
-                    <p>Follow the next steps to get your Zend Expressive or DotKernel3 project <strong>CORS friendly</strong>.</p>
+                    <p>Follow the next steps to get your Zend Expressive or Dotkernel3 project <strong>CORS friendly</strong>.</p>
 
                     <h3>Create the CORS config file</h3>
                     <p>Create a <strong>cors.global.php</strong> file in the config/autoload directory.</p>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/adding-composer-support-in-your-dotkernel-project.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/adding-composer-support-in-your-dotkernel-project.html.twig
index e2d830b3..0f5f5a41 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/adding-composer-support-in-your-dotkernel-project.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/adding-composer-support-in-your-dotkernel-project.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/adding-composer-support-in-your-dotkernel-project.jsonld.twig') }} {% endblock %}
 
-{% block title %}Adding Composer support in your DotKernel project{% endblock %}
+{% block title %}Adding Composer support in your Dotkernel project{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -22,13 +22,13 @@
                 <div class="entry">
 Composer is an application-level package manager. Composer auto-loads the dependencies on demand and can also auto-load custom classes .
 
-This article will cover the needed steps to add composer support to your DotKernel project or even "composify" it.
+This article will cover the needed steps to add composer support to your Dotkernel project or even "composify" it.
 
-Assuming that you know how to use composer (if not you should consider reading <a href="https://www.codementor.io/php/tutorial/composer-install-php-dependency-manager" target="_blank" rel="noopener noreferrer">this article</a>) we wil move on to your DotKernel project "composification".
+Assuming that you know how to use composer (if not you should consider reading <a href="https://www.codementor.io/php/tutorial/composer-install-php-dependency-manager" target="_blank" rel="noopener noreferrer">this article</a>) we wil move on to your Dotkernel project "composification".
 
 &nbsp;
 <h2>First things first</h2>
-The DotKernel project must have a <strong>composer.json</strong> file so that composer can work.
+The Dotkernel project must have a <strong>composer.json</strong> file so that composer can work.
 
 Our <strong>composer.json</strong> file should look like this:
 <pre>>{
@@ -54,7 +54,7 @@ The dependencies provided in the <strong>require</strong> section are also loade
 
 &nbsp;
 
-In order to have these components instaled you must run the following command in your DotKernel root path
+In order to have these components instaled you must run the following command in your Dotkernel root path
 <pre>>composer update</pre>
 If the <em>vendor </em>folder is present composer will check for updates, and update the packages as needed.
 
@@ -63,7 +63,7 @@ If the <em>vendor</em> folder does not exist composer will create a vendor folde
 Composer will create an autoload file, which will be use to load our dependencies/packages.
 
 &nbsp;
-<h2>Adding Composer Support to DotKernel</h2>
+<h2>Adding Composer Support to Dotkernel</h2>
 The autoload file created by composer will be used to load our packages.
 <pre>>$composerAutoLoaderPath = <a href="http://php.net/manual/en/function.realpath.php" target="_blank" rel="noopener noreferrer">realpath</a>(APPLICATION_PATH.'/vendor/autoload.php');
 require_once($composerAutoLoaderPath);</pre>
@@ -90,9 +90,9 @@ Later on, the packages can be used like this:
 
 $myDependency = new MyDependency($neededArguments);
 $myDependency->doSomething();</pre>
-Learn more about how to use dependencies in DotKernel 1.x by reading <a href="http://www.dotkernel.com/dotkernel/using-dotkernel-…ser-dependencies/" target="_blank" rel="noopener noreferrer">this article</a>.
+Learn more about how to use dependencies in Dotkernel 1.x by reading <a href="http://www.dotkernel.com/dotkernel/using-dotkernel-…ser-dependencies/" target="_blank" rel="noopener noreferrer">this article</a>.
 
-This article works for any <strong>DotKernel 1.x</strong> version if your server is running <strong>PHP &gt;5.4.0.</strong>
+This article works for any <strong>Dotkernel 1.x</strong> version if your server is running <strong>PHP &gt;5.4.0.</strong>
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
@@ -104,7 +104,7 @@ This article works for any <strong>DotKernel 1.x</strong> version if your server
         </div>
     </details>
     <details class="acc">
-        <summary>What must a DotKernel project have before Composer can be used? <span class="chev">+</span></summary>
+        <summary>What must a Dotkernel project have before Composer can be used? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">A composer.json file, for example requiring zendframework/zendframework1 at 1.12.* and mobiledetect/mobiledetectlib at 2.8.*, plus PHP &gt;=5.4.0 listed under require-dev.</p>
         </div>
@@ -122,9 +122,9 @@ This article works for any <strong>DotKernel 1.x</strong> version if your server
         </div>
     </details>
     <details class="acc">
-        <summary>Which DotKernel versions does this apply to? <span class="chev">+</span></summary>
+        <summary>Which Dotkernel versions does this apply to? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">The article states it works for any DotKernel 1.x version, as long as the server is running PHP greater than 5.4.0.</p>
+            <p class="mb-0">The article states it works for any Dotkernel 1.x version, as long as the server is running PHP greater than 5.4.0.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/adding-windows-10-os-and-browser-detection-in-dotkernel-projects.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/adding-windows-10-os-and-browser-detection-in-dotkernel-projects.html.twig
index 34374f69..c62a2258 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/adding-windows-10-os-and-browser-detection-in-dotkernel-projects.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/adding-windows-10-os-and-browser-detection-in-dotkernel-projects.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/adding-windows-10-os-and-browser-detection-in-dotkernel-projects.jsonld.twig') }} {% endblock %}
 
-{% block title %}Adding Windows 10 OS and Browser detection in DotKernel projects{% endblock %}
+{% block title %}Adding Windows 10 OS and Browser detection in Dotkernel projects{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -35,7 +35,7 @@ In this article we will have the icon upgrade guide.
     <li>Extract the archive in a folder, let's name it <strong>icons_patch
 </strong></li>
     <li>We recommend creating a backup of your project before you continue</li>
-    <li>Now copy all the files in the <strong>icons_patch</strong> folder in your DotKernel</li>
+    <li>Now copy all the files in the <strong>icons_patch</strong> folder in your Dotkernel</li>
     <li>You will be prompted to replace 2 files, simply replace the files and agree to merge the folders content (files will be added, not replaced this time)</li>
     <li>You need to clear the cache for changes to take effect, the os and browser xml's are cached. For more information read <a href="http://www.dotkernel.com/dotkernel/dotkernel-reserved-variable-names-for-caching/" target="_blank" rel="noopener noreferrer">this article</a> (look for <strong>Browser &amp; OS</strong>)</li>
     <li>You can now delete the <strong>icons_patch</strong> folder or use it to patch another project</li>
@@ -53,7 +53,7 @@ A /images/os/windows_metro.png</pre>
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What DotKernel version is required before applying this patch? <span class="chev">+</span></summary>
+        <summary>What Dotkernel version is required before applying this patch? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Your project must be running version 1.5.0 or newer.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/caching-in-dotkernel-using-zend-framework.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/caching-in-dotkernel-using-zend-framework.html.twig
index fece5c85..ab97d361 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/caching-in-dotkernel-using-zend-framework.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/caching-in-dotkernel-using-zend-framework.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/caching-in-dotkernel-using-zend-framework.jsonld.twig') }} {% endblock %}
 
-{% block title %}Caching in DotKernel using Zend Framework{% endblock %}
+{% block title %}Caching in Dotkernel using Zend Framework{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -25,7 +25,7 @@ It's very expensive to load configurations and settings from XML files, on every
 First because of latency of accessing files from hard drive, second because of the XML
 file parsing burden.
 
-Because of that , we implemented in upcoming 1.8 version of DotKernel a cache layer where to store<strong> router, acl_role, menu, options(including seo_xml), browser_xml, os_xml, test</strong> between requests. More information about the variables which DotKernel cache by default follow this link: <a title="DotKernel Reserved Variable Names for Caching" href="http://www.dotkernel.com/dotkernel/dotkernel-reserved-variable-names-for-caching" target="_blank" rel="noopener noreferrer">DotKernel Reserved Variable Names for Caching</a>
+Because of that , we implemented in upcoming 1.8 version of Dotkernel a cache layer where to store<strong> router, acl_role, menu, options(including seo_xml), browser_xml, os_xml, test</strong> between requests. More information about the variables which Dotkernel cache by default follow this link: <a title="Dotkernel Reserved Variable Names for Caching" href="http://www.dotkernel.com/dotkernel/dotkernel-reserved-variable-names-for-caching" target="_blank" rel="noopener noreferrer">Dotkernel Reserved Variable Names for Caching</a>
 
 <!--more-->
 
@@ -33,7 +33,7 @@ We are implementing 2 different cache factories to choose from: <strong>apc</str
 <h2>1. Configuring the cache</h2>
 The configuration can be set from /configs/application.ini, you can choose if you use the caching system, how long your cache stays valid, the cache namespace, and the storage provider (<strong>File</strong> or <strong>APC</strong>). I would disable the cache in development mode if I were you.
 
-For more info about the configuration and help configuring the cache see: <a title="DotKernel - Configuring the Cache in DotKernel" href="http://www.dotkernel.com/dotkernel/configuring-the-cache-in-dotkernel/" target="_blank" rel="noopener noreferrer">Configuring the Cache in DotKernel</a>.
+For more info about the configuration and help configuring the cache see: <a title="Dotkernel - Configuring the Cache in Dotkernel" href="http://www.dotkernel.com/dotkernel/configuring-the-cache-in-dotkernel/" target="_blank" rel="noopener noreferrer">Configuring the Cache in Dotkernel</a>.
 <h2>2. Using the Cache</h2>
 The cache is automatically loaded in the initialization and stored in the Registry.
 
@@ -67,7 +67,7 @@ else
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What data does DotKernel's cache layer store? <span class="chev">+</span></summary>
+        <summary>What data does Dotkernel's cache layer store? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Router, acl_role, menu, options (including seo_xml), browser_xml, os_xml, and test data between requests.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/configuring-the-cache-in-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/configuring-the-cache-in-dotkernel.html.twig
index 9773a8d6..fead19ab 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/configuring-the-cache-in-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/configuring-the-cache-in-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/configuring-the-cache-in-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}Configuring the Cache in DotKernel{% endblock %}
+{% block title %}Configuring the Cache in Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,9 +20,9 @@
 
             <article class="article">
                 <div class="entry">
-This article contains the DotKernel cache layer configuration guide.
+This article contains the Dotkernel cache layer configuration guide.
 
-The DotKernel Caching Layer is based on Zend Framework Cache, more configuration options can be found at the following links:
+The Dotkernel Caching Layer is based on Zend Framework Cache, more configuration options can be found at the following links:
 <ul>
     <li><a title="Zend Framework Cache Frontends" href="http://framework.zend.com/manual/1.12/en/zend.cache.frontends.html" target="_blank" rel="noopener noreferrer">Zend Framework Cache Frontends</a></li>
     <li><a title="Zend Framework Cache Backends" href="http://framework.zend.com/manual/1.12/en/zend.cache.backends.html" target="_blank" rel="noopener noreferrer">Zend Framework Cache Backends</a></li>
@@ -53,13 +53,13 @@ For more settings and caching alternatives see the Zend Framework Cache Links at
 The setting pattern and sample are below:
 <pre>>cache.BACKEND_NAME.SETTING = "VALUE"
 ; example:
-cache.file.file_name_prefix = "DotKernel"</pre>
+cache.file.file_name_prefix = "Dotkernel"</pre>
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What is DotKernel's caching layer based on? <span class="chev">+</span></summary>
+        <summary>What is Dotkernel's caching layer based on? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">It's based on Zend Framework Cache, configured through settings in application.ini, with more configuration options available at the Zend Framework Cache Frontends and Backends documentation links given in the article.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dependency-injection-made-easy-in-laminas-mezzio-applications.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dependency-injection-made-easy-in-laminas-mezzio-applications.html.twig
index 2f4c280c..89b5daee 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dependency-injection-made-easy-in-laminas-mezzio-applications.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dependency-injection-made-easy-in-laminas-mezzio-applications.html.twig
@@ -25,11 +25,11 @@
 
 <p class="mb-3">So, first thing first, the problem.<br><br>You have a <strong>Laminas / Mezzio</strong> application with a bunch of services that you need to use in a, let's say, controller class or in any other class, and you are tired of building, updating, and maintaining factories every time you add a new dependency to your class.</p>
 
-<p class="mb-3"><strong>DotKernel </strong>has you covered. We built a <strong>tool to autowire those dependencies in your class</strong>. There is no need for factories for every class you make. Just use one “factory” class that you tie to your custom class in the config, and that's it.</p>
+<p class="mb-3"><strong>Dotkernel </strong>has you covered. We built a <strong>tool to autowire those dependencies in your class</strong>. There is no need for factories for every class you make. Just use one “factory” class that you tie to your custom class in the config, and that's it.</p>
 
 <p class="mb-3">Sounds easy, right? Let’s finish with the chat and speak some code, first showing the problem and then the solution.</p>
 
-<blockquote><p class="mb-3">The examples below are from the <strong><a href="https://github.com/dotkernel/api" data-type="link" data-id="https://github.com/dotkernel/api" target="_blank" rel="noreferrer noopener">DotKernel API framework</a></strong>, but the pattern applies to all <strong>laminas </strong>and <strong>mezzio </strong>applications and to all PSR-11 applications.</p>
+<blockquote><p class="mb-3">The examples below are from the <strong><a href="https://github.com/dotkernel/api" data-type="link" data-id="https://github.com/dotkernel/api" target="_blank" rel="noreferrer noopener">Dotkernel API framework</a></strong>, but the pattern applies to all <strong>laminas </strong>and <strong>mezzio </strong>applications and to all PSR-11 applications.</p>
 </blockquote>
 
 <pre>class UserHandler implements RequestHandlerInterface
@@ -89,7 +89,7 @@
 
 <p class="mb-3">Now consider that we need to build the factory for this and update it when we add a new dependency, and so on. Also to build the logic in the factory to handle any dependencies missing from the container. Painful right?</p>
 
-<p class="mb-3">Now let's use <strong>DotKernel's</strong> <a href="https://github.com/dotkernel/dot-dependency-injection" target="_blank" rel="noreferrer noopener">dot-dependency-injection</a> package to inject the required dependency into your class.</p>
+<p class="mb-3">Now let's use <strong>Dotkernel's</strong> <a href="https://github.com/dotkernel/dot-dependency-injection" target="_blank" rel="noreferrer noopener">dot-dependency-injection</a> package to inject the required dependency into your class.</p>
 
 <p class="mb-3">After you install the package, your class needs to <code>use Dot\DependencyInjection\Attribute\Inject</code> , then you need to add the <code>#[Inject(...)]</code> attribute to the constructor definition to specify which dependencies should be injected.</p>
 
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/detecting-mobile-devices-in-dotkernel-1-6-0.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/detecting-mobile-devices-in-dotkernel-1-6-0.html.twig
index cfaade69..bdafdf76 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/detecting-mobile-devices-in-dotkernel-1-6-0.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/detecting-mobile-devices-in-dotkernel-1-6-0.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/detecting-mobile-devices-in-dotkernel-1-6-0.jsonld.twig') }} {% endblock %}
 
-{% block title %}Detecting Mobile Devices in DotKernel 1.6.0{% endblock %}
+{% block title %}Detecting Mobile Devices in Dotkernel 1.6.0{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,9 +20,9 @@
 
             <article class="article">
                 <div class="entry">
-The new DotKernel version 1.6.0 is comming with some changes how we are detecting mobile devices, this changes are because of the new Wurfl Cloud integration.
+The new Dotkernel version 1.6.0 is comming with some changes how we are detecting mobile devices, this changes are because of the new Wurfl Cloud integration.
 
-This version of DotKernel is not comming anymore with a working built in method for mobile detection, so first we have to configure it.
+This version of Dotkernel is not comming anymore with a working built in method for mobile detection, so first we have to configure it.
 
 <!--more-->
 <ul>
@@ -50,11 +50,11 @@ resources.useragent.wurflcloud.lib_dir = APPLICATION_PATH "/library/WurflCloud/"
 <strong>cache_lifetime</strong> - time in seconds to keep the results in cache (default: 3600)
 <strong>cache_namespace</strong> - the prefix used for cache keys (default: WURFLCLOUD)
 <strong>api_key</strong> - API Key from WURFL Cloud account (change this with your key)
-<strong>lib_dir</strong> - the wurfl cloud library location in DotKernel (don't change this, just if you want to move the library)
+<strong>lib_dir</strong> - the wurfl cloud library location in Dotkernel (don't change this, just if you want to move the library)
 
 Because of these changes we removed the old Dot_UserAgent_Wurfl class and added the new one Dot_UserAgent_WurflCloud wich is using the Wurfl Cloud API adapter.
 
-<h2>Example of Dot_UserAgent usage in DotKernel:</h2>
+<h2>Example of Dot_UserAgent usage in Dotkernel:</h2>
 
 Get Wurfl configuration
 <pre>>$wurflConf = $registry->configuration->resources->useragent->wurflcloud;</pre>
@@ -97,7 +97,7 @@ If detected device is an mobile device we will save device info in database and
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Why did mobile detection change in DotKernel 1.6.0? <span class="chev">+</span></summary>
+        <summary>Why did mobile detection change in Dotkernel 1.6.0? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Because of the new Wurfl Cloud integration. This version no longer ships with a working built-in method for mobile detection, so it must be configured first.</p>
         </div>
@@ -111,7 +111,7 @@ If detected device is an mobile device we will save device info in database and
     <details class="acc">
         <summary>Why choose the device_os and mobile_browser capabilities specifically? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">With these two capabilities, DotKernel's built-in methods can also derive extra capabilities such as isMobile, isSmartPhone, isIphone, isAndroid, isBlackberry, isSymbian, and isWindowsMobile. Choosing other capabilities from scientiamobile results in wrong detection of these extra capabilities.</p>
+            <p class="mb-0">With these two capabilities, Dotkernel's built-in methods can also derive extra capabilities such as isMobile, isSmartPhone, isIphone, isAndroid, isBlackberry, isSymbian, and isWindowsMobile. Choosing other capabilities from scientiamobile results in wrong detection of these extra capabilities.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/disable-wurfl-redirect-for-mobile-browsers.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/disable-wurfl-redirect-for-mobile-browsers.html.twig
index 045590d7..d00d96ba 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/disable-wurfl-redirect-for-mobile-browsers.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/disable-wurfl-redirect-for-mobile-browsers.html.twig
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-DotKernel has an example mobile site at <a href="http://v1.dotkernel.net/mobile" target="_blank" rel="noopener noreferrer">http://v1.dotkernel.net/mobile</a> that uses <a href="http://jquerymobile.com/">jQuery Mobile</a>.
+Dotkernel has an example mobile site at <a href="http://v1.dotkernel.net/mobile" target="_blank" rel="noopener noreferrer">http://v1.dotkernel.net/mobile</a> that uses <a href="http://jquerymobile.com/">jQuery Mobile</a>.
 
 Wurfl is also used to detect mobile browsers (as discussed in a <a href="http://www.dotkernel.com/dotkernel/wurfl-zend-framework-integration-into-dotkernel/">previous blog post</a>) and automatically redirect them to the mobile site the first time they view the homepage. Sometimes, this behavior isn't desired (for example when you don't have a mobile site, or you don't plan on using Wurfl at all)
 
@@ -35,7 +35,7 @@ if($config->resources->useragent->wurflapi->redirect && 'mobile' == Dot_Kernel::
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>How do you disable the automatic mobile redirect in DotKernel? <span class="chev">+</span></summary>
+        <summary>How do you disable the automatic mobile redirect in Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Starting with revision 408, set resources.useragent.wurflapi.redirect = false in application.ini. Per the article, this is also the default state of the redirect option.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/disambiguation-dotkernel-1-and-dotkernel-3.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/disambiguation-dotkernel-1-and-dotkernel-3.html.twig
index 0ba3e618..79a39ca3 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/disambiguation-dotkernel-1-and-dotkernel-3.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/disambiguation-dotkernel-1-and-dotkernel-3.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/disambiguation-dotkernel-1-and-dotkernel-3.jsonld.twig') }} {% endblock %}
 
-{% block title %}Disambiguation: DotKernel 1 and DotKernel 3{% endblock %}
+{% block title %}Disambiguation: Dotkernel 1 and Dotkernel 3{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,15 +20,15 @@
 
             <article class="article">
                 <div class="entry">
-<h2>What is DotKernel?</h2>
-The name <strong>DotKernel</strong> symbiotically  combines the string  <strong>Dot, </strong>as a
+<h2>What is Dotkernel?</h2>
+The name <strong>Dotkernel</strong> symbiotically  combines the string  <strong>Dot, </strong>as a
 representation of the Internet, and <strong>Kernel</strong>, the quintessence of any IT application.
 
 In other words <strong>Dotkernel</strong> wishes to be, with modesty, the central part of
 the Internet development and hence ensuring increased development
 productivity and run-time performance.
-<h2>What is DotKernel 1?</h2>
-DotKernel 1 is an <strong><em>PHP</em> <em>Application Framework</em></strong>, built on top of Zend Framework 1 (ZF1).
+<h2>What is Dotkernel 1?</h2>
+Dotkernel 1 is an <strong><em>PHP</em> <em>Application Framework</em></strong>, built on top of Zend Framework 1 (ZF1).
 
 It has the first public release  on July 2010.
 
@@ -36,31 +36,31 @@ It is tight coupled with <strong>Zend Framework 1</strong> , and add a set of cu
 external features (such as Router, Template Engine, etc.).
 
 It is composed of <strong>Zend Framework 1</strong> and a set of custom or external features (such as Router, Template Engine, etc.).
-DotKernel 1 architecture is based on <strong>MVC</strong>.
+Dotkernel 1 architecture is based on <strong>MVC</strong>.
 
 Latest version is <strong>1.8 Long Term Support</strong>.
 Will no be released a new version anymore, only bugfixes.
-<h2>What is DotKernel 3?</h2>
+<h2>What is Dotkernel 3?</h2>
 A <strong>collection</strong> of PSR-7 Middleware applications built on top of <a href="https://docs.zendframework.com/zend-expressive/" target="_blank" rel="noopener noreferrer"><strong>Zend Expressive</strong></a> microframework.
 
 It is composed of a set of custom and extended <a href="https://framework.zend.com/" target="_blank" rel="noopener noreferrer"><strong>Zend Framework 3</strong></a> components.
 
-DotKernel 3 architecture is based on <strong>Middleware</strong>.
+Dotkernel 3 architecture is based on <strong>Middleware</strong>.
 
-DotKernel implements the following PSR's: PSR-1, PSR-2, PSR-4, PSR-7, PSR-11.
+Dotkernel implements the following PSR's: PSR-1, PSR-2, PSR-4, PSR-7, PSR-11.
 
 Currently there are 2 applications: Frontend, Admin and a 3rd one is under development: API
-<h2>DotKernel = DotKernel 1 or DotKernel 3?</h2>
-In posts older than 2017 <strong>DotKernel 1</strong> was referred as <strong>DotKernel </strong>because it was the only DotKernel version.
+<h2>Dotkernel = Dotkernel 1 or Dotkernel 3?</h2>
+In posts older than 2017 <strong>Dotkernel 1</strong> was referred as <strong>Dotkernel </strong>because it was the only Dotkernel version.
 
-Since the release of <strong>DotKernel 3, </strong>is reffered to as <strong>DotKernel 3 </strong>or <strong>DotKernel</strong>.
+Since the release of <strong>Dotkernel 3, </strong>is reffered to as <strong>Dotkernel 3 </strong>or <strong>Dotkernel</strong>.
 
-All future references to DotKernel 1 will be explicitly made.
-<h3>As of DotKernel 3 release:</h3>
-DotKernel 1 = Dot Kernel 1
+All future references to Dotkernel 1 will be explicitly made.
+<h3>As of Dotkernel 3 release:</h3>
+Dotkernel 1 = Dot Kernel 1
 
-DotKernel 3 = DotKernel 3
-<h4><strong>DotKernel = DotKernel 3</strong></h4>
+Dotkernel 3 = Dotkernel 3
+<h4><strong>Dotkernel = Dotkernel 3</strong></h4>
 &nbsp;
 
 &nbsp;
@@ -70,33 +70,33 @@ DotKernel 3 = DotKernel 3
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What does the name "DotKernel" mean? <span class="chev">+</span></summary>
+        <summary>What does the name "Dotkernel" mean? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">It combines "Dot", as a representation of the Internet, with "Kernel", the quintessence of any IT application, reflecting the aim of being a central part of Internet development.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What is DotKernel 1? <span class="chev">+</span></summary>
+        <summary>What is Dotkernel 1? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">A PHP Application Framework built on top of Zend Framework 1, first publicly released in July 2010, with an architecture based on MVC. Its latest version is 1.8 Long Term Support, which per the article will not be followed by a new version, only bugfixes.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What is DotKernel 3? <span class="chev">+</span></summary>
+        <summary>What is Dotkernel 3? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">A collection of PSR-7 Middleware applications built on top of the Zend Expressive microframework, composed of a set of custom and extended Zend Framework 3 components, with an architecture based on Middleware. It implements PSR-1, PSR-2, PSR-4, PSR-7, and PSR-11.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>How many applications make up DotKernel 3? <span class="chev">+</span></summary>
+        <summary>How many applications make up Dotkernel 3? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">At the time of the article, there were two available applications, Frontend and Admin, with a third one, API, under development.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>When someone writes just "DotKernel", which version is meant? <span class="chev">+</span></summary>
+        <summary>When someone writes just "Dotkernel", which version is meant? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">In posts older than 2017, "DotKernel" referred to DotKernel 1, since it was the only version. Since the release of DotKernel 3, "DotKernel" refers to DotKernel 3, and all future references to DotKernel 1 are made explicitly.</p>
+            <p class="mb-0">In posts older than 2017, "Dotkernel" referred to Dotkernel 1, since it was the only version. Since the release of Dotkernel 3, "Dotkernel" refers to Dotkernel 3, and all future references to Dotkernel 1 are made explicitly.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/doctrine-cache-using-symfony-cache.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/doctrine-cache-using-symfony-cache.html.twig
index 442a23d0..411d138c 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/doctrine-cache-using-symfony-cache.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/doctrine-cache-using-symfony-cache.html.twig
@@ -33,7 +33,7 @@
 <figure></figure>
 <p class="mb-3"></p>
                                                     <img width="710" height="351" src="{{ asset('uploads/article/' ~ article.id ~ '/sdasdadsa.drawio.png') }}" alt="" srcset="/uploads/2024/02/sdasdadsa.drawio.png 710w, /uploads/2024/02/sdasdadsa.drawio-300x148.png 300w, /uploads/2024/02/sdasdadsa.drawio-71x35.png 71w, /uploads/2024/02/sdasdadsa.drawio-162x80.png 162w, /uploads/2024/02/sdasdadsa.drawio-394x195.png 394w" sizes="(max-width: 710px) 100vw, 710px">
-        <p class="mb-3">In this article our focus will be on enabling the <a href="https://packagist.org/packages/dotkernel/dot-cache" target="_blank" rel="noopener">dot-cache</a> component and effectively implementing caching in <a href="https://github.com/dotkernel/admin/" target="_blank" rel="noopener">DotKernel Admin</a>.</p>
+        <p class="mb-3">In this article our focus will be on enabling the <a href="https://packagist.org/packages/dotkernel/dot-cache" target="_blank" rel="noopener">dot-cache</a> component and effectively implementing caching in <a href="https://github.com/dotkernel/admin/" target="_blank" rel="noopener">Dotkernel Admin</a>.</p>
             <h2>Installation</h2>
         <p class="mb-3">Run the following command in your project directory:</p><pre>composer require dotkernel/dot-cache</pre><p class="mb-3">After installing, add the <code>DotCacheConfigProvider::class</code> class to your configuration aggregate (config/config.php).</p>
 <p class="mb-3">Before we continue with the configuration process we need to know a few things about how and where the data is stored.</p>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotboost-technologies-products-and-services-north-american-relaunch.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotboost-technologies-products-and-services-north-american-relaunch.html.twig
index c6f9ade0..8077c4c7 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotboost-technologies-products-and-services-north-american-relaunch.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotboost-technologies-products-and-services-north-american-relaunch.html.twig
@@ -24,7 +24,7 @@
 
 Dotboost is pleased to announce our North American Relaunch. This new phase comes as a result of dedicated research and analysis on how to best serve clients in Canada and the US.
 
-At the heart of our relaunch is the source release for our exclusive inhouse developed DotKernel framework. We have also added business IT integration and increased the clarity to our existing consulting services.
+At the heart of our relaunch is the source release for our exclusive inhouse developed Dotkernel framework. We have also added business IT integration and increased the clarity to our existing consulting services.
 <!--more-->
 
 We're not your average IT organization; we view our customers as strategic partners. This paradigm allows us to take a comprehensive approach towards creating solutions and gain the competitive advantage.
@@ -37,7 +37,7 @@ Founded in 2005, the Dotboost process can incorporate anywhere into your project
     <details class="acc" open>
         <summary>What is at the heart of Dotboost's North American relaunch? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">The source release of Dotboost's exclusive, in-house developed DotKernel framework, along with added business IT integration and increased clarity around existing consulting services.</p>
+            <p class="mb-0">The source release of Dotboost's exclusive, in-house developed Dotkernel framework, along with added business IT integration and increased clarity around existing consulting services.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-2-0-release.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-2-0-release.html.twig
index 4934289d..630e7d96 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-2-0-release.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-2-0-release.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-1-2-0-release.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel 1.2.0 release{% endblock %}
+{% block title %}Dotkernel 1.2.0 release{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-Finally we reached DotKernel 1.2.0 milestone.
+Finally we reached Dotkernel 1.2.0 milestone.
 
 Since the previous released 1.1.2, some changes have been made.
 <!--more-->
@@ -28,16 +28,16 @@ Since the previous released 1.1.2, some changes have been made.
     <li>On database, we changed the names and structure of tables to respect database naming convention. <a href="../dotkernel/dotkernel-database-naming-conventions-for-mysql/"><em>http://www.dotkernel.com/dotkernel/dotkernel-database-naming-conventions-for-mysql/</em></a></li>
 </ul>
 <ul>
-    <li>A new word came into our DotKernel discussions: <strong><em>dots.</em></strong> We use this term when talking about a submodule and all its component files. For example, <em>“user”</em> is a submodule of <em>frontend</em> module. Note that one dots can be part of multiple modules. (For example, <em>“user”</em> dots belong to <em>frontend</em> and <em>admin</em> module). For each dots, the configurations values have been added to xml files which are stored in <em>configs/dots</em> folder. In the preview versions, this values where hard-coded in the php files.</li>
+    <li>A new word came into our Dotkernel discussions: <strong><em>dots.</em></strong> We use this term when talking about a submodule and all its component files. For example, <em>“user”</em> is a submodule of <em>frontend</em> module. Note that one dots can be part of multiple modules. (For example, <em>“user”</em> dots belong to <em>frontend</em> and <em>admin</em> module). For each dots, the configurations values have been added to xml files which are stored in <em>configs/dots</em> folder. In the preview versions, this values where hard-coded in the php files.</li>
 </ul>
 <ul>
     <li>Another change made in <em>configs </em>folder is <em>resource.xml</em>, which contains the configuration values for the controllers of each module.</li>
 </ul>
-To be easier to start an application from DotKernel, in admin module, there are now the following dots:  admin, user and system.
+To be easier to start an application from Dotkernel, in admin module, there are now the following dots:  admin, user and system.
 
 New library classes have been implemented: Dot_Geoip and Dot_Seo, and some of the existing ones have been updated: Dot_Curl and Dot_Session (each module has his own session).
 
-In DotKernel, all SQL queries are written as prepared statements.  We strongly encourage this  practice: <em><a href="../php-development/protection-against-sql-injection-using-pdo-and-zend-framework/">http://www.dotkernel.com/php-development/protection-against-sql-injection-using-pdo-and-zend-framework/</a></em>
+In Dotkernel, all SQL queries are written as prepared statements.  We strongly encourage this  practice: <em><a href="../php-development/protection-against-sql-injection-using-pdo-and-zend-framework/">http://www.dotkernel.com/php-development/protection-against-sql-injection-using-pdo-and-zend-framework/</a></em>
 
 For more details, see  <a title=http://www.dotkernel.com/changelog/1-2-0/" href="http://www.dotkernel.com/changelog/1-2-0/">ChangeLog 1.2.0</a>
 
@@ -48,7 +48,7 @@ For more details, see  <a title=http://www.dotkernel.com/changelog/1-2-0/" href
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What is a "dots" in DotKernel, a term introduced in this release? <span class="chev">+</span></summary>
+        <summary>What is a "dots" in Dotkernel, a term introduced in this release? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">A term for a submodule and all its component files. For example, "user" is a dots of the frontend module, and one dots can belong to multiple modules, such as "user" belonging to both frontend and admin.</p>
         </div>
@@ -62,7 +62,7 @@ For more details, see  <a title=http://www.dotkernel.com/changelog/1-2-0/" href
     <details class="acc">
         <summary>What dots does the admin module include by default? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">admin, user, and system, to make it easier to start an application from DotKernel.</p>
+            <p class="mb-0">admin, user, and system, to make it easier to start an application from Dotkernel.</p>
         </div>
     </details>
     <details class="acc">
@@ -72,7 +72,7 @@ For more details, see  <a title=http://www.dotkernel.com/changelog/1-2-0/" href
         </div>
     </details>
     <details class="acc">
-        <summary>How are SQL queries written in DotKernel? <span class="chev">+</span></summary>
+        <summary>How are SQL queries written in Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">All SQL queries are written as prepared statements, a practice the article strongly encourages.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-2-2-release.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-2-2-release.html.twig
index 84e48c69..809ab085 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-2-2-release.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-2-2-release.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-1-2-2-release.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel 1.2.2 release{% endblock %}
+{% block title %}Dotkernel 1.2.2 release{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-Yesterday, we released <strong>DotKernel 1.2.2</strong>. It contains some bug fixes:
+Yesterday, we released <strong>Dotkernel 1.2.2</strong>. It contains some bug fixes:
 <ul>
     <li><span style="text-decoration: line-through;"><a href="http://www.dotkernel.net/view.php?id=31">31</a></span> – captcha errors try catch</li>
     <li><span style="text-decoration: line-through;"><a href="http://www.dotkernel.net/view.php?id=32">32</a></span> – pagination issue</li>
@@ -31,17 +31,17 @@ Yesterday, we released <strong>DotKernel 1.2.2</strong>. It contains some bug fi
 <!--more-->
 For more details see <a href="../changelog/1-2-2/">ChangeLog 1.2.2</a>. To get only the changed files from 1.2.1 to 1.2.2, download the <a href="../download/?did=17">upgrade</a> file
 
-<strong>Note*</strong>: because of the Bug 35, all php files have changed. To see what else has changed, check the <a href="http://www.dotkernel.net/">DotKernel Tracker</a> or the <a href="http://websvn.dotkernel.net/listing.php?repname=DotKernel+ver.+1">DotKernel WebSVN</a> .
+<strong>Note*</strong>: because of the Bug 35, all php files have changed. To see what else has changed, check the <a href="http://www.dotkernel.net/">Dotkernel Tracker</a> or the <a href="http://websvn.dotkernel.net/listing.php?repname=Dotkernel+ver.+1">Dotkernel WebSVN</a> .
 
-<em>P.S.</em> On July 22, 2010 we released <em>DotKernel 1.2.1.</em> You can check the <a href="../changelog/1-2-1/">ChangeLog 1.2.1</a> or download <a href="../download/?did=14">the upgrade 1.2.1</a> zip file.
+<em>P.S.</em> On July 22, 2010 we released <em>Dotkernel 1.2.1.</em> You can check the <a href="../changelog/1-2-1/">ChangeLog 1.2.1</a> or download <a href="../download/?did=14">the upgrade 1.2.1</a> zip file.
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What does the DotKernel 1.2.2 release include? <span class="chev">+</span></summary>
+        <summary>What does the Dotkernel 1.2.2 release include? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel 1.2.2 is a bug-fix release that closes five issues: captcha error handling (try/catch), a pagination issue, a wrong admin link, notices and a fatal error found by an Acunetix scan, and an update to the copyright line in files.</p>
+            <p class="mb-0">Dotkernel 1.2.2 is a bug-fix release that closes five issues: captcha error handling (try/catch), a pagination issue, a wrong admin link, notices and a fatal error found by an Acunetix scan, and an update to the copyright line in files.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-3-0-release.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-3-0-release.html.twig
index ffb029ad..72014e5b 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-3-0-release.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-3-0-release.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-1-3-0-release.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel 1.3.0 release{% endblock %}
+{% block title %}Dotkernel 1.3.0 release{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-<a href="../download/?did=23">DotKernel 1.3.0</a> is released at last. It contains important changes and new features.
+<a href="../download/?did=23">Dotkernel 1.3.0</a> is released at last. It contains important changes and new features.
 
 - <span style="text-decoration: line-through;"><a title="[closed] Skin switcher in admin" href="http://www.dotkernel.net/view.php?id=64">64</a></span>: <strong>[Feature]</strong> Skin switcher in admin - closed.
 
@@ -39,7 +39,7 @@ To protect a link that is accessible by members only, add this line in the contr
 - <span style="text-decoration: line-through;"><a title="[closed] Scan results Oct 1, 2010 on 1.3.0 RC" href="http://www.dotkernel.net/view.php?id=63">63</a></span>: <strong>[Bugs]</strong> Scan results Oct 1, 2010 on 1.3.0 RC - closed.
 - <span style="text-decoration: line-through;"><a title="[closed] reorganization of XMl files" href="http://www.dotkernel.net/view.php?id=69">69</a></span>: <strong>[Bugs]</strong> reorganization of XMl files - closed.
 
-Some xml files from configs folder have been changed to encompass the current needs of DotKernel. <em>resource.xml</em> has been deleted and its content split between <em>route.xml</em> and <em>dots.xml</em>. Check the manual to find more about <a href="../docs/router-xml/">route.xml</a> and <a href="../docs/dots-xml/">dots.xml</a>
+Some xml files from configs folder have been changed to encompass the current needs of Dotkernel. <em>resource.xml</em> has been deleted and its content split between <em>route.xml</em> and <em>dots.xml</em>. Check the manual to find more about <a href="../docs/router-xml/">route.xml</a> and <a href="../docs/dots-xml/">dots.xml</a>
 
 - <span style="text-decoration: line-through;"><a title="[closed] Security Issue // test controller " href="http://www.dotkernel.net/view.php?id=67">67</a></span>: <strong>[Bugs]</strong> Security Issue / test controller - closed.
 - <span style="text-decoration: line-through;"><a title="[closed] The canonical URL isn't escaped" href="http://www.dotkernel.net/view.php?id=68">68</a></span>: <strong>[Bugs]</strong> The canonical URL isn't escaped - closed.
@@ -56,13 +56,13 @@ Some xml files from configs folder have been changed to encompass the current ne
 
 For more details see <a href="../changelog/1-3-0/">ChangeLog 1.3.0</a>.
 
-<strong>Note*</strong>: because of the bug <span style="text-decoration: line-through;"><a title="[closed] reorganization of XMl files" href="http://www.dotkernel.net/view.php?id=69">69</a></span>, this release is not compatible with the previous versions. To see what else has changed, check <a href="http://www.dotkernel.net/">DotKernel Tracker</a> or <a href="http://websvn.dotkernel.net/listing.php?repname=DotKernel">DotKernel WebSVN</a>.
+<strong>Note*</strong>: because of the bug <span style="text-decoration: line-through;"><a title="[closed] reorganization of XMl files" href="http://www.dotkernel.net/view.php?id=69">69</a></span>, this release is not compatible with the previous versions. To see what else has changed, check <a href="http://www.dotkernel.net/">Dotkernel Tracker</a> or <a href="http://websvn.dotkernel.net/listing.php?repname=Dotkernel">Dotkernel WebSVN</a>.
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What is new in the admin interface in DotKernel 1.3.0? <span class="chev">+</span></summary>
+        <summary>What is new in the admin interface in Dotkernel 1.3.0? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">1.3.0 adds a skin switcher for the admin, with several ready-made skins (blue, brown, gray, green) that can be set via the settings.admin.skin configuration value.</p>
         </div>
@@ -80,7 +80,7 @@ For more details see <a href="../changelog/1-3-0/">ChangeLog 1.3.0</a>.
         </div>
     </details>
     <details class="acc">
-        <summary>Is DotKernel 1.3.0 backward compatible with earlier versions? <span class="chev">+</span></summary>
+        <summary>Is Dotkernel 1.3.0 backward compatible with earlier versions? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">No. Because of the XML file reorganization (bug 69), 1.3.0 is not compatible with previous versions.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-3-2-release.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-3-2-release.html.twig
index 41bb5d9e..2fd491fc 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-3-2-release.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-3-2-release.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-1-3-2-release.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel 1.3.2 release{% endblock %}
+{% block title %}Dotkernel 1.3.2 release{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-Before the winter holiday we came with a new release: <a href="http://www.dotkernel.com/download/?did=27">DotKernel 1.3.2</a>
+Before the winter holiday we came with a new release: <a href="http://www.dotkernel.com/download/?did=27">Dotkernel 1.3.2</a>
 It contains many bug fixes, some refactoring and a few minor features.
 
 <!--more-->Bugs fixes:
@@ -42,14 +42,14 @@ Minor features:
 Refactoring:
 <ul>
     <li style="text-decoration: line-through;"><a title="[closed] Zend_Paginator" href="http://www.dotkernel.net/view.php?id=110">0000110</a>: <strong>[REFACTOR]</strong> Zend_Paginator</li>
-    <li style="text-decoration: line-through;"><a title="[closed] Add a dojo dijit theme to DotKernel" href="http://www.dotkernel.net/view.php?id=107">0000107</a>: <strong>[REFACTOR]</strong> Add a dojo dijit theme to DotKernel</li>
+    <li style="text-decoration: line-through;"><a title="[closed] Add a dojo dijit theme to Dotkernel" href="http://www.dotkernel.net/view.php?id=107">0000107</a>: <strong>[REFACTOR]</strong> Add a dojo dijit theme to Dotkernel</li>
 </ul>
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What kind of release is DotKernel 1.3.2? <span class="chev">+</span></summary>
+        <summary>What kind of release is Dotkernel 1.3.2? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">It's mainly a maintenance release, containing many bug fixes, some refactoring, and a few minor features.</p>
         </div>
@@ -63,7 +63,7 @@ Refactoring:
     <details class="acc">
         <summary>What minor features and refactoring were included? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Minor features include a refactor of validIP in Dot_Kernel and showing the WURFL date and API version in admin. Refactoring covered Zend_Paginator and added a dojo dijit theme to DotKernel.</p>
+            <p class="mb-0">Minor features include a refactor of validIP in Dot_Kernel and showing the WURFL date and API version in admin. Refactoring covered Zend_Paginator and added a dojo dijit theme to Dotkernel.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-5-0-released.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-5-0-released.html.twig
index b314c9aa..7cf353c5 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-5-0-released.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-5-0-released.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-1-5-0-released.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel 1.5.0 Released{% endblock %}
+{% block title %}Dotkernel 1.5.0 Released{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,13 +20,13 @@
 
             <article class="article">
                 <div class="entry">
-After a longer wait than usual, DotKernel 1.5.0 was just released. Due to the large amount of changes and the long time spent in development, we chose to skip 1.4 and go straight to 1.5.0.
+After a longer wait than usual, Dotkernel 1.5.0 was just released. Due to the large amount of changes and the long time spent in development, we chose to skip 1.4 and go straight to 1.5.0.
 
-Here are a few of the many changes to DotKernel in the latest release:
+Here are a few of the many changes to Dotkernel in the latest release:
 <h2><!--more--></h2>
 <h2>Highlights of 1.5.0</h2>
 <h3>Switched from Dojo to jQuery</h3>
-Starting with 1.5.0 we've <a title="Intro to jQuery" href="http://www.dotkernel.com/javascript/intro-to-jquery/">switched from using Dojo to jQuery</a>. This doesn't mean you can't still use Dojo in your own projects, but only jQuery will be used and maintained in the DotKernel distribution.
+Starting with 1.5.0 we've <a title="Intro to jQuery" href="http://www.dotkernel.com/javascript/intro-to-jquery/">switched from using Dojo to jQuery</a>. This doesn't mean you can't still use Dojo in your own projects, but only jQuery will be used and maintained in the Dotkernel distribution.
 <h3>New designs</h3>
 We've redesigned the admin site, with new themes, and a dropdown menu, as well as a new and simpler design for the front-end.
 <h3>Model inheritance</h3>
@@ -36,11 +36,11 @@ To prevent this, we've introduced a <em>Dot_Model</em> class, and a way to defin
 <h3>Dashed controllers</h3>
 We've changed the way the controller name is parsed, so that you can have controller with multiple words, split with dashes, without breaking the coding standard (for example, <em>www.example.com/search-article</em> will call <em>SearchArticleController.php</em>)
 <h3>Zend Registry reorganization</h3>
-We've changed the structure of the registry, for more about this, please check <a title="Zend Registry usage in DotKernel" href="http://www.dotkernel.com/dotkernel/zend-registry-usage-in-dotkernel/">this blog post</a>.
+We've changed the structure of the registry, for more about this, please check <a title="Zend Registry usage in Dotkernel" href="http://www.dotkernel.com/dotkernel/zend-registry-usage-in-dotkernel/">this blog post</a>.
 
 &nbsp;
 
-There have been about 250 commits in our SVN repository since the latest release, so we can't cover all changes in this blog post. Please <a title="DotKernel 1.5.0" href="http://www.dotkernel.com/download/?did=33">download DotKernel 1.5.0</a> try it out yourself and tell us what you think.
+There have been about 250 commits in our SVN repository since the latest release, so we can't cover all changes in this blog post. Please <a title="Dotkernel 1.5.0" href="http://www.dotkernel.com/download/?did=33">download Dotkernel 1.5.0</a> try it out yourself and tell us what you think.
 
 &nbsp;
 
@@ -48,15 +48,15 @@ There have been about 250 commits in our SVN repository since the latest release
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Why did DotKernel jump from 1.3 straight to 1.5.0? <span class="chev">+</span></summary>
+        <summary>Why did Dotkernel jump from 1.3 straight to 1.5.0? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Because of the large amount of changes and the long time spent in development, the team chose to skip version 1.4 and go straight to 1.5.0.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>Did DotKernel switch from Dojo to jQuery in 1.5.0? <span class="chev">+</span></summary>
+        <summary>Did Dotkernel switch from Dojo to jQuery in 1.5.0? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Yes. Starting with 1.5.0, DotKernel switched from Dojo to jQuery for its own distribution, though Dojo can still be used in your own projects.</p>
+            <p class="mb-0">Yes. Starting with 1.5.0, Dotkernel switched from Dojo to jQuery for its own distribution, though Dojo can still be used in your own projects.</p>
         </div>
     </details>
     <details class="acc">
@@ -74,7 +74,7 @@ There have been about 250 commits in our SVN repository since the latest release
     <details class="acc">
         <summary>How much changed in the 1.5.0 release? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">About 250 commits went into the SVN repository since the previous release, so the blog post only covers the highlights - the full DotKernel 1.5.0 download is available to try out.</p>
+            <p class="mb-0">About 250 commits went into the SVN repository since the previous release, so the blog post only covers the highlights - the full Dotkernel 1.5.0 download is available to try out.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-8-0-lts-released.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-8-0-lts-released.html.twig
index c003c31c..a0772ac4 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-8-0-lts-released.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-8-0-lts-released.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-1-8-0-lts-released.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel 1.8.0 LTS Released{% endblock %}
+{% block title %}Dotkernel 1.8.0 LTS Released{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,35 +20,35 @@
 
             <article class="article">
                 <div class="entry">
-DotKernel 1.8.0 (LTS) was just released.
+Dotkernel 1.8.0 (LTS) was just released.
 <h2><strong>What is LTS?
 </strong></h2>
 Long-term support (LTS) is a type of special versions or editions of software designed to be supported for a longer than normal period. It is particularly applicable to open-source software projects. It contains many bug fixes, some refactoring and a few minor features. Find more details read <a href="http://www.dotkernel.com/long-term-support" target="_blank" rel="noopener noreferrer">this article</a>.
 
 &nbsp;
 
-Here are a few of the many changes to DotKernel in the latest release:
+Here are a few of the many changes to Dotkernel in the latest release:
 <h2><!--more--></h2>
 <h2>Highlights of 1.8.0 (LTS)</h2>
 &nbsp;
 <h3>Plugin Architecture</h3>
-Starting with 1.8.0 we will start using Plugins to make the DotKernel extending easier. We'll keep you up to date about how you create and use a plugin.
+Starting with 1.8.0 we will start using Plugins to make the Dotkernel extending easier. We'll keep you up to date about how you create and use a plugin.
 <h3>New design</h3>
 We've redesigned the admin module and the frontend module is now mobile-friendly, but you can still use the mobile module.
 <h3>Loads Faster</h3>
-The DotKernel framework just got a big boost because it supports APC &amp; File Caching within the framework, all the XML's and config files are cached in order to maximize response speed for more information about caching and how to cache your data see <a href="http://www.dotkernel.com/dotkernel/caching-in-dotkernel-using-zend-framework/" target="_blank" rel="noopener noreferrer">this article</a>.
+The Dotkernel framework just got a big boost because it supports APC &amp; File Caching within the framework, all the XML's and config files are cached in order to maximize response speed for more information about caching and how to cache your data see <a href="http://www.dotkernel.com/dotkernel/caching-in-dotkernel-using-zend-framework/" target="_blank" rel="noopener noreferrer">this article</a>.
 <h3>Easier Request Handling</h3>
 We've added a new class, Dot_Request, which lets you have control over the request data before you use it, for example the variables $_SERVER, $_GET and $_POST are only used within controllers.
 <h3>Features added</h3>
 <ul>
     <li>API with Rate Limit - we've added a simple API with a single key authentification and a simple implementation of a rate limit (see /configs/application.ini - section params.api)</li>
-    <li>Cache System - Built on the Zend_Cache backends, provides caching within DotKernel, but also in library, more details about this and how it works can be found <a href="http://www.dotkernel.com/dotkernel/dotkernel-reserved-variable-names-for-caching/" target="_blank" rel="noopener noreferrer">here</a>.</li>
+    <li>Cache System - Built on the Zend_Cache backends, provides caching within Dotkernel, but also in library, more details about this and how it works can be found <a href="http://www.dotkernel.com/dotkernel/dotkernel-reserved-variable-names-for-caching/" target="_blank" rel="noopener noreferrer">here</a>.</li>
 </ul>
 <h3>Other changes</h3>
 <ul>
-    <li>Removed WURFL integration, DotKernel can detect wether you use a mobile device separately now, the WURFL Library can be added as a Plugin from now on</li>
+    <li>Removed WURFL integration, Dotkernel can detect wether you use a mobile device separately now, the WURFL Library can be added as a Plugin from now on</li>
     <li>Removed multiple SMTP Transporter, it can be added as a plugin</li>
-    <li>Security scan in Admin Dashboard - you can now see which are the recommended settings (especially security related) for DotKernel to work at it's best</li>
+    <li>Security scan in Admin Dashboard - you can now see which are the recommended settings (especially security related) for Dotkernel to work at it's best</li>
     <li>Admin fail logins are no longer sent to the first admin, they are sent to all developers found in <em>devEmails</em> within <em>settings</em> table in the database</li>
     <li>Alert System - Alerts can be sent to all the developers to notify them if something goes wrong, for more information about alerts read <a href="http://www.dotkernel.com/dotkernel/how-to-use-alerts-in-dotkernel/" target="_blank" rel="noopener noreferrer">this article</a>.</li>
 </ul>
@@ -62,7 +62,7 @@ We've added a new class, Dot_Request, which lets you have control over the reque
 
 &nbsp;
 
-There have been a lot of commits in our SVN repository since the latest release, so we can't cover all changes in this blog post. Please <a title="DotKernel 1.5.0" href="http://www.dotkernel.com/download/?did=41" target="_blank" rel="noopener noreferrer">download DotKernel 1.8.0 (LTS)</a> try it out yourself and tell us what you think.
+There have been a lot of commits in our SVN repository since the latest release, so we can't cover all changes in this blog post. Please <a title="Dotkernel 1.5.0" href="http://www.dotkernel.com/download/?did=41" target="_blank" rel="noopener noreferrer">download Dotkernel 1.8.0 (LTS)</a> try it out yourself and tell us what you think.
 
 &nbsp;
 
@@ -70,7 +70,7 @@ There have been a lot of commits in our SVN repository since the latest release,
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What does LTS mean for DotKernel 1.8.0? <span class="chev">+</span></summary>
+        <summary>What does LTS mean for Dotkernel 1.8.0? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">LTS stands for Long-term support, a type of special version designed to be supported for longer than normal, which is particularly common for open-source software projects.</p>
         </div>
@@ -78,7 +78,7 @@ There have been a lot of commits in our SVN repository since the latest release,
     <details class="acc">
         <summary>What is the Plugin Architecture introduced in 1.8.0? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Starting with 1.8.0, DotKernel uses Plugins to make extending the framework easier.</p>
+            <p class="mb-0">Starting with 1.8.0, Dotkernel uses Plugins to make extending the framework easier.</p>
         </div>
     </details>
     <details class="acc">
@@ -94,7 +94,7 @@ There have been a lot of commits in our SVN repository since the latest release,
         </div>
     </details>
     <details class="acc">
-        <summary>What was removed from DotKernel in 1.8.0? <span class="chev">+</span></summary>
+        <summary>What was removed from Dotkernel in 1.8.0? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">WURFL integration was removed (mobile device detection is now handled separately, and WURFL can be added as a plugin), and support for multiple SMTP transporters was removed (it can also be added as a plugin).</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-8-1-upgrade-from-1-8-0-released.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-8-1-upgrade-from-1-8-0-released.html.twig
index 745d5ca9..4ec49eda 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-8-1-upgrade-from-1-8-0-released.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-1-8-1-upgrade-from-1-8-0-released.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-1-8-1-upgrade-from-1-8-0-released.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel 1.8.1 + Upgrade from 1.8.0 Released{% endblock %}
+{% block title %}Dotkernel 1.8.1 + Upgrade from 1.8.0 Released{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,24 +20,24 @@
 
             <article class="article">
                 <div class="entry">
-DotKernel 1.8.1 was just released.
+Dotkernel 1.8.1 was just released.
 
-Changes to DotKernel in the latest release:
+Changes to Dotkernel in the latest release:
 - Enhanced Cache Support, which means you can use tags in your cache system if the host suports it
 
 Here are some useful download links:
 
-<a href="http://www.dotkernel.com/download/?did=42" target="_blank" rel="noopener noreferrer">DotKernel 1.8.1</a>
+<a href="http://www.dotkernel.com/download/?did=42" target="_blank" rel="noopener noreferrer">Dotkernel 1.8.1</a>
 
-<a href="http://www.dotkernel.com/download/?did=43" target="_blank" rel="noopener noreferrer">Upgrade from DotKernel 1.8.0</a>
+<a href="http://www.dotkernel.com/download/?did=43" target="_blank" rel="noopener noreferrer">Upgrade from Dotkernel 1.8.0</a>
 
-<a href="http://www.dotkernel.com/download/?did=41" target="_blank" rel="noopener noreferrer">DotKernel 1.8.0 (LTS)</a>
+<a href="http://www.dotkernel.com/download/?did=41" target="_blank" rel="noopener noreferrer">Dotkernel 1.8.0 (LTS)</a>
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What's new in DotKernel 1.8.1? <span class="chev">+</span></summary>
+        <summary>What's new in Dotkernel 1.8.1? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">The main change is Enhanced Cache Support, which means you can use tags in your cache system if the host supports it.</p>
         </div>
@@ -45,7 +45,7 @@ Here are some useful download links:
     <details class="acc">
         <summary>How do I upgrade from 1.8.0 to 1.8.1? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">The post provides a dedicated "Upgrade from DotKernel 1.8.0" download link, separate from the full DotKernel 1.8.1 package and the original DotKernel 1.8.0 (LTS) download.</p>
+            <p class="mb-0">The post provides a dedicated "Upgrade from Dotkernel 1.8.0" download link, separate from the full Dotkernel 1.8.1 package and the original Dotkernel 1.8.0 (LTS) download.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-coding-standard.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-coding-standard.html.twig
index 8a7ee279..4faa45bc 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-coding-standard.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-coding-standard.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-coding-standard.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel Coding Standard{% endblock %}
+{% block title %}Dotkernel Coding Standard{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,10 +20,10 @@
 
             <article class="article">
                 <div class="entry">
-<strong>DotKernel</strong> will be a "skeleton"of <a href="http://framework.zend.com/" target="_blank" rel="noopener noreferrer"><strong>Zend Framework</strong></a>.
-DotKernel borrowed the coding standard from Zend Framework: <strong><a title="ZF Coding Standard" href="http://framework.zend.com/manual/en/coding-standard.php-file-formatting.html" target="_blank" rel="noopener noreferrer">ZF Coding Standard</a> </strong>with some exceptions.
+<strong>Dotkernel</strong> will be a "skeleton"of <a href="http://framework.zend.com/" target="_blank" rel="noopener noreferrer"><strong>Zend Framework</strong></a>.
+Dotkernel borrowed the coding standard from Zend Framework: <strong><a title="ZF Coding Standard" href="http://framework.zend.com/manual/en/coding-standard.php-file-formatting.html" target="_blank" rel="noopener noreferrer">ZF Coding Standard</a> </strong>with some exceptions.
 
-In what follows, we will make remarks only on those features that are slightly different in the coding standards of DotKernel.
+In what follows, we will make remarks only on those features that are slightly different in the coding standards of Dotkernel.
 <!--more-->
 
 <a href="http://framework.zend.com/manual/en/coding-standard.php-file-formatting.html" target="_blank" rel="noopener noreferrer"><strong>B.2. PHP File Formatting</strong></a>
@@ -62,15 +62,15 @@ e.g:
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What coding standard does DotKernel follow? <span class="chev">+</span></summary>
+        <summary>What coding standard does Dotkernel follow? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel borrows its coding standard from the Zend Framework Coding Standard, with some exceptions described in this article.</p>
+            <p class="mb-0">Dotkernel borrows its coding standard from the Zend Framework Coding Standard, with some exceptions described in this article.</p>
         </div>
     </details>
     <details class="acc">
         <summary>Tabs or spaces for indentation? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel indents with tabs, not spaces.</p>
+            <p class="mb-0">Dotkernel indents with tabs, not spaces.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-database-naming-conventions-for-mysql.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-database-naming-conventions-for-mysql.html.twig
index 947ca4ea..44d573fe 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-database-naming-conventions-for-mysql.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-database-naming-conventions-for-mysql.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-database-naming-conventions-for-mysql.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel Database Naming Conventions for MySQL{% endblock %}
+{% block title %}Dotkernel Database Naming Conventions for MySQL{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-DotKernel borrows the database naming conventions from <a href="http://fazend.com/a/2009-11-DataNaming.html" target="_blank" rel="noopener noreferrer">FaZend: Rules of naming of database tables and columns</a>. FaZend is an open-source PHP framework based on Zend Framework.
+Dotkernel borrows the database naming conventions from <a href="http://fazend.com/a/2009-11-DataNaming.html" target="_blank" rel="noopener noreferrer">FaZend: Rules of naming of database tables and columns</a>. FaZend is an open-source PHP framework based on Zend Framework.
 <!--more-->
 <strong>Database naming conventions for tables and columns:</strong>
 <ul>
@@ -65,7 +65,7 @@ The names of database tables and columns must follow <em>camelLetter</em> as nam
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Where do DotKernel's database naming conventions come from? <span class="chev">+</span></summary>
+        <summary>Where do Dotkernel's database naming conventions come from? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">They are borrowed from FaZend's "Rules of naming of database tables and columns," an open-source PHP framework based on Zend Framework.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-on-nginx.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-on-nginx.html.twig
index 416c3800..fb51a642 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-on-nginx.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-on-nginx.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-on-nginx.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel on Nginx{% endblock %}
+{% block title %}Dotkernel on Nginx{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -58,12 +58,12 @@ location ~ ^/configs/ {
 </li>
 </ul>
 </li>
-    <li>  Export a DotKernel copy from SVN
+    <li>  Export a Dotkernel copy from SVN
 <pre>>svn export --force  http://v1.dotkernel.net/svn/trunk/ /var/www/html</pre>
 </li>
     <li>Edit <em><strong>application.ini</strong></em> to reflect the current settings and check if is  protected
 <a href="http://nginx.dotkernel.net/configs/application.ini" target="_blank" rel="noopener noreferrer">http://nginx.dotkernel.net/configs/application.ini</a></li>
-    <li>And walla, site is running on Nginx       <a title="Nginx DotKernel" href="http://nginx.dotkernel.net/" target="_blank" rel="noopener noreferrer">http://nginx.dotkernel.net/</a>
+    <li>And walla, site is running on Nginx       <a title="Nginx Dotkernel" href="http://nginx.dotkernel.net/" target="_blank" rel="noopener noreferrer">http://nginx.dotkernel.net/</a>
 <em>Admin login is disabled due to security reason.</em></li>
 </ol>
 
@@ -89,7 +89,7 @@ location ~ ^/configs/ {
         </div>
     </details>
     <details class="acc">
-        <summary>How was the DotKernel codebase deployed onto the server? <span class="chev">+</span></summary>
+        <summary>How was the Dotkernel codebase deployed onto the server? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">It was exported directly from SVN using svn export --force http://v1.dotkernel.net/svn/trunk/ /var/www/html.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-reserved-variable-names-for-caching.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-reserved-variable-names-for-caching.html.twig
index 87e89dde..e5956f85 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-reserved-variable-names-for-caching.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-reserved-variable-names-for-caching.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-reserved-variable-names-for-caching.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel Reserved Variable Names for Caching{% endblock %}
+{% block title %}Dotkernel Reserved Variable Names for Caching{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,21 +20,21 @@
 
             <article class="article">
                 <div class="entry">
-This article is related to: <a title="DotKernel - Caching in DotKernel Using Zend Framework" href="http://www.dotkernel.com/dotkernel/caching-in-dotkernel-using-zend-framework" target="_blank" rel="noopener noreferrer">Caching in DotKernel with Zend Framework Cache</a>
+This article is related to: <a title="Dotkernel - Caching in Dotkernel Using Zend Framework" href="http://www.dotkernel.com/dotkernel/caching-in-dotkernel-using-zend-framework" target="_blank" rel="noopener noreferrer">Caching in Dotkernel with Zend Framework Cache</a>
 
-The variables that DotKernel cache are below:
+The variables that Dotkernel cache are below:
 <h2>Router</h2>
-Router is the object that load routes (modules, controllers, actions) settings from router.xml file. More info about router: <a title="DotKernel - router.xml" href="http://www.dotkernel.com/docs/router-xml/" target="_blank" rel="noopener noreferrer">http://www.dotkernel.com/docs/router-xml/</a>
+Router is the object that load routes (modules, controllers, actions) settings from router.xml file. More info about router: <a title="Dotkernel - router.xml" href="http://www.dotkernel.com/docs/router-xml/" target="_blank" rel="noopener noreferrer">http://www.dotkernel.com/docs/router-xml/</a>
 
 The router is cached as <em><strong>router.</strong></em><!--more-->
 <h2>Auth / ACL Role<strong>
 </strong></h2>
-The object which authorizes user methods (aka Dot_Auth), used in all DotKernel Applications, Dot_Auth uses <em>/configs/acl/role.xml</em> to define the users rights.
+The object which authorizes user methods (aka Dot_Auth), used in all Dotkernel Applications, Dot_Auth uses <em>/configs/acl/role.xml</em> to define the users rights.
 
 The <em>role.xml</em> file is cached as <em><strong>acl_role</strong>.</em>
 <h2>Menu</h2>
-The menu.xml from current <em><strong>module</strong>(<a title="DotKernel - Module Structure" href="http://www.dotkernel.com/docs/module-structure/" target="_blank" rel="noopener noreferrer">what is a module?</a>)</em>
-More about menu.xml : <em><a title="DotKernel - Menu Xml" href="http://www.dotkernel.com/docs/menu-xml/" target="_blank" rel="noopener noreferrer">http://www.dotkernel.com/docs/menu-xml/</a></em>
+The menu.xml from current <em><strong>module</strong>(<a title="Dotkernel - Module Structure" href="http://www.dotkernel.com/docs/module-structure/" target="_blank" rel="noopener noreferrer">what is a module?</a>)</em>
+More about menu.xml : <em><a title="Dotkernel - Menu Xml" href="http://www.dotkernel.com/docs/menu-xml/" target="_blank" rel="noopener noreferrer">http://www.dotkernel.com/docs/menu-xml/</a></em>
 
 The menu is cached as <em><strong>admin_menu</strong></em>, <em><strong>frontend_menu</strong></em><strong>.</strong>
 <h2>Options</h2>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-template-engine.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-template-engine.html.twig
index a4d38818..94ec2e5a 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-template-engine.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-template-engine.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-template-engine.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel Template Engine{% endblock %}
+{% block title %}Dotkernel Template Engine{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -22,14 +22,14 @@
                 <div class="entry">
 <h2>
 
-DotKernel Template Engine is an implementation of PHPLib Template engine for PHP5.</h2>
+Dotkernel Template Engine is an implementation of PHPLib Template engine for PHP5.</h2>
 It has an amazing ability to separate the application code from the presentation layer. Separates the manipulation of data (in the database as well as in PHP) from its final format, whether that format is HTML, XML or a formatted e-mail. The big advantage is that is allowing us to change the look and feel of a site quickly without having to delve immediately into a lot of PHP variable assignments and print statements.
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What is the DotKernel Template Engine based on? <span class="chev">+</span></summary>
+        <summary>What is the Dotkernel Template Engine based on? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">It's an implementation of the PHPLib Template engine for PHP5.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-version-1-0-in-action.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-version-1-0-in-action.html.twig
index d527bee1..0c875ee0 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-version-1-0-in-action.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/dotkernel-version-1-0-in-action.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/dotkernel-version-1-0-in-action.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel version 1.0 in action{% endblock %}
+{% block title %}Dotkernel version 1.0 in action{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -22,13 +22,13 @@
                 <div class="entry">
 <div>
 
-<span>DotKernel</span> is the<a href="http://www.dotboost.com" target="_blank" rel="noopener noreferrer"> DotBoost</a>'s in-house developed framework, based on Zend Framework.
-<strong>DotKernel </strong> is at version 1.0 ,  released under  <a href="http://opensource.org/licenses/osl-3.0.php" target="_blank" rel="noopener noreferrer">Open Software License (OSL 3.0)</a> ,  and is built on top of  <a href="http://framework.zend.com/" target="_blank" rel="noopener noreferrer">Zend Framework</a>.</div>
-<div>DotKernel is using a simplified <strong>MVC (Model-View-Controller)</strong> architecture, easy to learn by beginner and intermediate level programmers.
+<span>Dotkernel</span> is the<a href="http://www.dotboost.com" target="_blank" rel="noopener noreferrer"> DotBoost</a>'s in-house developed framework, based on Zend Framework.
+<strong>Dotkernel </strong> is at version 1.0 ,  released under  <a href="http://opensource.org/licenses/osl-3.0.php" target="_blank" rel="noopener noreferrer">Open Software License (OSL 3.0)</a> ,  and is built on top of  <a href="http://framework.zend.com/" target="_blank" rel="noopener noreferrer">Zend Framework</a>.</div>
+<div>Dotkernel is using a simplified <strong>MVC (Model-View-Controller)</strong> architecture, easy to learn by beginner and intermediate level programmers.
 It has eliminated the complexity of Zend Framework by using a different approach of how the web request are handled.
 
 <!--more--><br>
-<h2>From Zend Framework, DotKernel is using only the necessary classes:</h2>
+<h2>From Zend Framework, Dotkernel is using only the necessary classes:</h2>
 <ul>
     <li><strong>Zend_Config</strong> - While Zend Framework itself is configuration-less, it's often necessary to have some way to specify configurable options. Zend_Config provides multiple backends for configuration storage, and a simple, intuitive, object-oriented interface for accessing it. We store configuration as simple PHP arrays, which are then wrapped by Zend_Config.</li>
     <li><strong>Zend_Db and Zend_Db_Table</strong> - Zend_Db_Table is a classic implementation of both the Table Data Gateway and Row Data Gateway design patterns, allowing for easy and  intuitive access to database tables and rows, as well as an entry point for custom business logic surrounding our data.</li>
@@ -42,21 +42,21 @@ It has eliminated the complexity of Zend Framework by using a different approach
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Who developed DotKernel and what is it built on? <span class="chev">+</span></summary>
+        <summary>Who developed Dotkernel and what is it built on? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel is DotBoost's in-house developed framework, built on top of Zend Framework. At the time of this article it was at version 1.0, released under the Open Software License (OSL 3.0).</p>
+            <p class="mb-0">Dotkernel is DotBoost's in-house developed framework, built on top of Zend Framework. At the time of this article it was at version 1.0, released under the Open Software License (OSL 3.0).</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What architecture does DotKernel use? <span class="chev">+</span></summary>
+        <summary>What architecture does Dotkernel use? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">A simplified MVC (Model-View-Controller) architecture that's easy to learn for beginner and intermediate level programmers, achieved by eliminating much of Zend Framework's complexity through a different approach to handling web requests.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What does Zend_Config provide in DotKernel? <span class="chev">+</span></summary>
+        <summary>What does Zend_Config provide in Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">It provides multiple backends for configuration storage and a simple, intuitive, object-oriented interface for accessing it. DotKernel stores configuration as simple PHP arrays, which are then wrapped by Zend_Config.</p>
+            <p class="mb-0">It provides multiple backends for configuration storage and a simple, intuitive, object-oriented interface for accessing it. Dotkernel stores configuration as simple PHP arrays, which are then wrapped by Zend_Config.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/geoip-city-removed-from-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/geoip-city-removed-from-dotkernel.html.twig
index 45f38732..46c8561f 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/geoip-city-removed-from-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/geoip-city-removed-from-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/geoip-city-removed-from-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}GeoIP City Removed From DotKernel{% endblock %}
+{% block title %}GeoIP City Removed From Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -24,7 +24,7 @@ In the newest version we have removed the GeoIP City integration. The City datab
 
 <!--more-->
 
-This error occurs due to the extension incompatibility with the database(dat) file. If you have an older DotKernel version and version <strong>&gt;=1.1.0</strong> of GeoIP you might get this error.
+This error occurs due to the extension incompatibility with the database(dat) file. If you have an older Dotkernel version and version <strong>&gt;=1.1.0</strong> of GeoIP you might get this error.
 
 On some operating systems Apache will respond your request with HTTP Status Code 200 (OK) and a web page containing the text below.
 
@@ -36,7 +36,7 @@ The error might not be logged as the error is generated the GeoIP extension and
 
 If you don't want to use GeoIP City and just want to get rid of the error go to
 <ul>
-    <li>DotKernel/admin/System.php (Admin/System model) and comment or remove the lines below</li>
+    <li>Dotkernel/admin/System.php (Admin/System model) and comment or remove the lines below</li>
 </ul>
 <pre>>if(geoip_db_avail(GEOIP_CITY_EDITION_REV0))
 {
@@ -59,7 +59,7 @@ If you don't want to use GeoIP City and just want to get rid of the error go to
         $country = $countryName != false  ? $countryName : 'NA';
     }
 }</pre>
-Theese changes were also made in the latest version of DotKernel. You should use this fix only if you don't intend to use GeoIP City.
+Theese changes were also made in the latest version of Dotkernel. You should use this fix only if you don't intend to use GeoIP City.
 
 We recommend special coding for using GeoIP City and in the GeoIP extension in general.
 
@@ -69,7 +69,7 @@ Note that GeoIP is an obsolete extension, Maxmind recommends using GeoIP2.
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Why was GeoIP City removed from DotKernel? <span class="chev">+</span></summary>
+        <summary>Why was GeoIP City removed from Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">The City database on GeoIP extension version 1.1.0 and above was causing a segmentation fault, which resulted in crashing or outputting an error instead of executing the PHP code.</p>
         </div>
@@ -77,7 +77,7 @@ Note that GeoIP is an obsolete extension, Maxmind recommends using GeoIP2.
     <details class="acc">
         <summary>Who is affected by this error? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Users running an older DotKernel version together with GeoIP extension version 1.1.0 or newer, since the error comes from the extension's incompatibility with the database (dat) file.</p>
+            <p class="mb-0">Users running an older Dotkernel version together with GeoIP extension version 1.1.0 or newer, since the error comes from the extension's incompatibility with the database (dat) file.</p>
         </div>
     </details>
     <details class="acc">
@@ -89,7 +89,7 @@ Note that GeoIP is an obsolete extension, Maxmind recommends using GeoIP2.
     <details class="acc">
         <summary>How can you get rid of the error if you don't need GeoIP City? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Comment out or remove the relevant lines in DotKernel/admin/System.php (the Admin/System model) and in library/Dot/GeoIp.php (the Dot_GeoIp class). These changes were also made in the latest version of DotKernel, but this fix should only be used if you don't intend to use GeoIP City.</p>
+            <p class="mb-0">Comment out or remove the relevant lines in Dotkernel/admin/System.php (the Admin/System model) and in library/Dot/GeoIp.php (the Dot_GeoIp class). These changes were also made in the latest version of Dotkernel, but this fix should only be used if you don't intend to use GeoIP City.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/geoip-ip-address-location-in-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/geoip-ip-address-location-in-dotkernel.html.twig
index 727a0edd..29cca07e 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/geoip-ip-address-location-in-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/geoip-ip-address-location-in-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/geoip-ip-address-location-in-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}GeoIP: Ip Address Location In DotKernel{% endblock %}
+{% block title %}GeoIP: Ip Address Location In Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -22,7 +22,7 @@
                 <div class="entry">
 <em><strong>GeoIP</strong> </em>is the proprietary technology that drives <a href="http://www.maxmind.com/app/ip-location" target="_blank" rel="noopener noreferrer">MaxMind's</a> IP geolocation data and services. It is a non-invasive way to determine geographical and other information about Internet visitors in real-time. When a person visits your website, <strong><em>GeoIP </em></strong>can determine which country, region, city, postal code, area code the visitor is coming from.
 
-DotKernel uses <em><strong>GeoIP </strong></em>to get user statistics by country. The main file for <em><strong>GeoIP </strong></em>is <a href="http://websvn.dotkernel.net/filedetails.php?repname=DotKernel&amp;path=%2Ftrunk%2Flibrary%2FDot%2FGeoip.php" target="_blank" rel="noopener noreferrer">library/Dot/Geoip.php</a>
+Dotkernel uses <em><strong>GeoIP </strong></em>to get user statistics by country. The main file for <em><strong>GeoIP </strong></em>is <a href="http://websvn.dotkernel.net/filedetails.php?repname=Dotkernel&amp;path=%2Ftrunk%2Flibrary%2FDot%2FGeoip.php" target="_blank" rel="noopener noreferrer">library/Dot/Geoip.php</a>
 <!--more-->
 Let’s explain what function <strong><em>getCountryByIp </em></strong>does:
 <ul>
@@ -33,7 +33,7 @@ Next there are 4 <strong><em>if/else</em></strong> statements:
 <a name="1"></a>
 <strong>1. </strong>Line 43 – 57: <em><strong>mod_geoip </strong></em>PECL extension is not installed</a>
 <ul>
-    <li>In this case we use the already existing file <strong>externals/geoip/GeoIP.dat</strong> from DotKernel (If you don’t have it, download it from <a href="http://www.maxmind.com/app/geolitecountry">here</a>).</li>
+    <li>In this case we use the already existing file <strong>externals/geoip/GeoIP.dat</strong> from Dotkernel (If you don’t have it, download it from <a href="http://www.maxmind.com/app/geolitecountry">here</a>).</li>
 </ul>
 <strong>2. </strong>Line 58 – 63: <em><strong>mod_geoip</strong></em> is installed and <strong><em>GeoIP.dat</em></strong> file exists on the server: <em>geoip_db_avail(GEOIP_COUNTRY_EDITION)</em>
 <ul>
@@ -45,7 +45,7 @@ Next there are 4 <strong><em>if/else</em></strong> statements:
 </ul>
 <strong>4. </strong>Line 74 – 88 : <em><strong>mod_geoip</strong></em> is installed, but neither GeoIP.dat or GeoIPCity.dat exist
 <ul>
-    <li>This has the same behavior like item <a name="#1"></a>#1<a> in this list –  it uses <strong><em>externals/geoip/GeoIP.dat</em></strong> from the DotKernel framework</a></li>
+    <li>This has the same behavior like item <a name="#1"></a>#1<a> in this list –  it uses <strong><em>externals/geoip/GeoIP.dat</em></strong> from the Dotkernel framework</a></li>
 </ul>
 <pre> line="32">/**
  * Get the country by IP
@@ -113,13 +113,13 @@ public function getCountryByIp($ip)
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What is GeoIP and what does it let DotKernel do? <span class="chev">+</span></summary>
+        <summary>What is GeoIP and what does it let Dotkernel do? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">GeoIP is MaxMind's proprietary technology for IP geolocation data. DotKernel uses it to get user statistics by country, determining a visitor's country, region, city, postal code, or area code in real time.</p>
+            <p class="mb-0">GeoIP is MaxMind's proprietary technology for IP geolocation data. Dotkernel uses it to get user statistics by country, determining a visitor's country, region, city, postal code, or area code in real time.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>Where does the GeoIP logic live in DotKernel? <span class="chev">+</span></summary>
+        <summary>Where does the GeoIP logic live in Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">In library/Dot/Geoip.php, inside the getCountryByIp function.</p>
         </div>
@@ -127,7 +127,7 @@ public function getCountryByIp($ip)
     <details class="acc">
         <summary>What does getCountryByIp do when the mod_geoip PECL extension isn't installed? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">It falls back to the existing externals/geoip/GeoIP.dat file bundled with DotKernel (downloadable from MaxMind if not present).</p>
+            <p class="mb-0">It falls back to the existing externals/geoip/GeoIP.dat file bundled with Dotkernel (downloadable from MaxMind if not present).</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/handling-and-logging-errors-with-dot-errorhandler-and-dot-log.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/handling-and-logging-errors-with-dot-errorhandler-and-dot-log.html.twig
index 013f204e..cf5c2b73 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/handling-and-logging-errors-with-dot-errorhandler-and-dot-log.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/handling-and-logging-errors-with-dot-errorhandler-and-dot-log.html.twig
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-This article is a follow-up for:<strong> <a href="https://www.dotkernel.com/dotkernel/logging-with-dot-log-in-zend-expressive-and-dotkernel/" target="_blank" rel="noopener noreferrer">Logging with dot-log in Zend Expressive and DotKernel</a></strong>, the mentioned article is a guide to using dot-log.
+This article is a follow-up for:<strong> <a href="https://www.dotkernel.com/dotkernel/logging-with-dot-log-in-zend-expressive-and-dotkernel/" target="_blank" rel="noopener noreferrer">Logging with dot-log in Zend Expressive and Dotkernel</a></strong>, the mentioned article is a guide to using dot-log.
 
 &nbsp;
 
@@ -130,7 +130,7 @@ The tests we have made were the following:
     <details class="acc">
         <summary>What must already be in place before configuring the logging error handler? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">A configured logger as described in the "Logging with dot-log in Zend Expressive and DotKernel" article, with the logger named default_logger as used in the package's config example.</p>
+            <p class="mb-0">A configured logger as described in the "Logging with dot-log in Zend Expressive and Dotkernel" article, with the logger named default_logger as used in the package's config example.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/highcharts-integration-in-dotkernel-1-6-0.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/highcharts-integration-in-dotkernel-1-6-0.html.twig
index d73c8f95..9cbaa1b3 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/highcharts-integration-in-dotkernel-1-6-0.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/highcharts-integration-in-dotkernel-1-6-0.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/highcharts-integration-in-dotkernel-1-6-0.jsonld.twig') }} {% endblock %}
 
-{% block title %}Highcharts Integration in DotKernel 1.6.0{% endblock %}
+{% block title %}Highcharts Integration in Dotkernel 1.6.0{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-Integrating a new charting library in the latest version of DotKernel (1.6.0) we offer a new experience with this new intuitive and interactive charts.
+Integrating a new charting library in the latest version of Dotkernel (1.6.0) we offer a new experience with this new intuitive and interactive charts.
 
 <!--more-->
 
@@ -75,9 +75,9 @@ Take a quick view on the code to see how highcharts are working.
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What charting library was integrated in DotKernel 1.6.0? <span class="chev">+</span></summary>
+        <summary>What charting library was integrated in Dotkernel 1.6.0? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Highcharts was integrated in DotKernel 1.6.0, offering a new, intuitive and interactive charting experience.</p>
+            <p class="mb-0">Highcharts was integrated in Dotkernel 1.6.0, offering a new, intuitive and interactive charting experience.</p>
         </div>
     </details>
     <details class="acc">
@@ -87,7 +87,7 @@ Take a quick view on the code to see how highcharts are working.
         </div>
     </details>
     <details class="acc">
-        <summary>Where can the Highcharts library be found in a DotKernel project? <span class="chev">+</span></summary>
+        <summary>Where can the Highcharts library be found in a Dotkernel project? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">The Highcharts library is located in the <strong>externals</strong> directory of the project.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/how-to-group-log-files-by-date-using-dot-log.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/how-to-group-log-files-by-date-using-dot-log.html.twig
index d1cf708f..472a8649 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/how-to-group-log-files-by-date-using-dot-log.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/how-to-group-log-files-by-date-using-dot-log.html.twig
@@ -32,7 +32,7 @@
 
 <p class="mb-3">As always, we strongly suggest you to keep your packages updated. Allthough, if your application logs messages in a single file with a static name (eg: log/dk.log), you can skip the rest of this article - logging will work as before.</p>
 
-<h2>Configuring the logger with DotKernel</h2>
+<h2>Configuring the logger with Dotkernel</h2>
 
 <p class="mb-3">Your application should already have a <strong>config/autoload/error-handling.global.php</strong> file, similar to this:</p>
 
@@ -88,7 +88,7 @@ return &#91;
 
 <p class="mb-3">If the path to your log files contains other date format specifiers, make sure you adapt it accordingly. A complete list of the specifiers can be found <a rel="noreferrer noopener" href="https://www.php.net/manual/en/datetime.format.php" target="_blank">here</a>.</p>
 
-<h2>Configuring the logger without DotKernel</h2>
+<h2>Configuring the logger without Dotkernel</h2>
 
 <p class="mb-3">Locate dot-log configs in your application (probably /config/autoload/log.global.php). They should look similar to this:</p>
 
@@ -191,13 +191,13 @@ return &#91;
         </div>
     </details>
     <details class="acc">
-        <summary>How do I group log files by date when using DotKernel? <span class="chev">+</span></summary>
+        <summary>How do I group log files by date when using Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">In <strong>config/autoload/error-handling.global.php</strong>, locate every log writer by navigating to <code>dot_log-&gt;loggers-&gt;default_logger-&gt;writers</code> and replace a <code>stream</code> value like <code>sprintf('%s/../../log/error-log-%s.log', __DIR__, date('Y-m-d'))</code> with <code>__DIR__ . '/../../log/error-log-{Y}-{m}-{d}.log'</code>.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>How do I group log files by date without DotKernel? <span class="chev">+</span></summary>
+        <summary>How do I group log files by date without Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">In your dot-log config (e.g. /config/autoload/log.global.php), locate every writer under <code>dot_log-&gt;loggers-&gt;my_logger-&gt;writers</code> and replace a dynamic <code>stream</code> value such as <code>sprintf('%s/../../log/dk-%s.log', __DIR__, date('Y-m-d'))</code> with a formatter string like <code>__DIR__ . '/../../log/error-log-{Y}-{m}-{d}.log'</code>.</p>
         </div>
@@ -205,7 +205,7 @@ return &#91;
     <details class="acc">
         <summary>What must I do after changing the stream configuration? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Clear the config cache. In a DotKernel application, run <code>php bin/clear-config-cache.php</code>; in a non-DotKernel setup, make sure you clear your application's config before usage.</p>
+            <p class="mb-0">Clear the config cache. In a Dotkernel application, run <code>php bin/clear-config-cache.php</code>; in a non-Dotkernel setup, make sure you clear your application's config before usage.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/how-to-set-a-persistent-connection-to-database-with-zend-framework-zend-db-adapter.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/how-to-set-a-persistent-connection-to-database-with-zend-framework-zend-db-adapter.html.twig
index a0cf335a..01db53a0 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/how-to-set-a-persistent-connection-to-database-with-zend-framework-zend-db-adapter.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/how-to-set-a-persistent-connection-to-database-with-zend-framework-zend-db-adapter.html.twig
@@ -22,7 +22,7 @@
                 <div class="entry">
 From time to time, it may be a good idea to have a persistent connection to database.
 
-The place where it should be added that new configuration option is application.ini ( DotKernel approach as an example)
+The place where it should be added that new configuration option is application.ini ( Dotkernel approach as an example)
 
 Do <strong>not</strong> try something like below, will not work:
 <pre>>database.params.options.PDO::ATTR_PERSISTENT = TRUE</pre>
@@ -35,9 +35,9 @@ Instead , use the below line
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Where do you configure a persistent database connection in a DotKernel project? <span class="chev">+</span></summary>
+        <summary>Where do you configure a persistent database connection in a Dotkernel project? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">The option should be added in application.ini, as shown in the DotKernel approach used as an example in the article.</p>
+            <p class="mb-0">The option should be added in application.ini, as shown in the Dotkernel approach used as an example in the article.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/how-to-use-alerts-in-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/how-to-use-alerts-in-dotkernel.html.twig
index 87e96d88..a463a408 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/how-to-use-alerts-in-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/how-to-use-alerts-in-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/how-to-use-alerts-in-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}How to use Alerts in DotKernel{% endblock %}
+{% block title %}How to use Alerts in Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -22,13 +22,13 @@
                 <div class="entry">
 Alerts (or Dot_Alert's) are e-mails usually sent to the site developers, these messages are sent with <strong>mail()</strong> therefore you shouldn't use them to send regular mail. Alerts should only notify you as a developer: "<em><strong>Hey, something's wrong here, you might want to know this!</strong></em>"
 
-In this article you will find out how to use the Alerts system in DotKernel, we will also go through an existing example so this can be understood easier.
+In this article you will find out how to use the Alerts system in Dotkernel, we will also go through an existing example so this can be understood easier.
 
 The Dot_Alert class resembles with Dot_Email, the alerts, like a mail message, have at least the sender, a subject, a destination and a message and it can also be sent.
 
 <!--more-->
 
-In DotKernel we use the Alerts for notifying the developer that an email was not sent successfully.
+In Dotkernel we use the Alerts for notifying the developer that an email was not sent successfully.
 
 In this case we kept the message in the dots.xml file
 <pre>>
@@ -103,9 +103,9 @@ Everything is great, we can now send our alert:
         </div>
     </details>
     <details class="acc">
-        <summary>What's an example use of Alerts in DotKernel? <span class="chev">+</span></summary>
+        <summary>What's an example use of Alerts in Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel uses Alerts to notify the developer when an email was not sent successfully, with the message kept in the dots.xml file under the alertMessages section.</p>
+            <p class="mb-0">Dotkernel uses Alerts to notify the developer when an email was not sent successfully, with the message kept in the dots.xml file under the alertMessages section.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/implementing-the-new-password-hashing-api-from-php-5-5-in-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/implementing-the-new-password-hashing-api-from-php-5-5-in-dotkernel.html.twig
index 06ba0ea8..238aee99 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/implementing-the-new-password-hashing-api-from-php-5-5-in-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/implementing-the-new-password-hashing-api-from-php-5-5-in-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/implementing-the-new-password-hashing-api-from-php-5-5-in-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}Implementing the new Password Hashing API from PHP 5.5 in DotKernel{% endblock %}
+{% block title %}Implementing the new Password Hashing API from PHP 5.5 in Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-In order to use the new <a href="http://www.php.net/manual/en/book.password.php" target="_blank" rel="noopener noreferrer">Password Hashing</a> functions , introduced in PHP 5.5 , and unify all password related functions , used for both admin and users, we did a major refactor of DotKernel codebase, in version 1.8.0 , starting from revision 799.
+In order to use the new <a href="http://www.php.net/manual/en/book.password.php" target="_blank" rel="noopener noreferrer">Password Hashing</a> functions , introduced in PHP 5.5 , and unify all password related functions , used for both admin and users, we did a major refactor of Dotkernel codebase, in version 1.8.0 , starting from revision 799.
 
 See more on that matter<a href="http://www.brandonsavage.net/please-stop-hashing-passwords-yourself/" target="_blank" rel="noopener noreferrer"> here </a>
 
@@ -28,7 +28,7 @@ See more on that matter<a href="http://www.brandonsavage.net/please-stop-hashing
 
 Since those 4 new functions are available only since PHP 5.5 , we used the <a href="https://github.com/ircmaxell/password_compat" target="_blank" rel="noopener noreferrer">Password Compatibility library.</a>
 
-The minimum PHP version in order to run DotKernel was raised to PHP 5.3.8 .
+The minimum PHP version in order to run Dotkernel was raised to PHP 5.3.8 .
 
 &nbsp;
 
@@ -43,7 +43,7 @@ The minimum PHP version in order to run DotKernel was raised to PHP 5.3.8 .
 <ul>
     <li>Remove from application.ini the variable <strong>settings.admin.salt = 5F6WQ9U3YT</strong></li>
     <li>apply the patch . <a href="http://www.dotkernel.com/download/?did=40" target="_blank" rel="noopener noreferrer">Download</a></li>
-    <li>if you have trouble applying the patch, you can compare the files and see the log/diff in <a href="http://websvn.dotkernel.net/comp.php?repname=DotKernel&amp;compare[]=/@796&amp;compare[]=/@797" target="_blank" rel="noopener noreferrer">websvn </a></li>
+    <li>if you have trouble applying the patch, you can compare the files and see the log/diff in <a href="http://websvn.dotkernel.net/comp.php?repname=Dotkernel&amp;compare[]=/@796&amp;compare[]=/@797" target="_blank" rel="noopener noreferrer">websvn </a></li>
     <li>run the conversion script . You can find the details in the file Console/Controller.php , at line 47</li>
     <li>Hope that you will not break something :-)</li>
     <li>Admin passwords cannot be converted , so need to be recreated manually .</li>
@@ -58,25 +58,25 @@ The minimum PHP version in order to run DotKernel was raised to PHP 5.3.8 .
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Why was DotKernel refactored to use the new PHP 5.5 Password Hashing API? <span class="chev">+</span></summary>
+        <summary>Why was Dotkernel refactored to use the new PHP 5.5 Password Hashing API? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">To use the new Password Hashing functions introduced in PHP 5.5 and unify all password related functions used for both admin and users, DotKernel's codebase was refactored in version 1.8.0, starting from revision 799.</p>
+            <p class="mb-0">To use the new Password Hashing functions introduced in PHP 5.5 and unify all password related functions used for both admin and users, Dotkernel's codebase was refactored in version 1.8.0, starting from revision 799.</p>
         </div>
     </details>
     <details class="acc">
         <summary>How can PHP versions older than 5.5 use these new hashing functions? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Since the 4 new functions are only available since PHP 5.5, DotKernel used the Password Compatibility library (ircmaxell/password_compat).</p>
+            <p class="mb-0">Since the 4 new functions are only available since PHP 5.5, Dotkernel used the Password Compatibility library (ircmaxell/password_compat).</p>
         </div>
     </details>
     <details class="acc">
         <summary>What is the minimum PHP version required after this change? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">The minimum PHP version required to run DotKernel was raised to PHP 5.3.8.</p>
+            <p class="mb-0">The minimum PHP version required to run Dotkernel was raised to PHP 5.3.8.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What steps are needed to apply this refactor to an older DotKernel system? <span class="chev">+</span></summary>
+        <summary>What steps are needed to apply this refactor to an older Dotkernel system? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Change the password column definition in the admin and user tables via ALTER TABLE, remove the settings.admin.salt entry from application.ini, apply the provided patch, and run the conversion script described in Console/Controller.php at line 47.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/logging-with-dot-log-in-zend-expressive-and-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/logging-with-dot-log-in-zend-expressive-and-dotkernel.html.twig
index dba5dae1..4491e9b5 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/logging-with-dot-log-in-zend-expressive-and-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/logging-with-dot-log-in-zend-expressive-and-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/logging-with-dot-log-in-zend-expressive-and-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}Logging with dot-log in Zend Expressive and DotKernel{% endblock %}
+{% block title %}Logging with dot-log in Zend Expressive and Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-This article will explain the usage of the <strong><a href="https://github.com/dotkernel/dot-log" target="_blank" rel="noopener noreferrer">dot-log</a> </strong>component within DotKernel, Zend Expressive or in a project that uses Zend Service Manager.
+This article will explain the usage of the <strong><a href="https://github.com/dotkernel/dot-log" target="_blank" rel="noopener noreferrer">dot-log</a> </strong>component within Dotkernel, Zend Expressive or in a project that uses Zend Service Manager.
 
 Since dot-log extends zendframework/zend-log this tutorial mostly compatible with zend-log as well.
 
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/manual-upgrade-of-wurfl-xml-file-in-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/manual-upgrade-of-wurfl-xml-file-in-dotkernel.html.twig
index 980c9a3f..f0484c2d 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/manual-upgrade-of-wurfl-xml-file-in-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/manual-upgrade-of-wurfl-xml-file-in-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/manual-upgrade-of-wurfl-xml-file-in-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}Manual upgrade of WURFL xml file in DotKernel{% endblock %}
+{% block title %}Manual upgrade of WURFL xml file in Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-DotKernel Application Framework can be downloaded with WURFL XML file bundled in it, but is quite an old file,  the latest GPL version, from June 2011. Because of license changed of that WURFL file,  this bundled file will not be upgraded anymore by us.
+Dotkernel Application Framework can be downloaded with WURFL XML file bundled in it, but is quite an old file,  the latest GPL version, from June 2011. Because of license changed of that WURFL file,  this bundled file will not be upgraded anymore by us.
 
 You need to manually upgrade the xml file, if you still want to use it , and of course, please pay attention to license changes.
 <ol>
@@ -40,9 +40,9 @@ Again, please pay attention to WURFL license changes.
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Why does the WURFL xml file need to be manually upgraded in DotKernel? <span class="chev">+</span></summary>
+        <summary>Why does the WURFL xml file need to be manually upgraded in Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel bundles an old WURFL XML file (the latest GPL version, from June 2011). Because of a license change to that WURFL file, the bundled file will no longer be upgraded by DotKernel, so it must be upgraded manually if you still want to use it.</p>
+            <p class="mb-0">Dotkernel bundles an old WURFL XML file (the latest GPL version, from June 2011). Because of a license change to that WURFL file, the bundled file will no longer be upgraded by Dotkernel, so it must be upgraded manually if you still want to use it.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/php-formatter-and-templates-for-zend-studio-10-1.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/php-formatter-and-templates-for-zend-studio-10-1.html.twig
index 526aac60..01cf9eb0 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/php-formatter-and-templates-for-zend-studio-10-1.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/php-formatter-and-templates-for-zend-studio-10-1.html.twig
@@ -22,13 +22,13 @@
                 <div class="entry">
 Because Zend donated the Zend Studio's Formatter upstream to the PDT project, the Formatter plugin for Zend Studio 10.1 need to be changed: replace  "com.zend.php" to "org.eclipse.php".
 
-See  the updated file  <a href="http://www.dotkernel.com/download/?did=37" target="_blank" rel="noopener noreferrer">DotKernel PHP Formatter for Zend Studio 10.1</a>
+See  the updated file  <a href="http://www.dotkernel.com/download/?did=37" target="_blank" rel="noopener noreferrer">Dotkernel PHP Formatter for Zend Studio 10.1</a>
 
 About PHP Formatter , see <a href="http://files.zend.com/help/Zend-Studio-10/zend-studio.htm#formatter.htm" target="_blank" rel="noopener noreferrer">http://files.zend.com/help/Zend-Studio-10/zend-studio.htm#formatter.htm</a>
 
 &nbsp;
 
-Also, we created the templates file for Zend Studio 10.1 , according to DotKernel coding standard, see the file: <a href="http://www.dotkernel.com/download/?did=38" target="_blank" rel="noopener noreferrer">Templates for Zend Studio</a>
+Also, we created the templates file for Zend Studio 10.1 , according to Dotkernel coding standard, see the file: <a href="http://www.dotkernel.com/download/?did=38" target="_blank" rel="noopener noreferrer">Templates for Zend Studio</a>
 
 About Templates in Zend Studio and how to import/export: <a href="http://files.zend.com/help/Zend-Studio-10/zend-studio.htm#templates.htm" target="_blank" rel="noopener noreferrer">http://files.zend.com/help/Zend-Studio-10/zend-studio.htm#templates.htm</a>
 
@@ -44,9 +44,9 @@ About Templates in Zend Studio and how to import/export: <a href="http://files.z
         </div>
     </details>
     <details class="acc">
-        <summary>Where can I get DotKernel's updated Formatter and Templates files for Zend Studio 10.1? <span class="chev">+</span></summary>
+        <summary>Where can I get Dotkernel's updated Formatter and Templates files for Zend Studio 10.1? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">The updated PHP Formatter file for Zend Studio 10.1 and a templates file built according to the DotKernel coding standard are both available as downloads linked in the article.</p>
+            <p class="mb-0">The updated PHP Formatter file for Zend Studio 10.1 and a templates file built according to the Dotkernel coding standard are both available as downloads linked in the article.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/scientia-mobile-licensed-its-wurfl-cloud-php-library-to-dotkernel-1-6.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/scientia-mobile-licensed-its-wurfl-cloud-php-library-to-dotkernel-1-6.html.twig
index 259ac75e..b5367af7 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/scientia-mobile-licensed-its-wurfl-cloud-php-library-to-dotkernel-1-6.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/scientia-mobile-licensed-its-wurfl-cloud-php-library-to-dotkernel-1-6.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/scientia-mobile-licensed-its-wurfl-cloud-php-library-to-dotkernel-1-6.jsonld.twig') }} {% endblock %}
 
-{% block title %}Scientia Mobile licensed its Wurfl Cloud PHP library to DotKernel 1.6{% endblock %}
+{% block title %}Scientia Mobile licensed its Wurfl Cloud PHP library to Dotkernel 1.6{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,19 +20,19 @@
 
             <article class="article">
                 <div class="entry">
-In the DotKernel version 1.6.0 , released on May 16th, 2012 we have removed the GPL'ed WURFL PHP library , as the code it was obsolete anyway and also the structure of the XML file was changed.
+In the Dotkernel version 1.6.0 , released on May 16th, 2012 we have removed the GPL'ed WURFL PHP library , as the code it was obsolete anyway and also the structure of the XML file was changed.
 
 Instead , we implemented the <a title="Scientia Mobile" href="http://www.scientiamobile.com/" target="_blank" rel="noopener noreferrer">Scientia Mobile's </a>WURFL Cloud PHP  library .
 
 <!--more-->
 
-Instructions about how to signup for a free account , and how to setup your API key can be found <a title="Mbile Devices in DotKernel" href="http://www.dotkernel.com/dotkernel/detecting-mobile-devices-in-dotkernel-1-6/" target="_blank" rel="noopener noreferrer">here .</a>
+Instructions about how to signup for a free account , and how to setup your API key can be found <a title="Mbile Devices in Dotkernel" href="http://www.dotkernel.com/dotkernel/detecting-mobile-devices-in-dotkernel-1-6/" target="_blank" rel="noopener noreferrer">here .</a>
 
-In the near future, we will create a template in Wurfl Cloud API control panel,  at Scientia Mobile,  ready to be used in DotKernel implementations.
+In the near future, we will create a template in Wurfl Cloud API control panel,  at Scientia Mobile,  ready to be used in Dotkernel implementations.
 
 Also, we got a special license, please read the file:
 
-<a href="http://websvn.dotkernel.net/filedetails.php?repname=DotKernel&amp;path=%2Ftrunk%2Flibrary%2FWurflCloud%2FLICENSE.txt" target="_blank" rel="noopener noreferrer">dotkernel/library/WurflCloud/LICENSE.txt</a> and notice Dotkernel mention
+<a href="http://websvn.dotkernel.net/filedetails.php?repname=Dotkernel&amp;path=%2Ftrunk%2Flibrary%2FWurflCloud%2FLICENSE.txt" target="_blank" rel="noopener noreferrer">dotkernel/library/WurflCloud/LICENSE.txt</a> and notice Dotkernel mention
 <blockquote class="blockquote border-start border-4 ps-3 text-muted my-3">License is non-transferable, conditioned, limited to the version
 received and to the use and distribution of this software only in connection
 with the <strong>Dotkernel</strong> software framework, and does not allow making derivative works
@@ -44,25 +44,25 @@ and regardless of whether the code is not obfuscated.</blockquote>
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Why was the WURFL PHP library removed from DotKernel 1.6.0? <span class="chev">+</span></summary>
+        <summary>Why was the WURFL PHP library removed from Dotkernel 1.6.0? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">In DotKernel 1.6.0, released on May 16th, 2012, the GPL'ed WURFL PHP library was removed because the code was obsolete anyway and the structure of the XML file had changed.</p>
+            <p class="mb-0">In Dotkernel 1.6.0, released on May 16th, 2012, the GPL'ed WURFL PHP library was removed because the code was obsolete anyway and the structure of the XML file had changed.</p>
         </div>
     </details>
     <details class="acc">
         <summary>What replaced the old WURFL PHP library? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel implemented Scientia Mobile's WURFL Cloud PHP library instead.</p>
+            <p class="mb-0">Dotkernel implemented Scientia Mobile's WURFL Cloud PHP library instead.</p>
         </div>
     </details>
     <details class="acc">
         <summary>Where can I find instructions to set up the WURFL Cloud API key? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Instructions on how to sign up for a free account and set up your API key are linked in the article, pointing to the "Detecting Mobile Devices in DotKernel 1.6" article.</p>
+            <p class="mb-0">Instructions on how to sign up for a free account and set up your API key are linked in the article, pointing to the "Detecting Mobile Devices in Dotkernel 1.6" article.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What are the terms of DotKernel's special WURFL Cloud license? <span class="chev">+</span></summary>
+        <summary>What are the terms of Dotkernel's special WURFL Cloud license? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">The license is non-transferable, conditioned, limited to the version received, and restricted to use and distribution only in connection with the Dotkernel software framework. It does not allow making derivative works, even when source code is provided or the code is not obfuscated.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/templating-in-dotkernel3.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/templating-in-dotkernel3.html.twig
index c441267a..d22b6b13 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/templating-in-dotkernel3.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/templating-in-dotkernel3.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/templating-in-dotkernel3.jsonld.twig') }} {% endblock %}
 
-{% block title %}Templating in DotKernel3{% endblock %}
+{% block title %}Templating in Dotkernel3{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,10 +20,10 @@
 
             <article class="article">
                 <div class="entry">
-<strong>DotKernel3</strong> aims to improve the DotKernel stack in every way possible, and one of the painpoints in the previous version of DotKernel was the templating engine.
+<strong>Dotkernel3</strong> aims to improve the Dotkernel stack in every way possible, and one of the painpoints in the previous version of Dotkernel was the templating engine.
 Albeit a solid and robust templating engine, it was also 10 years old, and used techniques that's slightly outdated by now.
 
-In DotKernel 3, we made the move to the popular <a href="https://twig.symfony.com/" rel="noopener noreferrer" target="_blank"><strong>Twig Templating Engine</strong></a>, which will allow us to take our templates to a whole new level. It can now be written as HTML code, with some extra Twig tags; It is incredibly powerful and includes features such as:
+In Dotkernel 3, we made the move to the popular <a href="https://twig.symfony.com/" rel="noopener noreferrer" target="_blank"><strong>Twig Templating Engine</strong></a>, which will allow us to take our templates to a whole new level. It can now be written as HTML code, with some extra Twig tags; It is incredibly powerful and includes features such as:
 
 <ul>
 <li>Layouts</li>
@@ -32,7 +32,7 @@ In DotKernel 3, we made the move to the popular <a href="https://twig.symfony.co
 <li>Escaping</li>
 </ul>
 
-The templating engine in <strong>DotKernel3</strong> gives you the familiarity of HTML with the overview and convenience of PHP.
+The templating engine in <strong>Dotkernel3</strong> gives you the familiarity of HTML with the overview and convenience of PHP.
 
 You can read the official documentation here: <a href="https://docs.dotkernel.com/Prerequisites/Templates" rel="noopener noreferrer" target="_blank"><strong>Templates</strong></a>
 
@@ -40,25 +40,25 @@ You can read the official documentation here: <a href="https://docs.dotkernel.co
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Which templating engine does DotKernel3 use? <span class="chev">+</span></summary>
+        <summary>Which templating engine does Dotkernel3 use? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel3 moved to the popular Twig Templating Engine.</p>
+            <p class="mb-0">Dotkernel3 moved to the popular Twig Templating Engine.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>Why did DotKernel move away from the previous templating engine? <span class="chev">+</span></summary>
+        <summary>Why did Dotkernel move away from the previous templating engine? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">The previous templating engine, although solid and robust, was also 10 years old and used techniques that had become slightly outdated, and it was one of the pain points in the previous version of DotKernel.</p>
+            <p class="mb-0">The previous templating engine, although solid and robust, was also 10 years old and used techniques that had become slightly outdated, and it was one of the pain points in the previous version of Dotkernel.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What features does Twig bring to DotKernel3 templates? <span class="chev">+</span></summary>
+        <summary>What features does Twig bring to Dotkernel3 templates? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Templates can now be written as HTML code with extra Twig tags, and Twig includes features such as layouts, loops, variables, and escaping, giving the familiarity of HTML with the overview and convenience of PHP.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>Where can I read the official Twig templating documentation for DotKernel? <span class="chev">+</span></summary>
+        <summary>Where can I read the official Twig templating documentation for Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">The official documentation is linked in the article at docs.dotkernel.com/Prerequisites/Templates.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/using-dotkernel-with-composer-dependencies.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/using-dotkernel-with-composer-dependencies.html.twig
index aa071d4b..76f6ba75 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/using-dotkernel-with-composer-dependencies.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/using-dotkernel-with-composer-dependencies.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/using-dotkernel-with-composer-dependencies.jsonld.twig') }} {% endblock %}
 
-{% block title %}Using DotKernel with Composer Dependencies{% endblock %}
+{% block title %}Using Dotkernel with Composer Dependencies{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,9 +20,9 @@
 
             <article class="article">
                 <div class="entry">
-This article will cover the external dependency usage VIA composer within DotKernel applications.
+This article will cover the external dependency usage VIA composer within Dotkernel applications.
 
-There is also an article explaining how composer can be added to DotKernel <a href="http://www.dotkernel.com/dotkernel/adding-composer-support-in-your-dotkernel-project" target="_blank" rel="noopener noreferrer">learn more</a>.
+There is also an article explaining how composer can be added to Dotkernel <a href="http://www.dotkernel.com/dotkernel/adding-composer-support-in-your-dotkernel-project" target="_blank" rel="noopener noreferrer">learn more</a>.
 
 Composer automatically loads our dependencies so there is no need to include/require them.
 
@@ -88,13 +88,13 @@ The full examples can be found here:
 
 <a href="http://framework.zend.com/manual/current/en/modules/zend.barcode.creation.html#rendering-a-barcode" target="_blank" rel="noopener noreferrer">Zend Framework 2 - Rendering a barcode</a>
 
-This article works for any <strong>DotKernel 1.x</strong> version if your server is running <strong>PHP &gt;5.4.0.</strong>
+This article works for any <strong>Dotkernel 1.x</strong> version if your server is running <strong>PHP &gt;5.4.0.</strong>
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Do I need to manually include or require Composer dependencies in DotKernel? <span class="chev">+</span></summary>
+        <summary>Do I need to manually include or require Composer dependencies in Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">No. Composer automatically loads dependencies, so there is no need to include or require them yourself.</p>
         </div>
@@ -124,9 +124,9 @@ This article works for any <strong>DotKernel 1.x</strong> version if your server
         </div>
     </details>
     <details class="acc">
-        <summary>What DotKernel and PHP versions does this article apply to? <span class="chev">+</span></summary>
+        <summary>What Dotkernel and PHP versions does this article apply to? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">This article works for any DotKernel 1.x version if your server is running PHP greater than 5.4.0.</p>
+            <p class="mb-0">This article works for any Dotkernel 1.x version if your server is running PHP greater than 5.4.0.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/using-utf8-charset-in-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/using-utf8-charset-in-dotkernel.html.twig
index 66fe3e78..7d09c6f7 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/using-utf8-charset-in-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/using-utf8-charset-in-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/using-utf8-charset-in-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}Using  UTF8 charset in DotKernel{% endblock %}
+{% block title %}Using  UTF8 charset in Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,8 +20,8 @@
 
             <article class="article">
                 <div class="entry">
-In order to use UTF8 encoding in your DotKernel based system, is needed to make some changes in both database structure and in the application.ini file.
-<blockquote class="blockquote border-start border-4 ps-3 text-muted my-3">Those changes are commited into <strong>DotKernel 1.6.0 dev</strong> codebase, which will be released in next days.</blockquote>
+In order to use UTF8 encoding in your Dotkernel based system, is needed to make some changes in both database structure and in the application.ini file.
+<blockquote class="blockquote border-start border-4 ps-3 text-muted my-3">Those changes are commited into <strong>Dotkernel 1.6.0 dev</strong> codebase, which will be released in next days.</blockquote>
 <!--more-->
 <h2>Database</h2>
 set for all tables and columns proper collation , either <strong>utf8_general_ci</strong> or <strong>utf8_bin</strong>
@@ -45,7 +45,7 @@ Those differences happens only on <strong>MySQL</strong> level ( for instance in
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What needs to change to use UTF8 encoding in a DotKernel-based system? <span class="chev">+</span></summary>
+        <summary>What needs to change to use UTF8 encoding in a Dotkernel-based system? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Both the database structure and the application.ini file need changes: all tables and columns must have a proper UTF8 collation (utf8_general_ci or utf8_bin), and application.ini must load the utf8 charset.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/wurfl-cloud-integration-in-dotkernel-1-6-0.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/wurfl-cloud-integration-in-dotkernel-1-6-0.html.twig
index 5e89df38..474f44d4 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/wurfl-cloud-integration-in-dotkernel-1-6-0.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/wurfl-cloud-integration-in-dotkernel-1-6-0.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/wurfl-cloud-integration-in-dotkernel-1-6-0.jsonld.twig') }} {% endblock %}
 
-{% block title %}Wurfl Cloud Integration in DotKernel 1.6.0{% endblock %}
+{% block title %}Wurfl Cloud Integration in Dotkernel 1.6.0{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,26 +20,26 @@
 
             <article class="article">
                 <div class="entry">
-Another new feature in version 1.6.0 of DotKernel is the integration of Wurfl Cloud.
+Another new feature in version 1.6.0 of Dotkernel is the integration of Wurfl Cloud.
 
 Wurfl or Wireless Universal Resource FiLe is coming with a new way to deliver their services of device detection and they named it Wurfl Cloud.
 
-Because of the need to detect mobile devices in DotKernel we have integrated Wurfl Cloud as the default detection method.
+Because of the need to detect mobile devices in Dotkernel we have integrated Wurfl Cloud as the default detection method.
 
 <!--more-->
 
-If you want to see the Wurfl Cloud library you can find it in the library folder of DotKernel.
+If you want to see the Wurfl Cloud library you can find it in the library folder of Dotkernel.
 
-Quick steps to have a functional device detection in DotKernel.
+Quick steps to have a functional device detection in Dotkernel.
 <ul>
     <li>register for an Wurfl Cloud account <a title="Scientia Mobile account register" href="https://www.scientiamobile.com/register" target="_blank" rel="noopener noreferrer">here</a></li>
     <li>choose <strong>device_os</strong> and <strong>mobile_browser</strong> as your capabilities</li>
-    <li>copy your API Key in application.ini in DotKernel</li>
+    <li>copy your API Key in application.ini in Dotkernel</li>
 </ul>
 <pre>>resources.useragent.wurflcloud.api_key = 000000:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</pre>
 Now you can test it by changing the user agent in your browser to a mobile device and access your project. Now you can see that you are redirected to the mobile module.
 
-To see how mobile detection is working in DotKernel read this <a title="Detecting Mobile Devices in DotKernel 1.6.0" href="http://www.dotkernel.com/?p=1465">post</a>.
+To see how mobile detection is working in Dotkernel read this <a title="Detecting Mobile Devices in Dotkernel 1.6.0" href="http://www.dotkernel.com/?p=1465">post</a>.
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
@@ -47,13 +47,13 @@ To see how mobile detection is working in DotKernel read this <a title="Detectin
     <details class="acc" open>
         <summary>What is WURFL Cloud? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">WURFL Cloud is a new way that WURFL (Wireless Universal Resource FiLe) delivers its device detection services. DotKernel integrated it as the default detection method for mobile devices starting with version 1.6.0.</p>
+            <p class="mb-0">WURFL Cloud is a new way that WURFL (Wireless Universal Resource FiLe) delivers its device detection services. Dotkernel integrated it as the default detection method for mobile devices starting with version 1.6.0.</p>
         </div>
     </details>
     <details class="acc">
         <summary>How do I get a functional device detection setup with WURFL Cloud? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Register for a Wurfl Cloud account with Scientia Mobile, choose device_os and mobile_browser as your capabilities, then copy your API key into application.ini in DotKernel.</p>
+            <p class="mb-0">Register for a Wurfl Cloud account with Scientia Mobile, choose device_os and mobile_browser as your capabilities, then copy your API key into application.ini in Dotkernel.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/wurfl-php-api-license-incompatible-with-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/wurfl-php-api-license-incompatible-with-dotkernel.html.twig
index 9f8de9b9..7233a665 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/wurfl-php-api-license-incompatible-with-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/wurfl-php-api-license-incompatible-with-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/wurfl-php-api-license-incompatible-with-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}WURFL PHP API license incompatible with DotKernel{% endblock %}
+{% block title %}WURFL PHP API license incompatible with Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,16 +20,16 @@
 
             <article class="article">
                 <div class="entry">
-We integrated long time ago the WURFL PHP API into DotKernel code base. At that time, the license of that WURFL library was GNU/GPL, which make it perfect compatible with Zend Framework license( <strong>new BSD</strong>) and DotKernel ( <strong>OSL 3.0</strong>). Everybody was happy, users was able to make web applications for them or for their customers without worry about licensing costs at all.
+We integrated long time ago the WURFL PHP API into Dotkernel code base. At that time, the license of that WURFL library was GNU/GPL, which make it perfect compatible with Zend Framework license( <strong>new BSD</strong>) and Dotkernel ( <strong>OSL 3.0</strong>). Everybody was happy, users was able to make web applications for them or for their customers without worry about licensing costs at all.
 
-On June 6th, 2011, the WURFL PHP API library was updated to version 1.3.0. So we updated too the latest DotKernel 1.5.0 ( now in release candidate stage, soon to be released as stable) , without noticing the change on its license, from GNU/GPL to AGPL which suddenly transform it into a 'trial only' library, for "Product evaluation" only.
+On June 6th, 2011, the WURFL PHP API library was updated to version 1.3.0. So we updated too the latest Dotkernel 1.5.0 ( now in release candidate stage, soon to be released as stable) , without noticing the change on its license, from GNU/GPL to AGPL which suddenly transform it into a 'trial only' library, for "Product evaluation" only.
 
 <!--more-->See the official announcement <a href="http://www.scientiamobile.com/site/page/view/products#licenses" target="_blank" rel="noopener noreferrer"><strong>here</strong></a>.
 
 We respect the work of Luca Passani and Steve Kamerman ( thank you and keep up the good work :-) ).
-But we must keep <a href="http://www.dotkernel.com" target="_blank" rel="noopener noreferrer">DotKernel Application Framework</a> free, without such license limitations.  Only thing to do in this stage is :
+But we must keep <a href="http://www.dotkernel.com" target="_blank" rel="noopener noreferrer">Dotkernel Application Framework</a> free, without such license limitations.  Only thing to do in this stage is :
 <ul>
-    <li>remove WURFL PHP API library version 1.3.0 from DotKernel code base</li>
+    <li>remove WURFL PHP API library version 1.3.0 from Dotkernel code base</li>
     <li>integrate back version 1.2.1 which is still GNU/GPL</li>
     <li>we are still collecting device informations, so we will contribute to WURFL XML data which remain free. This file, which represent the data itself, it is and must be the<strong> industry standard</strong></li>
     <li>fork WURFL PHP APi 1.2.1 to a new library maybe ?</li>
@@ -43,21 +43,21 @@ But we must keep <a href="http://www.dotkernel.com" target="_blank" rel="noopene
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Why did the WURFL PHP API license become incompatible with DotKernel? <span class="chev">+</span></summary>
+        <summary>Why did the WURFL PHP API license become incompatible with Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">The WURFL PHP API used to be licensed under GNU/GPL, compatible with both Zend Framework's new BSD license and DotKernel's OSL 3.0 license. On June 6th, 2011, version 1.3.0 of the library changed its license to AGPL, turning it into a "trial only" library for product evaluation, which is incompatible with keeping DotKernel free.</p>
+            <p class="mb-0">The WURFL PHP API used to be licensed under GNU/GPL, compatible with both Zend Framework's new BSD license and Dotkernel's OSL 3.0 license. On June 6th, 2011, version 1.3.0 of the library changed its license to AGPL, turning it into a "trial only" library for product evaluation, which is incompatible with keeping Dotkernel free.</p>
         </div>
     </details>
     <details class="acc">
         <summary>Which version introduced the license change, and when? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Version 1.3.0 of the WURFL PHP API, released June 6th, 2011, changed the license from GNU/GPL to AGPL. DotKernel had updated to this version in its 1.5.0 release candidate without noticing the license change.</p>
+            <p class="mb-0">Version 1.3.0 of the WURFL PHP API, released June 6th, 2011, changed the license from GNU/GPL to AGPL. Dotkernel had updated to this version in its 1.5.0 release candidate without noticing the license change.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What did DotKernel do in response to the license change? <span class="chev">+</span></summary>
+        <summary>What did Dotkernel do in response to the license change? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel planned to remove WURFL PHP API version 1.3.0 from its codebase and reintegrate version 1.2.1, which was still GNU/GPL. It also intended to keep contributing to the free WURFL XML data, and considered forking the 1.2.1 library and renaming it to avoid trademark issues.</p>
+            <p class="mb-0">Dotkernel planned to remove WURFL PHP API version 1.3.0 from its codebase and reintegrate version 1.2.1, which was still GNU/GPL. It also intended to keep contributing to the free WURFL XML data, and considered forking the 1.2.1 library and renaming it to avoid trademark issues.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/wurfl-zend-framework-integration-into-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/wurfl-zend-framework-integration-into-dotkernel.html.twig
index fe943257..5d557354 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/wurfl-zend-framework-integration-into-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/wurfl-zend-framework-integration-into-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/wurfl-zend-framework-integration-into-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}WURFL Zend Framework Integration into DotKernel{% endblock %}
+{% block title %}WURFL Zend Framework Integration into Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,9 +20,9 @@
 
             <article class="article">
                 <div class="entry">
-<a href="http://wurfl.sourceforge.net/" target="_blank" rel="noopener noreferrer">WURFL</a> is integrated into DotKernel, using the <a href="http://framework.zend.com/manual/1.11/en/zend.http.user-agent.html" target="_blank" rel="noopener noreferrer">Zend_Http_UserAgent</a> class from the latest release <a href="http://framework.zend.com/download/latest" target="_blank" rel="noopener noreferrer">ZF 1.11.0rc1</a> ( Beta release at the date of this post).
+<a href="http://wurfl.sourceforge.net/" target="_blank" rel="noopener noreferrer">WURFL</a> is integrated into Dotkernel, using the <a href="http://framework.zend.com/manual/1.11/en/zend.http.user-agent.html" target="_blank" rel="noopener noreferrer">Zend_Http_UserAgent</a> class from the latest release <a href="http://framework.zend.com/download/latest" target="_blank" rel="noopener noreferrer">ZF 1.11.0rc1</a> ( Beta release at the date of this post).
 
-The integration of <a href="http://wurfl.sourceforge.net/" target="_blank" rel="noopener noreferrer">WURFL</a> into DotKernel is described below.
+The integration of <a href="http://wurfl.sourceforge.net/" target="_blank" rel="noopener noreferrer">WURFL</a> into Dotkernel is described below.
 
 Download <a href="http://sourceforge.net/projects/wurfl/files/WURFL%20PHP/1.1/wurfl-php-1.1.tar.gz/download" target="_blank" rel="noopener noreferrer">WURFL PHP API</a> and unzip it into folder <strong><em>wurfl-php-1.1</em></strong>
 
@@ -55,7 +55,7 @@ resources.useragent.wurflapi.wurfl_config_file = APPLICATION_PATH "/configs/wurf
 </li>
     <li>Copy the contents of the folder <strong><em>wurfl-php-1.1\WURFL</em> </strong>to <strong><em>library\Wurfl</em></strong><strong> </strong></li>
 </ul>
-<a href="http://wurfl.sourceforge.net/" target="_blank" rel="noopener noreferrer">WURFL</a> is integrated into DotKernel in the mobile module, but to access WURFL configuration, use
+<a href="http://wurfl.sourceforge.net/" target="_blank" rel="noopener noreferrer">WURFL</a> is integrated into Dotkernel in the mobile module, but to access WURFL configuration, use
 <pre>>$userAgent = new Zend_Http_UserAgent($config-&gt;resources-&gt;useragent);
 $device = $userAgent-&gt;getDevice();</pre>
 <em>$userAgent-&gt;getDevice()</em> returns all the relevant information about the current user agent <em>($_SERVER['HTTP_USER_AGENT'])</em>
@@ -64,13 +64,13 @@ $device = $userAgent-&gt;getDevice();</pre>
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Which Zend Framework class is used to integrate WURFL into DotKernel? <span class="chev">+</span></summary>
+        <summary>Which Zend Framework class is used to integrate WURFL into Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">WURFL is integrated using the Zend_Http_UserAgent class from Zend Framework 1.11.0rc1 (the beta release at the time of the post).</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What is the first step to integrate WURFL into DotKernel? <span class="chev">+</span></summary>
+        <summary>What is the first step to integrate WURFL into Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Download the WURFL PHP API and unzip it into a folder named wurfl-php-1.1.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/zend-auth-and-zend-acl-integrated-in-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/zend-auth-and-zend-acl-integrated-in-dotkernel.html.twig
index 3dcdbfc9..2860ed6d 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/zend-auth-and-zend-acl-integrated-in-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/zend-auth-and-zend-acl-integrated-in-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/zend-auth-and-zend-acl-integrated-in-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}Zend_Auth and Zend_Acl integrated in DotKernel{% endblock %}
+{% block title %}Zend_Auth and Zend_Acl integrated in Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-<a href="http://framework.zend.com/manual/en/zend.auth.html" target="_blank" rel="noopener noreferrer">Zend_Auth</a> and <a href="http://framework.zend.com/manual/en/zend.acl.html" target="_blank" rel="noopener noreferrer">Zend_Acl</a> have been integrated into the DotKernel, starting with version 1.5.0
+<a href="http://framework.zend.com/manual/en/zend.auth.html" target="_blank" rel="noopener noreferrer">Zend_Auth</a> and <a href="http://framework.zend.com/manual/en/zend.acl.html" target="_blank" rel="noopener noreferrer">Zend_Acl</a> have been integrated into the Dotkernel, starting with version 1.5.0
 
 With the integration of these two major components for user authorization and access we completely refactored the User and Admin models by using <em>Dot_Auth</em> and <em>Dot_Acl</em> classes.
 
@@ -37,7 +37,7 @@ The <em>Dot_Auth</em> class authenticates the user by checking the database –
         return $authAdapter;
     }</pre>
 ACL roles (user types) and permissions are configured in the <em>configs/acl/role.xml </em>file.
-In DotKernel there are 3 roles: <em>guest</em>, <em>user</em> and <em>admin</em>.
+In Dotkernel there are 3 roles: <em>guest</em>, <em>user</em> and <em>admin</em>.
 The resources for ACL are taken from <em>configs/router.xml</em> – see <em>controllers</em> tag.
 
 The <em>Dot_Acl</em> class
@@ -70,9 +70,9 @@ $dotAuth-&gt;checkIdentity('user');</pre>
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>When were Zend_Auth and Zend_Acl integrated into DotKernel? <span class="chev">+</span></summary>
+        <summary>When were Zend_Auth and Zend_Acl integrated into Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Zend_Auth and Zend_Acl were integrated starting with DotKernel version 1.5.0, as part of a refactor of the User and Admin models using the new Dot_Auth and Dot_Acl classes.</p>
+            <p class="mb-0">Zend_Auth and Zend_Acl were integrated starting with Dotkernel version 1.5.0, as part of a refactor of the User and Admin models using the new Dot_Auth and Dot_Acl classes.</p>
         </div>
     </details>
     <details class="acc">
@@ -82,9 +82,9 @@ $dotAuth-&gt;checkIdentity('user');</pre>
         </div>
     </details>
     <details class="acc">
-        <summary>What roles exist for ACL in DotKernel? <span class="chev">+</span></summary>
+        <summary>What roles exist for ACL in Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel defines 3 ACL roles (user types): guest, user, and admin. These roles and their permissions are configured in the configs/acl/role.xml file.</p>
+            <p class="mb-0">Dotkernel defines 3 ACL roles (user types): guest, user, and admin. These roles and their permissions are configured in the configs/acl/role.xml file.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/zend-console-implementation-in-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/zend-console-implementation-in-dotkernel.html.twig
index e53d2c06..2fbea5f0 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/zend-console-implementation-in-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/zend-console-implementation-in-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/zend-console-implementation-in-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}Zend_Console implementation in DotKernel{% endblock %}
+{% block title %}Zend_Console implementation in Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-Starting with 1.5, DotKernel has a Console bootstrap to easily run PHP scripts from the command line. The most common use for this is to be able to run cron jobs without using wget and going through Apache.
+Starting with 1.5, Dotkernel has a Console bootstrap to easily run PHP scripts from the command line. The most common use for this is to be able to run cron jobs without using wget and going through Apache.
 
 <!--more-->
 
@@ -33,7 +33,7 @@ Currently there are two command line arguments:
 </ul>
 Any other arguments set when calling the script will be available in the controller in the $registry-&gt;arguments array.
 
-The controller bundled with DotKernel has two example actions, "count-users" which demonstrates how to interact with models, and "send-newsletter" which reads the newsletter from the command line.
+The controller bundled with Dotkernel has two example actions, "count-users" which demonstrates how to interact with models, and "send-newsletter" which reads the newsletter from the command line.
 <h2>Examples</h2>
 <pre>>/var/www/vhosts/example.com/httpdocs/Cron/index.php -e staging -a count-users</pre>
 <pre>>/var/www/vhosts/example.com/httpdocs/Cron/index.php -e staging -a send-newsletter "test newsletter"</pre>
@@ -42,9 +42,9 @@ The controller bundled with DotKernel has two example actions, "count-users" whi
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What is the purpose of the Console bootstrap in DotKernel? <span class="chev">+</span></summary>
+        <summary>What is the purpose of the Console bootstrap in Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Starting with version 1.5, DotKernel has a Console bootstrap to easily run PHP scripts from the command line, most commonly used to run cron jobs without using wget or going through Apache.</p>
+            <p class="mb-0">Starting with version 1.5, Dotkernel has a Console bootstrap to easily run PHP scripts from the command line, most commonly used to run cron jobs without using wget or going through Apache.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/zend-framework-dropped-integration-of-wurfl-adapter.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/zend-framework-dropped-integration-of-wurfl-adapter.html.twig
index 68a62f7a..8fcdc4f9 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/zend-framework-dropped-integration-of-wurfl-adapter.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/zend-framework-dropped-integration-of-wurfl-adapter.html.twig
@@ -34,7 +34,7 @@ to change code when upgrading to ZF 1.12.0, or grab the WURFL adapter
 from a previous version.</blockquote>
 So its a good moment to check the old or current projects, and proceed.
 
-DotKernel framework is using its own WURFL adapter, so this will not affect projects built with it .
+Dotkernel framework is using its own WURFL adapter, so this will not affect projects built with it .
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
@@ -46,9 +46,9 @@ DotKernel framework is using its own WURFL adapter, so this will not affect proj
         </div>
     </details>
     <details class="acc">
-        <summary>Does this change affect projects built with DotKernel? <span class="chev">+</span></summary>
+        <summary>Does this change affect projects built with Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">No. DotKernel uses its own WURFL adapter, so the removal of the WURFL adapter from Zend_Http_UserAgent in ZF 1.12.0 will not affect projects built with DotKernel.</p>
+            <p class="mb-0">No. Dotkernel uses its own WURFL adapter, so the removal of the WURFL adapter from Zend_Http_UserAgent in ZF 1.12.0 will not affect projects built with Dotkernel.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/zend-registry-usage-in-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/zend-registry-usage-in-dotkernel.html.twig
index 4ff97a62..b699757c 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/zend-registry-usage-in-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/zend-registry-usage-in-dotkernel.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/zend-registry-usage-in-dotkernel.jsonld.twig') }} {% endblock %}
 
-{% block title %}Zend Registry usage in DotKernel{% endblock %}
+{% block title %}Zend Registry usage in Dotkernel{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-In DotKernel, Zend_Registry will contain the following variables:
+In Dotkernel, Zend_Registry will contain the following variables:
 <ul>
     <li><strong>startTime</strong> - the result of <a title="microtime" href="http://php.net/manual/en/function.microtime.php" target="_blank" rel="noopener noreferrer">microtime()</a> at the beginning of the request</li>
     <li><strong>configuration</strong> - the configuration options loaded from <em>configs/application.ini</em></li>
@@ -48,7 +48,7 @@ You can find more information about Zend_Registry, in the <a href="http://framew
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What variables does Zend_Registry contain in DotKernel? <span class="chev">+</span></summary>
+        <summary>What variables does Zend_Registry contain in Dotkernel? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">It contains startTime (the result of microtime() at the beginning of the request), configuration (loaded from configs/application.ini), router (loaded from configs/router.xml), database (the database adapter), settings (loaded from the database), requestModule/requestController/requestAction, request (additional request variables), seo (loaded from configs/dots/seo.xml), option (loaded from configs/dots/&lt;moduleName&gt;.xml), and session (the session object).</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/zend-session-usage-in-dotkernel-refactor-of-dot-session-class.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/zend-session-usage-in-dotkernel-refactor-of-dot-session-class.html.twig
index 76ac6f21..f18ad602 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/zend-session-usage-in-dotkernel-refactor-of-dot-session-class.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/zend-session-usage-in-dotkernel-refactor-of-dot-session-class.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/zend-session-usage-in-dotkernel-refactor-of-dot-session-class.jsonld.twig') }} {% endblock %}
 
-{% block title %}Zend_Session usage in DotKernel - Refactor of Dot_Session class{% endblock %}
+{% block title %}Zend_Session usage in Dotkernel - Refactor of Dot_Session class{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-We found a strange behaviour of sessions in one of our project, running DotKernel version 1.5.0
+We found a strange behaviour of sessions in one of our project, running Dotkernel version 1.5.0
 
 Similar to this one described <a href="http://trac.elgg.org/ticket/2677" target="_blank" rel="noopener noreferrer">here</a>
 
@@ -35,7 +35,7 @@ Quote from <a href="http://framework.zend.com/manual/1.11/en/zend.session.global
 <blockquote class="blockquote border-start border-4 ps-3 text-muted my-3">If you call the rememberMe() function, then don't use regenerateId(), since the former calls the latter.  If a user has successfully logged into your website, use rememberMe() instead of regenerateId().</blockquote>
 So i removed <strong>regenerateID() </strong>call,   also added 2 new settings in application.ini  related to session : <strong><em>use_only_cookies</em></strong>, which must be <strong>ON</strong> all the time in order to avoid<em> session fixation</em> , and <strong>remember_me_seconds</strong>.
 
-Those small bug fixes will be included in the new DotKernel version 1.5.1 which will be released  next days.
+Those small bug fixes will be included in the new Dotkernel version 1.5.1 which will be released  next days.
 
 <strong>TIP</strong>
 
@@ -49,7 +49,7 @@ if you encounter the same issue in IE8 and IE9 , then with all regret, you need
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What session bug was found in DotKernel 1.5.0? <span class="chev">+</span></summary>
+        <summary>What session bug was found in Dotkernel 1.5.0? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">In unknown circumstances, and only in IE8 and IE9, the session cookie was not saved on the client machine, forcing the user to log in over and over again. The only workaround found was to open a new tab with the same page.</p>
         </div>
@@ -63,7 +63,7 @@ if you encounter the same issue in IE8 and IE9 , then with all regret, you need
     <details class="acc">
         <summary>What was the fix, and where was it released? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">The regenerateID() call was removed, and two new application.ini settings were added: use_only_cookies, which must be ON at all times to avoid session fixation, and remember_me_seconds. These fixes were included in DotKernel version 1.5.1.</p>
+            <p class="mb-0">The regenerateID() call was removed, and two new application.ini settings were added: use_only_cookies, which must be ON at all times to avoid session fixation, and remember_me_seconds. These fixes were included in Dotkernel version 1.5.1.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel/zend-studio-php-formatter-file-for-dotkernel-coding-standard.html.twig b/src/Blog/templates/page/blog-resource/dotkernel/zend-studio-php-formatter-file-for-dotkernel-coding-standard.html.twig
index 245dd6af..2358df60 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel/zend-studio-php-formatter-file-for-dotkernel-coding-standard.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel/zend-studio-php-formatter-file-for-dotkernel-coding-standard.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel/zend-studio-php-formatter-file-for-dotkernel-coding-standard.jsonld.twig') }} {% endblock %}
 
-{% block title %}Zend Studio PHP Formatter file for DotKernel coding standard.{% endblock %}
+{% block title %}Zend Studio PHP Formatter file for Dotkernel coding standard.{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,9 +20,9 @@
 
             <article class="article">
                 <div class="entry">
-<a title="DotKernel PHP Formatter" href="http://www.dotkernel.com/download/?did=34" target="_blank" rel="noopener noreferrer">Here</a> is  uploaded the XML file , ready to be imported in your Zend Studio, version 9.x
+<a title="Dotkernel PHP Formatter" href="http://www.dotkernel.com/download/?did=34" target="_blank" rel="noopener noreferrer">Here</a> is  uploaded the XML file , ready to be imported in your Zend Studio, version 9.x
 
-This file follow DotKernel’s Coding standard.
+This file follow Dotkernel’s Coding standard.
 
 Unzip the file.
 Go to Zend Studio -&gt; Preferences -&gt; PHP -&gt; Code Style -&gt; Formatter
@@ -34,7 +34,7 @@ Import the xml file.
     <details class="acc" open>
         <summary>What is this file for? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">It is an XML file, downloadable from the linked page, that can be imported into Zend Studio (version 9.x) to set up the PHP code formatter so it follows DotKernel's coding standard.</p>
+            <p class="mb-0">It is an XML file, downloadable from the linked page, that can be imported into Zend Studio (version 9.x) to set up the PHP code formatter so it follows Dotkernel's coding standard.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel3/development-report-december-11-2017.html.twig b/src/Blog/templates/page/blog-resource/dotkernel3/development-report-december-11-2017.html.twig
index 2017841d..72ef5f6c 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel3/development-report-december-11-2017.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel3/development-report-december-11-2017.html.twig
@@ -20,9 +20,9 @@
 
             <article class="article">
                 <div class="entry">
-This report contains updates about the DotKernel3 documentation.
+This report contains updates about the Dotkernel3 documentation.
 
-We have added the release notes for DotKernel3 <strong>frontend</strong> and <strong>admin</strong>: you can now check the <a href="https://docs.dotkernel.com/Overview/Release-Notes.html" target="_blank" rel="noopener noreferrer">Release Notes</a> page.
+We have added the release notes for Dotkernel3 <strong>frontend</strong> and <strong>admin</strong>: you can now check the <a href="https://docs.dotkernel.com/Overview/Release-Notes.html" target="_blank" rel="noopener noreferrer">Release Notes</a> page.
 
 <a href="https://docs.dotkernel.com/Prerequisites/Webpack.html" target="_blank" rel="noopener noreferrer">Webpack</a> tutorial has been added in the <a href="https://docs.dotkernel.com/Prerequisites/" target="_blank" rel="noopener noreferrer">Prerequisites</a> section.
 
@@ -48,7 +48,7 @@ The <a href="https://docs.dotkernel.com/Guidelines/Documentation-Guidelines/Api
     <details class="acc" open>
         <summary>What documentation updates does this report cover? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Release notes were added for DotKernel3 frontend and admin, a Webpack tutorial was added to the Prerequisites section, and the Api Endpoint Documentation Guidelines were updated with a slightly different layout and some corrections.</p>
+            <p class="mb-0">Release notes were added for Dotkernel3 frontend and admin, a Webpack tutorial was added to the Prerequisites section, and the Api Endpoint Documentation Guidelines were updated with a slightly different layout and some corrections.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel-admin-v4.html.twig b/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel-admin-v4.html.twig
index 0389fffc..63d06b3a 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel-admin-v4.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel-admin-v4.html.twig
@@ -22,7 +22,7 @@
                 <div class="entry">
 <h2>Getting Started with Dotkernel Admin V4</h2>
 
-<p class="mb-3"><strong><a rel="noreferrer noopener" href="https://github.com/dotkernel/admin" target="_blank">DotKernel's PSR-7 Admin</a> </strong> is an application based on <strong><a rel="noreferrer noopener" href="https://getlaminas.org/" target="_blank">Mezzio</a></strong>, with the main purpose of managing and displaying tabular data from one or more databases components.</p>
+<p class="mb-3"><strong><a rel="noreferrer noopener" href="https://github.com/dotkernel/admin" target="_blank">Dotkernel's PSR-7 Admin</a> </strong> is an application based on <strong><a rel="noreferrer noopener" href="https://getlaminas.org/" target="_blank">Mezzio</a></strong>, with the main purpose of managing and displaying tabular data from one or more databases components.</p>
 
 <p class="mb-3">On 19 July 2022 <strong>Dotkernel Admin V4</strong> has been officially released. <strong>Dotkernel Admin V4</strong> comes with various interesting features and overall improvement of the core framework.</p>
 
@@ -219,7 +219,7 @@
     <details class="acc" open>
         <summary>When was Dotkernel Admin V4 released, and what is it built on? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Dotkernel Admin V4 was officially released on 19 July 2022. It's DotKernel's PSR-7 Admin, an application based on Mezzio, mainly for managing and displaying tabular data from one or more database components.</p>
+            <p class="mb-0">Dotkernel Admin V4 was officially released on 19 July 2022. It's Dotkernel's PSR-7 Admin, an application based on Mezzio, mainly for managing and displaying tabular data from one or more database components.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel3-stable-release-version-1-0.html.twig b/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel3-stable-release-version-1-0.html.twig
index 1e6df064..25a3c106 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel3-stable-release-version-1-0.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel3-stable-release-version-1-0.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/dotkernel3/dotkernel3-stable-release-version-1-0.jsonld.twig') }} {% endblock %}
 
-{% block title %}DotKernel3 - Stable Release version 1.0{% endblock %}
+{% block title %}Dotkernel3 - Stable Release version 1.0{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-DotKernel was updated to support <strong><a href="https://docs.zendframework.com/zend-expressive/" target="_blank" rel="noopener noreferrer">Zend Expressive 3</a> </strong>alongside with <strong>PSR-15 </strong>middleware.
+Dotkernel was updated to support <strong><a href="https://docs.zendframework.com/zend-expressive/" target="_blank" rel="noopener noreferrer">Zend Expressive 3</a> </strong>alongside with <strong>PSR-15 </strong>middleware.
 
 We have updated the core packages to support <strong><a href="https://www.php-fig.org/psr/psr-15/" target="_blank" rel="noopener noreferrer">PSR-15 Middleware</a>.</strong>
 
@@ -32,7 +32,7 @@ admin -&gt; <a target="_blank" href="https://packagist.org/packages/dotkernel/ad
 
 <!--more-->
 
-If your project is a DotKernel 3 instance (based on expressive 2), you can migrate your project to Zend Expressive 3 by following <a href="https://www.dotkernel.com/dotkernel3/migrating-dotkernel-3-from-zend-expressive-2-to-zend-expressive-3/" target="_blank" rel="noopener noreferrer">this guide</a>.
+If your project is a Dotkernel 3 instance (based on expressive 2), you can migrate your project to Zend Expressive 3 by following <a href="https://www.dotkernel.com/dotkernel3/migrating-dotkernel-3-from-zend-expressive-2-to-zend-expressive-3/" target="_blank" rel="noopener noreferrer">this guide</a>.
 <h2>What's new</h2>
 <ul>
      <li>Runs on Zend Stratigility / Zend Expressive 3.0</li>
@@ -98,7 +98,7 @@ If your project is a DotKernel 3 instance (based on expressive 2), you can migra
     <details class="acc" open>
         <summary>What is the headline change in this stable release? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel was updated to support Zend Expressive 3 alongside PSR-15 middleware, with the core packages updated to support PSR-15 Middleware, making both frontend and admin easier to migrate.</p>
+            <p class="mb-0">Dotkernel was updated to support Zend Expressive 3 alongside PSR-15 middleware, with the core packages updated to support PSR-15 Middleware, making both frontend and admin easier to migrate.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-admin.html.twig b/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-admin.html.twig
index 15c68b77..7247071b 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-admin.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-admin.html.twig
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-<p class="mb-3">With the release of <strong>PHP 8.3</strong>, the DotKernel team has been working on updating the dependencies in our packages. Eventually, this allowed us to update our Applications as well, starting with the <a href="https://github.com/dotkernel/admin" data-type="link" data-id="https://github.com/dotkernel/admin" target="_blank" rel="noreferrer noopener">Admin</a>, in release <strong>4.3.1</strong></p>
+<p class="mb-3">With the release of <strong>PHP 8.3</strong>, the Dotkernel team has been working on updating the dependencies in our packages. Eventually, this allowed us to update our Applications as well, starting with the <a href="https://github.com/dotkernel/admin" data-type="link" data-id="https://github.com/dotkernel/admin" target="_blank" rel="noreferrer noopener">Admin</a>, in release <strong>4.3.1</strong></p>
 
 <p class="mb-3">There were some issues and backward incompatibilities that we will list below.</p>
 
@@ -141,7 +141,7 @@
 
 <p class="mb-3"></p>
 
-<p class="mb-3">The DotKernel team is focused on the cache that has been removed in the current version because <em>doctrine/cache </em>deleted their cache implementation classes. We are also updating our existing projects to PHP 8.3 and testing the changes on live environments to iron out any other issues.</p>
+<p class="mb-3">The Dotkernel team is focused on the cache that has been removed in the current version because <em>doctrine/cache </em>deleted their cache implementation classes. We are also updating our existing projects to PHP 8.3 and testing the changes on live environments to iron out any other issues.</p>
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
diff --git a/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-api.html.twig b/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-api.html.twig
index 3ed27b2c..2b42d0e7 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-api.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-api.html.twig
@@ -124,7 +124,7 @@
 </ul>
 </li>
 
-<li><strong>Note</strong><ul><li>When upgrading from older versions of DotKernel API (before PHP 8.3), you may need to run <em>composer update</em> and/or install Sodium (run <em>sudo dnf install php-sodium.x86_64</em>)</li>
+<li><strong>Note</strong><ul><li>When upgrading from older versions of Dotkernel API (before PHP 8.3), you may need to run <em>composer update</em> and/or install Sodium (run <em>sudo dnf install php-sodium.x86_64</em>)</li>
 
 <li>Update your queries: replace <em>useQueryCache()</em> with <em>setCacheable()</em> wherever it's used</li>
 </ul>
diff --git a/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-frontend.html.twig b/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-frontend.html.twig
index 6d83c400..9d41b23b 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-frontend.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel3/php-8-3-support-in-dotkernel-frontend.html.twig
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-<p class="mb-3">To be able to take advantage of the support for <strong>PHP 8.3</strong> in the newest packages, the DotKernel team has updated the <a href="https://github.com/dotkernel/frontend" data-type="link" data-id="https://github.com/dotkernel/frontend" target="_blank" rel="noreferrer noopener">Frontend</a> Application to version <strong>4.2.0</strong>. Very much like for the Admin update before it, the Frontend must also remove support for PHP 8.1 and the no-longer-available PhpFileCache class until a replacement is implemented.</p>
+<p class="mb-3">To be able to take advantage of the support for <strong>PHP 8.3</strong> in the newest packages, the Dotkernel team has updated the <a href="https://github.com/dotkernel/frontend" data-type="link" data-id="https://github.com/dotkernel/frontend" target="_blank" rel="noreferrer noopener">Frontend</a> Application to version <strong>4.2.0</strong>. Very much like for the Admin update before it, the Frontend must also remove support for PHP 8.1 and the no-longer-available PhpFileCache class until a replacement is implemented.</p>
 
 <p class="mb-3">The full list of file changes is <a href="https://github.com/dotkernel/frontend/pull/417" data-type="link" data-id="https://github.com/dotkernel/admin/pull/218/files" target="_blank" rel="noreferrer noopener">here</a>.</p>
 
@@ -125,7 +125,7 @@
 </li>
 </ul>
 
-<p class="mb-3">Next on the menu is to implement these changes in the DotKernel Frontend live projects and process the feedback.</p>
+<p class="mb-3">Next on the menu is to implement these changes in the Dotkernel Frontend live projects and process the feedback.</p>
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
@@ -133,7 +133,7 @@
     <details class="acc" open>
         <summary>What update adds PHP 8.3 support to Dotkernel Frontend? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">The DotKernel team updated the Frontend application to version 4.2.0 so it can take advantage of PHP 8.3 support in the newest packages.</p>
+            <p class="mb-0">The Dotkernel team updated the Frontend application to version 4.2.0 so it can take advantage of PHP 8.3 support in the newest packages.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/headless-platform/complementary-admin-in-dotkernel-headless-platform.html.twig b/src/Blog/templates/page/blog-resource/headless-platform/complementary-admin-in-dotkernel-headless-platform.html.twig
index c5af1142..23b8391b 100644
--- a/src/Blog/templates/page/blog-resource/headless-platform/complementary-admin-in-dotkernel-headless-platform.html.twig
+++ b/src/Blog/templates/page/blog-resource/headless-platform/complementary-admin-in-dotkernel-headless-platform.html.twig
@@ -22,7 +22,7 @@
                 <div class="entry">
 <p class="mb-3">The Dotkernel Headless Platform is built with an architecture designed to be easy to maintain and expand indefinitely. Its core components are Dotkernel API and Dotkernel Queue, but the Dotkernel application suite also offers a fully separate, <strong>complementary Admin</strong> application designed to pair seamlessly with Dotkernel API.</p>
 
-<h2><a href="#what-is-dotkernel-admin"></a>What is DotKernel Admin?</h2>
+<h2><a href="#what-is-dotkernel-admin"></a>What is Dotkernel Admin?</h2>
 
 <p class="mb-3"><strong>Dotkernel Admin</strong> is a in separate repository and is a fully-functional, independent application. It's built on top of the same Mezzio + Laminas foundation, very much like Dotkernel API.</p>
 
diff --git a/src/Blog/templates/page/blog-resource/how-to/creating-admin-accounts-in-dotkernel-api.html.twig b/src/Blog/templates/page/blog-resource/how-to/creating-admin-accounts-in-dotkernel-api.html.twig
index acbe1e60..416ad847 100644
--- a/src/Blog/templates/page/blog-resource/how-to/creating-admin-accounts-in-dotkernel-api.html.twig
+++ b/src/Blog/templates/page/blog-resource/how-to/creating-admin-accounts-in-dotkernel-api.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/how-to/creating-admin-accounts-in-dotkernel-api.jsonld.twig') }} {% endblock %}
 
-{% block title %}Creating admin accounts in DotKernel API{% endblock %}
+{% block title %}Creating admin accounts in Dotkernel API{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,9 +20,9 @@
 
             <article class="article">
                 <div class="entry">
-<h2>Creating admin accounts in DotKernel API</h2>
+<h2>Creating admin accounts in Dotkernel API</h2>
 
-<p class="mb-3">Starting from v3, DotKernel API introduces support for admin accounts. In this article we will describe two different methods of creating an admin account.</p>
+<p class="mb-3">Starting from v3, Dotkernel API introduces support for admin accounts. In this article we will describe two different methods of creating an admin account.</p>
 
 <!--more-->
 
@@ -122,7 +122,7 @@
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What are the two ways to create an admin account in DotKernel API? <span class="chev">+</span></summary>
+        <summary>What are the two ways to create an admin account in Dotkernel API? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">You can either call the protected API endpoint <code>POST /admin</code> with a JSON body, or run the terminal command <code>php ./bin/cli.php admin:create</code>.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/how-to/database-migrations-and-how-to-use-them.html.twig b/src/Blog/templates/page/blog-resource/how-to/database-migrations-and-how-to-use-them.html.twig
index 55f9a467..f4eecc8a 100644
--- a/src/Blog/templates/page/blog-resource/how-to/database-migrations-and-how-to-use-them.html.twig
+++ b/src/Blog/templates/page/blog-resource/how-to/database-migrations-and-how-to-use-them.html.twig
@@ -25,7 +25,7 @@ Migrations ease the process of working together on projects, as well as deployin
 
 &nbsp;
 
-A newly released <a href="https://github.com/JapSeyz/Dot-migrations" target="_blank" rel="noopener noreferrer">package</a> for the DotKernel stack integrates migrations and seeders into the application; This is all done via the newly introduced "php dot" command that's available in the DotKernel stack.
+A newly released <a href="https://github.com/JapSeyz/Dot-migrations" target="_blank" rel="noopener noreferrer">package</a> for the Dotkernel stack integrates migrations and seeders into the application; This is all done via the newly introduced "php dot" command that's available in the Dotkernel stack.
 
 This article assumes that you're familiar with the basic concepts of migrations, if you're not, there's an excellent article available <a href="https://medium.com/@JapSeyz/database-migrations-and-why-you-should-use-them-11bfde52d7c2" target="_blank" rel="noopener noreferrer">here</a>
 
@@ -41,7 +41,7 @@ When pushing to production, the deployment script will automatically run the mig
 
 &nbsp;
 <h2>Getting started</h2>
-To setup migrations, simply follow the installation instructions in the package provided for DotKernel.
+To setup migrations, simply follow the installation instructions in the package provided for Dotkernel.
 After the package has been successfully setup, you're ready to go.
 To see the available commands, simply write "<em>php dot</em>" in a console that's located in your project root.
 
@@ -90,7 +90,7 @@ Seeders are created the same way as migrations, and also benefits hugely from be
     <details class="acc" open>
         <summary>What is a database migration? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">A database migration is a change to the database schema. The DotKernel stack integrates migrations (and seeders) via a package that adds the "php dot" command to the application.</p>
+            <p class="mb-0">A database migration is a change to the database schema. The Dotkernel stack integrates migrations (and seeders) via a package that adds the "php dot" command to the application.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/how-to/doctrine-cache-in-mezzio-and-dotkernel.html.twig b/src/Blog/templates/page/blog-resource/how-to/doctrine-cache-in-mezzio-and-dotkernel.html.twig
index ef525666..8c36ec5c 100644
--- a/src/Blog/templates/page/blog-resource/how-to/doctrine-cache-in-mezzio-and-dotkernel.html.twig
+++ b/src/Blog/templates/page/blog-resource/how-to/doctrine-cache-in-mezzio-and-dotkernel.html.twig
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-<h2>Doctrine caching in DotKernel</h2>
+<h2>Doctrine caching in Dotkernel</h2>
 
 <blockquote><p class="mb-3">Following version 2 of doctrine/cache, in 2024 we  published an update to this article here:<a href="https://www.dotkernel.com/dotkernel/doctrine-cache-using-symfony-cache/" target="_blank" rel="noreferrer noopener"> https://www.dotkernel.com/dotkernel/doctrine-cache-using-symfony-cache/</a></p>
 </blockquote>
diff --git a/src/Blog/templates/page/blog-resource/how-to/list-available-endpoints-in-dotkernel-api-using-dot-cli.html.twig b/src/Blog/templates/page/blog-resource/how-to/list-available-endpoints-in-dotkernel-api-using-dot-cli.html.twig
index f328f0aa..2c180f5f 100644
--- a/src/Blog/templates/page/blog-resource/how-to/list-available-endpoints-in-dotkernel-api-using-dot-cli.html.twig
+++ b/src/Blog/templates/page/blog-resource/how-to/list-available-endpoints-in-dotkernel-api-using-dot-cli.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/how-to/list-available-endpoints-in-dotkernel-api-using-dot-cli.jsonld.twig') }} {% endblock %}
 
-{% block title %}List available endpoints in  DotKernel API using dot-cli{% endblock %}
+{% block title %}List available endpoints in  Dotkernel API using dot-cli{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,9 +20,9 @@
 
             <article class="article">
                 <div class="entry">
-<h2>Displaying DotKernel API endpoints using dot-cli</h2>
+<h2>Displaying Dotkernel API endpoints using dot-cli</h2>
 
-<p class="mb-3">Starting from version 3, DotKernel API uses <a href="https://github.com/dotkernel/dot-cli" data-type="URL" data-id="https://github.com/dotkernel/dot-cli" target="_blank" rel="noreferrer noopener">dot-cli</a> to display a list of available endpoints.</p>
+<p class="mb-3">Starting from version 3, Dotkernel API uses <a href="https://github.com/dotkernel/dot-cli" data-type="URL" data-id="https://github.com/dotkernel/dot-cli" target="_blank" rel="noreferrer noopener">dot-cli</a> to display a list of available endpoints.</p>
 
 <h2>Usage</h2>
 
@@ -109,9 +109,9 @@
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What tool does DotKernel API use to list available endpoints? <span class="chev">+</span></summary>
+        <summary>What tool does Dotkernel API use to list available endpoints? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Starting from version 3, DotKernel API uses <a href="https://github.com/dotkernel/dot-cli" target="_blank" rel="noreferrer noopener">dot-cli</a> to display a list of available endpoints.</p>
+            <p class="mb-0">Starting from version 3, Dotkernel API uses <a href="https://github.com/dotkernel/dot-cli" target="_blank" rel="noreferrer noopener">dot-cli</a> to display a list of available endpoints.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/how-to/migrating-dotkernel-3-from-zend-expressive-2-to-zend-expressive-3.html.twig b/src/Blog/templates/page/blog-resource/how-to/migrating-dotkernel-3-from-zend-expressive-2-to-zend-expressive-3.html.twig
index 7bdff9ba..a8592264 100644
--- a/src/Blog/templates/page/blog-resource/how-to/migrating-dotkernel-3-from-zend-expressive-2-to-zend-expressive-3.html.twig
+++ b/src/Blog/templates/page/blog-resource/how-to/migrating-dotkernel-3-from-zend-expressive-2-to-zend-expressive-3.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/how-to/migrating-dotkernel-3-from-zend-expressive-2-to-zend-expressive-3.jsonld.twig') }} {% endblock %}
 
-{% block title %}Migrating DotKernel 3 from Zend Expressive 2 to Zend Expressive 3{% endblock %}
+{% block title %}Migrating Dotkernel 3 from Zend Expressive 2 to Zend Expressive 3{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-This article covers the steps required to migrate a DotKernel 3 instance to the latest Zend Expressive Version.
+This article covers the steps required to migrate a Dotkernel 3 instance to the latest Zend Expressive Version.
 
 <!--more-->
 
@@ -41,7 +41,7 @@ By updating your middleware the <strong>Delegate</strong>s will become <strong>
 If your project only contains controller-based middleware it can be migrated by following the guides below.
 
 &nbsp;
-<h2>DotKernel3 Migration - Expressive 2.0 -&gt; 3.0</h2>
+<h2>Dotkernel3 Migration - Expressive 2.0 -&gt; 3.0</h2>
 &nbsp;
 <h2><a target="_blank" id="user-content-packages" class="anchor" href="https://github.com/dotkernel/admin/blob/master/docs/Migration.md#packages" aria-hidden="true" rel="noopener noreferrer"></a>Packages</h2>
 In <code>composer.json</code> replace the matching repositories with the following:
diff --git a/src/Blog/templates/page/blog-resource/how-to/replacing-dot-console-with-dot-cli-based-on-laminas-cli.html.twig b/src/Blog/templates/page/blog-resource/how-to/replacing-dot-console-with-dot-cli-based-on-laminas-cli.html.twig
index 86b2626e..ebd1271e 100644
--- a/src/Blog/templates/page/blog-resource/how-to/replacing-dot-console-with-dot-cli-based-on-laminas-cli.html.twig
+++ b/src/Blog/templates/page/blog-resource/how-to/replacing-dot-console-with-dot-cli-based-on-laminas-cli.html.twig
@@ -24,7 +24,7 @@
 
 <h2>Implementing dot-cli in your application</h2>
 
-<p class="mb-3">DotKernel's <a href="https://github.com/dotkernel/dot-cli" data-type="URL" data-id="https://github.com/dotkernel/dot-cli" target="_blank" rel="noreferrer noopener">dot-cli</a> package comes as a replacement for <a href="https://github.com/dotkernel/dot-console" data-type="URL" data-id="https://github.com/dotkernel/dot-console" target="_blank" rel="noreferrer noopener">dot-console</a>, which was abandoned after Laminas abandoned their <a href="https://github.com/laminas/laminas-console" data-type="URL" data-id="https://github.com/laminas/laminas-console" target="_blank" rel="noreferrer noopener">laminas-console</a> package, that dot-console was based on.</p>
+<p class="mb-3">Dotkernel's <a href="https://github.com/dotkernel/dot-cli" data-type="URL" data-id="https://github.com/dotkernel/dot-cli" target="_blank" rel="noreferrer noopener">dot-cli</a> package comes as a replacement for <a href="https://github.com/dotkernel/dot-console" data-type="URL" data-id="https://github.com/dotkernel/dot-console" target="_blank" rel="noreferrer noopener">dot-console</a>, which was abandoned after Laminas abandoned their <a href="https://github.com/laminas/laminas-console" data-type="URL" data-id="https://github.com/laminas/laminas-console" target="_blank" rel="noreferrer noopener">laminas-console</a> package, that dot-console was based on.</p>
 
 <!--more-->
 
@@ -62,7 +62,7 @@
 
 <p class="mb-3">The output should look similar to this, containing information on how to start using dot-cli:</p>
 
-<pre>DotKernel CLI 1.0.0<br><br>Usage:<br>  command  <br><br>Options:<br>  -h, --help            Display help for the given command. When no command is given display help for the list command<br>  -q, --quiet           Do not output any message<br>  -V, --version         Display this application version<br>      --ansi            Force ANSI output<br>      --no-ansi         Disable ANSI output<br>  -n, --no-interaction  Do not ask any interactive question<br>  -v|vv|vvv, --verbose  Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug<br><br>Available commands:<br>  help          Display help for a command<br>  list          List commands<br> demo<br>  demo:command  Demo command description.</pre>
+<pre>Dotkernel CLI 1.0.0<br><br>Usage:<br>  command  <br><br>Options:<br>  -h, --help            Display help for the given command. When no command is given display help for the list command<br>  -q, --quiet           Do not output any message<br>  -V, --version         Display this application version<br>      --ansi            Force ANSI output<br>      --no-ansi         Disable ANSI output<br>  -n, --no-interaction  Do not ask any interactive question<br>  -v|vv|vvv, --verbose  Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug<br><br>Available commands:<br>  help          Display help for a command<br>  list          List commands<br> demo<br>  demo:command  Demo command description.</pre>
 
 <h2>Set up command as cronjob</h2>
 
diff --git a/src/Blog/templates/page/blog-resource/how-to/using-postman-for-documentation-in-dotkernel-api-3.html.twig b/src/Blog/templates/page/blog-resource/how-to/using-postman-for-documentation-in-dotkernel-api-3.html.twig
index 991503e8..364b0453 100644
--- a/src/Blog/templates/page/blog-resource/how-to/using-postman-for-documentation-in-dotkernel-api-3.html.twig
+++ b/src/Blog/templates/page/blog-resource/how-to/using-postman-for-documentation-in-dotkernel-api-3.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/how-to/using-postman-for-documentation-in-dotkernel-api-3.jsonld.twig') }} {% endblock %}
 
-{% block title %}Using Postman for documentation  in DotKernel API 3{% endblock %}
+{% block title %}Using Postman for documentation  in Dotkernel API 3{% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,9 +20,9 @@
 
             <article class="article">
                 <div class="entry">
-<h2>Using Postman documentation in DotKernel API 3</h2>
+<h2>Using Postman documentation in Dotkernel API 3</h2>
 
-<p class="mb-3">Starting from version 3.0 DotKernel API provides it's documentation using <a href="https://www.postman.com/" data-type="URL" data-id="https://www.postman.com/" target="_blank" rel="noreferrer noopener">Postman</a>.</p>
+<p class="mb-3">Starting from version 3.0 Dotkernel API provides it's documentation using <a href="https://www.postman.com/" data-type="URL" data-id="https://www.postman.com/" target="_blank" rel="noreferrer noopener">Postman</a>.</p>
 
 <p class="mb-3">In this article we will go into the details of creating and maintaining your application's documentation.</p>
 
@@ -32,7 +32,7 @@
 
 <p class="mb-3">In order to follow the steps, you will need the following:</p>
 
-<ul><li>a working installation of DotKernel API 3</li><li>download and install Postman from their <a href="https://www.postman.com/downloads/" target="_blank" rel="noreferrer noopener">download page</a>.</li></ul>
+<ul><li>a working installation of Dotkernel API 3</li><li>download and install Postman from their <a href="https://www.postman.com/downloads/" target="_blank" rel="noreferrer noopener">download page</a>.</li></ul>
 
 <p class="mb-3"><strong>TIP:</strong> If you don't have a Postman account, we recommend you to create one. This way Postman is able to backup your workspace in the cloud and synchronize it across multiple devices.</p>
 
@@ -40,7 +40,7 @@
 
 <p class="mb-3">For better understanding on how Postman works, we need to run through the "building blocks" of Postman:</p>
 
-<ul><li><strong>Workspace</strong>: is the main container that holds all your collections, APIs, environments etc</li><li><strong>Collection</strong>: holds all requests and dependencies of a project (for example DotKernel API's collection containing all requests)</li><li><strong>Environment</strong>: holds a set of environment-specific variables (for example DotKernel API's environment file cotaining the application URL specific to the development environment)</li><li><strong>Request</strong>: the definition of an API endpoint, including request method, name, description, URL, body, parameters and an example</li></ul>
+<ul><li><strong>Workspace</strong>: is the main container that holds all your collections, APIs, environments etc</li><li><strong>Collection</strong>: holds all requests and dependencies of a project (for example Dotkernel API's collection containing all requests)</li><li><strong>Environment</strong>: holds a set of environment-specific variables (for example Dotkernel API's environment file cotaining the application URL specific to the development environment)</li><li><strong>Request</strong>: the definition of an API endpoint, including request method, name, description, URL, body, parameters and an example</li></ul>
 
 <p class="mb-3">There are more terms to cover, like <em>Mock servers</em>, <em>Monitors</em> etc but they are not relevant yet in our case.</p>
 
@@ -48,7 +48,7 @@
 
 <p class="mb-3">Open Postman (and log in if you have an account), then follow the below steps:</p>
 
-<ul><li>open the import modal by clicking <code>File</code> -&gt; <code>Import</code> (or <code>Ctrl + O</code>)</li><li>inside the modal, make sure you're on the <code>File</code> tab, then click <code>Upload files</code></li><li>navigate to <code>documentation</code> directory of your DotKernel API 3 application and select both of the following files:<ul><li><strong>DotKernel_API.postman_collection.json</strong></li><li><strong>DotKernel_API.postman_environment.json</strong></li></ul></li><li>after clicking <code>Open</code> the modal should show the following:</li></ul>
+<ul><li>open the import modal by clicking <code>File</code> -&gt; <code>Import</code> (or <code>Ctrl + O</code>)</li><li>inside the modal, make sure you're on the <code>File</code> tab, then click <code>Upload files</code></li><li>navigate to <code>documentation</code> directory of your Dotkernel API 3 application and select both of the following files:<ul><li><strong>DotKernel_API.postman_collection.json</strong></li><li><strong>DotKernel_API.postman_environment.json</strong></li></ul></li><li>after clicking <code>Open</code> the modal should show the following:</li></ul>
 
 <pre>Select files to import . 2/2 selected
 NAME                 FORMAT                         IMPORT AS
@@ -59,7 +59,7 @@ NAME                 FORMAT                         IMPORT AS
 
 <p class="mb-3">Under <strong>My Workspace</strong> you should see a tab called <strong>Collections</strong>. Clicking on it should display all your collections, one of them called <code>DotKernel_API</code>. This collection holds all of the provided requests and serves as the documentation of your application.</p>
 
-<p class="mb-3">DotKernel API 3 collection and environment files ar now imported and ready to use.</p>
+<p class="mb-3">Dotkernel API 3 collection and environment files ar now imported and ready to use.</p>
 
 <p class="mb-3">For more information on importing files into Postman, please consult their <a rel="noreferrer noopener" href="https://learning.postman.com/docs/getting-started/importing-and-exporting-data/" data-type="URL" data-id="https://learning.postman.com/docs/getting-started/importing-and-exporting-data/" target="_blank">docs</a>.</p>
 
@@ -93,7 +93,7 @@ VARIABLE               INITIAL VALUE                CURRENT_VALUE
 
 <h2>Features</h2>
 
-<p class="mb-3">The collection provided by DotKernel API 3 comes with some built-in security features. </p>
+<p class="mb-3">The collection provided by Dotkernel API 3 comes with some built-in security features. </p>
 
 <h3>Global security</h3>
 
@@ -135,11 +135,11 @@ VARIABLE               INITIAL VALUE                CURRENT_VALUE
     <details class="acc" open>
         <summary>What are Postman's main "building blocks"? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Workspace (the main container holding all collections, APIs and environments), Collection (holds all requests and dependencies of a project, such as DotKernel API's collection), Environment (holds environment-specific variables, like the application URL), and Request (the definition of an API endpoint, including method, name, description, URL, body, parameters and an example).</p>
+            <p class="mb-0">Workspace (the main container holding all collections, APIs and environments), Collection (holds all requests and dependencies of a project, such as Dotkernel API's collection), Environment (holds environment-specific variables, like the application URL), and Request (the definition of an API endpoint, including method, name, description, URL, body, parameters and an example).</p>
         </div>
     </details>
     <details class="acc">
-        <summary>How do you import DotKernel API's documentation files into Postman? <span class="chev">+</span></summary>
+        <summary>How do you import Dotkernel API's documentation files into Postman? <span class="chev">+</span></summary>
         <div class="acc-body">
             <p class="mb-0">Open the import modal via <code>File -&gt; Import</code> (or <code>Ctrl + O</code>), go to the <code>File</code> tab, click <code>Upload files</code>, then select both <strong>DotKernel_API.postman_collection.json</strong> and <strong>DotKernel_API.postman_environment.json</strong> from the application's <code>documentation</code> directory, and click <code>Import</code>.</p>
         </div>
diff --git a/src/Blog/templates/page/blog-resource/how-to/using-the-urlgenerator-work-in-fastroute.html.twig b/src/Blog/templates/page/blog-resource/how-to/using-the-urlgenerator-work-in-fastroute.html.twig
index f37c1a24..beb2e14f 100644
--- a/src/Blog/templates/page/blog-resource/how-to/using-the-urlgenerator-work-in-fastroute.html.twig
+++ b/src/Blog/templates/page/blog-resource/how-to/using-the-urlgenerator-work-in-fastroute.html.twig
@@ -20,11 +20,11 @@
 
             <article class="article">
                 <div class="entry">
-DotKernel 3 uses <code>FastRoute</code> under the hood, which is an excellent and fast routing package, but it does have some <strong>quirks</strong>.
+Dotkernel 3 uses <code>FastRoute</code> under the hood, which is an excellent and fast routing package, but it does have some <strong>quirks</strong>.
 
 A wrong setup can lead to many headaches, as it's not prominent that the error you're experiencing is from FastRoute, and you may not know where exactly to look for the cause.
 
-To save you some time, here's a how-to for creating and using routes in <code>DotKernel 3</code>.
+To save you some time, here's a how-to for creating and using routes in <code>Dotkernel 3</code>.
 <h2>Declaring routes</h2>
 When defining routes in the <em>routes.php</em> file, they need to follow a specific pattern, a usual route would look like this:
 <pre>>$app-&gt;route('/page', , , 'page');</pre>
diff --git a/src/Blog/templates/page/blog-resource/how-to/what-is-psr-7-and-how-to-use-it.html.twig b/src/Blog/templates/page/blog-resource/how-to/what-is-psr-7-and-how-to-use-it.html.twig
index a5cbf605..8683f4a9 100644
--- a/src/Blog/templates/page/blog-resource/how-to/what-is-psr-7-and-how-to-use-it.html.twig
+++ b/src/Blog/templates/page/blog-resource/how-to/what-is-psr-7-and-how-to-use-it.html.twig
@@ -84,7 +84,7 @@ $body-&gt;write($contents); // stream contains "efabcd"
 </pre><blockquote class="blockquote border-start border-4 ps-3 text-muted my-3"><p class="mb-3">Note: <code>getContents()</code> seeks the stream while reading it, therefore if the second <code>rewind()</code> method call was not present the stream would have resulted in <code>abcdefabcd</code> because the <code>write()</code> method appends to stream if not preceeded by <code>rewind()</code> or <code>seek(0)</code>.</p></blockquote><h4 id="prepending-by-using-contents-as-a-string">Prepending by using contents as a string</h4><pre>>$body = $response-&gt;getBody();
 $body-&gt;rewind(); // or $body-&gt;seek(0);
 $bodyText = $body-&gt;getContends();
-</pre><p class="mb-3">More information can be found in the <a href="https://docs.dotkernel.com/Prerequisites/PSR-7.html">PSR-7 article</a> in<a href="https://docs.dotkernel.com/"> DotKernel3 documentation portal</a>.</p><p class="mb-3">Sources: <a href="http://www.php-fig.org/psr/psr-7/">PSR-7: HTTP messages</a> <a href="https://zendframework.github.io/zend-diactoros/">zend-diactoros</a></p>
+</pre><p class="mb-3">More information can be found in the <a href="https://docs.dotkernel.com/Prerequisites/PSR-7.html">PSR-7 article</a> in<a href="https://docs.dotkernel.com/"> Dotkernel3 documentation portal</a>.</p><p class="mb-3">Sources: <a href="http://www.php-fig.org/psr/psr-7/">PSR-7: HTTP messages</a> <a href="https://zendframework.github.io/zend-diactoros/">zend-diactoros</a></p>
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
diff --git a/src/Blog/templates/page/blog-resource/javascript/intro-to-jquery.html.twig b/src/Blog/templates/page/blog-resource/javascript/intro-to-jquery.html.twig
index d4dd46b8..0b49693c 100644
--- a/src/Blog/templates/page/blog-resource/javascript/intro-to-jquery.html.twig
+++ b/src/Blog/templates/page/blog-resource/javascript/intro-to-jquery.html.twig
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-Starting with the 1.5 release, DotKernel will make the switch from Dojo to jQuery.
+Starting with the 1.5 release, Dotkernel will make the switch from Dojo to jQuery.
 
 On jQuery's website, there's an excellent "<a href="http://docs.jquery.com/Tutorials:Getting_Started_with_jQuery" target="_blank" rel="noopener noreferrer">Getting started with jQuery tutorial</a>", as well as a extensive <a href="http://api.jquery.com/" target="_blank" rel="noopener noreferrer">documentation</a> for the framework, so I'll just go over a few basic concepts and common examples.
 <!--more-->
@@ -83,9 +83,9 @@ The following snippet can be used on a registration form to check whether the us
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Why is DotKernel switching to jQuery? <span class="chev">+</span></summary>
+        <summary>Why is Dotkernel switching to jQuery? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Starting with the 1.5 release, DotKernel makes the switch from Dojo to jQuery.</p>
+            <p class="mb-0">Starting with the 1.5 release, Dotkernel makes the switch from Dojo to jQuery.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/licensing/mit-versus-lgpl-in-practice-dotkernel-case.html.twig b/src/Blog/templates/page/blog-resource/licensing/mit-versus-lgpl-in-practice-dotkernel-case.html.twig
index c213421e..8c298b3f 100644
--- a/src/Blog/templates/page/blog-resource/licensing/mit-versus-lgpl-in-practice-dotkernel-case.html.twig
+++ b/src/Blog/templates/page/blog-resource/licensing/mit-versus-lgpl-in-practice-dotkernel-case.html.twig
@@ -20,7 +20,7 @@
 
             <article class="article">
                 <div class="entry">
-<p class="mb-3">After a recent analysis, we discovered that <strong>one of the upstream packages</strong> we use is <strong>licensed under <a href="https://www.gnu.org/licenses/lgpl-3.0.en.html" data-type="link" data-id="https://www.gnu.org/licenses/lgpl-3.0.en.html" target="_blank" rel="noreferrer noopener">LGPL v3</a></strong>. Even though we at <strong>DotKernel </strong>use the <strong><a href="https://opensource.org/license/mit" data-type="link" data-id="https://opensource.org/license/mit" target="_blank" rel="noreferrer noopener">MIT</a></strong> license for our open source projects, the more restrictive license must be applied to the whole application. We implemented a workaround detailed below.</p>
+<p class="mb-3">After a recent analysis, we discovered that <strong>one of the upstream packages</strong> we use is <strong>licensed under <a href="https://www.gnu.org/licenses/lgpl-3.0.en.html" data-type="link" data-id="https://www.gnu.org/licenses/lgpl-3.0.en.html" target="_blank" rel="noreferrer noopener">LGPL v3</a></strong>. Even though we at <strong>Dotkernel </strong>use the <strong><a href="https://opensource.org/license/mit" data-type="link" data-id="https://opensource.org/license/mit" target="_blank" rel="noreferrer noopener">MIT</a></strong> license for our open source projects, the more restrictive license must be applied to the whole application. We implemented a workaround detailed below.</p>
 
 <h2>Detailing the problem</h2>
 
@@ -28,9 +28,9 @@
 
 <h2>The solution</h2>
 
-<p class="mb-3">Some companies explicitly steer clear of scenarios of this nature and DotKernel has decided to do the same. Our <strong>solution </strong>for DotKernel applications and libraries is to <strong>discard the use of 3rd party packages with LGPL v3</strong>. In this particular case we used the <strong>matomo/device-detector</strong> package in our <a href="https://github.com/dotkernel/dot-user-agent-sniffer" data-type="link" data-id="https://github.com/dotkernel/dot-user-agent-sniffer" target="_blank" rel="noreferrer noopener"><strong>dotkernel/dot-user-agent-sniffer</strong></a> package for the purpose of identifying the user agent and using the results in internal reports.</p>
+<p class="mb-3">Some companies explicitly steer clear of scenarios of this nature and Dotkernel has decided to do the same. Our <strong>solution </strong>for Dotkernel applications and libraries is to <strong>discard the use of 3rd party packages with LGPL v3</strong>. In this particular case we used the <strong>matomo/device-detector</strong> package in our <a href="https://github.com/dotkernel/dot-user-agent-sniffer" data-type="link" data-id="https://github.com/dotkernel/dot-user-agent-sniffer" target="_blank" rel="noreferrer noopener"><strong>dotkernel/dot-user-agent-sniffer</strong></a> package for the purpose of identifying the user agent and using the results in internal reports.</p>
 
-<p class="mb-3">ALL of <strong><a href="https://github.com/dotkernel" data-type="link" data-id="https://github.com/dotkernel" target="_blank" rel="noreferrer noopener">DotKernel's</a> </strong>packages are licensed under <strong>MIT </strong>which <strong>has no restrictions</strong> regarding the <strong>source code</strong>, other than keeping the license and copyright notice in a file within each package. Other non-restrictive licenses include Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0 and OSL-3.0. Some of them are used by the dependencies in DotKernel’s packages instead of MIT, but are still deemed acceptable.</p>
+<p class="mb-3">ALL of <strong><a href="https://github.com/dotkernel" data-type="link" data-id="https://github.com/dotkernel" target="_blank" rel="noreferrer noopener">Dotkernel's</a> </strong>packages are licensed under <strong>MIT </strong>which <strong>has no restrictions</strong> regarding the <strong>source code</strong>, other than keeping the license and copyright notice in a file within each package. Other non-restrictive licenses include Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0 and OSL-3.0. Some of them are used by the dependencies in Dotkernel’s packages instead of MIT, but are still deemed acceptable.</p>
 
 <h2>The resolution</h2>
 
@@ -38,7 +38,7 @@
 
 <h2>Important note</h2>
 
-<p class="mb-3"><strong>Warning: Any application using dotkernel/dot-user-agent-sniffer with a version lower than 3.4.0 is still a legal liability</strong>. We at DotKernel will not abandon the issue as is, but are looking into a solution to bring back the device detector functionality in the future under a less restrictive license. For now we will not include dotkernel/dot-user-agent-sniffer in any of our applications by default.</p>
+<p class="mb-3"><strong>Warning: Any application using dotkernel/dot-user-agent-sniffer with a version lower than 3.4.0 is still a legal liability</strong>. We at Dotkernel will not abandon the issue as is, but are looking into a solution to bring back the device detector functionality in the future under a less restrictive license. For now we will not include dotkernel/dot-user-agent-sniffer in any of our applications by default.</p>
 
 <p class="mb-3">Rob Allen has created an automation to check the licenses of installed packages. You can follow his article <a href="https://akrabat.com/check-licenses-of-composer-dependencies/" data-type="link" data-id="https://akrabat.com/check-licenses-of-composer-dependencies/" target="_blank" rel="noreferrer noopener">here</a>.</p>
 
@@ -46,21 +46,21 @@
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>Why did DotKernel need a workaround for this package? <span class="chev">+</span></summary>
+        <summary>Why did Dotkernel need a workaround for this package? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">An analysis found that an upstream package, matomo/device-detector, was licensed under LGPL v3, which requires developers to share their derivative code publicly. Since DotKernel's own projects use the MIT license, and the more restrictive license would have to apply to the whole application, this conflicted with contractual obligations to keep client code business and enterprise friendly.</p>
+            <p class="mb-0">An analysis found that an upstream package, matomo/device-detector, was licensed under LGPL v3, which requires developers to share their derivative code publicly. Since Dotkernel's own projects use the MIT license, and the more restrictive license would have to apply to the whole application, this conflicted with contractual obligations to keep client code business and enterprise friendly.</p>
         </div>
     </details>
     <details class="acc">
         <summary>Where was the LGPL v3 package being used? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">The matomo/device-detector package was used in DotKernel's dot-user-agent-sniffer package to identify the user agent and use the results in internal reports.</p>
+            <p class="mb-0">The matomo/device-detector package was used in Dotkernel's dot-user-agent-sniffer package to identify the user agent and use the results in internal reports.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>What solution did DotKernel adopt? <span class="chev">+</span></summary>
+        <summary>What solution did Dotkernel adopt? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel decided to discard the use of third-party packages licensed under LGPL v3. All of DotKernel's own packages are licensed under MIT, which has no restrictions on the source code other than keeping the license and copyright notice in a file within each package. Other non-restrictive licenses considered acceptable include Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0 and OSL-3.0.</p>
+            <p class="mb-0">Dotkernel decided to discard the use of third-party packages licensed under LGPL v3. All of Dotkernel's own packages are licensed under MIT, which has no restrictions on the source code other than keeping the license and copyright notice in a file within each package. Other non-restrictive licenses considered acceptable include Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0 and OSL-3.0.</p>
         </div>
     </details>
     <details class="acc">
@@ -72,7 +72,7 @@
     <details class="acc">
         <summary>Is it still risky to use an older version of dot-user-agent-sniffer? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Yes. Any application using dotkernel/dot-user-agent-sniffer with a version lower than 3.4.0 is still a legal liability. DotKernel states it will not include dotkernel/dot-user-agent-sniffer in any of its applications by default for now, while it looks into bringing back the device detector functionality under a less restrictive license in the future.</p>
+            <p class="mb-0">Yes. Any application using dotkernel/dot-user-agent-sniffer with a version lower than 3.4.0 is still a legal liability. Dotkernel states it will not include dotkernel/dot-user-agent-sniffer in any of its applications by default for now, while it looks into bringing back the device detector functionality under a less restrictive license in the future.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/php-development/better-unicode-support-in-mysql-5-5-utf8mb4.html.twig b/src/Blog/templates/page/blog-resource/php-development/better-unicode-support-in-mysql-5-5-utf8mb4.html.twig
index 0b9ecadc..7a307321 100644
--- a/src/Blog/templates/page/blog-resource/php-development/better-unicode-support-in-mysql-5-5-utf8mb4.html.twig
+++ b/src/Blog/templates/page/blog-resource/php-development/better-unicode-support-in-mysql-5-5-utf8mb4.html.twig
@@ -23,7 +23,7 @@
 Beginning with version 5.5 of MySQL , <strong>utf8mb4 </strong> character set was introduced, in order to better support <strong>Unicode</strong>.
 Further reading: <a href="http://mzsanford.com/blog/mysql-and-unicode/" target="_blank" rel="noopener noreferrer">MySQL and Unicode</a> , also directly related to <a href="http://www.phptherightway.com/#php_and_utf8" target="_blank" rel="noopener noreferrer">PHP</a>
 
-Sample dk.sql file, part of DotKernel framework, was updated in <a title="Revision 793" href="http://websvn.dotkernel.net/filedetails.php?repname=DotKernel&amp;path=%2Ftrunk%2Fdot_kernel.sql&amp;rev=793&amp;peg=793" target="_blank" rel="noopener noreferrer">revision 793</a>
+Sample dk.sql file, part of Dotkernel framework, was updated in <a title="Revision 793" href="http://websvn.dotkernel.net/filedetails.php?repname=Dotkernel&amp;path=%2Ftrunk%2Fdot_kernel.sql&amp;rev=793&amp;peg=793" target="_blank" rel="noopener noreferrer">revision 793</a>
 
 Only one downside , is not possible to use anymore VARCHAR(255), as you will get the error:
 <pre>>#1071 - Specified key was too long; max key length is 767 bytes</pre>
diff --git a/src/Blog/templates/page/blog-resource/php-development/database-seeding-doctrine-data-fixtures-vs-phinx.html.twig b/src/Blog/templates/page/blog-resource/php-development/database-seeding-doctrine-data-fixtures-vs-phinx.html.twig
index efd11657..f0bd1349 100644
--- a/src/Blog/templates/page/blog-resource/php-development/database-seeding-doctrine-data-fixtures-vs-phinx.html.twig
+++ b/src/Blog/templates/page/blog-resource/php-development/database-seeding-doctrine-data-fixtures-vs-phinx.html.twig
@@ -26,7 +26,7 @@
 
 <p class="mb-3">Seeding the database the right way is no easy feat, and we will see why.</p>
 
-<p class="mb-3">Previous versions of <strong>DotKernel 3</strong> used <a href="https://github.com/cakephp" target="_blank" rel="noreferrer noopener">cakephp</a>/<strong><a href="https://github.com/cakephp/phinx" target="_blank" rel="noreferrer noopener">phinx</a></strong> for seeding the database. While the package did a great job at populating the database, we wanted more. We wanted more flexibility - so we started to search for alternatives.</p>
+<p class="mb-3">Previous versions of <strong>Dotkernel 3</strong> used <a href="https://github.com/cakephp" target="_blank" rel="noreferrer noopener">cakephp</a>/<strong><a href="https://github.com/cakephp/phinx" target="_blank" rel="noreferrer noopener">phinx</a></strong> for seeding the database. While the package did a great job at populating the database, we wanted more. We wanted more flexibility - so we started to search for alternatives.</p>
 
 <p class="mb-3">Because we are using Doctrine as our database abstraction layer, the obvious choice was to give <a href="https://github.com/doctrine/data-fixtures" data-type="URL" data-id="https://github.com/doctrine/data-fixtures" target="_blank" rel="noreferrer noopener">doctrine/data-fixtures</a> a shot and use it as our database seeder, instead of phinx - but there's a catch.</p>
 
@@ -40,7 +40,7 @@
 
 <h3>NOTE: </h3>
 
-<p class="mb-3">The package <a rel="noreferrer noopener" href="https://github.com/dotkernel/dot-data-fixtures" target="_blank">dotkernel/dot-data-fixture</a>  does <strong>NOT</strong> depend on other DotKernel packages. The only dependency is <strong>Doctrine</strong> </p>
+<p class="mb-3">The package <a rel="noreferrer noopener" href="https://github.com/dotkernel/dot-data-fixtures" target="_blank">dotkernel/dot-data-fixture</a>  does <strong>NOT</strong> depend on other Dotkernel packages. The only dependency is <strong>Doctrine</strong> </p>
 
 <h2>Installation</h2>
 
diff --git a/src/Blog/templates/page/blog-resource/php-development/mezzio-app-development-in-wsl2.html.twig b/src/Blog/templates/page/blog-resource/php-development/mezzio-app-development-in-wsl2.html.twig
index 40f984eb..3cbdd8f2 100644
--- a/src/Blog/templates/page/blog-resource/php-development/mezzio-app-development-in-wsl2.html.twig
+++ b/src/Blog/templates/page/blog-resource/php-development/mezzio-app-development-in-wsl2.html.twig
@@ -20,9 +20,9 @@
 
             <article class="article">
                 <div class="entry">
-<h2>Install a Mezzio app (DotKernel API) using WSL2</h2>
+<h2>Install a Mezzio app (Dotkernel API) using WSL2</h2>
 
-<p class="mb-3">This article will run you through the steps of installing a Mezzio application (DotKernel API) in <strong>WSL2 </strong>and run it on <strong>Ubuntu 20.04 LTS</strong>.</p>
+<p class="mb-3">This article will run you through the steps of installing a Mezzio application (Dotkernel API) in <strong>WSL2 </strong>and run it on <strong>Ubuntu 20.04 LTS</strong>.</p>
 
 <h3>Step 1:</h3>
 
@@ -42,7 +42,7 @@
 
 <pre><code>cd /home/<em>your-username</em>/projects/<em>your-virtualhost</em></code></pre>
 
-<p class="mb-3">Install DotKernel API, by following <a href="https://github.com/dotkernel/api" target="_blank" rel="noreferrer noopener">this guide</a>.</p>
+<p class="mb-3">Install Dotkernel API, by following <a href="https://github.com/dotkernel/api" target="_blank" rel="noreferrer noopener">this guide</a>.</p>
 
 <p class="mb-3">Make sure your <code>data</code> and <code>log</code> directories are writable by changing their permissions, as described <a rel="noreferrer noopener" href="https://github.com/dotkernel/development/blob/main/wsl/HELP.md#fix-common-permission-issues" target="_blank">here</a>.</p>
 
@@ -62,7 +62,7 @@
     <details class="acc" open>
         <summary>What does this guide help you accomplish? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">It walks you through installing a Mezzio application (DotKernel API) using WSL2 and running it on Ubuntu 20.04 LTS.</p>
+            <p class="mb-0">It walks you through installing a Mezzio application (Dotkernel API) using WSL2 and running it on Ubuntu 20.04 LTS.</p>
         </div>
     </details>
     <details class="acc">
@@ -78,9 +78,9 @@
         </div>
     </details>
     <details class="acc">
-        <summary>How do you install DotKernel API once the virtual host is ready? <span class="chev">+</span></summary>
+        <summary>How do you install Dotkernel API once the virtual host is ready? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Using your terminal, move into the virtual host directory you created (for example, <code>cd /home/your-username/projects/your-virtualhost</code>), then install DotKernel API by following its guide. Afterward, make sure the <code>data</code> and <code>log</code> directories are writable by changing their permissions, as described in the linked permission-fix guide.</p>
+            <p class="mb-0">Using your terminal, move into the virtual host directory you created (for example, <code>cd /home/your-username/projects/your-virtualhost</code>), then install Dotkernel API by following its guide. Afterward, make sure the <code>data</code> and <code>log</code> directories are writable by changing their permissions, as described in the linked permission-fix guide.</p>
         </div>
     </details>
     <details class="acc">
diff --git a/src/Blog/templates/page/blog-resource/php-development/using-aptana-to-connect-to-dotkernel-tracker-mantis.html.twig b/src/Blog/templates/page/blog-resource/php-development/using-aptana-to-connect-to-dotkernel-tracker-mantis.html.twig
index 9461dc65..990795dd 100644
--- a/src/Blog/templates/page/blog-resource/php-development/using-aptana-to-connect-to-dotkernel-tracker-mantis.html.twig
+++ b/src/Blog/templates/page/blog-resource/php-development/using-aptana-to-connect-to-dotkernel-tracker-mantis.html.twig
@@ -1,7 +1,7 @@
 {% extends '@layout/default.html.twig' %}
 {% block json_ld %} {{ include('@jsonld/php-development/using-aptana-to-connect-to-dotkernel-tracker-mantis.jsonld.twig') }} {% endblock %}
 
-{% block title %}Using Aptana to connect to DotKernel tracker (Mantis){% endblock %}
+{% block title %}Using Aptana to connect to Dotkernel tracker (Mantis){% endblock %}
 
 {% block page_title %}
     {{ include('@partial/title-section.html.twig', {
@@ -20,9 +20,9 @@
 
             <article class="article">
                 <div class="entry">
-In developing <strong>DotKernel</strong> application framework, we needed a tracking system. <strong><a href="http://www.dotkernel.net/">DotKernel Tracker</a></strong> is the place where the <em>bugs</em> are reported, new <em>features</em> are announced and other <em>general tickets</em> are added.
+In developing <strong>Dotkernel</strong> application framework, we needed a tracking system. <strong><a href="http://www.dotkernel.net/">Dotkernel Tracker</a></strong> is the place where the <em>bugs</em> are reported, new <em>features</em> are announced and other <em>general tickets</em> are added.
 
-<strong><a href="http://www.dotkernel.net/">DotKernel Tracker</a></strong> is a <strong><a href="http://www.mantisbt.org/">Mantis</a></strong> web-based bugtracking system. To simplify the development of <strong>DotKernel</strong>, we integrated our web development IDE – <strong><a href="http://www.aptana.com/">Aptana</a></strong> with our bugtracking system – <strong><a href="http://www.dotkernel.net/">DotKernel Tracker</a></strong>. In the <em><strong>Downloads</strong></em> section, you will find screenshots with the below steps for <strong><a href="../download/?did=24">Using Aptana with the Mylyn connector for Mantis</a></strong>
+<strong><a href="http://www.dotkernel.net/">Dotkernel Tracker</a></strong> is a <strong><a href="http://www.mantisbt.org/">Mantis</a></strong> web-based bugtracking system. To simplify the development of <strong>Dotkernel</strong>, we integrated our web development IDE – <strong><a href="http://www.aptana.com/">Aptana</a></strong> with our bugtracking system – <strong><a href="http://www.dotkernel.net/">Dotkernel Tracker</a></strong>. In the <em><strong>Downloads</strong></em> section, you will find screenshots with the below steps for <strong><a href="../download/?did=24">Using Aptana with the Mylyn connector for Mantis</a></strong>
 <!--more-->
 
 <strong>1. </strong>Install <strong>Aptana </strong>2.0.5 by following these steps: <strong><a href="../php-development/aptana-php-installation-in-aptana-2-x/">http://www.dotkernel.com/php-development/aptana-php-installation-in-aptana-2-x/</a></strong>
@@ -47,7 +47,7 @@ In developing <strong>DotKernel</strong> application framework, we needed a trac
 
 <em>Server </em>: <strong><a href="http://www.dotkernel.net/api/soap/mantisconnect.php">http://www.dotkernel.net/api/soap/mantisconnect.php</a></strong>
 
-<em>Label</em>: <strong>DotKernel Tracker</strong> (or a custom string )
+<em>Label</em>: <strong>Dotkernel Tracker</strong> (or a custom string )
 
 <em>User ID</em>: your username from <strong><a href="http://www.dotkernel.net/">http://www.dotkernel.net/</a></strong>. If you don’t have an account, signup <strong><a href="http://www.dotkernel.net/signup_page.php">here</a></strong>
 
@@ -55,7 +55,7 @@ In developing <strong>DotKernel</strong> application framework, we needed a trac
 
 <strong>9. </strong>A window will popup asking if you want to create a query;  click <em>Yes</em>
 
-<strong>10. </strong><em>Select project<strong>: DotKernel</strong></em>
+<strong>10. </strong><em>Select project<strong>: Dotkernel</strong></em>
 
 <em>Select filter: <strong>[Build-in] Latest Dot Kernel tasks</strong></em>
 
@@ -67,15 +67,15 @@ In developing <strong>DotKernel</strong> application framework, we needed a trac
 
 <div class="faq-list">
     <details class="acc" open>
-        <summary>What is DotKernel Tracker? <span class="chev">+</span></summary>
+        <summary>What is Dotkernel Tracker? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel Tracker is a Mantis-based, web-based bugtracking system used by the DotKernel application framework, where bugs are reported, new features are announced, and other general tickets are added.</p>
+            <p class="mb-0">Dotkernel Tracker is a Mantis-based, web-based bugtracking system used by the Dotkernel application framework, where bugs are reported, new features are announced, and other general tickets are added.</p>
         </div>
     </details>
     <details class="acc">
-        <summary>How is Aptana integrated with DotKernel Tracker? <span class="chev">+</span></summary>
+        <summary>How is Aptana integrated with Dotkernel Tracker? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">Aptana, the web development IDE used for DotKernel development, is integrated with DotKernel Tracker via the Mylyn plugin's Mantis connector, so tickets can be managed directly from within the IDE.</p>
+            <p class="mb-0">Aptana, the web development IDE used for Dotkernel development, is integrated with Dotkernel Tracker via the Mylyn plugin's Mantis connector, so tickets can be managed directly from within the IDE.</p>
         </div>
     </details>
     <details class="acc">
@@ -85,9 +85,9 @@ In developing <strong>DotKernel</strong> application framework, we needed a trac
         </div>
     </details>
     <details class="acc">
-        <summary>What information is needed to add DotKernel Tracker as a task repository? <span class="chev">+</span></summary>
+        <summary>What information is needed to add Dotkernel Tracker as a task repository? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">You need the server URL (http://www.dotkernel.net/api/soap/mantisconnect.php), a label of your choosing (e.g. "DotKernel Tracker"), and your User ID, which is your username from dotkernel.net (you can sign up if you don't already have an account).</p>
+            <p class="mb-0">You need the server URL (http://www.dotkernel.net/api/soap/mantisconnect.php), a label of your choosing (e.g. "Dotkernel Tracker"), and your User ID, which is your username from dotkernel.net (you can sign up if you don't already have an account).</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/zend-framework/scienta-zf-debug-bar-a-very-helpfull-zf-debug-tool.html.twig b/src/Blog/templates/page/blog-resource/zend-framework/scienta-zf-debug-bar-a-very-helpfull-zf-debug-tool.html.twig
index 4bcbff8c..7bcba450 100644
--- a/src/Blog/templates/page/blog-resource/zend-framework/scienta-zf-debug-bar-a-very-helpfull-zf-debug-tool.html.twig
+++ b/src/Blog/templates/page/blog-resource/zend-framework/scienta-zf-debug-bar-a-very-helpfull-zf-debug-tool.html.twig
@@ -24,7 +24,7 @@ Just found today a very interesting and helpful debug tool:
 
 <strong><a title="Scienta ZF Debug Bar" href="http://jokke.dk/software/scientadebugbar" target="_blank" rel="noopener noreferrer">Scienta</a></strong>
 
-We at DotKernel used some very basic debug bar:  queries, time spent , memory used.  But this <strong>Scienta</strong> is way more complex and nicer then our internal code,  so we switch to it and integrate it in DotKernel code base.
+We at Dotkernel used some very basic debug bar:  queries, time spent , memory used.  But this <strong>Scienta</strong> is way more complex and nicer then our internal code,  so we switch to it and integrate it in Dotkernel code base.
 
 <h2 id="user-content-faq">Frequently Asked Questions</h2>
 
@@ -36,9 +36,9 @@ We at DotKernel used some very basic debug bar:  queries, time spent , memory u
         </div>
     </details>
     <details class="acc">
-        <summary>Why did DotKernel switch from its own debug bar to Scienta? <span class="chev">+</span></summary>
+        <summary>Why did Dotkernel switch from its own debug bar to Scienta? <span class="chev">+</span></summary>
         <div class="acc-body">
-            <p class="mb-0">DotKernel had been using a very basic debug bar showing queries, time spent, and memory used, but found Scienta to be way more complex and nicer than their internal code, so they switched to it and integrated it into the DotKernel code base.</p>
+            <p class="mb-0">Dotkernel had been using a very basic debug bar showing queries, time spent, and memory used, but found Scienta to be way more complex and nicer than their internal code, so they switched to it and integrated it into the Dotkernel code base.</p>
         </div>
     </details>
 </div>
diff --git a/src/Blog/templates/page/blog-resource/zend-framework/zend-mail-and-zend-http-security-fixes-in-zend-framework-1-12-12.html.twig b/src/Blog/templates/page/blog-resource/zend-framework/zend-mail-and-zend-http-security-fixes-in-zend-framework-1-12-12.html.twig
index 7665f2e2..3b31b5f7 100644
--- a/src/Blog/templates/page/blog-resource/zend-framework/zend-mail-and-zend-http-security-fixes-in-zend-framework-1-12-12.html.twig
+++ b/src/Blog/templates/page/blog-resource/zend-framework/zend-mail-and-zend-http-security-fixes-in-zend-framework-1-12-12.html.twig
@@ -31,7 +31,7 @@ Also, the ZF  PEAR channel was updated to latest 1.12.12 release.
 <strong>pear upgrade zend/zend</strong>
 
 We strongly recommend that consumers of the Zend_Http and Zend_Mail components upgrade immediately.
-Also, DotKernel Application Framework use intensively the Zend_Mail component.
+Also, Dotkernel Application Framework use intensively the Zend_Mail component.
 
 If you cannot, you can download the patch separately and apply it to your ZF install: