Skip to content

Commit ac36a74

Browse files
markzegarellistayseesong
andauthored
Fixed broken links (#2997)
* Fixed broken links * Apply suggestions from code review Co-authored-by: stayseesong <[email protected]> Co-authored-by: stayseesong <[email protected]>
1 parent 2490a81 commit ac36a74

File tree

7 files changed

+38
-37
lines changed

7 files changed

+38
-37
lines changed

scripts/catalog_papi.js

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,8 @@ const updateSources = async () => {
180180
const hiddenSources = [
181181
'amp',
182182
'factual-engine',
183-
'twilio-event-streams-beta'
183+
'twilio-event-streams-beta',
184+
'ibm-watson-assistant'
184185
]
185186

186187
const regionalSourceEndpoint = regionalSupport.sources.endpoint

src/_data/catalog/sources.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -535,7 +535,7 @@ items:
535535
isCloudEventSource: false
536536
slug: ibm-watson-assistant
537537
url: connections/sources/catalog/cloud-apps/ibm-watson-assistant
538-
hidden: false
538+
hidden: true
539539
regions:
540540
- us
541541
endpoints:

src/connections/destinations/catalog/byteplus/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ This destination is maintained by BytePlus. For any issues with the destination,
2020
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
2121
2. Search for "BytePlus" in the Destinations Catalog, and select the "BytePlus" destination.
2222
3. Choose which Source should send data to the "BytePlus" destination.
23-
4. In BytePlus, go to your "[Organization Settings](https://docs.byteplus.com/data-intelligence/docs/create-your-organizations-and-projects)" > "Project List" and find the targeted project.
23+
4. In BytePlus, go to Organization Settings > Project List and find the targeted project.
2424
5. Click on **Details** for the targeted project and find the API key ("App Key") on the pop-out information page. This should be a 32-character string of numbers and letters.
2525
6. Enter the "API Key" in the "BytePlus" destination settings in Segment.
2626

src/connections/destinations/catalog/datarangers/index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,14 +18,14 @@ This destination is maintained by BytePlus. For any issues with the destination,
1818
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
1919
2. Search for "BytePlus" in the Destinations Catalog, and select the "BytePlus" destination.
2020
3. Choose which Source should send data to the "BytePlus" destination.
21-
4. In BytePlus, go to your "[Organization Settings](https://docs.byteplus.com/data-intelligence/docs/create-your-organizations-and-projects)" > "Project List" and find the targeted project.
21+
4. In BytePlus, go to Organization Settings > Project List and find the targeted project.
2222
5. Click on **Details** for the targeted project and find the API key ("App Key") on the pop-out information page. This should be a 32-character string of numbers and letters.
2323
6. Enter the "API Key" in the "BytePlus" destination settings in Segment.
2424

2525

2626
## Page
2727

28-
If you aren't familiar with the Segment Spec, take a look at the Page method documentation (https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like:
28+
If you aren't familiar with the Segment Spec, take a look at the Page method documentation (/docs/connections/spec/page/) to learn about what it does. An example call would look like:
2929

3030

3131
```js
@@ -37,7 +37,7 @@ Segment sends Page calls to BytePlus as a `page` event.
3737

3838
## Screen
3939

40-
If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like:
40+
If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like:
4141
```obj-c
4242
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
4343
```
@@ -46,7 +46,7 @@ Segment sends Screen calls to BytePlus as a`screen`event.
4646
4747
## Identify
4848
49-
If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like:
49+
If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like:
5050
5151
```js
5252
analytics.identify('userId123', {
@@ -57,7 +57,7 @@ Segment sends Identify calls to BytePlus as an `identify `event with `SSID`.
5757

5858
## Track
5959

60-
If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like:
60+
If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like:
6161
```js
6262
analytics.track('Login Button Clicked')
6363
```

src/connections/destinations/catalog/simplereach/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ rewrite: true
33
title: SimpleReach Destination
44
id: 55d3c70e0a20f4e22f0fb3eb
55
---
6-
[SimpleReach](https://simplereach.com/) helps brands, agencies, and publishers increase the impact of their content marketing. The SimpleReach Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-simplereach).
6+
SimpleReach helps brands, agencies, and publishers increase the impact of their content marketing. The SimpleReach Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-simplereach).
77

88
## Getting Started
99

src/connections/destinations/catalog/trafficguard/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This destination is maintained by TrafficGuard.
1616

1717
1. From the Segment web app, click **Catalog**.
1818
2. Search for "TrafficGuard" in the Catalog, select it, and choose which of your sources to connect the destination to.
19-
3. Enter the "API Key" into your Segment Settings UI which you can find in your property in the [TrafficGuard dashboard](https://dash.trafficguard.ai/dashboard).
19+
3. Enter the "API Key" into your Segment Settings UI which you can find in the property in the TrafficGuard dashboard.
2020

2121
![](images/trafficguard.png)
2222

0 commit comments

Comments
 (0)