docs: general fixes across docs (#4737)

* docs: general fixes across docs

* added deploy button to railway

* fix eslint errors

* fixes

docs/content/development/events/create-subscriber.md

@@ -15,9 +15,9 @@ After creating the file under `src/subscribers`, in the constructor of your subs
 
 The `eventBusService.subscribe` method receives the name of the event as a first parameter and as a second parameter a method in your subscriber that will handle this event.
 
-For example, here is the `OrderNotifierSubscriber` class created in `src/subscribers/orderNotifier.ts`:
+For example, here is the `OrderNotifierSubscriber` class created in `src/subscribers/order-notifier.ts`:
 
-```ts title=src/subscribers/orderNotifier.ts
+```ts title=src/subscribers/order-notifier.ts
 class OrderNotifierSubscriber {
   constructor({ eventBusService }) {
     eventBusService.subscribe("order.placed", this.handleOrder)
@@ -93,7 +93,7 @@ You can access any service through the dependencies injected to your subscriber
 
 For example:
 
-```ts title=src/subscribers/orderNotifier.ts
+```ts title=src/subscribers/order-notifier.ts
 class OrderNotifierSubscriber {
   constructor({ productService, eventBusService }) {
       this.productService = productService
@@ -109,7 +109,7 @@ class OrderNotifierSubscriber {
 
 You can then use `this.productService` anywhere in your subscriber’s methods. For example:
 
-```ts title=src/subscribers/orderNotifier.ts
+```ts title=src/subscribers/order-notifier.ts
 class OrderNotifierSubscriber {
   // ...
   handleOrder = async (data) => {
@@ -129,4 +129,6 @@ When using attributes defined in the subscriber, such as the `productService` in
 
 ## See Also
 
+- [Example: send order confirmation email](../../modules/orders/backend/send-order-confirmation.md)
+- [Example: send registration confirmation email](../../modules/customers/backend/send-confirmation.md)
 - [Create a Plugin](../plugins/create.mdx)

docs/content/development/events/index.mdx

@@ -13,6 +13,12 @@ In this document, you’ll learn what events are and why they’re useful in Med
 
 Events are used in Medusa to inform different parts of the commerce ecosystem that this event occurred. For example, when an order is placed, the `order.placed` event is triggered, which informs notification services like SendGrid to send a confirmation email to the customer.
 
+:::tip
+
+If you want to implement order confirmation emails, you can check this [step-by-step guide](../../modules/orders/backend/send-order-confirmation.md).
+
+:::
+
 The events system in Medusa is built on a publish/subscribe architecture. The Medusa core publish an event when an action takes place, and modules, plugins, or other forms of customizations can subscribe to that event. [Subscribers](./subscribers.mdx) can then perform a task asynchronously when the event is triggered.
 
 Although the core implements the main logic behind the events system, you’ll need to use an event module that takes care of the publish/subscribe functionality such as subscribing and emitting events. Medusa provides modules that you can use both for development and production, including Redis and Local modules.