Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ - update 'risk_update_24' entry for #971 #1043

Merged
merged 3 commits into from
Apr 22, 2021

Conversation

heinezen
Copy link
Member

@heinezen heinezen commented Apr 5, 2021

Changelog:

  • "Zero-Rating Verpflichtungen" needed additional dash

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Apr 5, 2021

Do we want to link to https://www.coronawarn.app/de/faq/#mobile_data_costs from this entry?
I think this would be quite sense full, to explain what the "Zero-Raitign Verpflichtung" is.

I can also open a new issue for that afterwards. (:

@heinezen
Copy link
Member Author

heinezen commented Apr 6, 2021

@Ein-Tim I think it's a good idea. We are still discussing internally how much interlinking between entries we want, but it would be no problem here, I think.

We will leave the batch of FAQ edits open for feedback anyway, so no need to create an issue for it yet.

@heinezen heinezen force-pushed the heinezen-refaq-risk-update24 branch from 82736ca to ac4968b Compare April 8, 2021 10:47
@heinezen
Copy link
Member Author

heinezen commented Apr 8, 2021

@Ein-Tim Solved!

@dsarkar dsarkar requested a review from a team April 22, 2021 09:34
@dsarkar
Copy link
Member

dsarkar commented Apr 22, 2021

@Ein-Tim @heinezen Thanks.

@dsarkar
Copy link
Member

dsarkar commented Apr 22, 2021

image

@dsarkar
Copy link
Member

dsarkar commented Apr 22, 2021

image

@dsarkar dsarkar merged commit adea730 into master Apr 22, 2021
@dsarkar dsarkar deleted the heinezen-refaq-risk-update24 branch April 22, 2021 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants