chore: add prose rules to CLAUDE.md and apply them

Author: mmanciop

CLAUDE.md

@@ -45,6 +45,21 @@ The metric definitions were produced by:
 - Deprecated Prometheus aliases (e.g., `dash0_spans_total`) get their own metric group entry with `deprecated: { reason: renamed, renamed_to: <otel_name> }`.
 - Every metric **must** have a `unit` field compliant with [UCUM](https://ucum.org/).
 
+## Prose rules
+
+Follow these rules when writing or editing prose in this project.
+
+- **One sentence per line** (semantic line breaks).
+  Each sentence starts on its own line; do not wrap mid-sentence.
+- Separate paragraphs with a single blank line.
+- Section headers use sentence case (e.g., "Key conventions").
+- Use inline Markdown links: `[visible text](url)`.
+  Link the most specific relevant term, not generic phrases.
+- Fence code blocks with triple backticks and a language identifier (e.g., ` ```yaml `).
+- End sentences with full stops.
+- Use the **Oxford comma** (e.g., "spans, logs, and metrics").
+- Write numbers as digits and spell out "percent" (e.g., "10 percent").
+
 ## README.md maintenance
 
 The `Conventions` section in `README.md` is a hand-maintained summary. When adding, removing, or renaming attributes, metrics, or events in the `model/` directory, update the corresponding entry in `README.md`:

CONTRIBUTING.md

@@ -1,15 +1,15 @@
-Contributing
-============
+# Contributing
 
 ## Prerequisites
 
 - Signing the [Contributor License Agreement](https://github.com/cla-assistant/cla-assistant)
 - [OTel Weaver](https://github.com/open-telemetry/weaver) (v0.21.2+)
 - Node.js (LTS) — used for converting JSON5 test data
 
-## Making Changes to the Model
+## Making changes to the model
 
-The semantic conventions are defined as YAML files under the `model/` directory, using the [OpenTelemetry Weaver](https://github.com/open-telemetry/weaver) registry format.
+The semantic conventions are defined as YAML files under the `model/` directory.
+They use the [OpenTelemetry Weaver](https://github.com/open-telemetry/weaver) registry format.
 
 - `model/registry_manifest.yaml` — Registry manifest declaring dependencies (e.g., on OTel semantic conventions).
 - `model/<domain>/entities.yaml` — Entity definitions.
@@ -21,7 +21,7 @@ When adding or modifying conventions:
 2. Run `weaver registry check -r ./model` to validate the model.
 3. Add or update test data under `tests/`.
 
-## Test Data
+## Test data
 
 Test data lives under the `tests/` directory as [JSON5](https://json5.org/) files:
 
@@ -30,7 +30,7 @@ Test data lives under the `tests/` directory as [JSON5](https://json5.org/) file
 
 When adding a new event or entity, add at least one valid and one invalid test case.
 
-## Validating Locally
+## Validating locally
 
 Check the registry model for correctness:
 
@@ -66,7 +66,7 @@ for file in $(find tests/invalid -name '*.json5' | sort); do
 done
 ```
 
-## Pull Requests
+## Pull requests
 
 All pull requests are validated in CI, which runs:
 

README.md

@@ -1,7 +1,11 @@
 # Dash0 Semantic Conventions
 
 This repository contains the semantic conventions for [Dash0](https://www.dash0.com).
-The conventions are defined using the [OpenTelemetry Weaver](https://github.com/open-telemetry/weaver) registry format and build on top of the [OpenTelemetry Semantic Conventions](https://opentelemetry.io/docs/specs/semconv/).
+The conventions are defined using the [OpenTelemetry Weaver](https://github.com/open-telemetry/weaver) registry format.
+They build on top of the [OpenTelemetry Semantic Conventions](https://opentelemetry.io/docs/specs/semconv/).
+
+The full registry documentation is published at [dash0hq.github.io/dash0-semantic-conventions](https://dash0hq.github.io/dash0-semantic-conventions/).
+This is a temporary location; the content will be merged into the [Dash0 Docs](https://docs.dash0.com) in a future release.
 
 ## Conventions