Skip to content

Commit

Permalink
Merge pull request #1438 from agorneo/agorneo-readme-minor-changes
Browse files Browse the repository at this point in the history
Update README.md
  • Loading branch information
tvdeyen authored Sep 18, 2018
2 parents 4c8c31a + c008d06 commit 972683b
Showing 1 changed file with 10 additions and 8 deletions.
18 changes: 10 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -194,17 +194,19 @@ http://markevans.github.io/dragonfly/cache

### Localization

Alchemy ships with one default English translation for the admin interface. If you want to use the admin interface in other languages please have a look at the [`alchemy_i18n` project](https://github.com/AlchemyCMS/alchemy_cms).
Alchemy ships with one default English translation for the admin interface. If you want to use the admin interface in other languages please have a look at the [`alchemy_i18n` project](https://github.com/AlchemyCMS/alchemy_i18n).

## Upgrading

The Alchemy team takes upgrades very seriously and tries to make them as smooth as we can.
Therefore we have build in upgrade tasks, that try to automate as much as possible.

That's why after updating the Alchemy gem you should **always run the upgrader**:
We, the Alchemy team, take upgrades very seriously and we try to make them as smooth as possible.
Therefore we have build an upgrade task, that tries to automate the upgrade procedure as much as possible.

That's why after the Alchemy gem has been updated, with explicit call to:
```shell
$ bundle update alchemy_cms
```
you should **always run the upgrader**:
```shell
$ bin/rake alchemy:upgrade
```

Expand All @@ -217,7 +219,7 @@ Also, `git diff` is your friend.

### Customize the upgrade preparation

The Alchemy upgrader comes prepared with with several rake tasks in a specific order.
The Alchemy upgrader comes prepared with several rake tasks in a specific order.
This is sometimes not what you want or could even break upgrades.
In order to customize the upgrade preparation process you can instead run each of the tasks on their own.

Expand Down Expand Up @@ -316,7 +318,7 @@ Alchemy specs are written **in RSpec 3**. Please **do not use deprecated RSpec 2
* Read the guidelines: http://guides.alchemy-cms.com.
* Read the documentation: http://rubydoc.info/github/AlchemyCMS/alchemy_cms
* If you found a bug please use the [issue tracker on Github](https://github.com/AlchemyCMS/alchemy_cms/issues).
* For questions about general usage please use [Stack Overflow](http://stackoverflow.com/questions/tagged/alchemy-cms), [the User Group](http://groups.google.com/group/alchemy-cms) or the [IRC channel](irc://irc.freenode.net#alchemy_cms).
* For questions about general usage please use [Stack Overflow](http://stackoverflow.com/questions/tagged/alchemy-cms), [the User Group](http://groups.google.com/group/alchemy-cms) or the [Slack](https://slackin.alchemy-cms.com).
* New features should be discussed on our [Trello Board](https://trello.com/alchemycms).

**PLEASE** don't use the Github issues for feature requests. If you want to contribute to Alchemy please [read the contribution guidelines](https://github.com/AlchemyCMS/alchemy_cms/blob/master/CONTRIBUTING.md) before doing so.
Expand All @@ -330,7 +332,7 @@ Alchemy specs are written **in RSpec 3**. Please **do not use deprecated RSpec 2
* Issue-Tracker: <https://github.com/AlchemyCMS/alchemy_cms/issues>
* Sourcecode: <https://github.com/AlchemyCMS/alchemy_cms>
* User Group: <http://groups.google.com/group/alchemy-cms>
* IRC Channel: <irc://irc.freenode.net#alchemy_cms>
* Slack: <https://slackin.alchemy-cms.com>
* Discussion Board: <https://trello.com/alchemycms>
* Twitter: <https://twitter.com/alchemy_cms>

Expand Down

0 comments on commit 972683b

Please sign in to comment.