fix: remove unwanted third party images (#533)

Achanandhi-M · amaan-bhati · Tvisha Raji · web-flow · commit 1db7add29147 · 2025-07-10T16:57:37.000+05:30
* feat: Added new docs structure (#521) * feat: Added New docs structure Signed-off-by: Achanandhi-M <achanandhi.m@gmail.com> * feat: add content for the utg-pr agent Signed-off-by: amaan-bhati <amaanbhati49@gmail.com> * chore: test commit/remove utg cli Signed-off-by: amaan-bhati <amaanbhati49@gmail.com> * feat: add/edit instructions and added them all to the sidebar Signed-off-by: amaan-bhati <amaanbhati49@gmail.com> * API testing * feat: trim down content, update pr agent link Signed-off-by: amaan-bhati <amaanbhati49@gmail.com> * add: revamp unit and api docs page Signed-off-by: Achanandhi-M <achanandhi.m@gmail.com> --------- Signed-off-by: Achanandhi-M <achanandhi.m@gmail.com> Signed-off-by: amaan-bhati <amaanbhati49@gmail.com> Co-authored-by: amaan-bhati <amaanbhati49@gmail.com> Co-authored-by: Amaan Bhati <94218318+amaan-bhati@users.noreply.github.com> Co-authored-by: Tvisha Raji <tvisharaji@Tvishas-MacBook-Air.local> Co-authored-by: Neha Gupta <gneha21@yahoo.in> * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * refactor: v3 (#525) Signed-off-by: Neha Gupta <gneha21@yahoo.in> * V3 (#526) * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> --------- Signed-off-by: Neha Gupta <gneha21@yahoo.in> * V3 (#527) * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> --------- Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix broken images (#528) * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> --------- Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images (#529) * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> --------- Signed-off-by: Neha Gupta <gneha21@yahoo.in> * refactor: v3 * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> --------- Signed-off-by: Neha Gupta <gneha21@yahoo.in> * Refactor (#532) * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: broken images Signed-off-by: Neha Gupta <gneha21@yahoo.in> --------- Signed-off-by: Neha Gupta <gneha21@yahoo.in> * fix: remove unwanted images Signed-off-by: Achanandhi-M <achanandhi.m@gmail.com> --------- Signed-off-by: Achanandhi-M <achanandhi.m@gmail.com> Signed-off-by: amaan-bhati <amaanbhati49@gmail.com> Signed-off-by: Neha Gupta <gneha21@yahoo.in> Signed-off-by: Achanandhi M <110651321+Achanandhi-M@users.noreply.github.com> Co-authored-by: amaan-bhati <amaanbhati49@gmail.com> Co-authored-by: Amaan Bhati <94218318+amaan-bhati@users.noreply.github.com> Co-authored-by: Tvisha Raji <tvisharaji@Tvishas-MacBook-Air.local> Co-authored-by: Neha Gupta <gneha21@yahoo.in>
diff --git a/versioned_docs/version-3.0.0/concepts/reference/glossary/behaviour-driven-development.md b/versioned_docs/version-3.0.0/concepts/reference/glossary/behaviour-driven-development.md
@@ -24,7 +24,7 @@ keywords:
 
 Behavior Driven Development (BDD) is an Agile methodology that emphasizes collaboration among developers, testers, and business stakeholders. It ensures that software meets users' needs by writing tests that describe the desired behavior in plain language. This approach encourages clear communication and shared understanding of software requirements, ultimately leading to better quality and more maintainable code.
 
-![Behavior Driven Development (BDD)](https://images.spiceworks.com/wp-content/uploads/2022/09/29100419/BDD-Development-Process.png)
+![Behavior Driven Development (BDD)](https://keploy-devrel.s3.us-west-2.amazonaws.com/BDD-Development-Process.png)
 
 ## BDD Fundamentals
 
@@ -168,7 +168,7 @@ Popular BDD tools include:
 | **Emphasis**         | Code correctness                        | Meeting user expectations and business goals                        |
 | **Collaboration**    | Within the development team             | Across all stakeholders                                             |
 
-![BDD vs. TDD](https://images.ctfassets.net/vrc8wif0t20g/6YGzPeOoQlewSQ07sX7a9P/6815d8dffd1523e43040b17e78a39f73/BDD_vs._TDD__Differences_Explained.png)
+![BDD vs. TDD](https://keploy-devrel.s3.us-west-2.amazonaws.com/BDD_vs._TDD__Differences_Explained.png)
 
 ## Conclusion
 
diff --git a/versioned_docs/version-3.0.0/concepts/reference/glossary/black-box-testing.md b/versioned_docs/version-3.0.0/concepts/reference/glossary/black-box-testing.md
@@ -42,8 +42,6 @@ This testing approach is essential for several reasons:
 
 - **Accessibility and Flexibility**: Black-box testing is accessible and adaptable to testers with varying levels of technical expertise. It does not require in-depth programming knowledge or access to source code, making it suitable for testers with diverse backgrounds and skill sets. Additionally, black-box testing techniques can be applied to different types of software applications, including web applications, mobile apps, and standalone software products.
 
-![Black Box Testing](https://res.cloudinary.com/practicaldev/image/fetch/s--shG8HMmV--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_66%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/f639sq6krordxspv1wxi.gif)
-
 ## What are the Benefits of Black-Box Testing?
 
 1. **Independence from Internal Implementation**: Allows unbiased and realistic assessment, mimicking end-user perspectives.
@@ -55,7 +53,7 @@ This testing approach is essential for several reasons:
 
 ## Whate are types of Black-Box Testing Techniques ?
 
-![How Black Box testing Works?](https://www.imperva.com/learn/wp-content/uploads/sites/13/2020/03/thumbnail_Black-box.jpg)
+![How Black Box testing Works?](https://keploy-devrel.s3.us-west-2.amazonaws.com/thumbnail_Black-box.jpg)
 
 ### 1. Equivalence Partitioning:
 
diff --git a/versioned_docs/version-3.0.0/concepts/reference/glossary/code-coverage.md b/versioned_docs/version-3.0.0/concepts/reference/glossary/code-coverage.md
@@ -41,7 +41,7 @@ It's analysis provides several benefits:
 
 Keploy has native integrations with your unit-testing libraries like go-test, jUnit, jest, pyTest. Keploy gives combined test-coverage and can also be integrated in existing CI pipelines easily within go-test, jUnit, jest, pyTest workflows.
 
-<img scr="https://keploy.io/docs/gif/replay-tc.gif?raw=true"/>
+<img src="https://keploy.io/docs/gif/replay-tc.gif?raw=true"/>
 
 By generating additional tests that exercise different parts of your codebase, you can increase the percentage of code that is covered by your tests. For example, in case of NodeJS application you can use Jest. Jest provides a built-in code coverage tool that can help you measure the effectiveness of your tests and identify areas of the code that need additional testing. By adding Keploy SDK with Jest, you can easily generate test cases and increase your code coverage. Let's create a `Keploy.test.js`
 
@@ -90,7 +90,3 @@ Now when let's the test cases with Jest, you can see the code coverage report ge
 ```bash
 npm test
 ```
-
-We can see below that the code coverage is 94.44% for the our application.
-
-<img src='https://raw.githubusercontent.com/priyankarpal/samples-typescript/ppal/express-mongo-priyank/images/jestcoverage.png?raw=true'/>
diff --git a/versioned_docs/version-3.0.0/concepts/reference/glossary/grey-box-testing.md b/versioned_docs/version-3.0.0/concepts/reference/glossary/grey-box-testing.md
@@ -36,8 +36,6 @@ Gray box testing is needed for several reasons:
 
 ## Types of Gray Box Testing Techniques
 
-![Types of gray box testing](https://wp.testbytes.net//wp-content/uploads/2019/04/Gray-box-testing-1-1.jpg)
-
 Gray box testing encompasses various techniques that leverage both functional testing methods and insights into the internal workings of the application. Here are some common types of gray box testing techniques:
 
 ### 1. Matrix Testing
diff --git a/versioned_docs/version-3.0.0/concepts/reference/glossary/idempotency.md b/versioned_docs/version-3.0.0/concepts/reference/glossary/idempotency.md
@@ -29,7 +29,7 @@ Certain HTTP methods are inherently idempotent:
 - **PUT:** Updating a resource with PUT is idempotent because sending the same update multiple times results in the same resource state.
 - **DELETE:** Deleting a resource with DELETE is idempotent because attempting to delete an already deleted or non-existent resource does not change the system state.
 
-![Methods](https://www.hubspot.com/hs-fs/hubfs/Google%20Drive%20Integration/Idempotent%20Api%20Draft-1.png?width=650&name=Idempotent%20Api%20Draft-1.png)
+![Methods](https://keploy-devrel.s3.us-west-2.amazonaws.com/Idempotent+Api+image.webp)
 
 ## Key Benefits of Idempotent APIs
 
@@ -69,7 +69,7 @@ Idempotency is particularly critical in distributed systems where network issues
 
 While **idempotent** methods guarantee the same outcome when repeated, **safe** methods are those that do not alter the system state at all. All safe methods (such as GET) are idempotent, but not all idempotent methods are safe (e.g., PUT and DELETE change the state, but in a controlled, repeatable manner).
 
-![Idempotent vs Safe](https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcSNpJRr8DjkwYCknq1yp0PNVbGQ9Gy0rcBwtg&s)
+![Idempotent vs Safe](https://keploy-devrel.s3.us-west-2.amazonaws.com/safe-methods-idempotency.png)
 
 ## Leveraging Keploy for Idempotency in API Testing
 
diff --git a/versioned_docs/version-3.0.0/concepts/reference/glossary/integration-testing.md b/versioned_docs/version-3.0.0/concepts/reference/glossary/integration-testing.md
@@ -25,7 +25,7 @@ There are two main types of integration testing:
 
 Both types of integration testing are essential for ensuring that all components of a software application work together correctly.
 
-![Approach Types](https://media.geeksforgeeks.org/wp-content/uploads/20201202190437/top2.png)
+![Approach Types](https://keploy-devrel.s3.us-west-2.amazonaws.com/integration-testing-approach-type.png)
 
 ### How to perform Integration Testing ?
 
diff --git a/versioned_docs/version-3.0.0/concepts/reference/glossary/software-testing-life-cycle.md b/versioned_docs/version-3.0.0/concepts/reference/glossary/software-testing-life-cycle.md
@@ -58,7 +58,7 @@ Software Testing Life Cycle (STLC) comprises several phases that guide the testi
    - **Objective**: Assess testing completion and readiness for release.
    - **Activities**: Evaluate test results, generate reports, and obtain stakeholder sign-off.
 
-![Software Testing Life Cycle Phases](https://cdn.hashnode.com/res/hashnode/image/upload/v1689231300018/f466f393-e402-4b1f-adef-259c93508aa8.png)
+![Software Testing Life Cycle Phases](https://keploy-devrel.s3.us-west-2.amazonaws.com/software-development-lifecycle.png)
 
 ## What are some common Practices in STLC ?
 
diff --git a/versioned_docs/version-3.0.0/concepts/reference/glossary/test-driven-development.md b/versioned_docs/version-3.0.0/concepts/reference/glossary/test-driven-development.md
@@ -55,7 +55,7 @@ TDD is particularly effective in scenarios such as:
 - **Ensuring Code Quality:**  
   The focus on writing testable, modular code results in higher overall code quality and easier maintenance.
 
-![Test Driven Development](https://media.licdn.com/dms/image/C5112AQHGTe-PjXMc4g/article-cover_image-shrink_600_2000/0/1552215937761?e=2147483647&v=beta&t=oU-XvoEKjrEtxRdTXFzZRdRLS1hUFTQQZtwb2HuP1E0)
+![Test Driven Development](https://keploy-devrel.s3.us-west-2.amazonaws.com/Test-driven-development.png)
 
 ## Fundamentals and Techniques of TDD
 
@@ -164,7 +164,7 @@ Implementing TDD comes with challenges that teams should be aware of:
 | **Emphasis**         | Code correctness                               | User expectations and business goals                  | Real-world behavior and system performance                     |
 | **Collaboration**    | Primarily within the development team          | High collaboration across stakeholders                | Collaboration among development, testing, and operations teams |
 
-![TDD vs. BDD vs. Traffic Driven Testing](https://images.ctfassets.net/vrc8wif0t20g/6YGzPeOoQlewSQ07sX7a9P/6815d8dffd1523e43040b17e78a39f73/BDD_vs._TDD__Differences_Explained.png)
+![TDD vs. BDD vs. Traffic Driven Testing](https://keploy-devrel.s3.us-west-2.amazonaws.com/BDD_vs._TDD__Differences_Explained.png)
 
 ## Conclusion
 
diff --git a/versioned_docs/version-3.0.0/concepts/reference/glossary/white-box-testing.md b/versioned_docs/version-3.0.0/concepts/reference/glossary/white-box-testing.md
@@ -39,7 +39,7 @@ White box testing is essential for verifying the correctness and efficiency of c
 - **Verify Calculations**: Ensures that calculations and data manipulations are correct.
 - **Assess Code Quality**: Checks the structure and organization of the code for better maintainability.
 
-![What is White box testing?](https://cdn.educba.com/academy/wp-content/uploads/2019/05/White-Box-Testing-1.jpg)
+![What is White box testing?](https://keploy-devrel.s3.us-west-2.amazonaws.com/Whitebox.png)
 
 ## Types of White Box Testing Techniques
 
diff --git a/versioned_docs/version-3.0.0/keploy-explained/supported-languages.md b/versioned_docs/version-3.0.0/keploy-explained/supported-languages.md
@@ -26,10 +26,11 @@ Keploy generates _and runs_ AI-powered unit tests for your Go projects.
 
 ## 🚀 Coming Soon
 
-**Java:**  
- Java support is on the way!
+**Java and Javascript:**
 
-We’ll bring the same AI-driven, high-quality test generation and validation workflow to Java soon.
+Java and Javascript support is on the way!
+
+We’ll bring the same AI-driven, high-quality test generation and validation workflow to Java and Javascript soon.
 
 ## 🧩 Why Only a Few Languages (for now)?
 
