Apply suggestions from code review

Co-authored-by: Brody <[email protected]>

Author: katmayb

src/langsmith/billing.mdx

@@ -26,7 +26,7 @@ To set up billing for your LangSmith organization, navigate to the [Usage and Bi
 
 ### Developer Plan: set up billing on your personal organization
 
-Personal organizations are limited to 5000 traces per month until a credit card is added. You can add a credit card on the Plans and Billing page as follows:
+Personal organizations are limited to 5000 traces per month until a credit card is added. You can add a credit card on the **Plans and Billing** page as follows:
 
 1. Click **Set up Billing**
 
@@ -39,7 +39,7 @@ Personal organizations are limited to 5000 traces per month until a credit card
 If you have not yet created an organization, you need to follow [this guide](/langsmith/set-up-a-workspace#set-up-an-organization) before setting up billing. The following steps assume you are already in a new organization.
 
 <Note>
-You cannot use a new organization until you have entered credit card information. After you complete the following steps, you will gain complete access to LangSmith.
+You can't use a new organization until you enter credit card information. After you complete the following steps, you will gain complete access to LangSmith.
 </Note>
 
 1. Click **Subscribe** on the **Plus** page.
@@ -64,12 +64,12 @@ Once this step is complete, your organization will have access to the rest of La
 
 If you joined LangSmith before pricing was introduced on April 2, 2024, you have the option to upgrade your existing account to set up billing. If you did not set up billing by July 8, 2024, then your account is now rate limited to a maximum of 5,000 traces per month.
 
-1. Navigate to the [Settings page](https://smith.langchain.com/settings) page under **Settings**.
+1. Navigate to the [Settings](https://smith.langchain.com/settings) page.
 2. Click **Set up Billing**.
 
   ![](/langsmith/images/setup-billing-legacy.png)
 
-3. Enter your credit card information. If you are on a Personal organization, this will add you to the Developer plan. If you are on a shared organization, this will add you to the Plus plan. For more information, refer to the guides for the [Developer](#developer-plan%3A-set-up-billing-on-your-personal-organization) or [Plus](#plus-plan%3A-set-up-billing-on-a-shared-organization) respectively, starting at step 2.
+3. Enter your credit card information. If you are on a Personal organization, this will add you to the Developer plan. If you are on a shared organization, this will add you to the Plus plan. For more information, refer to the guides for the [Developer](#developer-plan%3A-set-up-billing-on-your-personal-organization) or [Plus](#plus-plan%3A-set-up-billing-on-a-shared-organization) plans respectively, starting at step 2.
 4. Claim free credits as a thank you for being an early LangSmith user.
 
 ## Update your information
@@ -84,7 +84,7 @@ Business information, tax ID, and invoice email can only be updated for the Plus
 
 ![](/langsmith/images/update-invoice-email.png)
 
-To update the email address for invoices follow these steps:
+To update the email address for invoices, follow these steps:
 
 1. Navigate to the **Plans and Billing** tab.
 2. Locate the section beneath the payment method, where the current invoice email is displayed.
@@ -125,7 +125,7 @@ You may find it helpful to read the following pages, before continuing with this
 </Check>
 
 <Note>
-Some of the features mentioned in this guide are not currently available in Enterprise plan due to its custom nature of billing. If you are on Enterprise plan and have questions about cost optimization, please reach out to your sales rep or [[email protected]](mailto:[email protected]).
+Some of the features mentioned in this guide are not currently available on Enterprise plan due to its custom nature of billing. If you are on the Enterprise plan and have questions about cost optimization, reach out to your sales rep or [[email protected]](mailto:[email protected]).
 </Note>
 
 You will learn how to optimize existing spend and prevent future overspend in LangSmith, which includes:
@@ -172,7 +172,7 @@ In the GIF, you'll see that the charges for LangSmith Traces are broken up by "t
 
 These upgrades occur for two reasons:
 
-1. You use extended data retention tracing, whic means by default your traces are retained for 400 days.
+1. You use extended data retention tracing, which means by default your traces are retained for 400 days.
 2. You use base data retention tracing and use a feature that automatically extends the data retention of a trace. ([Refer to the Auto-Upgrade conceptual docs](/langsmith/administration-overview#data-retention).)
 
 Given that the number of total traces per day is equal to the number of extended retention traces per day, it's most likely the case that this organization is using extended data retention tracing everywhere. As a result, start by optimizing the retention settings.
@@ -242,7 +242,7 @@ Start by setting limits on production usage, since that is where the majority of
 
 #### Set a good total traces limit
 
-Picking the right "total traces" limit depends on the expected load of traces that you will send to LangSmith. It is important to consider potential growth before setting a limit. For example:
+Picking the right total traces limit depends on the expected load of traces that you will send to LangSmith. It is important to consider potential growth before setting a limit. For example:
 
 - **Current Load**: The gen AI application is called between 1.2-1.5 times per second, and each API request has a trace associated with it, meaning it logs around 100,000-130,000 traces per day.
 - **Expected Growth in Load**: The expectation is that this will double in size in the near future.
@@ -255,7 +255,7 @@ limit = current_load_per_day * expected_growth * days/month
       = 7,800,000 traces / month
 ```
 
-Click on the edit icon on the right side of the table for our **Prod** row, you can enter this limit as follows:
+Click on the edit icon on the right side of the table for the **Prod** row to enter the limit.
 
 ![](/langsmith/images/p2alllimitonly-v2.png)
 
@@ -272,14 +272,14 @@ From [Optimization 1](#optimization-1-manage-data-retention), you learned that t
 The maximum cost is cut from \~40k per month to \~7.5k per month, because you no longer allow as many expensive data retention upgrades. This ensures that new users on the platform will not accidentally cause cost to balloon.
 
 <Note>
-The extended data retention limit can cause features other than traces to stop working once reached. If you plan to use this feature, please read more about its functionality [here](/langsmith/administration-overview#side-effects-of-extended-data-retention-traces-limit).
+The extended data retention limit can cause features other than traces to stop working once reached. If you plan to use this feature, read more about its [functionality and side effects](/langsmith/administration-overview#side-effects-of-extended-data-retention-traces-limit).
 </Note>
 
 #### Set dev/staging limits and view total spent limit across workspaces
 
 Following a similar logic for the `dev` and `staging` environments, you can set limits at 10% of the production limit on usage for each workspace.
 
-While this works with this usage pattern, setting good dev and staging limits may vary depending on your use case with LangSmith. For example, if you run evals as part of CI/CD in dev or staging, you may want to be more liberal with your usage limits to avoid test failures.
+While this works with this usage pattern, setting good dev and staging limits may vary depending on your use case with LangSmith. For example, if you run evals as part of CI/CD in dev or staging, you may want to be more flexible with your usage limits to avoid test failures.
 
 With the limits set, LangSmith shows a maximum spend estimate across all workspaces:
 

src/langsmith/manage-datasets.mdx

@@ -24,7 +24,7 @@ By default, the version is defined by the timestamp of the change. When you clic
 
 ![Version Datasets](/langsmith/images/version-dataset.png)
 
-Note that examples are read-only when viewing a past version of the dataset. You will also see the operations that were between this version of the dataset and the "latest" version of the dataset. 
+Note that examples are read-only when viewing a past version of the dataset. You will also see the operations that were between this version of the dataset and the latest version of the dataset. 
 
 <Note>
 By default, the latest version of the dataset is shown in the **Examples** tab and experiments from all versions are shown in the **Tests** tab.
@@ -223,9 +223,11 @@ From the **Dataset & Experiments** tab, select a dataset, click **⋮** (top rig
 
 ### Unshare a dataset
 
-1. Click on **Unshare** by click on **Public** in the upper right hand corner of any publicly shared dataset, then **Unshare** in the dialog. ![Unshare Dataset](/langsmith/images/unshare-dataset.png)
+1. Click on **Unshare** by clicking on **Public** in the upper right hand corner of any publicly shared dataset, then **Unshare** in the dialog. ![Unshare Dataset](/langsmith/images/unshare-dataset.png)
 
-2. Navigate to your organization's list of publicly shared datasets, by clicking on **Settings** -> **Shared URLs** or [this link](https://smith.langchain.com/settings/shared), then click on **Unshare** next to the dataset you want to unshare. ![Unshare Trace List](/langsmith/images/unshare-trace-list.png)
+2. Navigate to your organization's list of publicly shared datasets, by clicking on **Settings** -> **Shared URLs** or [this link](https://smith.langchain.com/settings/shared), then click on **Unshare** next to the dataset you want to unshare.
+
+![Unshare Trace List](/langsmith/images/unshare-trace-list.png)
 
 ## Export a dataset
 

src/langsmith/set-up-a-workspace.mdx

@@ -57,7 +57,7 @@ For a full list of permissions associated with each role, refer to the [Administ
 
 ## Set up a workspace
 
-When you log in for the first time, a default [workspace](/langsmith/administration-overview#workspaces) will be created for you automatically in your personal organization. Workspaces are often used to separate resources between different teams or business units to establish clear trust boundaries between them. Within each workspace, Role-Based Access Control (RBAC) manages permissions and access levels, which ensures that users only have access to the resources and settings necessary for their role. Most LangSmith activity happens in the context of a workspace, each of which has its own settings and access controls.
+When you log in for the first time, a default [workspace](/langsmith/administration-overview#workspaces) will be created for you in your personal organization. Workspaces are often used to separate resources between different teams or business units to establish clear trust boundaries between them. Within each workspace, Role-Based Access Control (RBAC) manages permissions and access levels, which ensures that users only have access to the resources and settings necessary for their role. Most LangSmith activity happens in the context of a workspace, each of which has its own settings and access controls.
 
 To organize resources within a workspace, you can use [resource tags](/langsmith/set-up-resource-tags).