Improve docs consistency

Author: cjdsellers

docs/concepts/architecture.md

@@ -18,7 +18,7 @@ Throughout the documentation, the term *"Nautilus system boundary"* refers to op
 the runtime of a single Nautilus node (also known as a "trader instance").
 :::
 
-## Design philosophy
+## Design Philosophy
 
 The major architectural techniques and design patterns employed by NautilusTrader are:
 
@@ -30,7 +30,7 @@ The major architectural techniques and design patterns employed by NautilusTrade
 
 These techniques have been utilized to assist in achieving certain architectural quality attributes.
 
-### Quality attributes
+### Quality Attributes
 
 Architectural decisions are often a trade-off between competing priorities. The
 below is a list of some of the most important quality attributes which are considered
@@ -43,7 +43,7 @@ when making design and architectural decisions, roughly in order of 'weighting'.
 - Maintainability
 - Deployability
 
-## System architecture
+## System Architecture
 
 The NautilusTrader codebase is actually both a framework for composing trading
  systems, and a set of default system implementations which can operate in various
@@ -110,7 +110,7 @@ Provides comprehensive risk management:
 - Real-time risk calculations.
 - Configurable risk rules and limits.
 
-### Environment contexts
+### Environment Contexts
 
 An environment context in NautilusTrader defines the type of data and trading venue you are working
 with. Understanding these contexts is crucial for effective backtesting, development, and live trading.
@@ -121,7 +121,7 @@ Here are the available environments you can work with:
 - `Sandbox`: Real-time data with simulated venues.
 - `Live`: Real-time data with live venues (paper trading or real accounts).
 
-### Common core
+### Common Core
 
 The platform has been designed to share as much common code between backtest, sandbox and live trading systems as possible.
 This is formalized in the `system` subpackage, where you will find the `NautilusKernel` class,

docs/concepts/overview.md

@@ -55,7 +55,7 @@ have all been written entirely in [Rust](https://www.rust-lang.org/) or [Cython]
 This means we're using the right tools for the job, where systems programming languages compile performant binaries,
 with CPython C extension modules then able to offer a Python-native environment, suitable for professional quantitative traders and trading firms.
 
-## Use cases
+## Use Cases
 
 There are three main use cases for this software package:
 
@@ -80,7 +80,7 @@ include the application and infrastructure layers.
 The platform is designed to be easily integrated into a larger distributed system.
 To facilitate this, nearly all configuration and domain objects can be serialized using JSON, MessagePack or Apache Arrow (Feather) for communication over the network.
 
-## Common core
+## Common Core
 
 The common system core is utilized by all node [environment contexts](/concepts/architecture.md#environment-contexts) (`backtest`, `sandbox`, and `live`).
 User-defined `Actor`, `Strategy` and `ExecAlgorithm` components are managed consistently across these environment contexts.
@@ -90,7 +90,7 @@ User-defined `Actor`, `Strategy` and `ExecAlgorithm` components are managed cons
 Backtesting can be achieved by first making data available to a `BacktestEngine` either directly or via
 a higher level `BacktestNode` and `ParquetDataCatalog`, and then running the data through the system with nanosecond resolution.
 
-## Live trading
+## Live Trading
 
 A `TradingNode` can ingest data and events from multiple data and execution clients.
 Live deployments can use both demo/paper trading accounts, or real accounts.
@@ -100,7 +100,7 @@ The platform supports both demo/paper trading accounts and real accounts. High p
 asynchronously on a single [event loop](https://docs.python.org/3/library/asyncio-eventloop.html),
 with the potential to further boost performance by leveraging the [uvloop](https://github.com/MagicStack/uvloop) implementation (available for Linux and macOS).
 
-## Domain model
+## Domain Model
 
 The platform features a comprehensive trading domain model that includes various value types such as
 `Price` and `Quantity`, as well as more complex entities such as `Order` and `Position` objects,
@@ -142,7 +142,7 @@ Example: `2d89666b-1a1e-4a75-b193-4eb3b454c757`
 
 For the complete specification, refer to [RFC 4122: A Universally Unique IDentifier (UUID) URN Namespace](https://datatracker.ietf.org/doc/html/rfc4122).
 
-## Data types
+## Data Types
 
 The following market data types can be requested historically, and also subscribed to as live streams when available from a venue / data provider, and implemented in an integrations adapter.
 
@@ -163,7 +163,7 @@ The following `PriceType` options can be used for bar aggregations:
 - `MID`
 - `LAST`
 
-## Bar aggregations
+## Bar Aggregations
 
 The following `BarAggregation` methods are available:
 

docs/developer_guide/environment_setup.md

@@ -142,9 +142,9 @@ docker-compose up -d postgres
 
 Used services are:
 
-- `postgres`: Postgres database with root user `POSTRES_USER` which defaults to `postgres`, `POSTGRES_PASSWORD` which defaults to `pass` and `POSTGRES_DB` which defaults to `postgres`
-- `redis`: Redis server
-- `pgadmin`: PgAdmin4 for database management and administration
+- `postgres`: Postgres database with root user `POSTRES_USER` which defaults to `postgres`, `POSTGRES_PASSWORD` which defaults to `pass` and `POSTGRES_DB` which defaults to `postgres`.
+- `redis`: Redis server.
+- `pgadmin`: PgAdmin4 for database management and administration.
 
 :::info
 Please use this as development environment only. For production, use a proper and more secure setup.
@@ -217,8 +217,8 @@ POSTGRES_DATABASE=nautilus
 
 List of commands are:
 
-1. `nautilus database init`: Will bootstrap schema, roles and all sql files located in `schema` root directory (like `tables.sql`)
-2. `nautilus database drop`: Will drop all tables, roles and data in target Postgres database
+1. `nautilus database init`: Will bootstrap schema, roles and all sql files located in `schema` root directory (like `tables.sql`).
+2. `nautilus database drop`: Will drop all tables, roles and data in target Postgres database.
 
 ## Rust analyzer settings
 

docs/integrations/betfair.md

@@ -91,15 +91,15 @@ Betfair operates as a betting exchange with unique characteristics compared to t
 | `FOK`         | -       | Betting exchange uses different model.  |
 | `IOC`         | -       | Betting exchange uses different model.  |
 
-### Advanced order features
+### Advanced Order Features
 
 | Feature            | Betfair | Notes                                    |
 |--------------------|---------|------------------------------------------|
 | Order Modification | ✓       | Limited to non-exposure changing fields. |
 | Bracket/OCO Orders | -       | *Not supported*.                         |
 | Iceberg Orders     | -       | *Not supported*.                         |
 
-### Configuration options
+### Configuration Options
 
 The following execution client configuration options affect order behavior:
 

docs/integrations/binance.md

@@ -63,7 +63,7 @@ Most users will simply define a configuration for a live trading node (as below)
 and won't need to necessarily work with these lower level components directly.
 :::
 
-## Data types
+## Data Types
 
 To provide complete API functionality to traders, the integration includes several
 custom data types:
@@ -125,15 +125,15 @@ Only *limit* order types support `post_only`.
 | `FOK`         | ✓    | ✓      | ✓            | ✓            | Fill or Kill.                                   |
 | `IOC`         | ✓    | ✓      | ✓            | ✓            | Immediate or Cancel.                            |
 
-### Advanced order features
+### Advanced Order Features
 
 | Feature            | Spot | Margin | USDT Futures | Coin Futures | Notes                                        |
 |--------------------|------|--------|--------------|--------------|----------------------------------------------|
 | Order Modification | ✓    | ✓      | ✓            | ✓            | Price and quantity for `LIMIT` orders only.  |
 | Bracket/OCO Orders | ✓    | ✓      | ✓            | ✓            | One-Cancels-Other for stop loss/take profit. |
 | Iceberg Orders     | ✓    | ✓      | ✓            | ✓            | Large orders split into visible portions.    |
 
-### Configuration options
+### Configuration Options
 
 The following execution client configuration options affect order behavior:
 
@@ -146,7 +146,7 @@ The following execution client configuration options affect order behavior:
 | `futures_leverages`          | `None`  | Dict to set initial leverage per symbol for Futures accounts. |
 | `futures_margin_types`       | `None`  | Dict to set margin type (isolated/cross) per symbol for Futures accounts. |
 
-### Trailing stops
+### Trailing Stops
 
 Binance uses the concept of an activation price for trailing stops, as detailed in their [documentation](https://www.binance.com/en/support/faq/what-is-a-trailing-stop-order-360042299292).
 This approach is somewhat unconventional. For trailing stop orders to function on Binance, the activation price should be set using the `activation_price` parameter.
@@ -223,7 +223,7 @@ node.add_exec_client_factory(BINANCE, BinanceLiveExecClientFactory)
 node.build()
 ```
 
-### API credentials
+### API Credentials
 
 There are two options for supplying your credentials to the Binance clients.
 Either pass the corresponding `api_key` and `api_secret` values to the configuration objects, or
@@ -267,7 +267,7 @@ using the `BinanceAccountType` enum. The account type options are:
 We recommend using environment variables to manage your credentials.
 :::
 
-### Base url overrides
+### Base URL Overrides
 
 It's possible to override the default base URLs for both HTTP Rest and
 WebSocket APIs. This is useful for configuring API clusters for performance reasons,
@@ -308,7 +308,7 @@ config = TradingNodeConfig(
 )
 ```
 
-### Aggregated trades
+### Aggregated Trades
 
 Binance provides aggregated trade data endpoints as an alternative source of trades.
 In comparison to the default trade endpoints, aggregated trade data endpoints can return all
@@ -317,7 +317,7 @@ ticks between a `start_time` and `end_time`.
 To use aggregated trades and the endpoint features, set the `use_agg_trade_ticks` option
 to `True` (this is `False` by default.)
 
-### Parser warnings
+### Parser Warnings
 
 Some Binance instruments are unable to be parsed into Nautilus objects if they
 contain enormous field values beyond what can be handled by the platform.
@@ -337,15 +337,15 @@ instrument_provider=InstrumentProviderConfig(
 )
 ```
 
-### Futures Hedge mode
+### Futures Hedge Mode
 
 Binance Futures Hedge mode is a position mode where a trader opens positions in both long and short
 directions to mitigate risk and potentially profit from market volatility.
 
 To use Binance Future Hedge mode, you need to follow the three items below:
 
 - 1. Before starting the strategy, ensure that hedge mode is configured on Binance.
-- 2. Set the `use_reduce_only` option to `False` in BinanceExecClientConfig (this is `True` by default.)
+- 2. Set the `use_reduce_only` option to `False` in BinanceExecClientConfig (this is `True` by default).
 
     ```python
     from nautilus_trader.adapters.binance import BINANCE
@@ -428,8 +428,8 @@ subscription will be used by the Binance data client.
 
 Order book snapshot rebuilds will be triggered on:
 
-- Initial subscription of the order book data
-- Data websocket reconnects
+- Initial subscription of the order book data.
+- Data websocket reconnects.
 
 The sequence of events is as follows:
 

docs/integrations/bybit.md

@@ -119,15 +119,15 @@ All the order types listed below can be used as *either* entries or exits, excep
 | `FOK`         | ✓    | ✓      | ✓       | Fill or Kill.                |
 | `IOC`         | ✓    | ✓      | ✓       | Immediate or Cancel.         |
 
-### Advanced order features
+### Advanced Order Features
 
 | Feature            | Spot | Linear | Inverse | Notes                                  |
 |--------------------|------|--------|---------|----------------------------------------|
 | Order Modification | ✓    | ✓      | ✓       | Price and quantity modification.       |
 | Bracket/OCO Orders | ✓    | ✓      | ✓       | UI only; API users implement manually. |
 | Iceberg Orders     | ✓    | ✓      | ✓       | Max 10 per account, 1 per symbol.      |
 
-### Configuration options
+### Configuration Options
 
 The following execution client configuration options affect order behavior:
 
@@ -147,7 +147,7 @@ The following limitations apply to SPOT products, as positions are not tracked o
 - `reduce_only` orders are *not supported*.
 - Trailing stop orders are *not supported*.
 
-### Trailing stops
+### Trailing Stops
 
 Trailing stops on Bybit do not have a client order ID on the venue side (though there is a `venue_order_id`).
 This is because trailing stops are associated with a netted position for an instrument.
@@ -162,11 +162,11 @@ Consider the following points when using trailing stops on Bybit:
 
 The product types for each client must be specified in the configurations.
 
-### Data clients
+### Data Clients
 
 If no product types are specified then all product types will be loaded and available.
 
-### Execution clients
+### Execution Clients
 
 Because Nautilus does not support a "unified" account, the account type must be either cash **or** margin.
 This means there is a limitation that you cannot specify SPOT with any of the other derivative product types.
@@ -225,7 +225,7 @@ node.add_exec_client_factory(BYBIT, BybitLiveExecClientFactory)
 node.build()
 ```
 
-### API credentials
+### API Credentials
 
 There are two options for supplying your credentials to the Bybit clients.
 Either pass the corresponding `api_key` and `api_secret` values to the configuration objects, or

docs/integrations/coinbase_intx.md

@@ -103,7 +103,7 @@ The WebSocket client handles automatic reconnection and re-subscribes to active
 
 **The adapter is designed to trade one Coinbase International portfolio per execution client.**
 
-### Selecting a portfolio
+### Selecting a Portfolio
 
 To identify your available portfolios and their IDs, use the REST client by running the following script:
 
@@ -128,7 +128,7 @@ This will output a list of portfolio details, similar to the example below:
   'user_uuid': 'd4fbf7ea-9515-1068-8d60-4de91702c108'}]
 ```
 
-### Configuring the portfolio
+### Configuring the Portfolio
 
 To specify a portfolio for trading, set the `COINBASE_INTX_PORTFOLIO_ID` environment variable to
 the desired `portfolio_id`. If you're using multiple execution clients, you can alternatively define
@@ -166,15 +166,15 @@ Coinbase International offers market, limit, and stop order types, enabling a br
 | `FOK`         | ✓           | ✓    | Fill or Kill.                                    |
 | `IOC`         | ✓           | ✓    | Immediate or Cancel.                             |
 
-### Advanced order features
+### Advanced Order Features
 
 | Feature            | Derivatives | Spot | Notes                                       |
 |--------------------|-------------|------|---------------------------------------------|
 | Order Modification | ✓           | ✓    | Price and quantity modification.             |
 | Bracket/OCO Orders | ?           | ?    | Requires further investigation.              |
 | Iceberg Orders     | ✓           | ✓    | Available via FIX protocol.                 |
 
-### Configuration options
+### Configuration Options
 
 The following execution client configuration options are available:
 
@@ -183,7 +183,7 @@ The following execution client configuration options are available:
 | `portfolio_id`               | `None`  | Specifies the Coinbase International portfolio to trade. Required for execution. |
 | `http_timeout_secs`          | `60`    | Default timeout for HTTP requests in seconds. |
 
-### FIX Drop Copy integration
+### FIX Drop Copy Integration
 
 The Coinbase International adapter includes a FIX (Financial Information eXchange) [drop copy](https://docs.cdp.coinbase.com/intx/docs/fix-msg-drop-copy) client.
 This provides reliable, low-latency execution updates directly from Coinbase's matching engine.
@@ -210,7 +210,7 @@ No additional configuration is required beyond providing valid API credentials.
 The REST client handles processing `REJECTED` and `ACCEPTED` status execution messages on order submission.
 :::
 
-### Account and position management
+### Account and Position Management
 
 On startup, the execution client requests and loads your current account and execution state including:
 
@@ -277,7 +277,7 @@ node.add_exec_client_factory(COINBASE_INTX, CoinbaseIntxLiveExecClientFactory)
 node.build()
 ```
 
-### API credentials
+### API Credentials
 
 Provide credentials to the clients using one of the following methods.
 

docs/integrations/dydx.md

@@ -161,15 +161,15 @@ dYdX supports perpetual futures trading with a comprehensive set of order types
 | `FOK`         | ✓          | Fill or Kill.                                   |
 | `IOC`         | ✓          | Immediate or Cancel.                            |
 
-### Advanced order features
+### Advanced Order Features
 
 | Feature            | Perpetuals | Notes                                           |
 |--------------------|------------|-------------------------------------------------|
 | Order Modification | ✓          | Short-term orders only; cancel-replace method.  |
 | Bracket/OCO Orders | -          | *Not supported*.                                |
 | Iceberg Orders     | -          | *Not supported*.                                |
 
-### Configuration options
+### Configuration Options
 
 The following execution client configuration options are available:
 
@@ -191,7 +191,7 @@ dYdX classifies orders as either **short-term** or **long-term** orders:
 
 The product types for each client must be specified in the configurations.
 
-### Execution clients
+### Execution Clients
 
 The account type must be a margin account to trade the perpetual futures contracts.
 
@@ -239,7 +239,7 @@ node.add_exec_client_factory("DYDX", DYDXLiveExecClientFactory)
 node.build()
 ```
 
-### API credentials
+### API Credentials
 
 There are two options for supplying your credentials to the dYdX clients.
 Either pass the corresponding `wallet_address` and `mnemonic` values to the configuration objects, or
@@ -286,7 +286,7 @@ config = TradingNodeConfig(
 )
 ```
 
-### Parser warnings
+### Parser Warnings
 
 Some dYdX instruments are unable to be parsed into Nautilus objects if they
 contain enormous field values beyond what can be handled by the platform.