forked from typora/typora-issues
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix typos and make the readme readable.
- Loading branch information
Showing
1 changed file
with
10 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,23 +1,23 @@ | ||
| # Typora | ||
|
|
||
| [Typora](http:https://typora.io)(beta) is a minimal markdown editor, providing new ways for reading and writing markdown. | ||
| [Typora](http:https://typora.io) (beta) is a minimal markdown editor, providing new ways for reading and writing markdown. | ||
|
|
||
| # What's this Repository for | ||
| # What this Repository is for | ||
|
|
||
| This repository is created to as an alternative way to gather users' feedbacks and discussions. | ||
| This repository has been created as an alternative way to gather users' feedback and discussions. | ||
|
|
||
| Currently, user can use email to send bug reports or suggestions, but to increase the transparency of the beta sutiation, a public forum is a better option. User should know exisiting bugs reported by other users (since beta is not so stable) and future developing plans if they want to use typora in long term or pre-order typora before the real release. | ||
| Currently, users can use email to send bug reports or suggestions, but to increase the transparency of the beta situation, a public forum is a better option. Users should read exisiting bugs reported by other users first (since the beta is not so stable). | ||
|
|
||
| Aslo, as a developer, I want to make typora prefect, so a new approach to listener to user's opinion is always welcomed. | ||
| Also, as a developer, I want to make typora perfect, so a new approach to listen to user's opinions is always welcome. | ||
|
|
||
| # Find Support | ||
|
|
||
| If you want some help on using Typora, before creating an issue, you could find some answers from <http:https://support.typora.io>, or find answers/discussions from exisitng issues. If you cannot find the solution to solve your problem, please feel free to submit an issue or mail us. | ||
| If you want help on using Typora, before creating an issue, you search for answers at <http:https://support.typora.io>, or find answers/discussions from existing issues. If you cannot find the solution to solve your problem, please feel free to submit a new issue or email us. | ||
|
|
||
| # How to participant. | ||
| # How to participate | ||
|
|
||
| Click `issue` tab, and join the conversation! | ||
| Click the `issue` tab, and join the conversation! | ||
|
|
||
| For bug reports, please provide OS version and Typora version and if possible, detailed steps to reproduce the bug. | ||
| For bug reports, please provide your OS version and Typora version and if possible, detailed steps to reproduce the bug. | ||
|
|
||
| If you have multiple issues and bug reports and they are not closely related, we recommand you to seperate them in different issues. | ||
| If you have multiple issues and bug reports and they are not closely related, we recommend you to separate them in different issues. |