Merge pull request #288 from AdobeDocs/fix-events-links

fix: events links

src/pages/getting_started/first_app.md

@@ -211,7 +211,7 @@ There are a few sample flows listed below. Some developers may not have access t
     Each option indicates a feature you can enable for your App Builder application. Select one or all the options depending on the application you intend to build. We recommend you select all for now to fully explore all the options.
 
     - **Actions: Deploy Runtime actions:** adding the boilerplate for backend serverless actions on [Adobe I/O Runtime](/runtime)
-    - **Events: Publish to Adobe I/O Events:** adding the boilerplate for a serverless action that publishes [Custom I/O Events](/apis/experienceplatform/events/docs.html#!adobedocs/adobeio-events/master/using/custom_events.md)
+    - **Events: Publish to Adobe I/O Events:** adding the boilerplate for a serverless action that publishes [Custom I/O Events](/events/docs/guides/using/custom_events/)
     - **Web Assets: Deploy hosted static assets:** adding the boilerplate for frontend [React-Spectrum](https://react-spectrum.adobe.com/) SPA and static assets
     - **CI/CD: Include GitHub Actions based workflows for Build, Test and Deploy:** adding the boilerplate for Github Actions supporting CI/CD process of the application
 

src/pages/resources/event-driven/lesson4.md

@@ -20,7 +20,7 @@ There are three ways one can consume event:
 For enterprise developers, Adobe offers journaling to consume events. The Adobe I/O Events Journaling API enables enterprise integrations to consume events according to their own cadence and process them in bulk. Unlike webhooks, no additional registration or other configuration is required; every enterprise integration that is registered for events is automatically enabled for journaling. Journaling data is retained for 7 days. 
 
 After you fire event, you should be able to verify your event through journaling `UNIQUE API ENDPOINT` you get from console by follow below instruction
-[Journaling api](/apis/experienceplatform/events/docs.html#!adobedocs/adobeio-events/master/intro/journaling_api.md)
+[Journaling api](/events/docs/guides/api/journaling_api/)
 you could use `Curl` command or `POSTMAN` to call this journaling `UNIQUE API ENDPOINT` to see your fired event.
 Or you can use [Custom event SDK](https://github.com/adobe/aio-lib-events/) to call Journaling API to retrieve your event.
 
@@ -144,7 +144,7 @@ Your webhook needs to
 -   be reachable over HTTPS
 -   correctly respond to a "challenge" request
 For more details, follow the link below: 
-[how to use webhook](/apis/experienceplatform/events/docs.html#!adobedocs/adobeio-events/master/intro/webhook_docs_intro.md)
+[how to use webhook](/events/docs/guides/)
 
 ## Let's test it, and fire events
 With that,once you fire the event (in our codelab case, click the invoke button) you should see them appearing in above three options:

src/pages/resources/event-driven/welldone.md

@@ -16,7 +16,7 @@ Explore more features with custom event SDK
 [Custom event SDK](https://github.com/adobe/aio-lib-events/) and [Custom Event CLI Plugin](https://github.com/adobe/aio-cli-plugin-events)
 
 If you would like to use API, here is the API doc: 
-[Event API](/apis/experienceplatform/events/ioeventsapi.html#!adobedocs/adobeio-events/master/events-api-reference.yaml)
+[Event API](/events/docs/guides/api/)
 
 In addition, more to read about Adobe I/O Event: 
 [Adobe I/O Event](/experienceplatform/events.html)

src/pages/resources/journaling-events/requirements.md

@@ -19,5 +19,5 @@ In addition to above pre-requisites, you'll need to read through the below docs
 * [Getting Started with Adobe I/O Custom Events](../event-driven/index.md)
 * [Setting up Your Environment](../cron-jobs/index.md)
 * [Adobe I/O Events CLI Plugin](https://github.com/adobe/aio-cli-plugin-events)
-* [Journaling API](/apis/experienceplatform/events/docs.html#!adobedocs/adobeio-events/master/api/journaling_api.md)
+* [Journaling API](/events/docs/guides/api/journaling_api/)