Minor grammatical changes

Author: reeshabh90

blog/2026-05-05-docwire-returns.md

@@ -12,7 +12,7 @@ In course of human history, there has not been a time like the present era when
 Away from the noise, contemplating in silence, working through perseverance, Docwire SDK was being evolved into an infrastructure layer for modern data workflows to sustain the demands of modern day information processing. The journey has been long and arduous but the result has been equally satisfying. And it is time we present to you the much more evolved Docwire SDK, along with anecdotes about the philosophy behind it and the direction forward.
 <!-- truncate -->
 ## The Invisible Engine
-Every interface we interact with is a surface level reality, but the entity itself is supported by an engine which remains invisible. Same is true for the virtual world. Some of the most important softwares are never seen. When you tap a payment card or rely on an embedded medical device, complex logic runs quietly in the background. Document processing plays a similar role in many systems — critical, yet hidden. And Docwire has been designed to serve exactly the same purpose. An engine that extracts, normalizes, and transforms unstructured documents into structured, usable data — locally, securely and reliably. And it still adheres to its “Plug and Play” philosophy. Developers integrate it once and it simply works! Only better this time, with support for more file formats and a fluent ingestion layer for building data processing pipeline.
+Every interface we interact with is a surface level reality, but the entity itself is supported by an engine which remains invisible. Same is true for the virtual world. Some of the most important software is never seen. When you tap a payment card or rely on an embedded medical device, complex logic runs quietly in the background. Document processing plays a similar role in many systems — critical, yet hidden. And Docwire has been designed to serve exactly the same purpose. An engine that extracts, normalizes, and transforms unstructured documents into structured, usable data — locally, securely and reliably. And it still adheres to its “Plug and Play” philosophy. Developers integrate it once and it simply works! Only better this time, with support for more file formats and a fluent ingestion layer for building data processing pipeline.
 
 
 ## What Changed since 2023
@@ -28,7 +28,7 @@ We started this journey of evolving Docwire with following ideas as underlying p
 And this is where Docwire shines. Docwire is not simply AI-based or AI-driven, but AI-integrated SDK, which handles your document data processing requirements. It gives the user enough flexibility to process the data across various file formats and integrate it further with AI models of their choice, be it local or through APIs.
 
 ## From Files to Pipelines
-Docwire's evolution is not limited to supporting various file formats but integrating more workflows. In its inception, it was a file parsing tool and in its evolution, it is becoming pipeline construction SDK with various tools at your disposal:<br/>
+DocWire's evolution is not limited to supporting various file formats but integrating more workflows. In its inception, it was a file parsing tool and in its evolution, it is becoming pipeline construction SDK with various tools at your disposal:<br/>
 <b>Documents → Extraction → Normalization → Transformation → Output</b><br/>
 
 These pipelines can feed search, analytics, knowledge bases, or AI systems, often running entirely within controlled environments.

tech-dive/2026-05-06-reducing-compile-time-dependencies.md

@@ -40,7 +40,6 @@ Y::~Y() = default;
 
 void Y::someImpl() { std::cout << d_.num << std::endl; }
 ------------------------------
-`
 ```
 The file to notice here is `y.h` since this is the file that will be included in some main.cpp. Usually, programmers #include many more headers than necessary, which unfortunately degrades build times, especially when a popular header file includes too many other headers. Ours above is a simplistic one, yet enough to convey the message. Can we somehow remove any header from this file while still having our code compile and run successfully?
 

tech-dive/2026-05-07-docwire-parsing-chain.md

@@ -5,7 +5,7 @@ tags: [C++20, compile time, optimization]
 ---
 
 ## Introduction
-[Docwire's](https://docwire.io/) is a powerful data extraction tool, developed on Modern C++, that converts text from nearly all known file formats into searchable and editable data. Powered by the Tesseract OCR engine, DocWire is a solution for digitizing text from many image types, MS Office files, e-mails, or e-mail attachments. DocWire outputs data to plain text that may be transmitted for further processing.
+[Docwire](https://docwire.io/) is a powerful data extraction tool, developed on Modern C++, that converts text from nearly all known file formats into searchable and editable data. Powered by the Tesseract OCR engine, DocWire is a solution for digitizing text from many image types, MS Office files, e-mails, or e-mail attachments. DocWire outputs data to plain text that may be transmitted for further processing.
 
 One of the interesting aspects of Docwire SDK is its ability to process documents locally (or even make an OpenAI API call) through a series of customizable steps that can be added or removed as per requirements. For example, consider the following code example ():
 ```cpp
@@ -17,7 +17,7 @@ In the above pipeline processing, a document is being picked, its content type i
 std::filesystem::path("data_processing_definition.doc") | content_type::detector{} | office_formats_parser{} | PlainTextExporter() | local_ai::model_chain_element("Translate to spanish:\n\n") | out_stream;
 ```
 
-🔗Docwire Code examples can be accessed at this [link](https://docwire.readthedocs.io/en/latest/examples.html).
+🔗Explore Docwire code examples in the [official examples documentation](https://docwire.readthedocs.io/en/latest/examples.html).
 
 Now, we have added a local model to translate the text in the document to Spanish and then stream the output. It seems as if the product is moving on a conveyor belt, and necessary customizations can be applied, such that output of the previous step acts as an input of the next step, exactly how a pipeline chain would work. In software terms, this emulates exactly how the Unix pipe operator `|` works in the terminal.
 
@@ -46,7 +46,7 @@ struct EndMessage : Message {};
 
 We have defined a base entity and various types of such entities, and based on the types, the parsing steps will decide how to act. 
 
-*_Note_*: <u>In C++, classes are nothing but structs. I have taken the approach of structs here, as the intention is to keep the implementation short and minimal.</u>
+*_Note_*: <u>In C++, classes are primarily structs. I have taken the approach of structs here, as the intention is to keep the implementation short and minimal.</u>
 
 The intended behavior is as follows: