update formatting for the develop section

Author: eshaben

.CONTRIBUTING.md

@@ -30,9 +30,9 @@ You may want to spin up a local version of the documentation site to preview you
 
 Building and serving the site requires cloning two repositories:
 
-- **[Polkadot MkDocs](https://github.com/papermoonio/polkadot-mkdocs)** - contains the MkDocs configuration files, theme overrides, and custom CSS for the Polkadot documentation site
+- **[Polkadot MkDocs](https://github.com/papermoonio/polkadot-mkdocs)**: Contains the MkDocs configuration files, theme overrides, and custom CSS for the Polkadot documentation site.
 
-- **[Polkadot Docs](https://github.com/polkadot-developers/polkadot-docs)** - the actual content is stored in the `polkadot-docs` repository and pulled into the `polkadot-mkdocs` directory during build
+- **[Polkadot Docs](https://github.com/polkadot-developers/polkadot-docs)**: The actual content is stored in the `polkadot-docs` repository and pulled into the `polkadot-mkdocs` directory during build.
 
 For everything to work correctly, the file structure needs to be as follows:
 
@@ -90,16 +90,16 @@ When adding new pages to the documentation site, it is important to ensure all r
 
 To create a new section of pages, you will first need to create a subdirectory with the desired name of the section. The root directory, and every subdirectory, must contain the following files:
 
-- `.pages` - defines the structure of the documentation site
-- `index.md` - a landing page which can be used to provide more context about the content in the section
+- **`.pages`**: Defines the structure of the documentation site.
+- **`index.md`**: A landing page which can be used to provide more context about the content in the section.
 
 #### Example `.pages` File
 
 ```markdown
 title: Application Developers
 nav: 
   - index.md
-  - 'Polkadot SDK': 'polkadot-sdk.md'
+  - **'Polkadot SDK'**: 'polkadot-sdk.md'
   - interact
   - tooling
 ```
@@ -108,10 +108,10 @@ This example would result in adding 'Application Developers' as a section with t
 
 Some important things to note:
 
-- The `title` field at the top of the page represents the display name for the section. This is displayed on the left-side navigation bar when viewing the site
-- The `index.md` page should always be the first item in the `nav` list
-- Files follow the convention of `'Display Name': 'file-name.md'`
-- Sections are listed by their directory name in the source code. For example, the Tooling section will be added to the navigation simply by using the directory name: `tooling`
+- The `title` field at the top of the page represents the display name for the section. This is displayed on the left-side navigation bar when viewing the site.
+- The `index.md` page should always be the first item in the `nav` list.
+- Files follow the convention of `'Display Name': 'file-name.md'`.
+- Sections are listed by their directory name in the source code. For example, the Tooling section will be added to the navigation simply by using the directory name: `tooling`.
 
 #### Example `index.md` File
 
@@ -126,22 +126,22 @@ description: Learn how to build and customize blockchains with Polkadot SDK. Exp
 
 Some important things to note:
 
-- The `title` represents the `<title>` tag and is used for SEO purposes
-- The `description` represents the meta-description and is also used for SEO purposes
+- The `title` represents the `<title>` tag and is used for SEO purposes.
+- The `description` represents the meta-description and is also used for SEO purposes.
 
 ### Adding Pages to Existing Section
 
 If you are adding pages to an existing section, the steps are simplified. However, it's essential to ensure you complete these steps to display the new page and its title on the documentation site correctly:
 
 - Add the new markdown page to the appropriate section. Note that the filename becomes part of the URL for this page. See the [style guide](https://github.com/papermoonio/documentation-style-guide/blob/main/style-guide.md#naming-conventions) for additional guidance on naming conventions.
 - Ensure the new content page includes the following:
-    - **`title`** - represents the `<title>` tag and is used for SEO purposes (not displayed on the published site) Titles have a maximum length of 45 characters.
-    - **`description`** - represents the meta-description and is also used for SEO purposes (not displayed on the published site). Descriptions should be 120-160 characters and should provide a preview into the page topic.
-    - **Page title** - an H1 heading title to be displayed at the top of the page
+    - **`title`**: Represents the `<title>` tag and is used for SEO purposes (not displayed on the published site) Titles have a maximum length of 45 characters.
+    - **`description`**: Represents the meta-description and is also used for SEO purposes (not displayed on the published site). Descriptions should be 120-160 characters and should provide a preview into the page topic.
+    - **Page title**: An H1 heading title to be displayed at the top of the page.
 
-    - **`## Checking Prerequisites` section** - if the guide requires the user to have specific developer tools installed, for example, Docker or MetaMask, it should be listed here
+    - **`## Checking Prerequisites` section**: If the guide requires the user to have specific developer tools installed, for example, Docker or MetaMask, it should be listed here.
 
-- Add the 'Display Name': 'file-name.md' for the new page to the `.pages` folder in the same subdirectory where you added the new page
+- **Add the 'Display Name'**: 'file-name.md' for the new page to the `.pages` folder in the same subdirectory where you added the new page.
 
 An example new content page might look like:
 
@@ -172,10 +172,10 @@ More resources for [SEO Optimization](#search-engine-optimization-seo) of titles
     git checkout -b INSERT_NEW_BRANCH_NAME
     ```
 
-2. Modify content as desired. Remember to place images and code snippets in the appropriate folders (see the following sections for details)
-3. Review the [style guide](https://github.com/papermoonio/documentation-style-guide/blob/main/style-guide.md) to ensure your new content meets the guidelines
-3. Once you commit and push all of your changes, open a pull request for the new content branch against the `main` branch
-4. Monitor notifications and pull requests for feedback from code owners. At least one approval is required before merging content
+2. Modify content as desired. Remember to place images and code snippets in the appropriate folders (see the following sections for details).
+3. Review the [style guide](https://github.com/papermoonio/documentation-style-guide/blob/main/style-guide.md) to ensure your new content meets the guidelines.
+3. Once you commit and push all of your changes, open a pull request for the new content branch against the `main` branch.
+4. Monitor notifications and pull requests for feedback from code owners. At least one approval is required before merging content.
 
 If your additions or modifications are limited to content on an existing page, there is no need to worry about the [`.pages`](#example-pages-file) or [`index.md`](#example-indexmd-file) files, as changes to page content don't affect these files.
 
@@ -222,11 +222,11 @@ In general, titles should be between 50 and 60 characters and descriptions shoul
 
 There are a few tools you may find useful for proofreading and editing your contributions:
 
-- **[Vale](https://vale.sh/)** - the `polkadot-mkdocs` repository contains configuration for Vale, an open source NLP-powered linter for text. The configuration is a work in progress with a growing custom dictionary tailored toward software engineering, blockchain, and Polkadot terms. Running Vale against your files locally can serve as a first round of feedback to speed up the review process
+- **[Vale](https://vale.sh/)**: The `polkadot-mkdocs` repository contains configuration for Vale, an open source NLP-powered linter for text. The configuration is a work in progress with a growing custom dictionary tailored toward software engineering, blockchain, and Polkadot terms. Running Vale against your files locally can serve as a first round of feedback to speed up the review process.
 
 To use Vale locally to screen your work:
 
-1. Visit the Vale site and follow the [installation instructions](https://vale.sh/docs/vale-cli/installation/) 
+1. Visit the Vale site and follow the [installation instructions](https://vale.sh/docs/vale-cli/installation/).
 2. From the `polkadot-mkdocs` directory, run the following in your terminal:
 
     ```bash
@@ -237,8 +237,8 @@ To use Vale locally to screen your work:
 
     ![Vale sample terminal output](images/contributing/vale-output-01.webp)
 
-3. You can use CMD+click to open the file with the flagged items. This is especially helpful if you run Vale against a directory with multiple files
+3. You can use CMD+click to open the file with the flagged items. This is especially helpful if you run Vale against a directory with multiple files.
 
-4. Each flag tells you the line and location of the flagged item, the level of the flag (error, warning, or suggestion), and a suggestion for how to resolve the flag
+4. Each flag tells you the line and location of the flagged item, the level of the flag (error, warning, or suggestion), and a suggestion for how to resolve the flag.
 
-5. Once you have addressed the flagged items and made edits as needed, you can complete the normal steps to commit your changes and open a pull request to review for merge
+5. Once you have addressed the flagged items and made edits as needed, you can complete the normal steps to commit your changes and open a pull request to review for merge.

.snippets/code/develop/toolkit/interoperability/asset-transfer-api/reference/transfer-arg-opts.md

@@ -18,8 +18,8 @@ Options for customizing the claim assets transaction. These options allow you to
 
     The Asset ID to pay fees on the current common good parachain. The defaults are as follows:
 
-    - Polkadot Asset Hub - `'DOT'`
-    - Kusama Asset Hub - `'KSM'`
+    - **Polkadot Asset Hub**: `'DOT'`
+    - **Kusama Asset Hub**: `'KSM'`
 
     ---
 

.snippets/code/develop/toolkit/interoperability/asset-transfer-api/reference/tx-result.md

@@ -133,6 +133,6 @@ A promise containing the result of constructing the transaction.
 
         The `ConstructedFormat` type is a conditional type that returns a specific type based on the value of the TxResult `format` field.
 
-        - **Payload format** - if the format field is set to `'payload'`, the `ConstructedFormat` type will return a [`GenericExtrinsicPayload`](https://github.com/polkadot-js/api/blob/v15.8.1/packages/types/src/extrinsic/ExtrinsicPayload.ts#L87){target=\_blank}
-        - **Call format** - if the format field is set to `'call'`, the `ConstructedFormat` type will return a hexadecimal string (`0x${string}`). This is the encoded representation of the extrinsic call
-        - **Submittable format** - if the format field is set to `'submittable'`, the `ConstructedFormat` type will return a [`SubmittableExtrinsic`](https://github.com/polkadot-js/api/blob/v15.8.1/packages/api-base/src/types/submittable.ts#L56){target=\_blank}. This is a Polkadot.js type that represents a transaction that can be submitted to the blockchain
+        - **Payload format**: If the format field is set to `'payload'`, the `ConstructedFormat` type will return a [`GenericExtrinsicPayload`](https://github.com/polkadot-js/api/blob/v15.8.1/packages/types/src/extrinsic/ExtrinsicPayload.ts#L87){target=\_blank}.
+        - **Call format**: If the format field is set to `'call'`, the `ConstructedFormat` type will return a hexadecimal string (`0x${string}`). This is the encoded representation of the extrinsic call.
+        - **Submittable format**: If the format field is set to `'submittable'`, the `ConstructedFormat` type will return a [`SubmittableExtrinsic`](https://github.com/polkadot-js/api/blob/v15.8.1/packages/api-base/src/types/submittable.ts#L56){target=\_blank}. This is a Polkadot.js type that represents a transaction that can be submitted to the blockchain.

develop/index.md

@@ -11,14 +11,14 @@ template: index-page.html
 This guide is a starting point for developers who wish to build in the Polkadot ecosystem. To get the most from this section:
 
 1. Identify your development pathway:
-    - [**Parachain developers**](#parachain-developers) - build, deploy, and maintain custom parachains with the Polkadot SDK
-    - [**Smart contract developers**](#smart-contract-developers) - leverage smart contracts and execute custom logic over existing chains to streamline your development process
-    - [**Application developers**](#application-developers) - leverage Polkadot's underlying protocol features to create solutions for your users to interact with the ecosystem
+    - **[Parachain developers](#parachain-developers)**: Build, deploy, and maintain custom parachains with the Polkadot SDK.
+    - **[Smart contract developers](#smart-contract-developers)**: Leverage smart contracts and execute custom logic over existing chains to streamline your development process.
+    - **[Application developers](#application-developers)**: Leverage Polkadot's underlying protocol features to create solutions for your users to interact with the ecosystem.
 2. Use the sections under your pathway as follows:
-    - **Learn** - content to deepen your knowledge and understanding
-    - **Build** - connect to goal-oriented guides and step-by-step tutorials
-    - **Tools** - tools commonly used in your pathway
-    - **Resources** - resources for your pathway, including references, code repositories, and outside documentation
+    - **Learn**: Content to deepen your knowledge and understanding.
+    - **Build**: Connect to goal-oriented guides and step-by-step tutorials.
+    - **Tools**: Tools commonly used in your pathway.
+    - **Resources**: Resources for your pathway, including references, code repositories, and outside documentation.
 
 ## Development Pathways
 
@@ -36,9 +36,9 @@ graph TD
 
 All three pathways can leverage Cross-Consensus Messaging (XCM) to create innovative cross-chain workflows and applications. To get started with XCM, see these resources:
 
-- [**Introduction to XCM**](/develop/interoperability/intro-to-xcm/){target=\_blank} - introduces key concepts, core function definitions, and code examples
-- [**XCM Tools**](/develop/toolkit/interoperability/xcm-tools/){target=\_blank} - provides an overview of popular XCM tools
-- [**Tutorials for Managing XCM Channels**](/tutorials/interoperability/xcm-channels/){target=\_blank} - guides for using [Polkadot.js Apps](https://polkadot.js.org/apps/#/explorer){target=\_blank} UI to establish cross-chain messaging channels 
+- **[Introduction to XCM](/develop/interoperability/intro-to-xcm/){target=\_blank}**: Introduces key concepts, core function definitions, and code examples.
+- **[XCM Tools](/develop/toolkit/interoperability/xcm-tools/){target=\_blank}**: Provides an overview of popular XCM tools.
+- **[Tutorials for Managing XCM Channels](/tutorials/interoperability/xcm-channels/){target=\_blank}**: Guides for using [Polkadot.js Apps](https://polkadot.js.org/apps/#/explorer){target=\_blank} UI to establish cross-chain messaging channels.
 
 ### Parachain Developers
 

develop/interoperability/index.md

@@ -8,8 +8,8 @@ template: index-page.html
 
 This section covers everything you need to know about building and implementing [Cross-Consensus Messaging (XCM)](/develop/interoperability/intro-to-xcm/){target=\_blank} solutions in the Polkadot ecosystem. Whether you're working on establishing cross-chain channels, sending and receiving XCM messages, or testing and debugging your cross-chain configurations, you'll find the essential resources and tools here to support your interoperability needs, regardless of your development focus.
 
-- Not sure where to start? Visit the [Interoperability](/polkadot-protocol/parachain-basics/interoperability/){target=\_blank} overview page to explore different options and find the right fit for your project
-- Ready to dive in? Head over to [Send XCM Messages](/develop/interoperability/send-messages/) to learn how to send a message cross-chain via XCM
+- Not sure where to start? Visit the [Interoperability](/polkadot-protocol/parachain-basics/interoperability/){target=\_blank} overview page to explore different options and find the right fit for your project.
+- Ready to dive in? Head over to [Send XCM Messages](/develop/interoperability/send-messages/) to learn how to send a message cross-chain via XCM.
 
 ## In This Section