chore: fixing the broken image link due to s3 bucket deletion issue (#42)

Author: kotharironak

src/pages/platform-ui/index.md

@@ -5,11 +5,7 @@ template: docs
 ---
 ## Hypertrace Dashboard
 
-| ![space-1.jpg](https://s3.amazonaws.com/hypertrace-docs/dashboard-3.png) | 
-|:--:| 
-
-
-| ![space-1.jpg](https://s3.amazonaws.com/hypertrace-docs/dashboard-2.png) | 
+| ![space-1.jpg](https://raw.githubusercontent.com/hypertrace/hypertrace-docs-website/main/static/images/dashboard-2.png) | 
 |:--:| 
 | *Hypertrace Dashboard* |
 
@@ -26,7 +22,7 @@ Then if you scroll down you will get lists of top assets including top endpoints
 
 ## Application flow 
 
-| ![space-1.jpg](https://s3.amazonaws.com/hypertrace-docs/flow.png) | 
+| ![space-1.jpg](https://raw.githubusercontent.com/hypertrace/hypertrace-docs-website/main/static/images/flow.png) | 
 |:--:| 
 | *Application Flow with Hypertrace* |
 
@@ -36,15 +32,15 @@ Of course this does normal controls like zoom and refresh which you can find in
 
 
 ## Services
-| ![space-1.jpg](https://s3.amazonaws.com/hypertrace-docs/services.png) | 
+| ![space-1.jpg](https://raw.githubusercontent.com/hypertrace/hypertrace-docs-website/main/static/images/services.png) | 
 |:--:| 
 | *List of all services in application with Hypertrace* |
 
 Services section in hypertrace shows you all the services your application has and if you increase timeframe you can even see list of all services sent traces to Hypertrace in last few hours or even days. 
 
 ## Service details
 
-| ![space-1.jpg](https://hypertrace-docs.s3.amazonaws.com/services.gif) | 
+| ![space-1.jpg](https://raw.githubusercontent.com/hypertrace/hypertrace-docs-website/main/static/images/frontend-service.png) | 
 |:--:| 
 | *Frontend microservice details with Hypertrace* |
 
@@ -56,7 +52,7 @@ At the same time, there can be millions of traces, so search is an important fea
 
 ## Traces
 
-| ![space-1.jpg](https://s3.amazonaws.com/hypertrace-docs/traces.png) | 
+| ![space-1.jpg](https://raw.githubusercontent.com/hypertrace/hypertrace-docs-website/main/static/images/traces.png) | 
 |:--:| 
 | *Tracing with Hypertrace* |
 
@@ -67,15 +63,15 @@ At the same time, there can be millions of traces, so search is an important fea
 
 ## Backends
 
-| ![space-1.jpg](https://s3.amazonaws.com/hypertrace-docs/backends.png) | 
+| ![space-1.jpg](https://raw.githubusercontent.com/hypertrace/hypertrace-docs-website/main/static/images/backends.png) | 
 |:--:| 
 | *Backends with Hypertrace* |
 
 Backends are typically databases, like MySQL and Redis. Insights here are derived from client requests and most helpful to infrastructure teams trying to understand which queries are causing performance problems. a backend overview should look familiar. It  visualizes latency, error and call count along with a list of services using this backend! The traces tab is tuned for the backend owner, for example to see requests coming into MySQL
 
 ## Explorer
 
-| ![space-1.jpg](https://s3.amazonaws.com/hypertrace-docs/explore.png) | 
+| ![space-1.jpg](https://raw.githubusercontent.com/hypertrace/hypertrace-docs-website/main/static/images/explorer.png) | 
 |:--:| 
 | *Hypertrace Explorer* |
 

src/pages/sample-app/index.md

@@ -33,7 +33,7 @@ Use pre-built Docker images and a release manifest that is easy to deploy to an
 
 **Online Boutique** is composed of microservices written in multiple languages that talk to each other over gRPC.
 
-| ![space-1.jpg](https://s3.amazonaws.com/fininity.tech/DT/architecture-diagram.png) | 
+| ![space-1.jpg](https://raw.githubusercontent.com/hypertrace/hypertrace-docs-website/main/static/image/online-boutique-architecture-diagram.png) | 
 |:--:| 
 | *Microservices Architecture* |