Update from Capgemini/blog-private@0bd96b0

Capgemini · May 19, 2024 · 4c1a921 · 4c1a921
1 parent 6759bb6
commit 4c1a921
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/_data/jobs.yml b/_data/jobs.yml
@@ -40,5 +40,5 @@ web_platforms:
 Digital_Security_and_Trust:
     title: Join our Digital Security and Trust Team
     link: https://www.capgemini.com/gb-en/careers/shape-your-future-at-capgemini-invent/?utm_source=githubmsblog&utm_medium=referral&utm_campaign=tracking
-    description: "If you're interested in helping organisations become more secure in today's fast paced digtial environment, then take a look at our Jobs page, we're hiring!" 
+    description: "If you're interested in helping organisations become more secure in today's fast paced digital environment, then take a look at our Jobs page, we're hiring!" 
 
diff --git a/_posts/2015-05-15-drupal-integration-patterns.md b/_posts/2015-05-15-drupal-integration-patterns.md
@@ -113,7 +113,7 @@ alternative front ends.
 
 [Headless Drupal](https://github.com/davidhwang/horseman) is a phrase that has gained a lot of momentum in the Drupal
 community - the basic concept being that Drupal purely responds with RESTful
-endpoints, and completely independant front-end code using frameworks such as Angular.js
+endpoints, and completely independent front-end code using frameworks such as Angular.js
 is used to render the data and completely separate content from presentation.
 
 Personally, I prefer to think of a "nearly headless" approach - where Drupal is