reorder sections in apple usage so simplest thing is above the fold (#13883)

Co-authored-by: Alex Krawiec <[email protected]>

Author: 2 people

docs/platforms/apple/common/usage/index.mdx

@@ -17,18 +17,18 @@ Key terms:
 
 </Alert>
 
-The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
+## Capturing Messages
 
-While capturing an event, you can also record the breadcrumbs that lead up to that event. Breadcrumbs are different from events: they will not create an event in Sentry, but will be buffered until the next event is sent. Learn more about breadcrumbs in our <PlatformLink to="/enriching-events/breadcrumbs/">Breadcrumbs documentation</PlatformLink>.
+The simplest operation is to capture a bare message: textual information that should be sent to Sentry. Typically, our SDKs won't automatically capture messages, but you can capture them manually.
 
-## Capturing Errors
+Messages show up as issues on your issue stream, with the message as the issue name.
 
-<PlatformContent includePath="capture-error" />
+<PlatformContent includePath="capture-message" />
 
-## Capturing Messages
+## Capturing Errors
 
-Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.
+The most common usage of the Apple SDKs is to capture errors. In general, if you have something that looks like an exception, it can be captured, though this varies by platform. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. This is also useful for manual reporting of errors or messages to Sentry.
 
-Messages show up as issues on your issue stream, with the message as the issue name.
+While capturing an event, you can also record the breadcrumbs that lead up to that event. Breadcrumbs are different from events: they will not create an event in Sentry, but will be buffered until the next event is sent. Learn more in our <PlatformLink to="/enriching-events/breadcrumbs/">Breadcrumbs documentation</PlatformLink>.
 
-<PlatformContent includePath="capture-message" />
+<PlatformContent includePath="capture-error" />