Fixed nits

Signed-off-by: JonahSussman <[email protected]>

src/content/blog/kai-incident-storage-2024/index.mdx

@@ -1,6 +1,6 @@
 ---
 author: JonahSussman
-date: 2024-08-16
+date: 2024-08-29
 description: >-
     A walkthrough of how incident data is leveraged in Konveyor AI's (Kai) 
     workflow to improve the generation of results.
@@ -25,7 +25,7 @@ modernizing a single application is an intimidating task.
 
 This kind of work is often one of the most unglamorous, and error-prone tasks
 that developers have to do. It involves rewriting large portions of the
-codebase, which can daunting for even the most battle-hardened of developers.
+codebase, which can be daunting for even the most battle-hardened of developers.
 There's an interconnected web of functions, classes, and modules that all depend
 on each other. One wrong move and the whole thing can come crashing down. 
 
@@ -284,11 +284,11 @@ configurability for how we handle it on the table.
 
 Currently, there are two types of producers:
 
-- **text_only**: The solution only contains a textual difference between the old
-  and new.
+- **text_only**: The solution only contains a diff of the source code from the
+  original to the updated version.
 - **llm_lazy**: The same as text_only as well as the solution is earmarked for
-  LLM summary generation. The llm summary is the generated only when the
-  solution is needed, i.e. lazily.
+  LLM summary generation. LLM summary is the generated only when the solution is
+  needed, i.e. lazily.
 
 Let's take a look at the solutions generated by Kai for one of the incidents
 of the io issue: