From dfdd103f18b46b734155133f2705185f1270ed4e Mon Sep 17 00:00:00 2001
From: Allan <>
Date: Tue, 25 Feb 2025 13:51:37 +0000
Subject: [PATCH] wording

---
 content/blog/afa-insurance/index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/blog/afa-insurance/index.md b/content/blog/afa-insurance/index.md
index dd82c44..9cb81fe 100644
--- a/content/blog/afa-insurance/index.md
+++ b/content/blog/afa-insurance/index.md
@@ -32,7 +32,7 @@ We have batches running and checking if there are new signals, and we have set u
 So it is very easy for us now to do that process!
 
 ### Why are you using Data Controller, instead of another approach or tool?
-We heard about Data Controller from the community, and it seemed like a great fit for our use case - it’s SAS friendly and it’s SAS built and it’s easy to incorporate.  
+We heard about Data Controller from the community, and it seemed like a great fit for our use case - it’s SAS friendly, it’s built on SAS, and it’s easy to incorporate.  
 
 The things we really like are the EDIT and APPROVAL process, and the HISTORY of all changes that is built into the product.
 
@@ -45,7 +45,7 @@ We also have some percentages (relating to payments) with levels that change dur
 |:--:| 
 | *Henrik Forsell (HF)* |
 
-
+ 
 (HF)  This takes us completely out of the equation – we don’t have to do the changes, it’s all on them, they own it.
 
 (FE)  Yes – their data, their controls.  We can leave it to them from the development environment, so they are not dependent on us for any changes, so it’s really good.