Docs: "send data in, query data out"

docs/content/getting-started/data-in.md

@@ -1,11 +1,11 @@
 ---
-title: Get data into Rerun
+title: Send data to Rerun
 order: 400
 ---
 
-This section shows you how to get data into Rerun from either your running applications or existing files.
+This section shows you how to send data to Rerun from either your running applications or existing files.
 
--   Streaming data from your code
+-   Sending data from your code
     -   [C++](./data-in/cpp.md)
     -   [Python](./data-in/python.md)
     -   [Rust](./data-in/rust.md)

docs/content/getting-started/data-in/cpp.md

@@ -1,5 +1,5 @@
 ---
-title: Stream from C++
+title: Send from C++
 order: 1
 ---
 

docs/content/getting-started/data-in/python.md

@@ -1,5 +1,5 @@
 ---
-title: Stream from Python
+title: Send from Python
 order: 2
 ---
 

docs/content/getting-started/data-in/rust.md

@@ -1,5 +1,5 @@
 ---
-title: Stream from Rust
+title: Send from Rust
 order: 3
 ---
 

docs/content/getting-started/data-out.md

@@ -1,5 +1,5 @@
 ---
-title: Get data out of Rerun
+title: Query data out of Rerun
 order: 450
 ---
 

docs/content/howto/get-data-out.md

@@ -1,6 +1,6 @@
 ---
-title: Get data out of Rerun
-order: 0
+title: Query data out of Rerun
+order: 100
 ---
 
 Rerun comes with a Dataframe API, which enables getting data out of Rerun from code. This page provides an overview of the API, as well as recipes to load the data in popular packages such as [Pandas](https://pandas.pydata.org), [Polars](https://pola.rs), and [DuckDB](https://duckdb.org).

docs/content/howto/logging.md

@@ -1,5 +1,5 @@
 ---
-title: Logging
-order: 100
+title: Send data to Rerun
+order: 0
 redirect: howto/logging/send-columns
 ---

docs/content/howto/logging/custom-data.md

@@ -1,5 +1,5 @@
 ---
-title: Log arbitrary data
+title: Send user-defined data
 order: 200
 description: How to use Rerun with custom data
 ---

docs/content/howto/logging/send-columns.md

@@ -1,5 +1,5 @@
 ---
-title: Log entire timeseries at once
+title: Send entire timeseries at once
 order: 0
 description: How to use the Rerun SDK to log big chunks of data in one call
 ---

docs/content/howto/visualization/reuse-blueprints.md

@@ -3,7 +3,7 @@ title: Re-use blueprints across sessions and SDKs
 order: 150
 ---
 
-While the [blueprint APIs](configure-viewer-through-code) are currently only available through [🐍 Python](https://ref.rerun.io/docs/python/stable/common/blueprint_apis/), blueprints can be saved to file and then re-logged as needed from any language our SDKs support.
+While the [blueprint APIs](configure-viewer-through-code.md) are currently only available through [🐍 Python](https://ref.rerun.io/docs/python/stable/common/blueprint_apis/), blueprints can be saved to file and then re-logged as needed from any language our SDKs support.
 
 This enables you to re-use your saved blueprints both from any language we support as well as across different recordings that share a similar-enough structure, and makes it possible to share those blueprints with other users.
 

docs/content/reference/dataframes.md

@@ -64,7 +64,7 @@ Check out the blueprint API and `log_file_from_path` references to learn more:
 * [🦀 Rust `log_file_from_path`](https://docs.rs/rerun/latest/rerun/struct.RecordingStream.html#method.log_file_from_path)
 * [🌊 C++ `log_file_from_path`](https://ref.rerun.io/docs/cpp/stable/classrerun_1_1RecordingStream.html#a20798d7ea74cce5c8174e5cacd0a2c47)
 
-You can learn more in our [dedicated page about blueprint re-use](../howto/visualization/reuse-blueprints).
+You can learn more in our [dedicated page about blueprint re-use](../howto/visualization/reuse-blueprints.md).
 
 
 ### Setting up dataframe view manually in the UI