You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TRANSLATING.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -265,7 +265,7 @@ When you submit a PR for a translation, you should only include changes to one l
265
265
266
266
Translations PRs will be tagged with a label indicating the language to make them easier to identify and review. For example, contributions to the Spanish translation will be tagged with 'lang-es'.
267
267
268
-
TODO: This tagging could be automated with a GitHub action.
268
+
TODO: This tagging could be automated with a GitHub Actions.
269
269
270
270
When you submit the PR, make sure to include a short description of the changes you made and any context that might be helpful for the reviewer (e.g., you translated new strings, you reviewed fuzzy entries, you fixed typos, etc.)
271
271
@@ -340,7 +340,7 @@ TODO: There are many approaches here, some projects release a translation as soo
340
340
341
341
### How can I get help with my translation?
342
342
343
-
If you have any questions or need help with your translation, you can create an issue in the repository if you encounter any problems or need assistance.
343
+
If you have any questions or need help with your translation, you can create an issue in the repository.
344
344
345
345
TODO: Maybe [Discourse](https://pyopensci.discourse.group/) could be used as a way for contributors to ask for help with translations or the translation workflow?
Copy file name to clipboardExpand all lines: documentation/hosting-tools/myst-markdown-rst-doc-syntax.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ syntax. It is the default syntax used in Jupyter Notebooks. There are tools that
6
6
colored call out blocks and other custom elements to your documentation, you will
7
7
need to use either **myST** or **rST**.
8
8
1.[rST (ReStructured Text):](https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html). **rST** is the native syntax that sphinx supports. rST was the default syntax used for documentation for many years. However, in recent years myST has risen to the top as a favorite for documentation given the flexibility that it allows.
9
-
1.[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html) myST is a combination of vanilla of `markdown` and `rST` syntax. It is a nice option if you are comfortable writing markdown. `myst` is preferred by many because it offers both the rich functionality
9
+
1.[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html) myST is a combination of `markdown` and `rST` syntax. It is a nice option if you are comfortable writing markdown. `myst` is preferred by many because it offers both the rich functionality
10
10
of rST combined with a simple-to-write markdown syntax.
11
11
12
12
While you can chose to use any of the syntaxes listed above, we suggest using
0 commit comments