From 771e835e806417f6d34644b743fcf3e609bdfe56 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Thu, 17 Oct 2024 16:33:16 +0100 Subject: [PATCH] Typo --- source/_daily_emails/2024-10-06.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_daily_emails/2024-10-06.md b/source/_daily_emails/2024-10-06.md index f552f1f8..7cd7694a 100644 --- a/source/_daily_emails/2024-10-06.md +++ b/source/_daily_emails/2024-10-06.md @@ -13,7 +13,7 @@ drupal_planet: true With Drupal 7's end-of-life date of the 5th of January 2025 quickly approaching, I've recently seen again a number of companies offering support for Drupal 7 after its end-of-life date. -I've seen the same in corporate IT environments where they're running versions of software post their EOL date, so it's only Drupal 7, but I wonder if this is a good thing? +I've seen the same in corporate IT environments where they're running versions of software post their EOL date, so it's not only Drupal 7, but I wonder if this is a good thing? Is this deterring companies from upgrading if they know this is an option, or should everyone upgrade and we can move forward from Drupal 7 and other end-of-life software?