fix: lint issues

Author: pratik-mahalle

vale_styles/config/vocabularies/Base/accept.txt

@@ -127,4 +127,14 @@ async
 substring
 llm
 shorteners
-matchType
+matchType
+anonymization
+Jira
+interdependencies
+teardown
+protobuf
+protoc
+Unary
+RPCs
+viewport
+Gradle

versioned_docs/version-3.0.0/concepts/reference/glossary/component-testing.md

@@ -56,7 +56,7 @@ Testing your code in small parts does not have to be complex. Here are the steps
 
 ## Types of Software Component Testing
 
-![Typinge of Component test](/img/glossary/types-of-component-testing.webp)
+![Types of Component testing](/img/glossary/types-of-component-testing.webp)
 
 Component testing validates separate parts of a given system before integration. This testing generally consists of unit testing, module testing, and program testing.
 
@@ -80,7 +80,7 @@ Not entirely, but they are very similar and often confused.
 | ------------- | ----------------------------------------- | ---------------------------------------------- |
 | What it tests | Smallest parts (functions, methods)       | Groups of parts working together (modules)     |
 | Goal          | Check if each small piece works correctly | Check if the combined parts work well together |
-| Dependencies  | No dependencies — tests are isolated      | May use stubs or drivers for missing pieces    |
+| Dependencies  | No dependencies—tests are isolated        | May use stubs or drivers for missing pieces    |
 | Speed         | Very fast                                 | A bit slower, tests bigger parts               |
 | Example       | A sum() function                          | A payment module                               |
 

versioned_docs/version-3.0.0/concepts/reference/glossary/defect-management.md

@@ -45,12 +45,12 @@ The **Defect Management Process (DMP)** is a systematic process of detecting, do
 
 ### A proper Defect Management Process involves:
 
-- **Detection** – Detecting defects during testing.
-- **Logging** – Recording defects with detailed information.
-- **Prioritization** – Prioritizing defects based on severity and impact.
-- **Assignment** – Assigning the defect to developers.
-- **Resolution** – Fix implementation.
-- **Verification** – Testing the fix.
+- **Detection**—Detecting defects during testing.
+- **Logging**—Recording defects with detailed information.
+- **Prioritization**—Prioritizing defects based on severity and impact.
+- **Assignment**—Assigning the defect to developers.
+- **Resolution**—Fix implementation.
+- **Verification**—Testing the fix.
 
 ## Why is Defect Management Process Important?
 
@@ -224,7 +224,7 @@ Attach a screenshot of the unresponsive login button and a video showing the ste
 - Include extra details that might help developers understand the defect better.
 
 **Example:**  
-\_The issue seems to occur only when the device is in low battery mode.
+The issue seems to occur only when the device is in low battery mode.
 
 ### Step 8: Review and Revise
 
@@ -242,7 +242,7 @@ Good defect management leads to good test management. Platforms like **Keploy**
 
 ## Conclusion
 
-In this blog, we covered the fundamentals of **Defect Management in software testing** — from defect identification, reporting, tracking, verification, to closure.
+In this blog, we covered the fundamentals of **Defect Management in software testing**—from defect identification, reporting, tracking, verification, to closure.
 
 By following a disciplined defect management process:
 

versioned_docs/version-3.0.0/concepts/reference/glossary/grpc.md

@@ -26,7 +26,7 @@ The framework's design philosophy centers around efficiency, type safety, and cr
 
 ## Core Architecture and Components
 
-gRPC's architecture consists of several key components that work together to provide a robust communication framework. The Protocol Buffer compiler (protoc) generates code from service definitions, creating strongly-typed interfaces that eliminate runtime errors common in loosely-typed systems.
+gRPC`s architecture consists of several key components that work together to provide a robust communication framework. The Protocol Buffer compiler (protoc) generates code from service definitions, creating strongly typed interfaces that eliminate runtime errors common in loosely typed systems.
 
 ![gRPC Architecture](/img/glossary/gRPC-architecture.webp)
 
@@ -40,7 +40,7 @@ The performance benefits of gRPC become apparent in high-throughput scenarios. P
 
 HTTP/2's multiplexing capabilities eliminate the head-of-line blocking issues that plague HTTP/1.1 connections. Multiple requests can be processed simultaneously over a single connection, reducing the overhead associated with establishing multiple TCP connections. This improvement is especially noticeable in microservices architectures where services frequently communicate with each other.
 
-The strongly-typed nature of Protocol Buffers enables compile-time validation, catching errors early in the development process. This type safety extends to the wire format, ensuring that data corruption during transmission is detected and handled appropriately.
+The strongly typed nature of Protocol Buffers enables compile-time validation, catching errors early in the development process. This type safety extends to the wire format, ensuring that data corruption during transmission is detected and handled appropriately.
 
 ## Communication Patterns
 
@@ -146,7 +146,7 @@ gRPC uses Protocol Buffers' backward compatibility features. You can add new fie
 
 ### Is gRPC suitable for mobile applications?
 
-Absolutely. gRPC's efficient binary protocol and HTTP/2 multiplexing make it ideal for mobile environments where bandwidth and battery life are concerns. The smaller message sizes and reduced connection overhead provide significant benefits.
+Absolutely. gRPC`s efficient binary protocol and HTTP/2 multiplexing make it ideal for mobile environments where bandwidth and battery life are concerns. The smaller message sizes and reduced connection overhead provide significant benefits.
 
 ### What programming languages support gRPC?
 

versioned_docs/version-3.0.0/concepts/reference/glossary/junit.md

@@ -12,11 +12,11 @@ keywords:
   - Java
 ---
 
-Testing remains one of the most critical aspects of software development, yet many developers struggle to implement effective testing strategies. JUnit has emerged as the de facto standard for Java testing, providing a robust framework that enables developers to write reliable, maintainable tests that drive quality throughout the development lifecycle.
+Testing remains one of the most critical aspects of software development, yet many developers struggle to implement effective testing strategies. JUnit has emerged as the de-facto standard for Java testing, providing a robust framework that enables developers to write reliable, maintainable tests that drive quality throughout the development lifecycle.
 
 ## The Evolution of JUnit
 
-JUnit's journey began in the late 1990s when Kent Beck and Erich Gamma recognized the need for a simple, effective testing framework for Java applications. What started as a lightweight solution has evolved into a comprehensive testing ecosystem that powers millions of applications worldwide.
+JUnit's journey began in the late 1990's when Kent Beck and Erich Gamma recognized the need for a simple, effective testing framework for Java applications. What started as a lightweight solution has evolved into a comprehensive testing ecosystem that powers millions of applications worldwide.
 
 The framework's design philosophy centers on simplicity and effectiveness. Rather than overwhelming developers with complex configurations, JUnit provides intuitive annotations and assertions that make test writing straightforward and maintainable. This approach has contributed significantly to its widespread adoption across enterprises of all sizes.