Update to docs - naming (#136)

* Documentation edits made through Mintlify web editor

* Documentation edits made through Mintlify web editor

---------

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

integrations/linear.mdx

@@ -6,12 +6,12 @@ title: 'Linear integration'
 
 To easily keep track of feature requests and bugs reported in Plain, you can connect your Linear workspace with Plain.
 
-This lets you easily link a Linear issue to a thread – and ensures you're always prompted to reply to a customer when their bug is fixed or feature request is shipped. 
+This lets you easily link a Linear issue to a thread – and ensures you're always prompted to reply to a customer when their bug is fixed or feature request is shipped.
 
 To do this, head to **Settings** → **Linear integration** and connect your workspace.
 
 Once you've linked your Linear workspace to Plain, you can create a Linear issue (or link an existing Linear issue) directly to a customer request in the sidebar on the right hand side of a thread – or by pressing the shortcut:`i`.
 
 Once a Linear issue is linked, the thread will move back to `Close the loop` when the Linear issue is completed or canceled.
 
-Once you connect your Linear account and start linking issues to customer requests, you'll get access to a new Linear issues page in Plain – where you'll be able to get a ranked view of your top customer requests from Linear directly in Plain. You can also dig into each request, to understand which customers requested each feature, the tier breakdown of these customers and when the request was initially made.
+Once you connect your Linear account and start linking issues to customer requests, you'll get access to a new Product insights page in Plain – where you'll be able to get a ranked view of your top customer requests from Linear directly in Plain. You can also dig into each request, to understand which customers requested each feature, the tier breakdown of these customers and when the request was initially made.

thread-discussions.mdx

@@ -1,18 +1,18 @@
 ---
-title: 'Thread Discussions'
+title: "Slack Discussions"
 ---
 
 <Frame>![Example Thread Discussion](/public/images/discussions-introduction.png)</Frame>
 
-<br/>
-<Info>
-Thread Discussions are available on the [Grow pricing plan](https://www.plain.com/pricing) and above.
+<br />
 
-If you are interested in trying this feature, please reach out to us at [email protected] or via our shared Slack channel.
+<Info>
+  Slack Discussions are available on the [Grow pricing plan](https://www.plain.com/pricing) and above.
 
+  If you are interested in trying this feature, please reach out to us at [email protected] or via our shared Slack channel.
 </Info>
 
-Thread discussions allow you to lead conversations with your team about support requests in Slack.
+Slack discussions allow you to lead conversations with your team about support requests in Slack.
 
 To start a discussion you can either do it from within the thread in Plain or simply copy & paste the thread link to that channel.
 
@@ -21,24 +21,25 @@ For your convenience, the discussion will also be visible in the Plain thread.
 
 Any messages you or your team sends on the slack thread will show up in Plain, along with their reactions, mentions and attachments. You can respond either via Slack or directly through Plain.
 
-When a discussion is started, Plain will post a message with a "Resolve discussion" button. That can be used by anyone to signal that the discussion is concluded and the Plain thread will be moved back to Todo.
+When a discussion is started, Plain will post a message with a "Resolve discussion" button. That can be used by anyone to signal that the discussion is concluded and the Plain thread will be moved back to the "Close the loop" status – nudging your team to update the customer.
 
 To enable this functionality, you will need to setup your [Slack integration](/slack) and add the Plain bot to your channel.
 
 <Warning>
-  When Plain is added to a channel, we automatically classify it as a [Customer channel](/slack) if it's a _Slack Connect_ channel or one for internal discussions otherwise.
-
-For customer channels, we treat messages from non-Plain users as support requests, which are ingested as threads into Plain.
+  When Plain is added to a channel, we automatically classify it as a [Customer channel](/slack) if it's a *Slack Connect* channel or one for internal discussions otherwise.
 
-In discussion channels, on the other hand, we only ingest messages related to an on-going discussion.
+  For customer channels, we treat messages from non-Plain users as support requests, which are ingested as threads into Plain.
 
+  In discussion channels, on the other hand, we only ingest messages related to an on-going discussion.
 </Warning>
 
 For good data hygiene, we don't start discussions on all links to a Plain thread.
 We will not start a discussion if:
 
-- the link is posted by someone who is not a user in Plain.
-- the link is posted in a private channel Plain doesn't have access to.
-- the link is posted in a customer channel (typically _Slack Connect_), although you can always adjust this from your Slack settings.
+* the link is posted by someone who is not a user in Plain.
+
+* the link is posted in a private channel Plain doesn't have access to.
+
+* the link is posted in a customer channel (typically *Slack Connect*), although you can always adjust this from your Slack settings.
 
-If you want to opt out completely, you can disable thread discussions and link unfurling in your Slack integration settings.
+If you want to opt out completely, you can disable Slack discussions and link unfurling in your Slack integration settings.