Skip to content

Commit 6d04f33

Browse files
authored
Merge pull request #68 from forkcms/fix-broken-links
Fix broken links
2 parents ef330cc + fd29a7d commit 6d04f33

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

05. module guide/03. routing.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ If a page is found (*mini-blog*), the next part of the URL (if any) will be inte
9292
in the module linked to the page, that action will be executed. If it doesn't exist, the default
9393
action defined in the config-file of the module will be executed.
9494

95-
The action-part in the url (in this case: detail) will map to a matching [action-translation](translations-and-locale).
95+
The action-part in the url (in this case: detail) will map to a matching [action-translation](08. translations_or_locale.md).
9696
*detail* is one of the default actions already, but if you're adding a new or uncommon action, don't
9797
forget to create a translation for it. Internally, the action-part in the url will be searched for
9898
in the translations, and it's reference code will be used to route to the correct action, this way

06. contribute/03. features.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ When collaborating on the same source you need a Version Control System to keep
2222

2323
After you installed [Git](https://help.github.com/articles/set-up-git), start by [forking](https://help.github.com/articles/fork-a-repo) the Fork CMS [Repository](https://github.com/forkcms/forkcms). Afterwards, [create a branch](https://help.github.com/articles/fork-a-repo#create-branches), please don't work in `master` directly.
2424

25-
After you [comitted](https://help.github.com/articles/create-a-repo#step-2-commit-your-readme) all changes to your branch and [pushed](https://help.github.com/articles/create-a-repo#step-3-push-your-commit) them to your forked version, you'll have to do a [pull request](https://help.github.com/articles/using-pull-requests). Make sure you explain what and why you want to change a part to the core. After the pull request has been voted or discussed on the [technical board meeting](index.md) it will get merged.
25+
After you [comitted](https://help.github.com/articles/create-a-repo#step-2-commit-your-readme) all changes to your branch and [pushed](https://help.github.com/articles/create-a-repo#step-3-push-your-commit) them to your forked version, you'll have to do a [pull request](https://help.github.com/articles/using-pull-requests). Make sure you explain what and why you want to change a part to the core. After the pull request has been voted or discussed on the [technical board meeting](01. introduction.md) it will get merged.
2626

2727
More information about working with GitHub can found on the [help](https://help.github.com/) of GitHub, in the [documentation](http://git-scm.com/documentation) of Git, in the [Git Workflows](http://documentup.com/skwp/git-workflows-book) book or learn Git Branching [interactively](http://pcottle.github.io/learnGitBranching/).
2828

0 commit comments

Comments
 (0)