scratch-l10n 5.0.194 → 5.0.196

package/editor/interface/is.json

@@ -77,6 +77,57 @@
     "gui.customProcedures.cancel": "Hætta við",
     "gui.customProcedures.ok": "Í lagi",
     "gui.debugModal.title": "Debugging | Getting Unstuck",
+    "gui.debugModal.readAloud.title": "Read Aloud",
+    "gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
+    "gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
+    "gui.debugModal.readAloud.description3": "Are your instructions clear?",
+    "gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
+    "gui.debugModal.breakItDown.title": "Break It Down",
+    "gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
+    "gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
+    "gui.debugModal.breakItDown.description3": "The process is called decomposition.",
+    "gui.debugModal.slowItDown.title": "Slow It Down",
+    "gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
+    "gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
+    "gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
+    "gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
+    "gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
+    "gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
+    "gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
+    "gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
+    "gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
+    "gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
+    "gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
+    "gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
+    "gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
+    "gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
+    "gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
+    "gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
+    "gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
+    "gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
+    "gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
+    "gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
+    "gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
+    "gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
+    "gui.debugModal.checkTheValues.title": "Check the Values",
+    "gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
+    "gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
+    "gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
+    "gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
+    "gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
+    "gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
+    "gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
+    "gui.debugModal.commentYourCode.title": "Comment Your Code",
+    "gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
+    "gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
+    "gui.debugModal.takeABreak.title": "Take a Break, Step Away",
+    "gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
+    "gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
+    "gui.debugModal.askForHelp.title": "Ask for Help",
+    "gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
+    "gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
     "gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
     "gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
     "gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
@@ -279,6 +330,8 @@
     "gui.alerts.cloudInfo": "Please note, cloud variables only support numbers, not letters or symbols. {learnMoreLink}",
     "gui.alerts.cloudInfoLearnMore": "Learn more.",
     "gui.alerts.importing": "Importing…",
+    "gui.defaultProject.meow": "Meow",
+    "gui.defaultProject.variable": "my variable",
     "gui.howtos.intro-move-sayhello-hat.name": "Hefjast handa",
     "gui.howtos.intro-move.step_stepMove": "Bættu við hreyfi kubb",
     "gui.howtos.add-a-move-block.step_stepSay": "Add a say block",

package/editor/interface/it.json

@@ -77,6 +77,57 @@
     "gui.customProcedures.cancel": "Annulla",
     "gui.customProcedures.ok": "OK",
     "gui.debugModal.title": "Debugging | Getting Unstuck",
+    "gui.debugModal.readAloud.title": "Read Aloud",
+    "gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
+    "gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
+    "gui.debugModal.readAloud.description3": "Are your instructions clear?",
+    "gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
+    "gui.debugModal.breakItDown.title": "Break It Down",
+    "gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
+    "gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
+    "gui.debugModal.breakItDown.description3": "The process is called decomposition.",
+    "gui.debugModal.slowItDown.title": "Slow It Down",
+    "gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
+    "gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
+    "gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
+    "gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
+    "gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
+    "gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
+    "gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
+    "gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
+    "gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
+    "gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
+    "gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
+    "gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
+    "gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
+    "gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
+    "gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
+    "gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
+    "gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
+    "gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
+    "gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
+    "gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
+    "gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
+    "gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
+    "gui.debugModal.checkTheValues.title": "Check the Values",
+    "gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
+    "gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
+    "gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
+    "gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
+    "gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
+    "gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
+    "gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
+    "gui.debugModal.commentYourCode.title": "Comment Your Code",
+    "gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
+    "gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
+    "gui.debugModal.takeABreak.title": "Take a Break, Step Away",
+    "gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
+    "gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
+    "gui.debugModal.askForHelp.title": "Ask for Help",
+    "gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
+    "gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
     "gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
     "gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
     "gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
@@ -279,6 +330,8 @@
     "gui.alerts.cloudInfo": "Ricorda che le variabili cloud supportano solo numeri, non supportano lettere o simboli. {learnMoreLink}",
     "gui.alerts.cloudInfoLearnMore": "Per saperne di più.",
     "gui.alerts.importing": "Importazione in corso...",
+    "gui.defaultProject.meow": "Meow",
+    "gui.defaultProject.variable": "my variable",
     "gui.howtos.intro-move-sayhello-hat.name": "Per Iniziare",
     "gui.howtos.intro-move.step_stepMove": "Aggiungi un blocco di movimento",
     "gui.howtos.add-a-move-block.step_stepSay": "Aggiungere un blocco dire",

package/editor/interface/ja-Hira.json

@@ -77,6 +77,57 @@
     "gui.customProcedures.cancel": "キャンセル",
     "gui.customProcedures.ok": "OK",
     "gui.debugModal.title": "Debugging | Getting Unstuck",
+    "gui.debugModal.readAloud.title": "Read Aloud",
+    "gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
+    "gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
+    "gui.debugModal.readAloud.description3": "Are your instructions clear?",
+    "gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
+    "gui.debugModal.breakItDown.title": "Break It Down",
+    "gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
+    "gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
+    "gui.debugModal.breakItDown.description3": "The process is called decomposition.",
+    "gui.debugModal.slowItDown.title": "Slow It Down",
+    "gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
+    "gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
+    "gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
+    "gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
+    "gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
+    "gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
+    "gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
+    "gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
+    "gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
+    "gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
+    "gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
+    "gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
+    "gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
+    "gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
+    "gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
+    "gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
+    "gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
+    "gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
+    "gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
+    "gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
+    "gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
+    "gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
+    "gui.debugModal.checkTheValues.title": "Check the Values",
+    "gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
+    "gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
+    "gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
+    "gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
+    "gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
+    "gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
+    "gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
+    "gui.debugModal.commentYourCode.title": "Comment Your Code",
+    "gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
+    "gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
+    "gui.debugModal.takeABreak.title": "Take a Break, Step Away",
+    "gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
+    "gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
+    "gui.debugModal.askForHelp.title": "Ask for Help",
+    "gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
+    "gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
     "gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
     "gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
     "gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
@@ -279,6 +330,8 @@
     "gui.alerts.cloudInfo": "クラウドへんすうはすうじのみサポートしています。もじやきごうはいれられません。{learnMoreLink}",
     "gui.alerts.cloudInfoLearnMore": "もっとくわしく。",
     "gui.alerts.importing": "よみこみちゅう...",
+    "gui.defaultProject.meow": "Meow",
+    "gui.defaultProject.variable": "my variable",
     "gui.howtos.intro-move-sayhello-hat.name": "さあ、はじめましょう",
     "gui.howtos.intro-move.step_stepMove": "うごきブロックをついかして、",
     "gui.howtos.add-a-move-block.step_stepSay": "「( )という」ブロックをついかする",

package/editor/interface/ja.json

@@ -77,6 +77,57 @@
     "gui.customProcedures.cancel": "キャンセル",
     "gui.customProcedures.ok": "OK",
     "gui.debugModal.title": "Debugging | Getting Unstuck",
+    "gui.debugModal.readAloud.title": "Read Aloud",
+    "gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
+    "gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
+    "gui.debugModal.readAloud.description3": "Are your instructions clear?",
+    "gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
+    "gui.debugModal.breakItDown.title": "Break It Down",
+    "gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
+    "gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
+    "gui.debugModal.breakItDown.description3": "The process is called decomposition.",
+    "gui.debugModal.slowItDown.title": "Slow It Down",
+    "gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
+    "gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
+    "gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
+    "gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
+    "gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
+    "gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
+    "gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
+    "gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
+    "gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
+    "gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
+    "gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
+    "gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
+    "gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
+    "gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
+    "gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
+    "gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
+    "gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
+    "gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
+    "gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
+    "gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
+    "gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
+    "gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
+    "gui.debugModal.checkTheValues.title": "Check the Values",
+    "gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
+    "gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
+    "gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
+    "gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
+    "gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
+    "gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
+    "gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
+    "gui.debugModal.commentYourCode.title": "Comment Your Code",
+    "gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
+    "gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
+    "gui.debugModal.takeABreak.title": "Take a Break, Step Away",
+    "gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
+    "gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
+    "gui.debugModal.askForHelp.title": "Ask for Help",
+    "gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
+    "gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
     "gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
     "gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
     "gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
@@ -279,6 +330,8 @@
     "gui.alerts.cloudInfo": "クラウド変数は数字のみサポートしています。文字や記号は入れられません。{learnMoreLink}",
     "gui.alerts.cloudInfoLearnMore": "もっと詳しく。",
     "gui.alerts.importing": "読み込み中...",
+    "gui.defaultProject.meow": "Meow",
+    "gui.defaultProject.variable": "my variable",
     "gui.howtos.intro-move-sayhello-hat.name": "さあ、始めましょう",
     "gui.howtos.intro-move.step_stepMove": "動きのブロックを追加して、",
     "gui.howtos.add-a-move-block.step_stepSay": "「( )と言う」ブロックを追加する",

package/editor/interface/ka.json

@@ -77,6 +77,57 @@
     "gui.customProcedures.cancel": "გააუქმება",
     "gui.customProcedures.ok": "OK",
     "gui.debugModal.title": "Debugging | Getting Unstuck",
+    "gui.debugModal.readAloud.title": "Read Aloud",
+    "gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
+    "gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
+    "gui.debugModal.readAloud.description3": "Are your instructions clear?",
+    "gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
+    "gui.debugModal.breakItDown.title": "Break It Down",
+    "gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
+    "gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
+    "gui.debugModal.breakItDown.description3": "The process is called decomposition.",
+    "gui.debugModal.slowItDown.title": "Slow It Down",
+    "gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
+    "gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
+    "gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
+    "gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
+    "gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
+    "gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
+    "gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
+    "gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
+    "gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
+    "gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
+    "gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
+    "gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
+    "gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
+    "gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
+    "gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
+    "gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
+    "gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
+    "gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
+    "gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
+    "gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
+    "gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
+    "gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
+    "gui.debugModal.checkTheValues.title": "Check the Values",
+    "gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
+    "gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
+    "gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
+    "gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
+    "gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
+    "gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
+    "gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
+    "gui.debugModal.commentYourCode.title": "Comment Your Code",
+    "gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
+    "gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
+    "gui.debugModal.takeABreak.title": "Take a Break, Step Away",
+    "gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
+    "gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
+    "gui.debugModal.askForHelp.title": "Ask for Help",
+    "gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
+    "gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
     "gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
     "gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
     "gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
@@ -279,6 +330,8 @@
     "gui.alerts.cloudInfo": "გთხოვთ გაითვალისწინოთ, რომ ღრუბლოვანი ცვლადები წარმოადგენენ მხოლოდ რიცხვებს და არა ასოებსა და სიმბოლოებს. {learnMoreLink}",
     "gui.alerts.cloudInfoLearnMore": "გაიგე მეტი.",
     "gui.alerts.importing": "წარმოებს იმპორტი...",
+    "gui.defaultProject.meow": "Meow",
+    "gui.defaultProject.variable": "my variable",
     "gui.howtos.intro-move-sayhello-hat.name": "პირველი ნაბიჯები",
     "gui.howtos.intro-move.step_stepMove": "დაამატე გადაადგილების ბლოკი",
     "gui.howtos.add-a-move-block.step_stepSay": "დაამატე ბლოკი “თქვი”",

package/editor/interface/kk.json

@@ -77,6 +77,57 @@
     "gui.customProcedures.cancel": "Болдырмау",
     "gui.customProcedures.ok": "Жақсы",
     "gui.debugModal.title": "Debugging | Getting Unstuck",
+    "gui.debugModal.readAloud.title": "Read Aloud",
+    "gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
+    "gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
+    "gui.debugModal.readAloud.description3": "Are your instructions clear?",
+    "gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
+    "gui.debugModal.breakItDown.title": "Break It Down",
+    "gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
+    "gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
+    "gui.debugModal.breakItDown.description3": "The process is called decomposition.",
+    "gui.debugModal.slowItDown.title": "Slow It Down",
+    "gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
+    "gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
+    "gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
+    "gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
+    "gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
+    "gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
+    "gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
+    "gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
+    "gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
+    "gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
+    "gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
+    "gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
+    "gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
+    "gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
+    "gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
+    "gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
+    "gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
+    "gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
+    "gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
+    "gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
+    "gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
+    "gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
+    "gui.debugModal.checkTheValues.title": "Check the Values",
+    "gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
+    "gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
+    "gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
+    "gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
+    "gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
+    "gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
+    "gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
+    "gui.debugModal.commentYourCode.title": "Comment Your Code",
+    "gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
+    "gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
+    "gui.debugModal.takeABreak.title": "Take a Break, Step Away",
+    "gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
+    "gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
+    "gui.debugModal.askForHelp.title": "Ask for Help",
+    "gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
+    "gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
     "gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
     "gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
     "gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
@@ -279,6 +330,8 @@
     "gui.alerts.cloudInfo": "Назар аударыңыз, бұлтты айнымалылар символдар мен әріптерді емес,  тек сандарды ғана қолдайды{learnMoreLink}",
     "gui.alerts.cloudInfoLearnMore": "Толығырақ.",
     "gui.alerts.importing": "Импорттау...",
+    "gui.defaultProject.meow": "Meow",
+    "gui.defaultProject.variable": "my variable",
     "gui.howtos.intro-move-sayhello-hat.name": "Неден бастауға болады",
     "gui.howtos.intro-move.step_stepMove": "Қозғалу блогын қосу",
     "gui.howtos.add-a-move-block.step_stepSay": "Айту блогын қосу",

package/editor/interface/km.json

@@ -77,6 +77,57 @@
     "gui.customProcedures.cancel": "បោះបង់",
     "gui.customProcedures.ok": "យល់ព្រម",
     "gui.debugModal.title": "Debugging | Getting Unstuck",
+    "gui.debugModal.readAloud.title": "Read Aloud",
+    "gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
+    "gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
+    "gui.debugModal.readAloud.description3": "Are your instructions clear?",
+    "gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
+    "gui.debugModal.breakItDown.title": "Break It Down",
+    "gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
+    "gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
+    "gui.debugModal.breakItDown.description3": "The process is called decomposition.",
+    "gui.debugModal.slowItDown.title": "Slow It Down",
+    "gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
+    "gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
+    "gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
+    "gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
+    "gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
+    "gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
+    "gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
+    "gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
+    "gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
+    "gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
+    "gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
+    "gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
+    "gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
+    "gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
+    "gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
+    "gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
+    "gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
+    "gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
+    "gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
+    "gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
+    "gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
+    "gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
+    "gui.debugModal.checkTheValues.title": "Check the Values",
+    "gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
+    "gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
+    "gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
+    "gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
+    "gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
+    "gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
+    "gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
+    "gui.debugModal.commentYourCode.title": "Comment Your Code",
+    "gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
+    "gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
+    "gui.debugModal.takeABreak.title": "Take a Break, Step Away",
+    "gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
+    "gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
+    "gui.debugModal.askForHelp.title": "Ask for Help",
+    "gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
+    "gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
     "gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
     "gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
     "gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
@@ -279,6 +330,8 @@
     "gui.alerts.cloudInfo": "សូមចាំថាអថេរលើបណ្តាញអាចតែជាលេខប៉ុណ្ណោះ មិនអាចជាអក្សរ ឬសញ្ញាទេ។ {learnMoreLink}",
     "gui.alerts.cloudInfoLearnMore": "ស្វែងយល់បន្ថែម",
     "gui.alerts.importing": "កំពុងនាំចូល...",
+    "gui.defaultProject.meow": "Meow",
+    "gui.defaultProject.variable": "my variable",
     "gui.howtos.intro-move-sayhello-hat.name": "ចាប់ផ្តើម",
     "gui.howtos.intro-move.step_stepMove": "បន្ថែមប្លុកផ្លាស់ទី",
     "gui.howtos.add-a-move-block.step_stepSay": "បន្ថែមប្លុកនិយាយ",

package/editor/interface/ko.json

@@ -77,6 +77,57 @@
     "gui.customProcedures.cancel": "취소",
     "gui.customProcedures.ok": "확인",
     "gui.debugModal.title": "Debugging | Getting Unstuck",
+    "gui.debugModal.readAloud.title": "Read Aloud",
+    "gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
+    "gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
+    "gui.debugModal.readAloud.description3": "Are your instructions clear?",
+    "gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
+    "gui.debugModal.breakItDown.title": "Break It Down",
+    "gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
+    "gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
+    "gui.debugModal.breakItDown.description3": "The process is called decomposition.",
+    "gui.debugModal.slowItDown.title": "Slow It Down",
+    "gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
+    "gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
+    "gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
+    "gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
+    "gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
+    "gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
+    "gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
+    "gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
+    "gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
+    "gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
+    "gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
+    "gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
+    "gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
+    "gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
+    "gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
+    "gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
+    "gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
+    "gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
+    "gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
+    "gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
+    "gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
+    "gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
+    "gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
+    "gui.debugModal.checkTheValues.title": "Check the Values",
+    "gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
+    "gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
+    "gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
+    "gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
+    "gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
+    "gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
+    "gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
+    "gui.debugModal.commentYourCode.title": "Comment Your Code",
+    "gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
+    "gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
+    "gui.debugModal.takeABreak.title": "Take a Break, Step Away",
+    "gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
+    "gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
+    "gui.debugModal.askForHelp.title": "Ask for Help",
+    "gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
+    "gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
     "gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
     "gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
     "gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
@@ -279,6 +330,8 @@
     "gui.alerts.cloudInfo": "클라우드 변수는 숫자만 지원하며 문자나 특수기호는 지원하지 않습니다. {learnMoreLink}",
     "gui.alerts.cloudInfoLearnMore": "더 알아보기",
     "gui.alerts.importing": "Importing…",
+    "gui.defaultProject.meow": "Meow",
+    "gui.defaultProject.variable": "my variable",
     "gui.howtos.intro-move-sayhello-hat.name": "시작하기",
     "gui.howtos.intro-move.step_stepMove": "이동 블록 추가하기 ",
     "gui.howtos.add-a-move-block.step_stepSay": "Add a say block",