Add images and fix formatting issues

Author: MaedahBatool

docs/batch-changes/push-only-changesets.mdx

@@ -1,26 +1,26 @@
-**Pushing code to a code host**
+# Pushing code to a code host
 
 <p className="subtitle">Learn how to push code changes to a code host without making a merge request.</p>
 
 <Callout type="note">Pushed-only changesets work on GitHub and GitLab only. They do not yet work with forked repositories.</Callout>
 
+After you've [created a batch change](/batch-changes/create-a-batch-change), you will be redirected to a page displaying a list of the changesets the Batch Change created. From this page, you can apply any bulk operation to more than one changesets.
 
-After you've [created a batch change](/batch-changes/create-a-batch-change), you will be redirected to a page displaying a list of the changesets the Batch Change created. From this page, you can apply any bulk operation to 1+ changesets. 
+ To push code to a new branch on a code host without also creating a merge request, simply select **Push to code host only** from the dropdown menu:
 
+![push-only-dropdown](https://storage.googleapis.com/sourcegraph-assets/Docs/push-only-dropdown-0625.png)
 
- To push code to a new branch on a code host without also creating a merge request, simply select 'push only' from the dropdown menu: 
+## Few important considerations
 
- [image would go here]
-
-
-## Notes
-- With pushed-only changesets, you are still able see CI feedback, as long as it triggers on code pushes.
-- The `review` status of a pushed-only changeset is always "N/A." 
-- The `status` of a pushed-only changeset is always "OPEN."
-- To publish a pushed-only changeset, simply select the changeset in the Batch Changes UI and select 'Publish.'
+- With pushed-only changesets, you are still able see CI feedback, as long as it triggers on code pushes
+- The `review` status of a pushed-only changeset is always "N/A"
+- The `status` of a pushed-only changeset is always "Open"
+- To publish a pushed-only changeset, simply select the changeset in the Batch Changes UI and select **Publish**
 
+![push-only-changesets-executed](https://storage.googleapis.com/sourcegraph-assets/Docs/push-only-executed-0625.png)
 
 ## Requirements
+
 To push code to a new branch on a code host, you will need:
 
 - [Admin permissions for the batch change](/batch-changes/permissions-in-batch-changes#permission-levels-for-batch-changes)

docs/batch-changes/quickstart.mdx

@@ -102,10 +102,8 @@ The batch change's **changesets** still need to be published, which means they e
 
 So far, nothing has been created on your code hosts. To do so, you can tell Sourcegraph to either **publish** or **push** a changeset.
 
-- **Publishing** a changeset results in the creation of a merge request on your code host (e.g. a Pull Request on GitHub).
-
-- **Pushing** a changeset (available on GitHub and GitLab only) results in pushing your code changes to a new branch on your code host _without_ also creating a merge request. You are able to see any CI feedback set to trigger upon code-pushes in the Batch Changs UI. 
-    - Read more about push-only changesets under the Bulk Operations heading.
+- **[Publishing](/batch-changes/publishing-changesets)** a changeset results in the creation of a merge request on your code host (e.g. a Pull Request on GitHub).
+- **[Pushing](/batch-changes/push-only-changesets)** a changeset (available on GitHub and GitLab only) results in pushing your code changes to a new branch on your code host without also creating a merge request. You are able to see any CI feedback set to trigger upon code-pushes in the Batch Changs UI.
 
 ### Configure code host credentials