Skip to content

Commit ec1ab32

Browse files
committed
fix i18n typos
1 parent 702b63e commit ec1ab32

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

i18n.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ You can find the translated version at the following address: https://sveltefr.d
88

99
**We recommend that you fork the [original Svelte repo](https://github.com/sveltejs/svelte)** rather than this one to keep the original repo as reference.
1010

11-
Either way, you should know that the main modifications we made to original repo are the following :
11+
Either way, you should know that the main modifications we made to the original repo are the following:
1212
- removed original workflows
1313
- added docs tracking workflow
1414
- modified Github templates
@@ -126,7 +126,7 @@ The core of the work to accomplish is in the `documentation` folder. You will fi
126126

127127
Do not forget to translate the `meta.json` files, which provide metadata like section titles.
128128

129-
We did not feel necessary to translate the folder names, since it would 'only' affect URLs. This might have an bad influence on SEO. However, the subsections titles in the `.md` files that you will eventually translate will break links throughout your site. You will need to fix those before deployment.
129+
We did not feel necessary to translate the folder names, since it would 'only' affect URLs. This might have a bad influence on SEO. However, the subsections titles in the `.md` files that you will eventually translate will break links throughout your site. You will need to fix those before deployment.
130130

131131
#### `examples`
132132

@@ -175,7 +175,7 @@ Additionally, you also might want to change the `lang` attribute in `sites/svelt
175175

176176
The 'Types' sections of the docs directly refer to the Svelte compiler source code. For instance, the documentation [here](https://svelte.dev/docs/svelte-store#types-readable) is not written anywhere in the `documentation` folder, but in the compiler source code instead.
177177

178-
If you want the types description to also be translated, then you will need to work on these files:
178+
If you want the types descriptions to also be translated, then you will need to work on these files:
179179
- `packages/svelte/src/compiler/interfaces.d.ts`
180180
- `packages/svelte/src/runtime/action/public.d.ts`
181181
- `packages/svelte/src/runtime/internal/dev.js`
@@ -192,9 +192,9 @@ You might feel differently about AI tools, use them if you find them relevant.
192192

193193
## Glossary
194194

195-
In a web development context, some words do not translate well in some languages – or at least in french –, even if they technically have an official translation. This is because people have taken the habit to use the original word in english rather than the translated one. These are called _anglicisms_.
195+
In a web development context, some words do not translate well in some languages – or at least in French –, even if they technically have an official translation. This is because people have taken the habit to use the original word in English rather than the translated one. These are called _anglicisms_.
196196

197-
For example, in french, _callback_ should be translated to _fonction de rappel_. But in practice almost nobody uses the translated word, and we stick to _callback_ instead.
197+
For example, in French, _callback_ should be translated to _fonction de rappel_. But in practice almost nobody uses the translated word, and we stick to _callback_ instead.
198198

199199
For this reason, **we chose to remain as close as possible to the actual usage**, and keep such words in their original version.
200200

0 commit comments

Comments
 (0)