Skip to content

Commit 05ce54b

Browse files
authored
Change to header
1 parent 2746ed3 commit 05ce54b

File tree

1 file changed

+5
-3
lines changed
  • src/connections/auto-instrumentation

1 file changed

+5
-3
lines changed

src/connections/auto-instrumentation/setup.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -62,8 +62,9 @@ Follow these steps to integrate the Signals SDK into your Swift application:
6262

6363
Verify that you replaced `<WRITE_KEY>` with the actual write key you copied in Step 1.
6464

65-
> info "SwiftUI Projects"
66-
> If your app is written in SwiftUI, you will need to add a `TypeAlias.swift` file to your project in order to capture interaction and navigation Signals. Refer to the example below for more information
65+
#### SwiftUI projects
66+
67+
If your app is written in SwiftUI, you'll need to add a `TypeAlias.swift` file to your project that captures interaction and navigation Signals, like in this example:
6768
6869
```swift
6970
import Foundation
@@ -75,6 +76,7 @@ typealias NavigationLink = SignalNavigationLink
7576
typealias TextField = SignalTextField
7677
typealias SecureField = SignalSecureField
7778
```
79+
7880
### Kotlin
7981
8082
Follow these steps to integrate the Signals SDK into your Kotlin application:
@@ -149,4 +151,4 @@ Redeployment ensures that the new rules are active and that your application can
149151
150152
## Next steps
151153
152-
This guide walked you through initial Signals SDK/Auto-Instrumentation setup. Next, read the [Auto-Instrumentation Signals Implementation Guide](/docs/connections/auto-instrumentation/configuration/), which dives deeper into Signals and offers examples rules.
154+
This guide walked you through initial Signals SDK/Auto-Instrumentation setup. Next, read the [Auto-Instrumentation Signals Implementation Guide](/docs/connections/auto-instrumentation/configuration/), which dives deeper into Signals and offers examples rules.

0 commit comments

Comments
 (0)