Corrections

Author: limbonaut

docs/platforms/godot/configuration/stack-traces.mdx

@@ -1,6 +1,6 @@
 ---
 title: Readable Stack Traces
-description: "Learn how to get readable stack traces in Sentry with Sentry SDK for Godot Engine."
+description: "Learn how to get readable stack traces in Sentry with SDK for Godot Engine."
 ---
 
 Debug information files allow Sentry to extract stack traces and provide additional information about crash reports. In order to get readable stack traces in Sentry when your game crashes, you need to export your project using an export template that contains debug information. For the official builds, Godot Engine only provides templates without debug symbols. This guide covers how to create such templates and use them to export your project with full debug information available in Sentry.
@@ -9,7 +9,7 @@ Debug information files allow Sentry to extract stack traces and provide additio
 
 To get debug information, we need to compile export templates with debug symbols produced. You'll need Git, SCons build tool, Python, and a C++ compiler for your target platform installed.
 
-Ensure you have a compatible C++ compiler. On Windows, for instance, you can use [Visual Studio Community 2022](https://visualstudio.microsoft.com/) with the C++ workload installed.
+Ensure you have a compatible C++ compiler. On Windows, for instance, you can use [Visual Studio Community 2022](https://visualstudio.microsoft.com/) with the C++ workload installed, GCC on Linux and Clang on macOS.
 
 Here are a few ways to install the **SCons** build tool:
 
@@ -104,7 +104,7 @@ If you need to `Export with Debug`, you can compile a debug template using the `
 
 ## Uploading Debug Symbols
 
-In order to see readable stack traces in Sentry, you also need to upload your debug symbols. The easiest way to do it is by using Sentry CLI tools. These tools allow you to upload the necessary debug information, making the stack traces useful for debugging.
+In order to get readable stack traces in Sentry, you also need to upload your debug symbols. The easiest way to do it is by using Sentry CLI tools. These tools allow you to upload the necessary debug information, making the stack traces useful for debugging.
 
 <Expandable title="Installing Sentry CLI">