diff --git a/docs/defining-blocks.md b/docs/defining-blocks.md
index 4fb9a829e12b..0b950479e01a 100644
--- a/docs/defining-blocks.md
+++ b/docs/defining-blocks.md
@@ -120,7 +120,7 @@ For example,
 
 ```typescript-ignore
 //% block="square $x"
-//% block.loc.fr="$x au carré"
+//% block.loc.fr-FR="$x au carré"
 export function square(x: number): number {}
 ```
 
@@ -137,9 +137,9 @@ PARAM.loc.LOCALE = parameter jsdoc
     @param x the number to square
 **/
 //% block="square $x"
-//% block.loc.fr="$x au carré"
-//% jsdoc.loc.fr="Calcule le carré de x"
-//% x.loc.fr="le nombre"
+//% block.loc.fr-FR="$x au carré"
+//% jsdoc.loc.fr-FR="Calcule le carré de x"
+//% x.loc.fr-FR="le nombre"
 export function square(x: number): number {}
 ```
 
@@ -896,4 +896,4 @@ A few tips gathered while designing various APIs for the Block Editor.
 * **Anything that snaps together will be tried by the user**: your runtime should deal with invalid input with graceful degradation rather than abrupt crashes.
 Some users will try to snap anything together - get ready for it.
 * **OO is cumbersome** in blocks: we recommend using a C-like APIs -- just function -- rather than OO classes. It maps better to blocks.
-* **Keep the number of blocks small**: there's only so much space in the toolbox. Be specific about each API you want to see in blocks.
\ No newline at end of file
+* **Keep the number of blocks small**: there's only so much space in the toolbox. Be specific about each API you want to see in blocks.