Merging Topics Transparency and Easy to Read

After the changes discussed in a previous topic have been applied, I see much less differences between Topic 36 (renamed Transparency) and Topic 33 (Easy to Read).

Having terms that are easy to understand, short and providing archives of their versions is important for transparency, so I’d say these topics should be merged together, keeping the title of Topic 36 as it would seem more appropriate.

1 Like

I agree. I’d even go so far as to say the Changes to the Terms section could be merged in also, but that is a separate discussion.

Do you mean Topic Changes (ToS;DR Phoenix), Topic Notice of Changing Terms (ToS;DR Phoenix) or Topic User Involvement in Changing Terms (ToS;DR Phoenix)?

For the first one, I’d agree since it refers to information the service would give about their agreements and it’s somehow related to transparency.

Regarding Topic Notice of Changing Terms (ToS;DR Phoenix) it would be logical to be merged too, but then the topic would contain too much cases in my opinion (exactly as much as the Topic Governance).

1 Like