update links

open-telemetry · Oct 16, 2024 · cba412e · cba412e
1 parent 7e0ce25
commit cba412e
Show file tree

Hide file tree

Showing 2 changed files with 24 additions and 22 deletions.
diff --git a/specification/logs/event-api.md b/specification/logs/event-api.md
@@ -9,17 +9,18 @@
 
 <!-- toc -->
 
-- [Logs Instrumentation API Development](#logs-instrumentation-api-development)
-- [Event Data model](#event-data-model)
-- [Event API use cases](#event-api-use-cases)
-- [EventLoggerProvider](#eventloggerprovider)
-  * [EventLoggerProvider operations](#eventloggerprovider-operations)
-    + [Get an EventLogger](#get-an-eventlogger)
-- [EventLogger](#eventlogger)
-  * [EventLogger Operations](#eventlogger-operations)
-    + [Emit Event](#emit-event)
-- [Optional and required parameters](#optional-and-required-parameters)
-- [References](#references)
+- [Events API](#events-api)
+  - [Logs Instrumentation API Development](#logs-instrumentation-api-development)
+  - [Event Data model](#event-data-model)
+  - [Event API use cases](#event-api-use-cases)
+  - [EventLoggerProvider](#eventloggerprovider)
+    - [EventLoggerProvider operations](#eventloggerprovider-operations)
+      - [Get an EventLogger](#get-an-eventlogger)
+  - [EventLogger](#eventlogger)
+    - [EventLogger Operations](#eventlogger-operations)
+      - [Emit Event](#emit-event)
+  - [Optional and required parameters](#optional-and-required-parameters)
+  - [References](#references)
 
 <!-- tocstop -->
 
@@ -34,7 +35,7 @@ The Event API consists of these main components:
 ## Logs Instrumentation API Development
 
 > [!NOTE]
-> We are currently in the process of defining a new [Logs Instrumentation API](./bridge-api.md#logs-instrumentation-api).
+> We are currently in the process of defining a new [Logs Instrumentation API](./bridge-api.md#log-instrumentation-operations).
 
 The intent is that this Logs Instrumentation API will incorporate the current functionality of this existing Events API and once it is defined and implemented, the Events API usage will be migrated, deprecated, renamed and eventually removed.
 

diff --git a/specification/logs/event-sdk.md b/specification/logs/event-sdk.md
@@ -9,15 +9,16 @@
 
 <!-- toc -->
 
-- [Logs Instrumentation API Development](#logs-instrumentation-api-development)
-- [Overview](#overview)
-- [EventLoggerProvider](#eventloggerprovider)
-  * [EventLoggerProvider Creation](#eventloggerprovider-creation)
-  * [EventLogger Creation](#eventlogger-creation)
-  * [Configuration](#configuration)
-  * [ForceFlush](#forceflush)
-- [EventLogger](#eventlogger)
-  * [Emit Event](#emit-event)
+- [Events SDK](#events-sdk)
+  - [Logs Instrumentation API Development](#logs-instrumentation-api-development)
+  - [Overview](#overview)
+  - [EventLoggerProvider](#eventloggerprovider)
+    - [EventLoggerProvider Creation](#eventloggerprovider-creation)
+    - [EventLogger Creation](#eventlogger-creation)
+    - [Configuration](#configuration)
+    - [ForceFlush](#forceflush)
+  - [EventLogger](#eventlogger)
+    - [Emit Event](#emit-event)
 
 <!-- tocstop -->
 
@@ -33,7 +34,7 @@ All implementations of the OpenTelemetry API MUST provide an SDK.
 ## Logs Instrumentation API Development
 
 > [!NOTE]
-> We are currently in the process of defining a new [Logs Instrumentation API](./bridge-api.md#logs-instrumentation-api).
+> We are currently in the process of defining a new [Logs Instrumentation API](./bridge-api.md#log-instrumentation-operations).
 
 The intent is that Logs SDK will incorporate the current functionality of this existing Events SDK and once it is defined and implemented, the Events SDK usage will be migrated, deprecated, renamed and eventually removed.