fix(docs): fix broken links

Author: artus9033

docs/docs/docs/interop-otel/quick-start.mdx

@@ -6,11 +6,11 @@ Ottrelite provides interoperability with OpenTelemetry (OTEL) through a set of a
 
 #### Javascript
 
-Firstly, Ottrelite provides its own `TracerProvider` ([`OttreliteTracerProvider.ts`](./src/otel/OttreliteTracerProvider.ts)) that provides adequate configuration for JS (configures the default resource to carry ottrelite's metadata, registers W3C & trace context baggage propagators, by default - `StackContextManager`). Invoking `register` on it, apart from the aforementioned, also calls invokes configuration of the global C++ API provider, described in the section below.
+Firstly, Ottrelite provides its own `TracerProvider` ([`OttreliteTracerProvider.ts`](https://github.com/callstackincubator/ottrelite/blob/main/packages/interop-otel/src/otel/OttreliteTracerProvider.ts)) that provides adequate configuration for JS (configures the default resource to carry ottrelite's metadata, registers W3C & trace context baggage propagators, by default - `StackContextManager`). Invoking `register` on it, apart from the aforementioned, also calls invokes configuration of the global C++ API provider, described in the section below.
 
-The analogous applies to [`OttreliteMeterProvider`](src/otel/OttreliteMeterProvider.ts). An implementation detail difference is that the meter provider hooks into returned instrument creation methods & their return values dynamically by replacing properties on instances, to call its own logic before the original is executed.
+The analogous applies to [`OttreliteMeterProvider`](https://github.com/callstackincubator/ottrelite/blob/main/packages/interop-otel/src/otel/OttreliteMeterProvider.ts). An implementation detail difference is that the meter provider hooks into returned instrument creation methods & their return values dynamically by replacing properties on instances, to call its own logic before the original is executed.
 
-The OTEL API is also hooked into by the [`DevSpanProcessorInterceptor.ts`](src/otel/processor/DevSpanProcessorInterceptor.ts), which can be registered to propagate all OTEL spans live to the [Development API](../../README.md#development-api).
+The OTEL API is also hooked into by the [`DevSpanProcessorInterceptor.ts`](https://github.com/callstackincubator/ottrelite/blob/main/packages/interop-otel/src/otel/processor/DevSpanProcessorInterceptor.ts), which can be registered to propagate all OTEL spans live to the [Development API](https://callstackincubator.github.io/ottrelite/docs/core/quick-start.html#development-api-1).
 
 #### C++
 
@@ -53,7 +53,7 @@ After codegen-ing the C++ glue code from this spec, implement the exporter in C+
 
 Those methods are standard for OTEL exporters in according to its specification, yet the methods accept internal Ottrelite object types.
 
-The `OTLPExporterConfig` is Nitro-codegened from [`OTLPExporterConfig.ts`](src/types/OTLPExporterConfig.ts) and represents the most important JS configuration for exporters in general. If some more configuration levels are needed to be covered, please file a PR or issue.
+The `OTLPExporterConfig` is Nitro-codegened from [`OTLPExporterConfig.ts`](https://github.com/callstackincubator/ottrelite/blob/main/packages/interop-otel/src/types/OTLPExporterConfig.ts) and represents the most important JS configuration for exporters in general. If some more configuration levels are needed to be covered, please file a PR or issue.
 
 The `ExportResult` is trivial and is a 1:1 CPP-JS mapping of the result type.