Improve Getting started guide for snap-ins (#158)

* Improve Getting started guide

* Update fern/docs/pages/tutorials/timer-ticket-creator.mdx

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* merge notes

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: codeon

fern/docs/pages/start.mdx

@@ -122,7 +122,8 @@ devrev snap_in draft
 ```
 
 <Callout intent="note">
-To install the snap-in, you must be a member of the **Admins** group in the dev org.
+1. To install the snap-in, you must be a member of the **Admins** group in the dev org.
+2. If you get a `snap-in version is not ready` error, check the version state with `devrev snap_in_version show`. The state should be `ready` for installation. If `build_failed`, check the logs for errors.
 </Callout>
 
 <br />
@@ -150,6 +151,14 @@ To make a connection available to other members in your organization, create it
 Once you have provided the required configuration, the **Deploy snap-in** button is enabled on the UI. Click on it to deploy the snap-in.
 That's it, the snap-in should now be active and ready to use.
 
+### Check snap-in logs
+
+To check the logs for the snap-in, run the following command:
+
+```bash
+devrev snap_in_package logs | jq
+```
+
 ### Delete the snap-in
 
 The snap-in can be deleted from the UI or run the following command:

fern/docs/pages/tutorials/timer-ticket-creator.mdx

@@ -4,9 +4,8 @@ The objective is to build a snap-in that creates a new ticket every 10 minutes.
 
 ## Background context
 
-In the [Getting Started](/snapin-development/tutorials/getting-started) tutorial, you learned how to create a
-hello-world snap-in which prints a log message when a work item is created. In this tutorial, you will make the following changes to the snap-in:
-
+The [Getting Started](/snapin-development/tutorials/getting-started) tutorial creates a hello-world snap-in which prints a log message when a work item is created.
+This tutorial makes the following changes to the snap-in:
 1. Update the trigger condition to run every 10 minutes instead of work
    creation.
 2. Create a ticket whenever the snap-in is triggered.