codeninjasllc/discourse
1
0
Fork 0
mirror of https://github.com/codeninjasllc/discourse.git synced 2024-11-28 01:56:01 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

remove login-specific info

Browse source
This commit is contained in:
Jeff Atwood 2014-03-14 10:21:33 -07:00
parent e22f1ae186
commit 93bced5a5e
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
config/locales/server.en.yml
View file

@ -1128,7 +1128,7 @@ en:
To log in again, either: To log in again, either:
1. Use Facebook, Google, Twitter, or many other supported credentials -- but that credential must resolve to the **same email address** that you received your original invitation email at. Otherwise we won't be able to tell it is you! 1. Log in however you like -- but that login must resolve to the **same email address** that you received your original invitation email at. Otherwise we won't be able to tell it is you!
2. Create a unique password for %{site_name} on [your user profile][prefs], then log in with that. 2. Create a unique password for %{site_name} on [your user profile][prefs], then log in with that.

2
config/locales/server.id.yml
View file

@ -641,7 +641,7 @@ id:
To log in again, either: To log in again, either:
1. Use Facebook, Google, Twitter, or many other supported credentials -- but that credential must resolve to the **same email address** that you received your original invitation email at. Otherwise we won't be able to tell it is you! 1. Log in however you like -- but that login must resolve to the **same email address** that you received your original invitation email at. Otherwise we won't be able to tell it is you!
2. Create a unique password for %{site_name} on [your user profile][prefs], then log in with that. 2. Create a unique password for %{site_name} on [your user profile][prefs], then log in with that.

2
config/locales/server.sv.yml
View file

@ -697,7 +697,7 @@ sv:
To log in again, either: To log in again, either:
1. Use Facebook, Google, Twitter, or many other supported credentials -- but that credential must resolve to the **same email address** that you received your original invitation email at. Otherwise we won't be able to tell it is you! 1. Log in however you like -- but that login must resolve to the **same email address** that you received your original invitation email at. Otherwise we won't be able to tell it is you!
2. Create a unique password for %{site_name} on [your user profile][prefs], then log in with that. 2. Create a unique password for %{site_name} on [your user profile][prefs], then log in with that.