fixup! EDU-1502: Adds bigQuery page

Author: franrob-projects

content/bigquery.textile

@@ -30,6 +30,8 @@ Set up the necessary BigQuery resources, permissions, and authentication to enab
 
 h3(#settings). BigQuery rule settings
 
+The following explains the components of the BigQuery rule settings:
+
 |_. Section |_. Purpose |
 | *Source* | Defines the type of event(s) for delivery. |
 | *Channel filter* | A regular expression to filter which channels to capture. Only events on channels matching this regex are streamed into BigQuery. |
@@ -38,7 +40,7 @@ h3(#settings). BigQuery rule settings
 | *Partitioning* | _(Optional)_ The table must be created with the desired partitioning settings in BigQuery before making the rule in Ably. |
 | *Advanced settings* | Any additional configuration or custom fields relevant to your BigQuery setup (for future enhancements). |
 
-h4(#dashboard). Create a BigQuery rule in the Dashboard
+h4(#dashboard). Create a BigQuery rule in the dashboard
 
 The following steps to create a BigQuery rule using the Ably dashboard:
 
@@ -51,7 +53,7 @@ The following steps to create a BigQuery rule using the Ably dashboard:
 
 h4(#api-rule). Create a BigQuery rule using the Control API
 
-The following steps to create a BigQuery rule using the Control API:
+The following steps to create a BigQuery rule using the "Control API:":https://ably.com/docs/api#control-api
 
 * Using the required "rules":/control-api#examples-rules to specify the following parameters:
 ** @ruleType@: Set this to "bigquery" to define the rule as a BigQuery integration.
@@ -61,7 +63,6 @@ The following steps to create a BigQuery rule using the Control API:
 ** @format@ (optional): Define the data format based on how you want messages to be structured.
 * Make an HTTP request to the Control API to create the rule.
 
-
 h3(#schema). JSON Schema
 
 You can run queries directly against the Ably-managed BigQuery table. For example, if the message payloads are stored as raw JSON in the data column, you can parse them using the following query:
@@ -88,10 +89,10 @@ WHERE channel = “my-channel”
 
 The following explains the components of the query:
 
-|. Query Function |. Purpose |
-| CAST(data AS STRING) | Converts the data column from BYTES (if applicable) into a STRING format. |
-| PARSE_JSON(…) | Parses the string into a structured JSON object for easier querying. |
-| WHERE channel = “my-channel” | Filters results to retrieve messages only from a specific Ably channel. |
+|_. Query Function |_. Purpose |
+| @CAST(data AS STRING)@ | Converts the data column from BYTES (if applicable) into a STRING format. |
+| @PARSE_JSON(…)@ | Parses the string into a structured JSON object for easier querying. |
+| @WHERE channel = “my-channel”@ | Filters results to retrieve messages only from a specific Ably channel. |
 
 <aside data-type='note'>
 <p>Parsing JSON at query time can be computationally expensive for large datasets. If your queries need frequent JSON parsing, consider pre-processing and storing structured fields in a secondary table using an ETL pipeline for better performance.</p>