docs: separated-host warning still says RPC transport will be deprecated in v0.8.0

[Xelp66]

Summary

docs/running-an-arc-node.md still says the RPC/HTTP Engine API transport
“will be deprecated in v0.8.0.” Version v0.8.0 has now been released,
and the current documentation describes that transport as already deprecated.

Proposed change

Change:

which will be deprecated in v0.8.0

to:

which is deprecated as of v0.8.0

This keeps the warning temporally accurate without changing its guidance.

I’d be happy to submit this one-line documentation fix.
Please assign this issue to me (@Xelp66) if you’d like me to proceed.

[osr21]

Verified against main (66ad2d5, the v0.8.0 tag) — the premise is right, and the deprecation is real in the shipped binary, not just planned: CHANGELOG.md has the v0.8.0 entry ("Deprecate the RPC/HTTP transport between CL and EL in favor of IPC; RPC configurations now emit a startup warning ahead of removal in v0.9.0"), and crates/malachite-cli/src/cmd/start.rs emits a DEPRECATION: startup warning when any RPC transport option is set, with unit tests covering both polarities (warns on RPC config, silent on IPC). So the doc's last sentence in that admonition ("The consensus layer logs a startup warning…") is accurate — only the tense is stale.

One correction to the proposed wording, though: the full line at docs/running-an-arc-node.md:408 is

which will be deprecated in v0.8.0 and will be removed in v0.9.0.

The suggested replacement ("which is deprecated as of v0.8.0") drops the removal clause, which is the operationally important half for anyone running separated hosts today. Suggested full replacement:

which is deprecated as of v0.8.0 and will be removed in v0.9.0.

Supporting data point: this is the only stale future-tense instance left — line 789 in the same file already uses present tense ("HTTP/RPC transport (deprecated):"), so line 408 is just the straggler from the pre-release edit pass.

On process: you generally don't need to wait for assignment on this repo — external PRs are accepted directly (they sit behind first-time-contributor CI approval, and since main syncs from internal development as squashed release commits, small doc fixes may get ported rather than merged as-is). Referencing this issue from the PR is enough.

[kutluhaneth46]

Taking this — one-line doc fix to reflect that v0.8.0 has shipped and the RPC transport is now deprecated (not future tense). Opening a PR shortly.

[melekes]

good catch 👍 thanks