Update platform-includes/capture-error/go.mdx

ribice · cleptric · web-flow · commit debd8c48e327 · 2024-12-20T19:04:50.000+01:00
Co-authored-by: Michi Hoffmann &lt;cleptric@users.noreply.github.com&gt;
diff --git a/platform-includes/capture-error/go.mdx b/platform-includes/capture-error/go.mdx
@@ -1,4 +1,4 @@
-To capture an event in Go, you can pass any struct implementing an `error` interface to `CaptureException()`. If you use a 3rd party library instead of native `errors` package and it implements `Unwrap() error` or `Cause() error` method, we'll follow the chain of errors and extract the stack trace from the root cause.
+To capture an event in Go, you can pass any struct implementing an `error` interface to `CaptureException()`. If you use a 3rd party library instead of the native `errors` package and it implements the `Unwrap() error` or `Cause() error` method, we'll follow the chain of errors and extract the stack trace from the root cause.
 
 The SDK is fully compatible with (but not limited to):
 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		-To capture an event in Go, you can pass any struct implementing an `error` interface to `CaptureException()`. If you use a 3rd party library instead of native `errors` package and it implements `Unwrap() error` or `Cause() error` method, we'll follow the chain of errors and extract the stack trace from the root cause.
	`1`	+To capture an event in Go, you can pass any struct implementing an `error` interface to `CaptureException()`. If you use a 3rd party library instead of the native `errors` package and it implements the `Unwrap() error` or `Cause() error` method, we'll follow the chain of errors and extract the stack trace from the root cause.
`2`	`2`
`3`	`3`	`The SDK is fully compatible with (but not limited to):`
`4`	`4`