Our writing voice
We write as Davonium Technologies, using direct language about our products, decisions, scope, and current limitations. We do not describe our own company from the outside or leave template instructions in public copy.
We use “we” and “our” when explaining company choices, and neutral factual language when explaining browser or search-service behaviour. We name the audience and the task a page supports. We remove generic filler, repeated checklists, and instructions intended for an internal author rather than the public.
Claims and product status
We state only product features, dates, security controls, integrations, and availability that we can substantiate. A capability in development is not described as released, and a product build is not presented as generally available unless that status has been confirmed.
- Ready2Go Learning — In development.
- Marvel Chat — Built; active development.
- Davonium Nexus — In development.
We use specific examples instead of unsupported superlatives and update status when a verified release changes it.
Public documentation
Each guide has its own subject, descriptive title, stable address, summary, useful headings, and related links. We do not reuse the same generic paragraph to make unrelated pages look complete. Important content remains readable on the page; search narrows the guide list rather than creating guide content after someone types.
We explain terms when they are needed, link to authoritative references for changing platform behaviour, and avoid describing internal development choices unless a detail is necessary to help a reader use a product.
Review and corrections
We update pages when product behaviour, company decisions, or external requirements change. A review date describes editorial review, not a legal certification or a promise that external services remain unchanged.
When we find inaccurate copy, we correct it and preserve limitations that materially affect readers. We do not publish unverified performance figures, endorsements, awards, or guarantees.
How we review public claims
Before publishing a product or service claim, we confirm that the wording matches a capability we can verify, that the status is current, and that a reader can find the relevant product or support page.