@@ -34,16 +34,15 @@ without using the Native SDK, see the following resources:
34
34
35
35
## Integrating the SDK
36
36
37
- The Native SDK currently supports ** Windows, macOS, Linux and Android** .
37
+ The Native SDK currently supports ** Windows** , ** macOS** , ** Linux** , and ** Android** .
38
38
39
39
### Building the SDK
40
40
41
41
To build the SDK, download the latest release of the SDK from the [ Releases
42
42
page] ( https://github.com/getsentry/sentry-native/releases ) .
43
- The SDK is managed as a [ CMake] project, which additionally supports a number
44
- of configuration options, such as the backend to use.
43
+ The SDK is managed as a [ CMake] project, which additionally supports several configuration options, such as the backend to use.
45
44
46
- ` CMake ` can be used for example like this (on macOS):
45
+ For example, ` CMake ` can be used like this (on macOS):
47
46
48
47
``` sh
49
48
# configure the cmake build into the `build` directory, with crashpad (on macOS)
@@ -398,7 +397,7 @@ background thread or thread pool to avoid blocking execution.
398
397
and libraries. Similar to plugins, they extend the functionality of the Sentry
399
398
SDK.
400
399
401
- The Native SDK can use different backends that are responsible to capture
400
+ The Native SDK can use different backends that are responsible for capturing
402
401
crashes. The backend is configured at build-time, using the `SENTRY_BACKEND`
403
402
CMake option.
404
403
@@ -447,7 +446,7 @@ in the same request, such as log files.
447
446
{% include platforms/event-attachments.md %}
448
447
449
448
To add an attachment, the path to the file has to be configured when
450
- initializing the SDK. It will monitor the file and upload it along any event
449
+ initializing the SDK. It will monitor the file and upload it along with any event
451
450
or crash that is sent to Sentry:
452
451
453
452
```c
0 commit comments