Fix links in Jaeger projects

programs/lfx-mentorship/2024/03-Sep-Nov/project_ideas.md

@@ -160,7 +160,7 @@ Expected Outcome: Gadget developers have a way to run unit tests in different ke
 
 #### Fix bugs found by fuzzer
 
-- Description: WasmEdge received several bug reports, which Fuzzer found. We would like to ask mentees to investigate and determine whether the issue is real, figure out solutions, or mark it as a `won't-fix` issue if it's invalid. To apply for this mentorship, you should also submit a proposal as part of the application materials. Please check the upstream issue for the detailed target list and the proposal template. 
+- Description: WasmEdge received several bug reports, which Fuzzer found. We would like to ask mentees to investigate and determine whether the issue is real, figure out solutions, or mark it as a `won't-fix` issue if it's invalid. To apply for this mentorship, you should also submit a proposal as part of the application materials. Please check the upstream issue for the detailed target list and the proposal template.
 - Expected Outcome: At least fix/determine 60% of the mentioned issues.
 - Recommended Skills: git, C++, WebAssembly
 - Mentor(s):
@@ -212,29 +212,25 @@ Expected Outcome: Gadget developers have a way to run unit tests in different ke
 - Upstream Issue: https://github.com/WasmEdge/WasmEdge/issues/3580
 
 ### Jaeger
-#### Jaeger v2 Kubernetes Operator  
-- Description: Jaeger-v1 has its own Kubernetes Operator (https://github.com/jaegertracing/jaeger-operator) which deploys Jaeger components according to the deployment strategy as well as the database or datastore. The goal of this project is to develop a new operator for [Jaeger-v2](https://github.com/jaegertracing/jaeger/issues/4843) that achieves feature parity with the v1 operator while introducing improvements and new capabilities. This new operator will leverage the [OpenTelemetry operator](https://github.com/open-telemetry/opentelemetry-operator) for Jaeger-v2 deployment while maintaining and enhancing the storage management features from the v1 operator.
+#### Jaeger v2 Kubernetes Operator
+- Description: Jaeger-v1 has its own Kubernetes Operator (https://github.com/jaegertracing/jaeger-operator) which deploys Jaeger components according to the deployment strategy as well as the database or datastore. The goal of this project is to develop a new operator for [Jaeger-v2](https://github.com/jaegertracing/jaeger/issues/4843) that achieves feature parity with the v1 operator while introducing improvements and new capabilities. This new operator will leverage the [OpenTelemetry operator](https://github.com/open-telemetry/opentelemetry-operator) for Jaeger-v2 deployment while maintaining and enhancing the storage management features from the v1 operator. More details in the [upstream issue](https://github.com/jaegertracing/jaeger/issues/5766).
 - Expected Outcome: By the end of this project, we aim to achieve full feature parity between the Jaeger v2 operator and the v1 operator, with the added benefits of OpenTelemetry integration. The new operator will provide a seamless experience for users, maintaining the robustness and flexibility of v1 while introducing the advantages of v2 and OpenTelemetry.
 - Recommended Skills: Go, scripting, kubernetes, operator framework, CI/CD
-- Mentor(s):  
+- Mentor(s):
   - Yuri Shkuro (@yurishkuro, github@ysh.us)
-  - Jonah Kowall (@jkowall, jkowall@kowall.net 
+  - Jonah Kowall (@jkowall, jkowall@kowall.net)
 - Upstream Issue: https://github.com/jaegertracing/jaeger/issues/5766
-#### Jaeger v2 Helm Chart 
-- Description: Currently, Jaeger v1 has an official Helm chart (https://github.com/jaegertracing/helm-charts), but there isn't one yet for Jaeger v2. The goal of this project is to develop a comprehensive Helm chart for Jaeger v2 that allows for easy deployment and management of Jaeger v2 components in Kubernetes environments. This chart should provide flexibility in configuration, support various deployment scenarios, and integrate well with the new architecture of Jaeger v2. Relevant links:
- - Jaeger: https://www.jaegertracing.io/
- - Jaeger v2 announcement: https://medium.com/jaegertracing/announcing-jaeger-v2-a-new-architecture-for-distributed-tracing-e87b1fea0fe4
- - Helm: https://helm.sh/
- - Existing Jaeger Helm charts: https://github.com/jaegertracing/helm-charts
+#### Jaeger v2 Helm Chart
+- Description: Currently, Jaeger v1 has an official Helm chart (https://github.com/jaegertracing/helm-charts), but there isn't one yet for Jaeger v2. The goal of this project is to develop a comprehensive Helm chart for Jaeger v2 that allows for easy deployment and management of Jaeger v2 components in Kubernetes environments. This chart should provide flexibility in configuration, support various deployment scenarios, and integrate well with the new architecture of Jaeger v2. More details in the [upstream issue](https://github.com/jaegertracing/jaeger/issues/5767).
 - Expected Outcome: By the end of this project, we aim to have a production-ready Helm chart for Jaeger v2 that is:
  - Fully functional and tested on the current version of Kubernetes
  - Well-documented with clear usage instructions and examples
  - Flexible enough to support a wide range of deployment scenarios
  - Ready for submission to the official Jaeger Helm chart repository
 - Recommended Skills: Go, scripting, kubernetes, helm, CI/CD
-- Mentor(s):  
+- Mentor(s):
   - Yuri Shkuro (@yurishkuro, github@ysh.us)
-  - Jonah Kowall (@jkowall, jkowall@kowall.net 
+  - Jonah Kowall (@jkowall, jkowall@kowall.net)
 - Upstream Issue: https://github.com/jaegertracing/jaeger/issues/5767