fix doc

Author: cijothomas

opentelemetry-sdk/CHANGELOG.md

@@ -337,25 +337,6 @@ let processor = BatchLogProcessor::builder(exporter)
     .build();
 ```
 
-- Added `with_periodic_exporter` method to `MeterProviderBuilder`, allowing
- users to easily attach an exporter with a PeriodicReader for automatic metric
- export. Retained with_reader() for advanced use cases where a custom
- MetricReader configuration is needed.
-Example Usage:
-
-```rust
-SdkMeterProvider::builder()
-    .with_periodic_exporter(exporter)
-    .build();
-```
-
-Using a custom PeriodicReader (advanced use case):
-
-let reader = PeriodicReader::builder(exporter).build();
-SdkMeterProvider::builder()
-    .with_reader(reader)
-    .build();
-
 ## 0.27.1
 
 Released 2024-Nov-27

opentelemetry-sdk/src/metrics/meter_provider.rs

@@ -245,7 +245,7 @@ impl MeterProviderBuilder {
     }
 
     /// Associates a [MetricReader] with a [MeterProvider].
-    /// [`with_periodic_exporter`] can be used to add a PeriodicReader which is
+    /// [`MeterProviderBuilder::with_periodic_exporter()] can be used to add a PeriodicReader which is
     /// the most common use case.
     ///
     /// A [MeterProvider] will export no metrics without [MetricReader]
@@ -265,8 +265,8 @@ impl MeterProviderBuilder {
     ///
     /// Most users should use this method to attach an exporter. Advanced users
     /// who need finer control over the export process can use
-    /// [`PeriodicReaderBuilder`] to configure a custom reader and attach it
-    /// using [`with_reader`].
+    /// [`crate::metrics::PeriodicReaderBuilder`] to configure a custom reader and attach it
+    /// using [`MeterProviderBuilder::with_reader()`].
     pub fn with_periodic_exporter<T>(mut self, exporter: T) -> Self
     where
         T: PushMetricExporter,