akka/akka-core

Consistency in calling stages "rate detached" in docs?

Open

#24,819 opened on Mar 30, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Scala (3,547 forks)batch import
1 - triagedhelp wantedt:docst:stream

Repository metrics

Stars
 (13,277 stars)
PR merge metrics
 (Avg merge 8d 19h) (10 merged PRs in 30d)

Description

https://discuss.lightbend.com/t/splitting-messages-into-separate-streams-and-maintaining-order/517/3

I think we actually always call those rate-detached so docs should do the same?

Contributor guide

Research direction
Find instances in the documentation where the term 'rate detached' is used inconsistently and replace them with 'rate detached'.
Tech stack
scala
Domain
backend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90