asyavee/medusa-store
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: correct typos in documentation (#4413)

Browse Source 
* Correct typos in documentation

* Remove changes to References directory

---------

Co-authored-by: Shahed Nasser <shahednasser@gmail.com>
This commit is contained in:
Bhyn
2023-07-10 22:36:23 +10:00
committed by GitHub
parent 78a1f3943b
commit 6c3eeb8d18
29 changed files with 32 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/content/plugins/analytics/segment.md
View File

@@ -199,7 +199,7 @@ The `SegmentService` also provides the method `identify` to tie a user to their
After adding the above subscriber, run your backend again if it isn’t running and create a customer using the REST APIs or one of the Medusa storefronts. If you check the Debugger in your Segment source, you should see a new event “Customer Created” tracked. If you click on it, you’ll see the data you passed to the `track` method.
![The customer created event is recoreded on the Segment source](https://res.cloudinary.com/dza7lstvk/image/upload/v1668000759/Medusa%20Docs/Segment/4LD41xE_qungdw.png)
![The customer created event is recorded on the Segment source](https://res.cloudinary.com/dza7lstvk/image/upload/v1668000759/Medusa%20Docs/Segment/4LD41xE_qungdw.png)
---

2
docs/content/plugins/cms/contentful/index.md
View File

@@ -183,7 +183,7 @@ Using the Medusa admin, you can add products to your Medusa backend. This will t
This section explains how you can establish a two-way sync between Medusa and Contentful. This would ensure that not only is the data updated from the Medusa backend to Contentful, but also ensure the updates are relayed from Contentful to the Medusa backend.
However, to perform this sync, it's required that you deploy your backend so that it can be publically accessible. You can learn how to do that through the [backend deployment](../../../deployments/server/index.mdx) guides.
However, to perform this sync, it's required that you deploy your backend so that it can be publicly accessible. You can learn how to do that through the [backend deployment](../../../deployments/server/index.mdx) guides.
Configuring two-way sync requires configuring Webhooks in Contentful. To do that:

2
docs/content/plugins/notifications/slack.md
View File

@@ -20,7 +20,7 @@ The notification contains details about the order including:
The plugin registers a subscriber to the `order.placed` event. When an order is placed, the subscriber handler method uses the ID of the order to retrieve order details mentioned above.
Then, the order notificaiton is sent to Slack using Webhooks. So, you'll need to create a Slack App, add it into your workspace, and activate Incoming Webhooks.
Then, the order notification is sent to Slack using Webhooks. So, you'll need to create a Slack App, add it into your workspace, and activate Incoming Webhooks.
---