partial documentation update for workflows for updating documentation

Author: Tridecatrix

.github/workflows/check-links.yaml

@@ -1,4 +1,4 @@
-name: Check external href links in the documentation
+name: Check links
 
 on:
   push:

en/.gitbook/assets/run-workflow-thru-github.png

@@ -54,35 +54,28 @@ That's it! The JabRef team will review your changes and publish them on [docs.ja
 
 To edit more than one file at a time, add screenshots, and for other more advanced changes, we recommend that you checkout this repository locally and create a Pull Request of your changes using the standard git and GitHub workflow.
 
-### Tables
+### Github workflows
 
-The best way to enter tables is to use this [Table Generator](http://www.tablesgenerator.com/markdown\_tables) for Markdown. It has the nice feature to generate markdown tables from different sources, e.g. you can directly copy the table from a spreadsheet or upload a csv file. Just copy and paste the generated markdown into the documentation.
+In order to find broken links and find Markdown errors, you can use the "Check Links" and "Lint" workflows respectively. These are provided in `.github/workflows` and run each time you push to the documentation repo. You are recommended to check the results of these workflows on your local fork after pushing changes to it to catch minor mistakes.
+- Lint workflow checks for minor Markdown formatting style issues.
+- Check links workflow checks for broken links, e.g. to images or external resources.
 
-### How to regenerate `SUMMARY.md` from scratch
+On your local fork, you can check the results of the workflows in the Actions tab > All actions panel on Github as shown below. Click on a specific workflow and its run to check it.
 
-Use <https://github.com/koppor/gitbook-summary-generator>.
+### Notes on links workflow
 
-### How to find broken links
+Links to external resources that aren't essential should be added to `.lycheeignore`. Resources can change URL or be taken down, and it isn't the best use of contributor resources to constantly keep fixing them, so try to spare us the headache!
 
-1. Install [markdown-link-check](https://github.com/tcort/markdown-link-check): `npm install -g markdown-link check`
-2. `find . -name \*.md -exec markdown-link-check -qq {} \; > bad-links.txt`
+Note that check links may fail on links which you did not modify in your changes, in which case you can ignore them. Just do make sure that you don't introduce any additional broken links.
 
-### How to find Markdown errors
+### Tables
 
-You can use the [markdown-lint docker image](https://github.com/marketplace/actions/markdown-linting-action):
+The best way to enter tables is to use this [Table Generator](http://www.tablesgenerator.com/markdown\_tables) for Markdown. It has the nice feature to generate markdown tables from different sources, e.g. you can directly copy the table from a spreadsheet or upload a csv file. Just copy and paste the generated markdown into the documentation.
 
-```shell
-docker run --rm \
-    -v "$(pwd):/tmp/check" \
-    -e INPUT_CONFIG=/tmp/check/.markdownlint.yml \
-    avtodev/markdown-lint:v1 \
-    /tmp/check/en
-```
+### How to regenerate `SUMMARY.md` from scratch
 
-Alternatively, you can run the GitHub Lint workflow:
+Use <https://github.com/koppor/gitbook-summary-generator>.
 
-```shell
-act --rm --platform ubuntu-latest=fwilhe2/act-runner:latest -W .github/workflows/lint.yaml
 ```
 
 ## Run workflows through Github