From 9b2d5bfcd7702730b5c4688e9f158b261cd11b8f Mon Sep 17 00:00:00 2001
From: camperbot <dev@freecodecamp.org>
Date: Mon, 16 Sep 2024 14:01:58 +0000
Subject: [PATCH] chore(i18n,learn): processed translations

---
 .../build-a-periodic-table-database.md        |   2 +-
 .../5f3ef6e0a81099d9a697b550.md               |   8 +
 .../introduction-flexbox-lesson-j.md          |   6 +-
 .../introduction-flexbox-lesson-k.md          |   6 +-
 .../learn-block-and-inline-lesson-b.md        |   6 +-
 .../learn-block-and-inline-lesson-g.md        |   2 +-
 ...problems-and-understand-errors-lesson-a.md |   6 +-
 ...problems-and-understand-errors-lesson-b.md |   6 +-
 ...problems-and-understand-errors-lesson-c.md |   6 +-
 .../657b69e10d6606a0185d4d4f.md               |   2 +-
 .../657dce8ff35869721311a5e3.md               |   2 +-
 .../657dcee413423174ca3747f5.md               |   2 +-
 .../5f1a4ef5d5d6b5ab580fc6ae.md               |  25 +
 .../5a8b073d06fa14fcfde687aa.md               | 611 ++++++++++++++++++
 .../602da04c22201c65d2a019f4.md               |  25 +
 .../bd7158d8c443edefaeb5bdff.md               |  65 ++
 .../bd7158d8c443edefaeb5bd0e.md               | 107 +++
 .../5f9771307d4d22b9d2b75a94.md               |  25 +
 .../66a96127422411756204bc1b.md               |   4 +-
 .../66a962954f4e0d76223b37ed.md               |   2 +-
 .../66a972137acd1179fa3fe8a0.md               |   2 +-
 .../66a97ca8c4cbae7d0bb6e0ad.md               |   2 +-
 .../66c8ba41a77db20a93f9d7a1.md               |  71 ++
 .../66c8ba975ee7230e29f6c4ac.md               |  53 ++
 .../66c8ba975ee7230e29f6c4ad.md               |  55 ++
 .../66c8ba975ee7230e29f6c4af.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b0.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b1.md               |  54 ++
 .../66c8ba975ee7230e29f6c4b2.md               | 165 +++++
 .../5f2c289f164c29556da632fd.md               |  19 +
 .../587d7fb3367417b2b2512bfb.md               |  53 ++
 .../587d7fb3367417b2b2512bfc.md               |  43 ++
 .../587d7fb4367417b2b2512bfd.md               |  75 +++
 .../587d7fb4367417b2b2512bfe.md               |  39 ++
 .../587d7fb4367417b2b2512bff.md               |  37 ++
 .../587d7fb4367417b2b2512c00.md               |  68 ++
 .../587d7fb5367417b2b2512c01.md               |  64 ++
 .../587d7fb5367417b2b2512c02.md               |  66 ++
 .../587d7fb5367417b2b2512c03.md               |  66 ++
 .../587d7fb5367417b2b2512c04.md               |  43 ++
 .../build-a-periodic-table-database.md        |   2 +-
 .../5f3ef6e0a81099d9a697b550.md               |   8 +
 .../646de7b64467e96b7d35b5cd.md               |   2 +-
 .../introduction-flexbox-lesson-j.md          |   6 +-
 .../introduction-flexbox-lesson-k.md          |   6 +-
 .../learn-block-and-inline-lesson-b.md        |   6 +-
 .../learn-block-and-inline-lesson-g.md        |   2 +-
 ...problems-and-understand-errors-lesson-a.md |   6 +-
 ...problems-and-understand-errors-lesson-b.md |   6 +-
 ...problems-and-understand-errors-lesson-c.md |   6 +-
 .../657b69e10d6606a0185d4d4f.md               |   2 +-
 .../657dce8ff35869721311a5e3.md               |   2 +-
 .../657dcee413423174ca3747f5.md               |   2 +-
 .../5f1a4ef5d5d6b5ab580fc6ae.md               |  25 +
 .../5a8b073d06fa14fcfde687aa.md               | 611 ++++++++++++++++++
 .../602da04c22201c65d2a019f4.md               |  25 +
 .../bd7158d8c443edefaeb5bdff.md               |  65 ++
 .../bd7158d8c443edefaeb5bd0e.md               | 107 +++
 .../5f9771307d4d22b9d2b75a94.md               |  25 +
 .../66a96127422411756204bc1b.md               |   4 +-
 .../66a962954f4e0d76223b37ed.md               |   2 +-
 .../66a972137acd1179fa3fe8a0.md               |   2 +-
 .../66a97ca8c4cbae7d0bb6e0ad.md               |   2 +-
 .../66c8ba41a77db20a93f9d7a1.md               |  71 ++
 .../66c8ba975ee7230e29f6c4ac.md               |  53 ++
 .../66c8ba975ee7230e29f6c4ad.md               |  55 ++
 .../66c8ba975ee7230e29f6c4af.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b0.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b1.md               |  54 ++
 .../66c8ba975ee7230e29f6c4b2.md               | 165 +++++
 .../5f2c289f164c29556da632fd.md               |  19 +
 .../587d7fb3367417b2b2512bfb.md               |  53 ++
 .../587d7fb3367417b2b2512bfc.md               |  43 ++
 .../587d7fb4367417b2b2512bfd.md               |  75 +++
 .../587d7fb4367417b2b2512bfe.md               |  39 ++
 .../587d7fb4367417b2b2512bff.md               |  37 ++
 .../587d7fb4367417b2b2512c00.md               |  68 ++
 .../587d7fb5367417b2b2512c01.md               |  64 ++
 .../587d7fb5367417b2b2512c02.md               |  66 ++
 .../587d7fb5367417b2b2512c03.md               |  66 ++
 .../587d7fb5367417b2b2512c04.md               |  43 ++
 .../build-a-periodic-table-database.md        |   2 +-
 .../5f3ef6e0a81099d9a697b550.md               |   8 +
 .../646de7b64467e96b7d35b5cd.md               |   2 +-
 .../introduction-flexbox-lesson-j.md          |   6 +-
 .../introduction-flexbox-lesson-k.md          |   6 +-
 .../learn-block-and-inline-lesson-b.md        |   6 +-
 .../learn-block-and-inline-lesson-g.md        |   2 +-
 ...problems-and-understand-errors-lesson-a.md |   6 +-
 ...problems-and-understand-errors-lesson-b.md |   6 +-
 ...problems-and-understand-errors-lesson-c.md |   6 +-
 .../657b69e10d6606a0185d4d4f.md               |   2 +-
 .../657dce8ff35869721311a5e3.md               |   2 +-
 .../657dcee413423174ca3747f5.md               |   2 +-
 .../5f1a4ef5d5d6b5ab580fc6ae.md               |  25 +
 .../5a8b073d06fa14fcfde687aa.md               | 611 ++++++++++++++++++
 .../602da04c22201c65d2a019f4.md               |  25 +
 .../bd7158d8c443edefaeb5bdff.md               |  65 ++
 .../bd7158d8c443edefaeb5bd0e.md               | 107 +++
 .../5f9771307d4d22b9d2b75a94.md               |  25 +
 .../66a96127422411756204bc1b.md               |   4 +-
 .../66a962954f4e0d76223b37ed.md               |   2 +-
 .../66a972137acd1179fa3fe8a0.md               |   2 +-
 .../66a97ca8c4cbae7d0bb6e0ad.md               |   2 +-
 .../66c8ba41a77db20a93f9d7a1.md               |  71 ++
 .../66c8ba975ee7230e29f6c4ac.md               |  53 ++
 .../66c8ba975ee7230e29f6c4ad.md               |  55 ++
 .../66c8ba975ee7230e29f6c4af.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b0.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b1.md               |  54 ++
 .../66c8ba975ee7230e29f6c4b2.md               | 165 +++++
 .../5f2c289f164c29556da632fd.md               |  19 +
 .../587d7fb3367417b2b2512bfb.md               |  53 ++
 .../587d7fb3367417b2b2512bfc.md               |  43 ++
 .../587d7fb4367417b2b2512bfd.md               |  75 +++
 .../587d7fb4367417b2b2512bfe.md               |  39 ++
 .../587d7fb4367417b2b2512bff.md               |  37 ++
 .../587d7fb4367417b2b2512c00.md               |  68 ++
 .../587d7fb5367417b2b2512c01.md               |  64 ++
 .../587d7fb5367417b2b2512c02.md               |  66 ++
 .../587d7fb5367417b2b2512c03.md               |  66 ++
 .../587d7fb5367417b2b2512c04.md               |  43 ++
 ...of-audio-content-with-the-audio-element.md |   2 +-
 .../create-movement-using-css-animation.md    |   2 +-
 ...by-fading-an-element-from-left-to-right.md |   2 +-
 .../basic-css/style-the-html-body-element.md  |   2 +-
 .../add-columns-with-grid-template-columns.md |   2 +-
 .../basic-javascript/record-collection.md     |   4 +-
 ...visualize-data-with-a-scatterplot-graph.md |   2 +-
 .../serialization-of-a-user-object.md         |   2 +-
 ...ality-with-.deepequal-and-.notdeepequal.md |   4 +-
 .../compare-the-properties-of-two-elements.md |   4 +-
 .../learn-how-javascript-assertions-work.md   |   4 +-
 ...sponse-using-chai-http-iii---put-method.md |   2 +-
 ...-tests-on-api-endpoints-using-chai-http.md |  12 +-
 ...ional-tests-using-a-headless-browser-ii.md |   2 +-
 ...nctional-tests-using-a-headless-browser.md |   2 +-
 .../test-for-truthiness.md                    |   4 +-
 .../test-if-a-value-is-an-array.md            |   4 +-
 .../test-if-an-object-has-a-property.md       |   4 +-
 ...-object-is-an-instance-of-a-constructor.md |   4 +-
 ...s-below-or-at-least-as-large-as-another.md |   2 +-
 .../use-assert.isok-and-assert.isnotok.md     |   4 +-
 ...se-regular-expressions-to-test-a-string.md |   4 +-
 ...triple-equals-to-assert-strict-equality.md |   4 +-
 .../american-british-translator.md            |   4 +-
 .../issue-tracker.md                          |   6 +-
 .../metric-imperial-converter.md              |  86 +--
 .../medical-data-visualizer.md                |   6 +-
 .../page-view-time-series-visualizer.md       |   8 +-
 .../port-scanner.md                           |   2 +-
 .../secure-real-time-multiplayer-game.md      |   2 +-
 ...client-side-caching-with-helmet.nocache.md |   2 +-
 ...sh-and-compare-passwords-asynchronously.md |   2 +-
 ...ash-and-compare-passwords-synchronously.md |   2 +-
 ...-information-using-helmet.hidepoweredby.md |   2 +-
 .../install-and-require-helmet.md             |   2 +-
 ...pting-xss-attacks-with-helmet.xssfilter.md |   4 +-
 ...ing-untrusted-html-with-helmet.ienoopen.md |   4 +-
 ...olicy-with-helmet.contentsecuritypolicy.md |  16 +-
 ...d-a-new-element-to-a-binary-search-tree.md |   2 +-
 .../take-home-projects/build-a-pong-game.md   |   8 +-
 .../take-home-projects/build-a-recipe-box.md  |  18 +-
 .../chart-the-stock-market.md                 |  12 +-
 .../use-the-twitch-json-api.md                |  18 +-
 .../neural-network-sms-text-classifier.md     |  12 +-
 ...earning-algorithms-hidden-markov-models.md |  10 +-
 .../tensorflow/core-learning-algorithms.md    |   2 +-
 ...roduction-machine-learning-fundamentals.md |  10 +-
 ...processing-with-rnns-training-the-model.md |   4 +-
 .../tensorflow/neural-networks-optimizers.md  |  10 +-
 .../neural-networks-with-tensorflow.md        |  12 +-
 .../build-a-periodic-table-database.md        |   2 +-
 .../5f3ef6e0a81099d9a697b550.md               |   8 +
 .../introduction-flexbox-lesson-j.md          |   6 +-
 .../introduction-flexbox-lesson-k.md          |   6 +-
 .../learn-block-and-inline-lesson-b.md        |   6 +-
 .../learn-block-and-inline-lesson-g.md        |   2 +-
 ...problems-and-understand-errors-lesson-a.md |   6 +-
 ...problems-and-understand-errors-lesson-b.md |   6 +-
 ...problems-and-understand-errors-lesson-c.md |   6 +-
 .../657b69e10d6606a0185d4d4f.md               |   2 +-
 .../657dce8ff35869721311a5e3.md               |   2 +-
 .../657dcee413423174ca3747f5.md               |   2 +-
 .../5f1a4ef5d5d6b5ab580fc6ae.md               |  25 +
 .../5a8b073d06fa14fcfde687aa.md               | 611 ++++++++++++++++++
 .../602da04c22201c65d2a019f4.md               |  25 +
 .../bd7158d8c443edefaeb5bdff.md               |  65 ++
 .../bd7158d8c443edefaeb5bd0e.md               | 107 +++
 .../5f9771307d4d22b9d2b75a94.md               |  25 +
 .../66a96127422411756204bc1b.md               |   4 +-
 .../66a962954f4e0d76223b37ed.md               |   2 +-
 .../66a972137acd1179fa3fe8a0.md               |   2 +-
 .../66a97ca8c4cbae7d0bb6e0ad.md               |   2 +-
 .../66c8ba41a77db20a93f9d7a1.md               |  71 ++
 .../66c8ba975ee7230e29f6c4ac.md               |  53 ++
 .../66c8ba975ee7230e29f6c4ad.md               |  55 ++
 .../66c8ba975ee7230e29f6c4af.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b0.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b1.md               |  54 ++
 .../66c8ba975ee7230e29f6c4b2.md               | 165 +++++
 .../5f2c289f164c29556da632fd.md               |  19 +
 .../587d7fb3367417b2b2512bfb.md               |  53 ++
 .../587d7fb3367417b2b2512bfc.md               |  43 ++
 .../587d7fb4367417b2b2512bfd.md               |  75 +++
 .../587d7fb4367417b2b2512bfe.md               |  39 ++
 .../587d7fb4367417b2b2512bff.md               |  37 ++
 .../587d7fb4367417b2b2512c00.md               |  68 ++
 .../587d7fb5367417b2b2512c01.md               |  64 ++
 .../587d7fb5367417b2b2512c02.md               |  66 ++
 .../587d7fb5367417b2b2512c03.md               |  66 ++
 .../587d7fb5367417b2b2512c04.md               |  43 ++
 .../build-a-periodic-table-database.md        |   2 +-
 .../5f3ef6e0a81099d9a697b550.md               |   8 +
 .../introduction-flexbox-lesson-j.md          |   6 +-
 .../introduction-flexbox-lesson-k.md          |   6 +-
 .../learn-block-and-inline-lesson-b.md        |   6 +-
 .../learn-block-and-inline-lesson-g.md        |   2 +-
 ...problems-and-understand-errors-lesson-a.md |   6 +-
 ...problems-and-understand-errors-lesson-b.md |   6 +-
 ...problems-and-understand-errors-lesson-c.md |   6 +-
 .../657b69e10d6606a0185d4d4f.md               |   2 +-
 .../657dce8ff35869721311a5e3.md               |   2 +-
 .../657dcee413423174ca3747f5.md               |   2 +-
 .../5f1a4ef5d5d6b5ab580fc6ae.md               |  25 +
 .../5a8b073d06fa14fcfde687aa.md               | 611 ++++++++++++++++++
 .../602da04c22201c65d2a019f4.md               |  25 +
 .../bd7158d8c443edefaeb5bdff.md               |  65 ++
 .../bd7158d8c443edefaeb5bd0e.md               | 107 +++
 .../5f9771307d4d22b9d2b75a94.md               |  25 +
 .../66a96127422411756204bc1b.md               |   4 +-
 .../66a962954f4e0d76223b37ed.md               |   2 +-
 .../66a972137acd1179fa3fe8a0.md               |   2 +-
 .../66a97ca8c4cbae7d0bb6e0ad.md               |   2 +-
 .../66c8ba41a77db20a93f9d7a1.md               |  71 ++
 .../66c8ba975ee7230e29f6c4ac.md               |  53 ++
 .../66c8ba975ee7230e29f6c4ad.md               |  55 ++
 .../66c8ba975ee7230e29f6c4af.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b0.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b1.md               |  54 ++
 .../66c8ba975ee7230e29f6c4b2.md               | 165 +++++
 .../5f2c289f164c29556da632fd.md               |  19 +
 .../587d7fb3367417b2b2512bfb.md               |  53 ++
 .../587d7fb3367417b2b2512bfc.md               |  43 ++
 .../587d7fb4367417b2b2512bfd.md               |  75 +++
 .../587d7fb4367417b2b2512bfe.md               |  39 ++
 .../587d7fb4367417b2b2512bff.md               |  37 ++
 .../587d7fb4367417b2b2512c00.md               |  68 ++
 .../587d7fb5367417b2b2512c01.md               |  64 ++
 .../587d7fb5367417b2b2512c02.md               |  66 ++
 .../587d7fb5367417b2b2512c03.md               |  66 ++
 .../587d7fb5367417b2b2512c04.md               |  43 ++
 .../build-a-periodic-table-database.md        |   2 +-
 .../5f3ef6e0a81099d9a697b550.md               |   8 +
 .../introduction-flexbox-lesson-j.md          |   6 +-
 .../introduction-flexbox-lesson-k.md          |   6 +-
 .../learn-block-and-inline-lesson-b.md        |   6 +-
 .../learn-block-and-inline-lesson-g.md        |   2 +-
 ...problems-and-understand-errors-lesson-a.md |   6 +-
 ...problems-and-understand-errors-lesson-b.md |   6 +-
 ...problems-and-understand-errors-lesson-c.md |   6 +-
 .../657b69e10d6606a0185d4d4f.md               |   2 +-
 .../657dce8ff35869721311a5e3.md               |   2 +-
 .../657dcee413423174ca3747f5.md               |   2 +-
 .../5f1a4ef5d5d6b5ab580fc6ae.md               |  25 +
 .../5a8b073d06fa14fcfde687aa.md               | 611 ++++++++++++++++++
 .../602da04c22201c65d2a019f4.md               |  25 +
 .../bd7158d8c443edefaeb5bdff.md               |  65 ++
 .../bd7158d8c443edefaeb5bd0e.md               | 107 +++
 .../5f9771307d4d22b9d2b75a94.md               |  25 +
 .../66a96127422411756204bc1b.md               |   4 +-
 .../66a962954f4e0d76223b37ed.md               |   2 +-
 .../66a972137acd1179fa3fe8a0.md               |   2 +-
 .../66a97ca8c4cbae7d0bb6e0ad.md               |   2 +-
 .../66c8ba41a77db20a93f9d7a1.md               |  71 ++
 .../66c8ba975ee7230e29f6c4ac.md               |  53 ++
 .../66c8ba975ee7230e29f6c4ad.md               |  55 ++
 .../66c8ba975ee7230e29f6c4af.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b0.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b1.md               |  54 ++
 .../66c8ba975ee7230e29f6c4b2.md               | 165 +++++
 .../5f2c289f164c29556da632fd.md               |  19 +
 .../587d7fb3367417b2b2512bfb.md               |  53 ++
 .../587d7fb3367417b2b2512bfc.md               |  43 ++
 .../587d7fb4367417b2b2512bfd.md               |  75 +++
 .../587d7fb4367417b2b2512bfe.md               |  39 ++
 .../587d7fb4367417b2b2512bff.md               |  37 ++
 .../587d7fb4367417b2b2512c00.md               |  68 ++
 .../587d7fb5367417b2b2512c01.md               |  64 ++
 .../587d7fb5367417b2b2512c02.md               |  66 ++
 .../587d7fb5367417b2b2512c03.md               |  66 ++
 .../587d7fb5367417b2b2512c04.md               |  43 ++
 .../build-a-periodic-table-database.md        |   2 +-
 .../5f3ef6e0a81099d9a697b550.md               |   8 +
 .../introduction-flexbox-lesson-j.md          |   6 +-
 .../introduction-flexbox-lesson-k.md          |   6 +-
 .../learn-block-and-inline-lesson-b.md        |   6 +-
 .../learn-block-and-inline-lesson-g.md        |   2 +-
 ...problems-and-understand-errors-lesson-a.md |   6 +-
 ...problems-and-understand-errors-lesson-b.md |   6 +-
 ...problems-and-understand-errors-lesson-c.md |   6 +-
 .../657b69e10d6606a0185d4d4f.md               |   2 +-
 .../657dce8ff35869721311a5e3.md               |   2 +-
 .../657dcee413423174ca3747f5.md               |   2 +-
 .../5f1a4ef5d5d6b5ab580fc6ae.md               |  25 +
 .../5a8b073d06fa14fcfde687aa.md               | 611 ++++++++++++++++++
 .../602da04c22201c65d2a019f4.md               |  25 +
 .../bd7158d8c443edefaeb5bdff.md               |  65 ++
 .../bd7158d8c443edefaeb5bd0e.md               | 107 +++
 .../5f9771307d4d22b9d2b75a94.md               |  25 +
 .../66a96127422411756204bc1b.md               |   4 +-
 .../66a962954f4e0d76223b37ed.md               |   2 +-
 .../66a972137acd1179fa3fe8a0.md               |   2 +-
 .../66a97ca8c4cbae7d0bb6e0ad.md               |   2 +-
 .../66c8ba41a77db20a93f9d7a1.md               |  71 ++
 .../66c8ba975ee7230e29f6c4ac.md               |  53 ++
 .../66c8ba975ee7230e29f6c4ad.md               |  55 ++
 .../66c8ba975ee7230e29f6c4af.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b0.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b1.md               |  54 ++
 .../66c8ba975ee7230e29f6c4b2.md               | 165 +++++
 .../5f2c289f164c29556da632fd.md               |  19 +
 .../587d7fb3367417b2b2512bfb.md               |  53 ++
 .../587d7fb3367417b2b2512bfc.md               |  43 ++
 .../587d7fb4367417b2b2512bfd.md               |  75 +++
 .../587d7fb4367417b2b2512bfe.md               |  39 ++
 .../587d7fb4367417b2b2512bff.md               |  37 ++
 .../587d7fb4367417b2b2512c00.md               |  68 ++
 .../587d7fb5367417b2b2512c01.md               |  64 ++
 .../587d7fb5367417b2b2512c02.md               |  66 ++
 .../587d7fb5367417b2b2512c03.md               |  66 ++
 .../587d7fb5367417b2b2512c04.md               |  43 ++
 .../chunky-monkey.md                          |  16 +-
 .../factorialize-a-number.md                  |  22 +-
 .../find-the-longest-word-in-a-string.md      |  18 +-
 .../finders-keepers.md                        |   8 +-
 .../basic-algorithm-scripting/mutations.md    |  34 +-
 .../repeat-a-string-repeat-a-string.md        |  20 +-
 .../return-largest-numbers-in-arrays.md       |  14 +-
 .../reverse-a-string.md                       |  14 +-
 .../slice-and-splice.md                       |  22 +-
 .../truncate-a-string.md                      |  16 +-
 .../where-do-i-belong.md                      |  40 +-
 .../build-a-periodic-table-database.md        |   2 +-
 .../5f3ef6e0a81099d9a697b550.md               |   8 +
 .../introduction-flexbox-lesson-j.md          |   6 +-
 .../introduction-flexbox-lesson-k.md          |   6 +-
 .../learn-block-and-inline-lesson-b.md        |   6 +-
 .../learn-block-and-inline-lesson-g.md        |   2 +-
 ...problems-and-understand-errors-lesson-a.md |   6 +-
 ...problems-and-understand-errors-lesson-b.md |   6 +-
 ...problems-and-understand-errors-lesson-c.md |   6 +-
 .../657b69e10d6606a0185d4d4f.md               |   2 +-
 .../657dce8ff35869721311a5e3.md               |   2 +-
 .../657dcee413423174ca3747f5.md               |   2 +-
 .../5f1a4ef5d5d6b5ab580fc6ae.md               |  25 +
 .../5a8b073d06fa14fcfde687aa.md               | 611 ++++++++++++++++++
 .../602da04c22201c65d2a019f4.md               |  25 +
 .../bd7158d8c443edefaeb5bdff.md               |  65 ++
 .../bd7158d8c443edefaeb5bd0e.md               | 107 +++
 .../5f9771307d4d22b9d2b75a94.md               |  25 +
 .../66a96127422411756204bc1b.md               |   4 +-
 .../66a962954f4e0d76223b37ed.md               |   2 +-
 .../66a972137acd1179fa3fe8a0.md               |   2 +-
 .../66a97ca8c4cbae7d0bb6e0ad.md               |   2 +-
 .../66c8ba41a77db20a93f9d7a1.md               |  71 ++
 .../66c8ba975ee7230e29f6c4ac.md               |  53 ++
 .../66c8ba975ee7230e29f6c4ad.md               |  55 ++
 .../66c8ba975ee7230e29f6c4af.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b0.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b1.md               |  54 ++
 .../66c8ba975ee7230e29f6c4b2.md               | 165 +++++
 .../5f2c289f164c29556da632fd.md               |  19 +
 .../587d7fb3367417b2b2512bfb.md               |  53 ++
 .../587d7fb3367417b2b2512bfc.md               |  43 ++
 .../587d7fb4367417b2b2512bfd.md               |  75 +++
 .../587d7fb4367417b2b2512bfe.md               |  39 ++
 .../587d7fb4367417b2b2512bff.md               |  37 ++
 .../587d7fb4367417b2b2512c00.md               |  68 ++
 .../587d7fb5367417b2b2512c01.md               |  64 ++
 .../587d7fb5367417b2b2512c02.md               |  66 ++
 .../587d7fb5367417b2b2512c03.md               |  66 ++
 .../587d7fb5367417b2b2512c04.md               |  43 ++
 .../build-a-periodic-table-database.md        |   2 +-
 .../5f3ef6e0a81099d9a697b550.md               |   8 +
 .../introduction-flexbox-lesson-a.md          |  34 +-
 .../introduction-flexbox-lesson-c.md          |  12 +-
 .../introduction-flexbox-lesson-d.md          |  14 +-
 .../introduction-flexbox-lesson-e.md          |  22 +-
 .../introduction-flexbox-lesson-i.md          |  20 +-
 .../introduction-flexbox-lesson-j.md          |  30 +-
 .../introduction-flexbox-lesson-k.md          |   6 +-
 .../learn-arrays-and-loops-lesson-a.md        |  16 +-
 .../learn-arrays-and-loops-lesson-c.md        |  20 +-
 .../learn-arrays-and-loops-lesson-d.md        |  22 +-
 .../learn-arrays-and-loops-lesson-e.md        |  10 +-
 .../learn-arrays-and-loops-lesson-f.md        |   8 +-
 .../learn-block-and-inline-lesson-b.md        |   6 +-
 .../learn-block-and-inline-lesson-d.md        |  12 +-
 .../learn-block-and-inline-lesson-e.md        |  14 +-
 .../learn-block-and-inline-lesson-f.md        |  12 +-
 .../learn-block-and-inline-lesson-g.md        |   2 +-
 .../learn-block-and-inline-lesson-i.md        |  10 +-
 .../learn-block-and-inline-lesson-j.md        |  14 +-
 .../learn-block-and-inline-lesson-k.md        |  14 +-
 .../css-foundations-lesson-a.md               |  12 +-
 .../css-foundations-lesson-d.md               |  16 +-
 .../css-foundations-lesson-e.md               |  18 +-
 .../css-foundations-lesson-f.md               |  26 +-
 .../css-foundations-lesson-g.md               |  16 +-
 .../the-cascade-of-css-lesson-a.md            |  18 +-
 .../the-cascade-of-css-lesson-e.md            |  16 +-
 .../the-cascade-of-css-lesson-f.md            |  10 +-
 .../the-cascade-of-css-lesson-g.md            |  18 +-
 ...rn-data-types-and-conditionals-lesson-a.md |  20 +-
 ...rn-data-types-and-conditionals-lesson-b.md |  12 +-
 ...rn-data-types-and-conditionals-lesson-e.md |  10 +-
 ...rn-data-types-and-conditionals-lesson-f.md |  24 +-
 ...rn-data-types-and-conditionals-lesson-g.md |  22 +-
 ...rn-data-types-and-conditionals-lesson-h.md |  12 +-
 ...rn-data-types-and-conditionals-lesson-k.md |  18 +-
 ...rn-data-types-and-conditionals-lesson-l.md |  10 +-
 .../learn-function-basics-lesson-c.md         |  12 +-
 .../learn-function-basics-lesson-d.md         |  20 +-
 .../learn-function-basics-lesson-e.md         |  18 +-
 .../learn-function-basics-lesson-f.md         |  18 +-
 .../html-foundations-lesson-a.md              |  22 +-
 .../html-foundations-lesson-c.md              |  30 +-
 .../html-foundations-lesson-e.md              |  30 +-
 .../html-foundations-lesson-f.md              |  20 +-
 .../html-foundations-lesson-g.md              |  12 +-
 ...problems-and-understand-errors-lesson-a.md |  30 +-
 ...problems-and-understand-errors-lesson-b.md |  36 +-
 ...problems-and-understand-errors-lesson-c.md |  26 +-
 ...problems-and-understand-errors-lesson-d.md |  16 +-
 ...problems-and-understand-errors-lesson-g.md |  20 +-
 ...problems-and-understand-errors-lesson-h.md |  20 +-
 .../learn-variables-and-operators-lesson-a.md |  20 +-
 .../learn-variables-and-operators-lesson-d.md |   8 +-
 .../learn-variables-and-operators-lesson-e.md |  32 +-
 .../learn-variables-and-operators-lesson-f.md |  32 +-
 .../learn-variables-and-operators-lesson-g.md |  20 +-
 .../learn-variables-and-operators-lesson-i.md |  42 +-
 .../links-and-images-lesson-a.md              |  32 +-
 .../links-and-images-lesson-e.md              |  52 +-
 .../links-and-images-lesson-f.md              |  58 +-
 .../links-and-images-lesson-g.md              |  52 +-
 .../the-box-model-lesson-c.md                 |  20 +-
 .../the-box-model-lesson-d.md                 |  20 +-
 .../the-box-model-lesson-e.md                 |  16 +-
 .../the-box-model-lesson-h.md                 |  14 +-
 .../the-box-model-lesson-i.md                 |  14 +-
 .../the-box-model-lesson-j.md                 |  10 +-
 .../the-box-model-lesson-k.md                 |   4 +-
 .../working-with-text-lesson-a.md             |  20 +-
 .../working-with-text-lesson-b.md             |  20 +-
 .../working-with-text-lesson-d.md             |  14 +-
 .../working-with-text-lesson-f.md             |  24 +-
 .../working-with-text-lesson-g.md             |  10 +-
 .../657b69e10d6606a0185d4d4f.md               |   2 +-
 .../657dce8ff35869721311a5e3.md               |   2 +-
 .../657dcee413423174ca3747f5.md               |   2 +-
 .../6543abeff5f028dba112f278.md               |  10 +-
 .../656a509eeac7e030e2a16bab.md               |   6 +-
 .../656a52da3392f631b9f3e022.md               |   8 +-
 .../656cc523e668741073c4e916.md               |  10 +-
 .../656cc6981cbf2711196a284f.md               |   6 +-
 .../656cd63a45146d1c2c51e682.md               |  18 +-
 .../657b1240ef768447b80817ad.md               |   8 +-
 .../657b163c9da40e62b904be1f.md               |   8 +-
 .../657b1e2fad2ffe84ab420a56.md               |  24 +-
 .../657b2310b8cd52a4f15c1818.md               |  18 +-
 .../666339cedcfb436e2c9fd550.md               |   8 +-
 .../666339dd9d6dc46efa85c8cb.md               |  10 +-
 .../655a54506b259313b2d59577.md               |  20 +-
 .../657e4fc397780aa2bc046ed7.md               |  20 +-
 .../657e77b682b49f70a3adcc0a.md               |  18 +-
 .../651dd5a46ffb500e3f2ce47b.md               |   2 +-
 .../657ca06716e21b803ffb55d5.md               |  14 +-
 .../657ca59e6e559782e4c10056.md               |  12 +-
 .../657cd6c342d0e8093dd5c540.md               |  10 +-
 .../657daa5ab8505427a5b99cd2.md               |  18 +-
 .../657daad61699f1281c5dca55.md               |  20 +-
 .../5f1a4ef5d5d6b5ab580fc6ae.md               |  25 +
 .../5a8b073d06fa14fcfde687aa.md               | 611 ++++++++++++++++++
 .../602da04c22201c65d2a019f4.md               |  25 +
 .../66bb3e20d3dc5b6d0a21f5dd.md               |  36 +-
 .../668f08ea07b99b1f4a91acab.md               |   2 +-
 .../bd7158d8c443edefaeb5bdff.md               |  65 ++
 .../66c051d13a6a20255a963695.md               |  72 +--
 .../bd7158d8c443edefaeb5bd0e.md               | 107 +++
 .../5f9771307d4d22b9d2b75a94.md               |  25 +
 .../66a33e9bd3aa213cd23d9c57.md               |   2 +-
 .../66cc0de2920bec775f610424.md               |   2 +-
 .../66cc281d687975858049fd8d.md               |   2 +-
 .../66a9ca099e3ecb1be10a2696.md               |   2 +-
 .../66add47d27763c4862492c8c.md               |   2 +-
 .../66a96127422411756204bc1b.md               |   4 +-
 .../66a962954f4e0d76223b37ed.md               |   2 +-
 .../66a972137acd1179fa3fe8a0.md               |   2 +-
 .../66a97ca8c4cbae7d0bb6e0ad.md               |   2 +-
 .../66a9843525e9fa8046d709b7.md               |   2 +-
 .../66c8ba41a77db20a93f9d7a1.md               |  71 ++
 .../66c8ba975ee7230e29f6c4ac.md               |  53 ++
 .../66c8ba975ee7230e29f6c4ad.md               |  55 ++
 .../66c8ba975ee7230e29f6c4af.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b0.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b1.md               |  54 ++
 .../66c8ba975ee7230e29f6c4b2.md               | 165 +++++
 .../5f2c289f164c29556da632fd.md               |  19 +
 .../587d7fb3367417b2b2512bfb.md               |  53 ++
 .../587d7fb3367417b2b2512bfc.md               |  43 ++
 .../587d7fb4367417b2b2512bfd.md               |  75 +++
 .../587d7fb4367417b2b2512bfe.md               |  39 ++
 .../587d7fb4367417b2b2512bff.md               |  37 ++
 .../587d7fb4367417b2b2512c00.md               |  68 ++
 .../587d7fb5367417b2b2512c01.md               |  64 ++
 .../587d7fb5367417b2b2512c02.md               |  66 ++
 .../587d7fb5367417b2b2512c03.md               |  66 ++
 .../587d7fb5367417b2b2512c04.md               |  43 ++
 .../66cf13fe7619e9a1d57c7b5e.md               |  14 +-
 .../66cf315cff4d36b27da828ba.md               |  32 +-
 .../66cf33305293e1b35c1aef7f.md               |  16 +-
 .../66cf34fcb005e7b447141afd.md               |  22 +-
 .../66cf35a75f891ab4f4e5497b.md               |  16 +-
 .../66cf3639aca119b5c00b02d3.md               |  36 +-
 .../66d05da61ff145d7a46fe41b.md               |  16 +-
 .../66d064c7d79408da050f8b2f.md               |  22 +-
 .../66d068348ca093db469b4d59.md               |  22 +-
 .../66d0746099f6f3de3678fd26.md               |  22 +-
 .../66d076040c7d1cdf36525af9.md               |  18 +-
 .../66d081d79b1d57e1b42caabf.md               |  22 +-
 .../66d085d37aeffce2ef786de3.md               |   8 +-
 .../66d8fade439d513e5f77c906.md               |  16 +-
 .../66c72b0ffbc5522525768558.md               |   2 +-
 .../66c748ffdfbe4f2ede268be2.md               |   2 +-
 .../66b59be6ab830800c4df9146.md               |   2 +-
 .../66b6e62423e8a031d6c1f03d.md               |   2 +-
 .../66b6e80d6c3f0b329c360283.md               |   2 +-
 .../66b7049b7709ea3a9547c79d.md               |   2 +-
 .../build-a-periodic-table-database.md        |   2 +-
 .../5f3ef6e0a81099d9a697b550.md               |   8 +
 .../introduction-flexbox-lesson-j.md          |   6 +-
 .../introduction-flexbox-lesson-k.md          |   6 +-
 .../learn-block-and-inline-lesson-b.md        |   6 +-
 .../learn-block-and-inline-lesson-g.md        |   2 +-
 ...problems-and-understand-errors-lesson-a.md |   6 +-
 ...problems-and-understand-errors-lesson-b.md |   6 +-
 ...problems-and-understand-errors-lesson-c.md |   6 +-
 .../657b69e10d6606a0185d4d4f.md               |   2 +-
 .../657dce8ff35869721311a5e3.md               |   2 +-
 .../657dcee413423174ca3747f5.md               |   2 +-
 .../5f1a4ef5d5d6b5ab580fc6ae.md               |  25 +
 .../5a8b073d06fa14fcfde687aa.md               | 611 ++++++++++++++++++
 .../602da04c22201c65d2a019f4.md               |  25 +
 .../bd7158d8c443edefaeb5bdff.md               |  65 ++
 .../bd7158d8c443edefaeb5bd0e.md               | 107 +++
 .../5f9771307d4d22b9d2b75a94.md               |  25 +
 .../66a96127422411756204bc1b.md               |   4 +-
 .../66a962954f4e0d76223b37ed.md               |   2 +-
 .../66a972137acd1179fa3fe8a0.md               |   2 +-
 .../66a97ca8c4cbae7d0bb6e0ad.md               |   2 +-
 .../66c8ba41a77db20a93f9d7a1.md               |  71 ++
 .../66c8ba975ee7230e29f6c4ac.md               |  53 ++
 .../66c8ba975ee7230e29f6c4ad.md               |  55 ++
 .../66c8ba975ee7230e29f6c4af.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b0.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b1.md               |  54 ++
 .../66c8ba975ee7230e29f6c4b2.md               | 165 +++++
 .../5f2c289f164c29556da632fd.md               |  19 +
 .../587d7fb3367417b2b2512bfb.md               |  53 ++
 .../587d7fb3367417b2b2512bfc.md               |  43 ++
 .../587d7fb4367417b2b2512bfd.md               |  75 +++
 .../587d7fb4367417b2b2512bfe.md               |  39 ++
 .../587d7fb4367417b2b2512bff.md               |  37 ++
 .../587d7fb4367417b2b2512c00.md               |  68 ++
 .../587d7fb5367417b2b2512c01.md               |  64 ++
 .../587d7fb5367417b2b2512c02.md               |  66 ++
 .../587d7fb5367417b2b2512c03.md               |  66 ++
 .../587d7fb5367417b2b2512c04.md               |  43 ++
 .../build-a-periodic-table-database.md        |   2 +-
 .../5f3ef6e0a81099d9a697b550.md               |   8 +
 .../646de7b64467e96b7d35b5cd.md               |   2 +-
 .../introduction-flexbox-lesson-j.md          |   6 +-
 .../introduction-flexbox-lesson-k.md          |   6 +-
 .../learn-block-and-inline-lesson-b.md        |   6 +-
 .../learn-block-and-inline-lesson-g.md        |   2 +-
 ...problems-and-understand-errors-lesson-a.md |   6 +-
 ...problems-and-understand-errors-lesson-b.md |   6 +-
 ...problems-and-understand-errors-lesson-c.md |   6 +-
 .../the-box-model-lesson-b.md                 |   2 +-
 .../the-box-model-lesson-c.md                 |   2 +-
 .../the-box-model-lesson-d.md                 |   2 +-
 .../657b69e10d6606a0185d4d4f.md               |   2 +-
 .../657dce8ff35869721311a5e3.md               |   2 +-
 .../657dcee413423174ca3747f5.md               |   2 +-
 .../5f1a4ef5d5d6b5ab580fc6ae.md               |  25 +
 .../5a8b073d06fa14fcfde687aa.md               | 611 ++++++++++++++++++
 .../602da04c22201c65d2a019f4.md               |  25 +
 .../bd7158d8c443edefaeb5bdff.md               |  65 ++
 .../bd7158d8c443edefaeb5bd0e.md               | 107 +++
 .../5f9771307d4d22b9d2b75a94.md               |  25 +
 .../66a96127422411756204bc1b.md               |   4 +-
 .../66a962954f4e0d76223b37ed.md               |   2 +-
 .../66a972137acd1179fa3fe8a0.md               |   2 +-
 .../66a97ca8c4cbae7d0bb6e0ad.md               |   2 +-
 .../66c8ba41a77db20a93f9d7a1.md               |  71 ++
 .../66c8ba975ee7230e29f6c4ac.md               |  53 ++
 .../66c8ba975ee7230e29f6c4ad.md               |  55 ++
 .../66c8ba975ee7230e29f6c4af.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b0.md               |  56 ++
 .../66c8ba975ee7230e29f6c4b1.md               |  54 ++
 .../66c8ba975ee7230e29f6c4b2.md               | 165 +++++
 .../5f2c289f164c29556da632fd.md               |  19 +
 .../587d7fb3367417b2b2512bfb.md               |  53 ++
 .../587d7fb3367417b2b2512bfc.md               |  43 ++
 .../587d7fb4367417b2b2512bfd.md               |  75 +++
 .../587d7fb4367417b2b2512bfe.md               |  39 ++
 .../587d7fb4367417b2b2512bff.md               |  37 ++
 .../587d7fb4367417b2b2512c00.md               |  68 ++
 .../587d7fb5367417b2b2512c01.md               |  64 ++
 .../587d7fb5367417b2b2512c02.md               |  66 ++
 .../587d7fb5367417b2b2512c03.md               |  66 ++
 .../587d7fb5367417b2b2512c04.md               |  43 ++
 624 files changed, 23080 insertions(+), 1641 deletions(-)
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
 create mode 100644 curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
 create mode 100644 curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
 create mode 100644 curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
 create mode 100644 curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
 create mode 100644 curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
 create mode 100644 curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
 create mode 100644 curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
 create mode 100644 curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
 create mode 100644 curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
 create mode 100644 curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
 create mode 100644 curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md

diff --git a/curriculum/challenges/arabic/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md b/curriculum/challenges/arabic/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
index db5b0c61e0..5608918f2f 100644
--- a/curriculum/challenges/arabic/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
+++ b/curriculum/challenges/arabic/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
@@ -8,7 +8,7 @@ dashedName: build-a-periodic-table-database
 
 # --description--
 
-This is one of the required projects to earn your certification. For this project, you will create Bash a script to get information about chemical elements from a periodic table database.
+This is one of the required projects to earn your certification. For this project, you will create a Bash script to get information about chemical elements from a periodic table database.
 
 # --instructions--
 
diff --git a/curriculum/challenges/arabic/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md b/curriculum/challenges/arabic/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
index 7651c8ad5f..c1612f1733 100644
--- a/curriculum/challenges/arabic/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
+++ b/curriculum/challenges/arabic/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
@@ -9,6 +9,8 @@ dashedName: step-64
 
 في داخل `footer`، أضف عنصر `p`. بعد ذلك، قم بدمج عنصر الرابط (`a`) في `p` الذي يربط الي `https://www.freecodecamp.org` ولديه النص `Visit our website`.
 
+Make sure that the link opens in a new tab by adding a `target` attribute with the value `_blank`.
+
 # --hints--
 
 لا يجب عليك تعديل عنصر `footer` الحالي.
@@ -43,6 +45,12 @@ assert(document.querySelector("footer > p > a")?.innerText === "Visit our websit
 assert(document.querySelector("footer > p > a")?.href === "https://www.freecodecamp.org/");
 ```
 
+Your new `a` element should have the `target` attribute set to `_blank`.
+
+```js
+assert.equal(document.querySelector("footer > p > a")?.target, "_blank");
+```
+
 # --seed--
 
 ## --seed-contents--
diff --git a/curriculum/challenges/arabic/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md b/curriculum/challenges/arabic/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
index d2ad72a1ea..1b6ca05444 100644
--- a/curriculum/challenges/arabic/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
+++ b/curriculum/challenges/arabic/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
@@ -21,12 +21,12 @@ Remove `flex: 1` from `.item` and add `justify-content: space-between` to `.cont
 
 `justify-content` aligns items across the **main axis**. There are a few values that you can use here. You'll learn the rest of them in the reading assignments, but for now try changing it to center, which should center the boxes along the main axis.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see what is possible with the `justify-content` property. Read this [interactive article on MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) and play around with the different values of `justify-content` on the example.
 
+# --question--
+
 ## --text--
 
 How does applying `justify-content: space-between` to a flex container affect the positioning of its items?
diff --git a/curriculum/challenges/arabic/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md b/curriculum/challenges/arabic/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
index d3137b0af5..59acb55a29 100644
--- a/curriculum/challenges/arabic/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
+++ b/curriculum/challenges/arabic/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
@@ -17,12 +17,12 @@ To change the placement of items along the cross axis use `align-items`. Try get
 
 Because `justify-content` and `align-items` are based on the main and cross axis of your container, their behavior changes when you change the flex-direction of a flex-container. For example, when you change `flex-direction` to `column`, `justify-content` aligns vertically and `align-items` aligns horizontally. The most common behavior, however, is the default, i.e. `justify-content` aligns items horizontally (because the main axis defaults to horizontal), and `align-items` aligns them vertically. One of the biggest sticking points that beginners have with flexbox is confusion when this behavior changes.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see if you can figure out how `align-items` behaves when you change the `flex-direction` property to `column`.
 
+# --question--
+
 ## --text--
 
 When changing the `flex-direction` property to `column` in a flex container, how does `align-items` behave in relation to the flex items?
diff --git a/curriculum/challenges/arabic/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md b/curriculum/challenges/arabic/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
index 1adf9ce84f..49edeac0e4 100644
--- a/curriculum/challenges/arabic/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
+++ b/curriculum/challenges/arabic/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
@@ -9,12 +9,12 @@ dashedName: learn-block-and-inline-lesson-b
 
 Inline elements, however, do not start on a new line. They appear in line with whatever elements they are placed beside. A clear example of an inline element is a link, or `<a>` tag. If you stick one of these in the middle of a paragraph of text, it will behave like a part of the paragraph. <a  href="https://www.freecodecamp.org/" target="_blank">(Like this)</a> The link’s text will sit alongside other words in that paragraph. Additionally, padding and margin behave differently on inline elements. In general, you do not want to try to put extra padding or margin on inline elements.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Search the web for a list of `block` elements and a list of `inline` elements.
 
+# --question--
+
 ## --text--
 
 What is the difference between a `block` element and an `inline` element?
diff --git a/curriculum/challenges/arabic/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md b/curriculum/challenges/arabic/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
index cdd4d5aa87..e75492e9c1 100644
--- a/curriculum/challenges/arabic/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
+++ b/curriculum/challenges/arabic/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-block-and-inline-lesson-g
 
 # --description--
 
-Now that you have some basic understanding of `block` and inline `elements`, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
+Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
 
 # --question--
 
diff --git a/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md b/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
index 995073b8a2..a7a2ee9a51 100644
--- a/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
+++ b/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
@@ -21,12 +21,12 @@ New programmers often find problem solving the hardest skill to build. It's not
 
 The best way to improve your problem solving ability is by building experience by making lots and lots of programs. The more practice you have the better you'll be prepared to solve real world problems.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Read <a href="https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/" target="_blank">How to Think Like a Programmer - Lessons in Problem Solving</a> by Richard Reis.
 
+# --question--
+
 ## --text--
 
 According to V. Anton Spraul in "Think Like a Programmer," what is problem solving in programming?
diff --git a/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md b/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
index ae905ecf89..c57a7d43e8 100644
--- a/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
+++ b/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
@@ -25,11 +25,11 @@ Now that you know what you’re aiming to solve, don’t jump into coding just y
 
 The last question is where you will write out an algorithm to solve the problem. You can think of an algorithm as a recipe for solving a particular problem. It defines the steps that need to be taken by the computer to solve a problem in pseudocode.
 
-# --question--
-
-## --assignment--
+# --assignment--
 Watch <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">How to Begin Thinking Like a Programmer</a> by Coding Tech. It’s an hour long but packed full of information and definitely worth your time watching.
 
+# --question--
+
 ## --text--
 
 What should you do before starting to code according to the provided text?
diff --git a/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md b/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
index c837fd9658..082f2d51ae 100644
--- a/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
+++ b/curriculum/challenges/arabic/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
@@ -22,12 +22,12 @@ Print the value of the counter variable
 
 This is a basic program to demonstrate how pseudocode looks. There will be more examples of pseudocode included in the assignments.
 
+# --assignment--
 
-# --question--
-
-## --assignment--
 Read this <a href="https://builtin.com/data-science/pseudocode" target="_blank"> Pseudocode: What It Is and How to Write It</a> article from Built In.
 
+# --question--
+
 ## --text--
 
 What are the benefits of using pseudocode according to the linked article?
diff --git a/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md b/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
index d1838e5943..e6aa3a19dc 100644
--- a/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
+++ b/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-So far you have learned how to create questions with the verb to be. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
+So far you have learned how to create questions with the verb `to be`. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
 
 `You are a developer` -> `Are you a developer?`
 
diff --git a/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md b/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
index 544d8f1988..8cd311a518 100644
--- a/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
+++ b/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
@@ -21,7 +21,7 @@ Which sentence is correct for describing one place near you?
 
 ### --feedback--
 
-`There are` is used for plural nouns, and `bank` is singular. You’ll learn about there are in the next few lessons.
+`There are` is used for plural nouns, and `bank` is singular. You’ll learn about `there are` in the next few lessons.
 
 ---
 
diff --git a/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md b/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
index 6526b1e95b..10c0845779 100644
--- a/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
+++ b/curriculum/challenges/arabic/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
@@ -7,7 +7,7 @@ dashedName: task-112
 
 # --description--
 
-To elaborate a question using `there is` you just need to change the order of the verb to be, like so:
+To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so:
 
 `There is an ATM nearby` -> `Is there an ATM nearby?`
 
diff --git a/curriculum/challenges/arabic/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md b/curriculum/challenges/arabic/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
new file mode 100644
index 0000000000..7d664a8876
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
@@ -0,0 +1,25 @@
+---
+id: 5f1a4ef5d5d6b5ab580fc6ae
+title: Build a Celestial Bodies Database
+challengeType: 13
+url: freeCodeCamp/learn-celestial-bodies-database
+dashedName: lab-celestial-bodies-database
+---
+
+# --description--
+
+For this project, you will build a database of celestial bodies using PostgreSQL.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `universe.sql` file so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `universe.sql`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/arabic/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md b/curriculum/challenges/arabic/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
new file mode 100644
index 0000000000..9492b82cb4
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
@@ -0,0 +1,611 @@
+---
+id: 5a8b073d06fa14fcfde687aa
+title: Build an Exercise Tracker
+challengeType: 4
+dashedName: build-an-exercise-tracker
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://exercise-tracker.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://exercise-tracker.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+Your responses should have the following structures.
+
+Exercise:
+
+```js
+{
+  username: "fcc_test",
+  description: "test",
+  duration: 60,
+  date: "Mon Jan 01 1990",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+User:
+
+```js
+{
+  username: "fcc_test",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Log:
+
+```js
+{
+  username: "fcc_test",
+  count: 1,
+  _id: "5fb5853f734231456ccb3b05",
+  log: [{
+    description: "test",
+    duration: 60,
+    date: "Mon Jan 01 1990",
+  }]
+}
+```
+
+**Hint:** For the `date` property, the `toDateString` method of the `Date` API can be used to achieve the expected output.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  const url = getUserInput('url');
+  assert(
+    !/.*\/exercise-tracker\.freecodecamp\.rocks/.test(getUserInput('url'))
+  );
+};
+```
+
+You can `POST` to `/api/users` with form data `username` to create a new user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The returned response from `POST /api/users` with form data `username` will be an object with `username` and `_id` properties.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    assert.exists(_id);
+    assert.exists(username);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users` to get a list of all users.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `GET` request to `/api/users` returns an array.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    assert.isArray(users);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Each element in the array returned from `GET /api/users` is an object literal containing a user's `username` and `_id`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    const user = users[0];
+    assert.exists(user);
+    assert.exists(user.username);
+    assert.exists(user._id);
+    assert.isString(user.username);
+    assert.isString(user._id);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can `POST` to `/api/users/:_id/exercises` with form data `description`, `duration`, and optionally `date`. If no date is supplied, the current date will be used.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+  assert.isTrue(addRes.ok);
+  if(!addRes.ok) {
+    throw new Error(`${addRes.status} ${addRes.statusText}`)
+  };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+The response returned from `POST /api/users/:_id/exercises` will be the user object with the exercise fields added.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    if (addRes.ok) {
+      const actual = await addRes.json();
+      assert.deepEqual(actual, expected);
+      assert.isString(actual.description);
+      assert.isNumber(actual.duration);
+      assert.isString(actual.date);
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users/:_id/logs` to retrieve a full exercise log of any user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+    assert.isTrue(logRes.ok);
+    if(!logRes.ok) {
+      throw new Error(`${logRes.status} ${logRes.statusText}`)
+    };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A request to a user's log `GET /api/users/:_id/logs` returns a user object with a `count` property representing the number of exercises that belong to that user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if (logRes.ok) {
+        const { count } = await logRes.json();
+        assert(count);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A `GET` request to `/api/users/:_id/logs` will return the user object with a `log` array of all the exercises added.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  })
+  if(res.ok){
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok){
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+Each item in the `log` array that is returned from `GET /api/users/:_id/logs` is an object that should have a `description`, `duration`, and `date` properties.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + `/api/users`, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+     const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.exists(exercise);
+        assert.exists(exercise.description);
+        assert.exists(exercise.duration);
+        assert.exists(exercise.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `description` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.description);
+        assert.equal(exercise.description, expected.description);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `duration` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a number.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isNumber(exercise.duration);
+        assert.equal(exercise.duration, expected.duration);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `date` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string. Use the `dateString` format of the `Date` API.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toLocaleDateString("en-US", {
+        timeZone: "UTC", weekday: "short", month: "short",
+        day: "2-digit", year: "numeric"
+      }).replaceAll(',', '')
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.date);
+        assert.equal(exercise.date, expected.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can add `from`, `to` and `limit` parameters to a `GET /api/users/:_id/logs` request to retrieve part of the log of any user. `from` and `to` are dates in `yyyy-mm-dd` format. `limit` is an integer of how many logs to send back.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addExerciseRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    const addExerciseTwoRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-03`
+    });
+    if (addExerciseRes.ok && addExerciseTwoRes.ok) {
+      const logRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1989-12-31&to=1990-01-04`
+      );
+      if (logRes.ok) {
+        const { log } = await logRes.json();
+        assert.isArray(log);
+        assert.equal(2, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+      const limitRes = await fetch(
+        url + `/api/users/${_id}/logs?limit=1`
+      );
+      if (limitRes.ok) {
+        const { log } = await limitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${limitRes.status} ${limitRes.statusText}`);
+      }
+      const filterDateBeforeLimitRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1990-01-02&to=1990-01-04&limit=1`
+      );
+      if (filterDateBeforeLimitRes.ok) {
+        const { log } = await filterDateBeforeLimitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${filterDateBeforeLimitRes.status} ${filterDateBeforeLimitRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${res.status} ${res.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
diff --git a/curriculum/challenges/arabic/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md b/curriculum/challenges/arabic/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
new file mode 100644
index 0000000000..ef87dc6720
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
@@ -0,0 +1,25 @@
+---
+id: 602da04c22201c65d2a019f4
+title: Build a Number Guessing Game
+challengeType: 13
+url: freeCodeCamp/learn-number-guessing-game
+dashedName: lab-number-guessing-game
+---
+
+# --description--
+
+For this lab, you will use Bash scripting, PostgreSQL, and Git to create a number guessing game that runs in the terminal and saves user information.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `number_guess.sql` file, as well as your `number_guess.sh` file, so you can complete step 2. There will be instructions on how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `number_guess.sql`, `number_guess.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/arabic/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md b/curriculum/challenges/arabic/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
new file mode 100644
index 0000000000..5040e27424
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
@@ -0,0 +1,65 @@
+---
+id: bd7158d8c443edefaeb5bdff
+title: Build a Request Header Parser Microservice
+challengeType: 4
+dashedName: lab-request-header-parser-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://request-header-parser-microservice.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://request-header-parser-microservice.freecodecamp.rocks/</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/request-header-parser-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+A request to `/api/whoami` should return a JSON object with your IP address in the `ipaddress` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.ipaddress && data.ipaddress.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your preferred language in the `language` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.language && data.language.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your software in the `software` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.software && data.software.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/arabic/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md b/curriculum/challenges/arabic/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
new file mode 100644
index 0000000000..0fbf80a0bf
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
@@ -0,0 +1,107 @@
+---
+id: bd7158d8c443edefaeb5bd0e
+title: URL Shortener Microservice
+challengeType: 4
+dashedName: url-shortener-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://url-shortener-microservice.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://url-shortener-microservice.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+**HINT:** Do not forget to use a body parsing middleware to handle the POST requests. Also, you can use the function `dns.lookup(host, cb)` from the `dns` core module to verify a submitted URL.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/url-shortener-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+You can POST a URL to `/api/shorturl` and get a JSON response with `original_url` and `short_url` properties. Here's an example: `{ original_url : 'https://freeCodeCamp.org', short_url : 1}`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (res.ok) {
+    const { short_url, original_url } = await res.json();
+    assert.isNotNull(short_url);
+    assert.strictEqual(original_url, `${url}/?v=${urlVariable}`);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+When you visit `/api/shorturl/<short_url>`, you will be redirected to the original URL.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  let shortenedUrlVariable;
+  const postResponse = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (postResponse.ok) {
+    const { short_url } = await postResponse.json();
+    shortenedUrlVariable = short_url;
+  } else {
+    throw new Error(`${postResponse.status} ${postResponse.statusText}`);
+  }
+  const getResponse = await fetch(
+    url + '/api/shorturl/' + shortenedUrlVariable
+  );
+  if (getResponse) {
+    const { redirected, url } = getResponse;
+    assert.isTrue(redirected);
+    assert.strictEqual(url,fullUrl);
+  } else {
+    throw new Error(`${getResponse.status} ${getResponse.statusText}`);
+  }
+};
+```
+
+If you pass an invalid URL that doesn't follow the valid `http://www.example.com` format, the JSON response will contain `{ error: 'invalid url' }`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=ftp:/john-doe.invalidTLD`
+  });
+  if (res.ok) {
+    const { error } = await res.json();
+    assert.isNotNull(error);
+    assert.strictEqual(error.toLowerCase(), 'invalid url');
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
diff --git a/curriculum/challenges/arabic/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md b/curriculum/challenges/arabic/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
new file mode 100644
index 0000000000..d77442a1ba
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
@@ -0,0 +1,25 @@
+---
+id: 5f9771307d4d22b9d2b75a94
+title: Build a World Cup Database
+challengeType: 13
+url: freeCodeCamp/learn-world-cup-database
+dashedName: lab-world-cup-database
+---
+
+# --description--
+
+For this project, you will create a Bash script that enters information from World Cup games into PostgreSQL, then query the database for useful statistics.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `worldcup.sql` file, as well as your `insert_data.sh` and `queries.sh` files, so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `worldcup.sql`, `insert_data.sh`, `queries.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md b/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
index 51ea9e3069..753ee1a6bb 100644
--- a/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
@@ -7,9 +7,9 @@ dashedName: step-22
 
 # --description--
 
-Add another label with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
+Add another `label` with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
 
-Below the label element, add another checkbox input with the `id`, `name` and `value` attributes set to `"recommendation"`.
+Below the `label` element, add another checkbox `input` with the `id`, `name` and `value` attributes set to `"recommendation"`.
 
 # --hints--
 
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md b/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
index 42c425209d..80a23ca86d 100644
--- a/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
@@ -11,7 +11,7 @@ Next, add another `label` element with the text of `Location` and the `for` attr
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"location"`.
 
-Below that `input` element, add another `label` element with the text of `Reputation` and the for attribute set to `"reputation"`.
+Below that `input` element, add another `label` element with the text of `Reputation` and the `for` attribute set to `"reputation"`.
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"reputation"`.
 
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md b/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
index 69efa4832c..09e3e6e59b 100644
--- a/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
@@ -7,7 +7,7 @@ dashedName: step-28
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attributes:**
 
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md b/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
index 6549345d45..22b9a707be 100644
--- a/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
@@ -7,7 +7,7 @@ dashedName: step-31
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attribute:**
 
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
new file mode 100644
index 0000000000..237515fd88
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
@@ -0,0 +1,71 @@
+---
+id: 66c8ba41a77db20a93f9d7a1
+title: Step 1
+challengeType: 1
+dashedName: step-1
+---
+
+# --description--
+
+In this workshop, you'll review JavaScript conditionals by building a loan qualification checker app.
+
+The app will check whether the user is eligible for a duplex, car, and condo loan based on their annual income and credit score. A credit score is a number that represents how good you are at managing borrowed money.
+
+To get started, create the following variables and values.
+
+| Variable Name             | Value   |
+| ------------------------- | ------- |
+| `minIncomeForDuplex`      | `60000` |
+| `minCreditScoreForDuplex` | `700`   |
+| `minIncomeForCondo`       | `45000` |
+| `minCreditScoreForCondo`  | `680`   |
+| `minIncomeForCar`         | `30000` |
+| `minCreditScoreForCar`    | `650`   |
+
+# --hints--
+
+You should create a `minIncomeForDuplex` variable set to `60000`.
+
+```js
+assert.equal(minIncomeForDuplex, 60000);
+```
+
+You should create a `minCreditScoreForDuplex` set to `700`.
+
+```js
+assert.equal(minCreditScoreForDuplex, 700);
+```
+
+You should create a `minIncomeForCar` variable set to `30000`.
+
+```js
+assert.equal(minIncomeForCar, 30000);
+```
+
+You should create a `minCreditScoreForCar` variable set to `650`.
+
+```js
+assert.equal(minCreditScoreForCar, 650);
+```
+
+You should create a `minIncomeForCondo` variable set to `45000`.
+
+```js
+assert.equal(minIncomeForCondo, 45000);
+```
+
+You should create a `minCreditScoreForCondo` variable set to `680`.
+
+```js
+assert.equal(minCreditScoreForCondo, 680);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
new file mode 100644
index 0000000000..7755f823c4
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
@@ -0,0 +1,53 @@
+---
+id: 66c8ba975ee7230e29f6c4ac
+title: Step 2
+challengeType: 1
+dashedName: step-2
+---
+
+# --description--
+
+When the user is eligible for a loan, you'll want to display a message to them in the console.
+
+For that, you'll build out a function inside which you'll have some checks that'll return what loan the applicant is eligible for.
+
+Create an empty `getLoanMessage` function with an `annualIncome` and `creditScore` parameters.
+
+# --hints--
+
+You should create a `getLoanMessage` function
+
+```js
+assert.isFunction(getLoanMessage)
+```
+
+Your `getLoanMessage` function should have an `annualIncome` and `creditScore` as parameters.
+
+```js
+assert.match(getLoanMessage?.toString(), /\(\s*annualIncome,\s*creditScore\s*\)|\(\s*creditScore,\s*annualIncome\s*\)/);
+```
+
+`getLoanMessage` should be an empty function.
+
+```js
+assert.match(getLoanMessage?.toString(), /\{\s*\}/);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
new file mode 100644
index 0000000000..82a29d7cd9
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
@@ -0,0 +1,55 @@
+---
+id: 66c8ba975ee7230e29f6c4ad
+title: Step 3
+challengeType: 1
+dashedName: step-3
+---
+
+# --description--
+
+To check which loan a user is qualified for based on the `annualIncome` and `creditScore`, you have to use `if/else if` statement or a ternary right inside the `getLoanMessage` function. You'll then return the appropraite message in the block of each condition.
+
+Starting with the duplex loan, check if `annualIncome` is greater than or equal to `minIncomeForDuplex` AND if `creditScore` is greater than `minCreditScoreForDuplex`.
+
+If that condition is true, then the applicant is eligible for a duplex loan and the other loans. So, inside the check, return the string `"You qualify for a car, duplex and Condo loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string.
+
+```js
+assert.isString(getLoanMessage(65000, 750));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a duplex, condo, and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(65000, 750), "You qualify for a duplex, condo, and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a duplex loan.
+
+```js
+assert.strictEqual(getLoanMessage(59000, 700), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+function getLoanMessage(annualIncome, creditScore) {
+
+}
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
new file mode 100644
index 0000000000..638e6291a4
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4af
+title: Step 4
+challengeType: 1
+dashedName: step-4
+---
+
+# --description--
+
+If the applicant's annual income is greater than or equal to `minIncomeForCondo`, AND if their credit score is greater than or equal to `minCreditScoreForCondo`, then they qualify for a condo and car loan.
+
+Check if that's true in the `getLoanMessage` function. If it is, return the string `"You qualify for a condo and car loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a condo and car loan.
+
+```js
+assert.isString(getLoanMessage(45000, 680));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a condo and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 680), "You qualify for a condo and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a condo loan.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 650), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
new file mode 100644
index 0000000000..374ba7b8fe
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4b0
+title: Step 5
+challengeType: 1
+dashedName: step-5
+---
+
+# --description--
+
+Now, you should check if the applicant is qualified for a car loan only. If they're, return the string `"You qualify for a car loan."`.
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a car loan.
+
+```js
+assert.isString(getLoanMessage(30000, 650));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 650), "You qualify for a car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a car loan.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 600), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+--fcc-editable-region--
+  } 
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
new file mode 100644
index 0000000000..16e8c7baca
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
@@ -0,0 +1,54 @@
+---
+id: 66c8ba975ee7230e29f6c4b1
+title: Step 6
+challengeType: 1
+dashedName: step-6
+---
+
+# --description--
+
+If the applicant's annual income and credit score fall below `minIncomeForCar` and `minCreditScoreForCar`, then they don't qualify for any loan. So, return the string `"You don't qualify for any loans."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant doesn't qualify for any loan.
+
+```js
+assert.isString(getLoanMessage(25000, 550));
+```
+
+Your `getLoanMessage` function should return the string `"You don't qualify for any loans."` if the applicant does not meet the requirements for any loan.
+
+```js
+assert.strictEqual(getLoanMessage(15000, 600), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(25000, 550), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(20000, 500), "You don't qualify for any loans.");
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
new file mode 100644
index 0000000000..9d19f9ea4c
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
@@ -0,0 +1,165 @@
+---
+id: 66c8ba975ee7230e29f6c4b2
+title: Step 7
+challengeType: 1
+dashedName: step-7
+---
+
+# --description--
+
+Now, it is time to test out your `getLoanMessage` function.
+
+Use the table below to create `4` variables and their values:
+
+| Variable Name   | Value                        |
+| --------------- | ---------------------------- |
+| `duplexLoanMsg` | `getLoanMessage(85000, 850)` |
+| `condoLoanMsg`  | `getLoanMessage(65000, 690)` |
+| `carLoanMsg`    | `getLoanMessage(45000, 660)` |
+| `noLoanMsg`     | `getLoanMessage(25000, 550)` |
+
+After that, log each variable to the console to see the messages.
+
+With that, your loan qualification checker project is complete!
+
+# --hints--
+
+You should have a variable called `duplexLoanMsg`.
+
+```js
+assert.isNotNull(duplexLoanMsg);
+```
+
+Your `duplexLoanMsg` variable should be set to the result of `getLoanMessage(85000, 850)`.
+
+```js
+assert.equal(duplexLoanMsg, getLoanMessage(85000, 850));
+```
+
+You should log the `duplexLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(duplexLoanMsg\)/)
+```
+
+You should have a variable called `condoLoanMsg`.
+
+```js
+assert.isNotNull(condoLoanMsg);
+```
+
+Your `condoLoanMsg` variable should be set to the result of `getLoanMessage(65000, 690)`.
+
+```js
+assert.equal(condoLoanMsg, getLoanMessage(65000, 690));
+```
+
+You should log the `condoLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(condoLoanMsg\)/)
+```
+
+You should have a variable called `carLoanMsg`.
+
+```js
+assert.isNotNull(carLoanMsg);
+```
+
+Your `carLoanMsg` variable should be set to the result of `getLoanMessage(45000, 660)`.
+
+```js
+assert.equal(carLoanMsg, getLoanMessage(45000, 660));
+```
+
+You should log the `carLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(carLoanMsg\)/)
+```
+
+You should have a variable called `noLoanMsg`.
+
+```js
+assert.isNotNull(noLoanMsg);
+```
+
+Your `noLoanMsg` variable should be set to the result of `getLoanMessage(25000, 550)`.
+
+```js
+assert.equal(noLoanMsg, getLoanMessage(25000, 550));
+```
+
+You should log the `noLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(noLoanMsg\)/)
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
+
+# --solutions--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+const duplexLoanMsg = getLoanMessage(85000, 850)
+console.log(duplexLoanMsg)
+
+const condoLoanMsg = getLoanMessage(65000, 690)
+console.log(condoLoanMsg)
+
+const carLoanMsg = getLoanMessage(45000, 660)
+console.log(carLoanMsg)
+
+const noLoanMsg = getLoanMessage(25000, 550)
+console.log(noLoanMsg)
+```
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md b/curriculum/challenges/arabic/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
new file mode 100644
index 0000000000..4e11751ca0
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
@@ -0,0 +1,19 @@
+---
+id: 5f2c289f164c29556da632fd
+title: Build a Mario Database
+challengeType: 12
+url: freeCodeCamp/learn-relational-databases-by-building-a-mario-database
+dashedName: build-a-mario-database
+---
+
+# --description--
+
+In this 165-lesson workshop, you will learn the basics of a relational database by creating a PostgreSQL database filled with video game characters.
+
+# --instructions--
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
new file mode 100644
index 0000000000..8d4c90410d
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
@@ -0,0 +1,53 @@
+---
+id: 587d7fb3367417b2b2512bfb
+title: How to Use package.json, the Core of Any Node.js Project or npm Package
+challengeType: 2
+forumTopicId: 301528
+dashedName: how-to-use-package-json-the-core-of-any-node-js-project-or-npm-package
+---
+
+# --description--
+
+Working on these challenges will involve you writing your code using one of the following methods:
+
+- Clone <a href="https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete these challenges locally.
+- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+The `package.json` file is the center of any Node.js project or npm package. It stores information about your project. It consists of a single JSON object where information is stored in key-value pairs. There are only two required fields; `name` and `version`, but it’s good practice to provide additional information.
+
+You can create the `package.json` file from the terminal using the `npm init` command. This will run a guided setup. Using `npm init` with the `-y` flag will generate the file without having it ask any questions, `npm init -y`.
+
+If you look at the file tree of your project, you will find the `package.json` file on the top level of the tree. This is the file that you will be improving in the next couple of challenges.
+
+One of the most common pieces of information in this file is the `author` field. It specifies who created the project, and can consist of a string or an object with contact or other details. An object is recommended for bigger projects, but a simple string like the following example will do for this project.
+
+```json
+"author": "Jane Doe",
+```
+
+# --instructions--
+
+Add your name as the `author` of the project in the `package.json` file.
+
+**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (") and be separated with a comma (,).
+
+If you are using Gitpod, make sure the app is running and the preview window is open. Copy the preview window's URL and paste it into the Solution Link input below.
+
+# --hints--
+
+`package.json` should have a valid "author" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.author, '"author" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
new file mode 100644
index 0000000000..37d15d5261
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb3367417b2b2512bfc
+title: Add a Description to Your package.json
+challengeType: 2
+forumTopicId: 301522
+dashedName: add-a-description-to-your-package-json
+---
+
+# --description--
+
+The next part of a good package.json file is the `description` field; where a short, but informative description about your project belongs.
+
+If some day you plan to publish a package to npm, this is the string that should sell your idea to the user when they decide whether to install your package or not. However, that’s not the only use case for the description, it’s a great way to summarize what a project does. It’s just as important in any Node.js project to help other developers, future maintainers or even your future self understand the project quickly.
+
+Regardless of what you plan for your project, a description is definitely recommended. Here's an example:
+
+```json
+"description": "A project that does something awesome",
+```
+
+# --instructions--
+
+Add a `description` to the package.json file of your project.
+
+**Note:** Remember to use double-quotes for field-names (") and commas (,) to separate fields.
+
+# --hints--
+
+package.json should have a valid "description" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.description, '"description" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
new file mode 100644
index 0000000000..a001cdd477
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
@@ -0,0 +1,75 @@
+---
+id: 587d7fb4367417b2b2512bfd
+title: Add Keywords to Your package.json
+challengeType: 2
+forumTopicId: 301526
+dashedName: add-keywords-to-your-package-json
+---
+
+# --description--
+
+The `keywords` field is where you can describe your project using related keywords. Here's an example:
+
+```json
+"keywords": [ "descriptive", "related", "words" ],
+```
+
+As you can see, this field is structured as an array of double-quoted strings.
+
+# --instructions--
+
+Add an array of suitable strings to the `keywords` field in the package.json file of your project.
+
+One of the keywords should be "freecodecamp".
+
+# --hints--
+
+package.json should have a valid "keywords" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.keywords, '"keywords" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" field should be an Array
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.isArray(packJson.keywords, '"keywords" is not an array');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" should include "freecodecamp"
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.include(
+        packJson.keywords,
+        'freecodecamp',
+        '"keywords" does not include "freecodecamp"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
new file mode 100644
index 0000000000..7b09acd042
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
@@ -0,0 +1,39 @@
+---
+id: 587d7fb4367417b2b2512bfe
+title: Add a License to Your package.json
+challengeType: 2
+forumTopicId: 301523
+dashedName: add-a-license-to-your-package-json
+---
+
+# --description--
+
+The `license` field is where you inform users of what they are allowed to do with your project.
+
+Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do. Here's an example of the license field:
+
+```json
+"license": "MIT",
+```
+
+# --instructions--
+
+Fill the `license` field in the package.json file of your project as you find suitable.
+
+# --hints--
+
+package.json should have a valid "license" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.license, '"license" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
new file mode 100644
index 0000000000..f2e571faed
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
@@ -0,0 +1,37 @@
+---
+id: 587d7fb4367417b2b2512bff
+title: Add a Version to Your package.json
+challengeType: 2
+forumTopicId: 301525
+dashedName: add-a-version-to-your-package-json
+---
+
+# --description--
+
+A `version` is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example:
+
+```json
+"version": "1.2.0",
+```
+
+# --instructions--
+
+Add a `version` to the package.json file of your project.
+
+# --hints--
+
+package.json should have a valid "version" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.version, '"version" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
new file mode 100644
index 0000000000..161c60fe69
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
@@ -0,0 +1,68 @@
+---
+id: 587d7fb4367417b2b2512c00
+title: Expand Your Project with External Packages from npm
+challengeType: 2
+forumTopicId: 301527
+dashedName: expand-your-project-with-external-packages-from-npm
+---
+
+# --description--
+
+One of the biggest reasons to use a package manager, is their powerful dependency management. Instead of manually having to make sure that you get all dependencies whenever you set up a project on a new computer, npm automatically installs everything for you. But how can npm know exactly what your project needs? Meet the `dependencies` section of your package.json file.
+
+In this section, packages your project requires are stored using the following format:
+
+```json
+"dependencies": {
+  "package-name": "version",
+  "express": "4.14.0"
+}
+
+```
+
+# --instructions--
+
+Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file.
+
+**Note:** `@freecodecamp/example` is a faux package used as a learning tool.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.1.0"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^[\^\~]?1\.1\.0/,
+        'Wrong version of "@freecodecamp/example" installed. It should be 1.1.0'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
new file mode 100644
index 0000000000..deda9b82de
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
@@ -0,0 +1,64 @@
+---
+id: 587d7fb5367417b2b2512c01
+title: Manage npm Dependencies By Understanding Semantic Versioning
+challengeType: 2
+forumTopicId: 301529
+dashedName: manage-npm-dependencies-by-understanding-semantic-versioning
+---
+
+# --description--
+
+`Versions` of the npm packages in the dependencies section of your package.json file follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes projects can expect if they update.
+
+Knowing SemVer can be useful when you develop software that uses external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things that worked yesterday suddenly don’t work today. This is how Semantic Versioning works according to the official website:
+
+```json
+"package": "MAJOR.MINOR.PATCH"
+```
+
+The MAJOR version should increment when you make incompatible API changes. The MINOR version should increment when you add functionality in a backwards-compatible manner. The PATCH version should increment when you make backwards-compatible bug fixes. This means that PATCHes are bug fixes and MINORs add new features but neither of them break what worked before. Finally, MAJORs add changes that won’t work with earlier versions.
+
+# --instructions--
+
+In the dependencies section of your `package.json` file, change the version of `@freecodecamp/example` to match MAJOR version 1, MINOR version 2 and PATCH version 13
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.equal(
+        packJson.dependencies["@freecodecamp/example"],
+        '1.2.13',
+        'Wrong version of "@freecodecamp/example". It should be 1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
new file mode 100644
index 0000000000..8eae5f51ee
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c02
+title: Use the Tilde-Character to Always Use the Latest Patch Version of a Dependency
+challengeType: 2
+forumTopicId: 301532
+dashedName: use-the-tilde-character-to-always-use-the-latest-patch-version-of-a-dependency
+---
+
+# --description--
+
+In the last challenge, you told npm to only include a specific version of a package. That’s a useful way to freeze your dependencies if you need to make sure that different parts of your project stay compatible with each other. But in most use cases, you don’t want to miss bug fixes since they often include important security patches and (hopefully) don’t break things in doing so.
+
+To allow an npm dependency to update to the latest PATCH version, you can prefix the dependency’s version with the tilde (`~`) character. Here's an example of how to allow updates to any `1.3.x` version.
+
+```json
+"package": "~1.3.8"
+```
+
+# --instructions--
+
+In the package.json file, your current rule for how npm may upgrade `@freecodecamp/example` is to use a specific version (`1.2.13`). But now, you want to allow the latest `1.2.x` version.
+
+Use the tilde (`~`) character to prefix the version of `@freecodecamp/example` in your dependencies, and allow npm to update it to any new _patch_ release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"~1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\~1\.2\.13/,
+        'Wrong version of "@freecodecamp/example". It should be ~1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
new file mode 100644
index 0000000000..adc3014ea4
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c03
+title: Use the Caret-Character to Use the Latest Minor Version of a Dependency
+challengeType: 2
+forumTopicId: 301531
+dashedName: use-the-caret-character-to-use-the-latest-minor-version-of-a-dependency
+---
+
+# --description--
+
+Similar to how the tilde we learned about in the last challenge allows npm to install the latest PATCH for a dependency, the caret (`^`) allows npm to install future updates as well. The difference is that the caret will allow both MINOR updates and PATCHes.
+
+Your current version of `@freecodecamp/example` should be `~1.2.13` which allows npm to install to the latest `1.2.x` version. If you were to use the caret (^) as a version prefix instead, npm would be allowed to update to any `1.x.x` version.
+
+```json
+"package": "^1.3.8"
+```
+
+This would allow updates to any `1.x.x` version of the package.
+
+# --instructions--
+
+Use the caret (`^`) to prefix the version of `@freecodecamp/example` in your dependencies and allow npm to update it to any new MINOR release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"^1.x.x"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\^1\./,
+        'Wrong version of "@freecodecamp/example". It should be ^1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
new file mode 100644
index 0000000000..5f695eed88
--- /dev/null
+++ b/curriculum/challenges/arabic/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb5367417b2b2512c04
+title: Remove a Package from Your Dependencies
+challengeType: 2
+forumTopicId: 301530
+dashedName: remove-a-package-from-your-dependencies
+---
+
+# --description--
+
+You have now tested a few ways you can manage dependencies of your project by using the package.json's dependencies section. You have also included external packages by adding them to the file and even told npm what types of versions you want, by using special characters such as the tilde or the caret.
+
+But what if you want to remove an external package that you no longer need? You might already have guessed it, just remove the corresponding key-value pair for that package from your dependencies.
+
+This same method applies to removing other fields in your package.json as well.
+
+# --instructions--
+
+Remove the `@freecodecamp/example` package from your dependencies.
+
+**Note:** Make sure you have the right amount of commas after removing it.
+
+# --hints--
+
+`"dependencies"` should not include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.notProperty(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" still includes "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese-traditional/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md b/curriculum/challenges/chinese-traditional/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
index b41ff255a4..379499275e 100644
--- a/curriculum/challenges/chinese-traditional/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
+++ b/curriculum/challenges/chinese-traditional/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
@@ -8,7 +8,7 @@ dashedName: build-a-periodic-table-database
 
 # --description--
 
-這是你獲得認證的必做項目之一。 對於此項目，你將創建 Bash 腳本以從元素週期表數據庫中獲取有關化學元素的信息。
+這是你獲得認證的必做項目之一。 For this project, you will create a Bash script to get information about chemical elements from a periodic table database.
 
 # --instructions--
 
diff --git a/curriculum/challenges/chinese-traditional/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md b/curriculum/challenges/chinese-traditional/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
index 8acf942f13..7827cdcb58 100644
--- a/curriculum/challenges/chinese-traditional/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
+++ b/curriculum/challenges/chinese-traditional/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
@@ -9,6 +9,8 @@ dashedName: step-64
 
 在 `footer` 中，添加一個 `p` 元素。 然後，在 `p` 中嵌套一個錨（`a`）元素，鏈接到 `https://www.freecodecamp.org`，並有文字 `Visit our website`。
 
+Make sure that the link opens in a new tab by adding a `target` attribute with the value `_blank`.
+
 # --hints--
 
 你不應該修改現有的 `footer` 元素。
@@ -43,6 +45,12 @@ assert(document.querySelector("footer > p > a")?.innerText === "Visit our websit
 assert(document.querySelector("footer > p > a")?.href === "https://www.freecodecamp.org/");
 ```
 
+Your new `a` element should have the `target` attribute set to `_blank`.
+
+```js
+assert.equal(document.querySelector("footer > p > a")?.target, "_blank");
+```
+
 # --seed--
 
 ## --seed-contents--
diff --git a/curriculum/challenges/chinese-traditional/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md b/curriculum/challenges/chinese-traditional/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md
index b9940170e8..b5899009cf 100644
--- a/curriculum/challenges/chinese-traditional/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md
+++ b/curriculum/challenges/chinese-traditional/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md
@@ -7,7 +7,7 @@ dashedName: step-47
 
 # --description--
 
-Move the right eye into position with a `position` property of `absolute`, a `top` of `54px`, and a `left` of `134px`.
+將右眼移動到位，其 `position` 屬性爲 `absolute`，`top` 爲 `54px`，`left` 爲 `134px`。
 
 # --hints--
 
diff --git a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
index d2ad72a1ea..1b6ca05444 100644
--- a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
+++ b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
@@ -21,12 +21,12 @@ Remove `flex: 1` from `.item` and add `justify-content: space-between` to `.cont
 
 `justify-content` aligns items across the **main axis**. There are a few values that you can use here. You'll learn the rest of them in the reading assignments, but for now try changing it to center, which should center the boxes along the main axis.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see what is possible with the `justify-content` property. Read this [interactive article on MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) and play around with the different values of `justify-content` on the example.
 
+# --question--
+
 ## --text--
 
 How does applying `justify-content: space-between` to a flex container affect the positioning of its items?
diff --git a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
index d3137b0af5..59acb55a29 100644
--- a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
+++ b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
@@ -17,12 +17,12 @@ To change the placement of items along the cross axis use `align-items`. Try get
 
 Because `justify-content` and `align-items` are based on the main and cross axis of your container, their behavior changes when you change the flex-direction of a flex-container. For example, when you change `flex-direction` to `column`, `justify-content` aligns vertically and `align-items` aligns horizontally. The most common behavior, however, is the default, i.e. `justify-content` aligns items horizontally (because the main axis defaults to horizontal), and `align-items` aligns them vertically. One of the biggest sticking points that beginners have with flexbox is confusion when this behavior changes.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see if you can figure out how `align-items` behaves when you change the `flex-direction` property to `column`.
 
+# --question--
+
 ## --text--
 
 When changing the `flex-direction` property to `column` in a flex container, how does `align-items` behave in relation to the flex items?
diff --git a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
index 1adf9ce84f..49edeac0e4 100644
--- a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
+++ b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
@@ -9,12 +9,12 @@ dashedName: learn-block-and-inline-lesson-b
 
 Inline elements, however, do not start on a new line. They appear in line with whatever elements they are placed beside. A clear example of an inline element is a link, or `<a>` tag. If you stick one of these in the middle of a paragraph of text, it will behave like a part of the paragraph. <a  href="https://www.freecodecamp.org/" target="_blank">(Like this)</a> The link’s text will sit alongside other words in that paragraph. Additionally, padding and margin behave differently on inline elements. In general, you do not want to try to put extra padding or margin on inline elements.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Search the web for a list of `block` elements and a list of `inline` elements.
 
+# --question--
+
 ## --text--
 
 What is the difference between a `block` element and an `inline` element?
diff --git a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
index cdd4d5aa87..e75492e9c1 100644
--- a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
+++ b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-block-and-inline-lesson-g
 
 # --description--
 
-Now that you have some basic understanding of `block` and inline `elements`, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
+Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
 
 # --question--
 
diff --git a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
index 995073b8a2..a7a2ee9a51 100644
--- a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
+++ b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
@@ -21,12 +21,12 @@ New programmers often find problem solving the hardest skill to build. It's not
 
 The best way to improve your problem solving ability is by building experience by making lots and lots of programs. The more practice you have the better you'll be prepared to solve real world problems.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Read <a href="https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/" target="_blank">How to Think Like a Programmer - Lessons in Problem Solving</a> by Richard Reis.
 
+# --question--
+
 ## --text--
 
 According to V. Anton Spraul in "Think Like a Programmer," what is problem solving in programming?
diff --git a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
index ae905ecf89..c57a7d43e8 100644
--- a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
+++ b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
@@ -25,11 +25,11 @@ Now that you know what you’re aiming to solve, don’t jump into coding just y
 
 The last question is where you will write out an algorithm to solve the problem. You can think of an algorithm as a recipe for solving a particular problem. It defines the steps that need to be taken by the computer to solve a problem in pseudocode.
 
-# --question--
-
-## --assignment--
+# --assignment--
 Watch <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">How to Begin Thinking Like a Programmer</a> by Coding Tech. It’s an hour long but packed full of information and definitely worth your time watching.
 
+# --question--
+
 ## --text--
 
 What should you do before starting to code according to the provided text?
diff --git a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
index c837fd9658..082f2d51ae 100644
--- a/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
+++ b/curriculum/challenges/chinese-traditional/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
@@ -22,12 +22,12 @@ Print the value of the counter variable
 
 This is a basic program to demonstrate how pseudocode looks. There will be more examples of pseudocode included in the assignments.
 
+# --assignment--
 
-# --question--
-
-## --assignment--
 Read this <a href="https://builtin.com/data-science/pseudocode" target="_blank"> Pseudocode: What It Is and How to Write It</a> article from Built In.
 
+# --question--
+
 ## --text--
 
 What are the benefits of using pseudocode according to the linked article?
diff --git a/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md b/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
index 67cd63830c..9e77d699c7 100644
--- a/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
+++ b/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-So far you have learned how to create questions with the verb to be. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
+So far you have learned how to create questions with the verb `to be`. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
 
 `You are a developer` -> `Are you a developer?`
 
diff --git a/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md b/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
index 544d8f1988..8cd311a518 100644
--- a/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
+++ b/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
@@ -21,7 +21,7 @@ Which sentence is correct for describing one place near you?
 
 ### --feedback--
 
-`There are` is used for plural nouns, and `bank` is singular. You’ll learn about there are in the next few lessons.
+`There are` is used for plural nouns, and `bank` is singular. You’ll learn about `there are` in the next few lessons.
 
 ---
 
diff --git a/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md b/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
index 6526b1e95b..10c0845779 100644
--- a/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
+++ b/curriculum/challenges/chinese-traditional/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
@@ -7,7 +7,7 @@ dashedName: task-112
 
 # --description--
 
-To elaborate a question using `there is` you just need to change the order of the verb to be, like so:
+To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so:
 
 `There is an ATM nearby` -> `Is there an ATM nearby?`
 
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
new file mode 100644
index 0000000000..7d664a8876
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
@@ -0,0 +1,25 @@
+---
+id: 5f1a4ef5d5d6b5ab580fc6ae
+title: Build a Celestial Bodies Database
+challengeType: 13
+url: freeCodeCamp/learn-celestial-bodies-database
+dashedName: lab-celestial-bodies-database
+---
+
+# --description--
+
+For this project, you will build a database of celestial bodies using PostgreSQL.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `universe.sql` file so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `universe.sql`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
new file mode 100644
index 0000000000..9492b82cb4
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
@@ -0,0 +1,611 @@
+---
+id: 5a8b073d06fa14fcfde687aa
+title: Build an Exercise Tracker
+challengeType: 4
+dashedName: build-an-exercise-tracker
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://exercise-tracker.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://exercise-tracker.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+Your responses should have the following structures.
+
+Exercise:
+
+```js
+{
+  username: "fcc_test",
+  description: "test",
+  duration: 60,
+  date: "Mon Jan 01 1990",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+User:
+
+```js
+{
+  username: "fcc_test",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Log:
+
+```js
+{
+  username: "fcc_test",
+  count: 1,
+  _id: "5fb5853f734231456ccb3b05",
+  log: [{
+    description: "test",
+    duration: 60,
+    date: "Mon Jan 01 1990",
+  }]
+}
+```
+
+**Hint:** For the `date` property, the `toDateString` method of the `Date` API can be used to achieve the expected output.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  const url = getUserInput('url');
+  assert(
+    !/.*\/exercise-tracker\.freecodecamp\.rocks/.test(getUserInput('url'))
+  );
+};
+```
+
+You can `POST` to `/api/users` with form data `username` to create a new user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The returned response from `POST /api/users` with form data `username` will be an object with `username` and `_id` properties.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    assert.exists(_id);
+    assert.exists(username);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users` to get a list of all users.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `GET` request to `/api/users` returns an array.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    assert.isArray(users);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Each element in the array returned from `GET /api/users` is an object literal containing a user's `username` and `_id`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    const user = users[0];
+    assert.exists(user);
+    assert.exists(user.username);
+    assert.exists(user._id);
+    assert.isString(user.username);
+    assert.isString(user._id);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can `POST` to `/api/users/:_id/exercises` with form data `description`, `duration`, and optionally `date`. If no date is supplied, the current date will be used.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+  assert.isTrue(addRes.ok);
+  if(!addRes.ok) {
+    throw new Error(`${addRes.status} ${addRes.statusText}`)
+  };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+The response returned from `POST /api/users/:_id/exercises` will be the user object with the exercise fields added.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    if (addRes.ok) {
+      const actual = await addRes.json();
+      assert.deepEqual(actual, expected);
+      assert.isString(actual.description);
+      assert.isNumber(actual.duration);
+      assert.isString(actual.date);
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users/:_id/logs` to retrieve a full exercise log of any user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+    assert.isTrue(logRes.ok);
+    if(!logRes.ok) {
+      throw new Error(`${logRes.status} ${logRes.statusText}`)
+    };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A request to a user's log `GET /api/users/:_id/logs` returns a user object with a `count` property representing the number of exercises that belong to that user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if (logRes.ok) {
+        const { count } = await logRes.json();
+        assert(count);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A `GET` request to `/api/users/:_id/logs` will return the user object with a `log` array of all the exercises added.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  })
+  if(res.ok){
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok){
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+Each item in the `log` array that is returned from `GET /api/users/:_id/logs` is an object that should have a `description`, `duration`, and `date` properties.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + `/api/users`, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+     const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.exists(exercise);
+        assert.exists(exercise.description);
+        assert.exists(exercise.duration);
+        assert.exists(exercise.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `description` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.description);
+        assert.equal(exercise.description, expected.description);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `duration` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a number.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isNumber(exercise.duration);
+        assert.equal(exercise.duration, expected.duration);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `date` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string. Use the `dateString` format of the `Date` API.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toLocaleDateString("en-US", {
+        timeZone: "UTC", weekday: "short", month: "short",
+        day: "2-digit", year: "numeric"
+      }).replaceAll(',', '')
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.date);
+        assert.equal(exercise.date, expected.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can add `from`, `to` and `limit` parameters to a `GET /api/users/:_id/logs` request to retrieve part of the log of any user. `from` and `to` are dates in `yyyy-mm-dd` format. `limit` is an integer of how many logs to send back.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addExerciseRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    const addExerciseTwoRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-03`
+    });
+    if (addExerciseRes.ok && addExerciseTwoRes.ok) {
+      const logRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1989-12-31&to=1990-01-04`
+      );
+      if (logRes.ok) {
+        const { log } = await logRes.json();
+        assert.isArray(log);
+        assert.equal(2, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+      const limitRes = await fetch(
+        url + `/api/users/${_id}/logs?limit=1`
+      );
+      if (limitRes.ok) {
+        const { log } = await limitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${limitRes.status} ${limitRes.statusText}`);
+      }
+      const filterDateBeforeLimitRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1990-01-02&to=1990-01-04&limit=1`
+      );
+      if (filterDateBeforeLimitRes.ok) {
+        const { log } = await filterDateBeforeLimitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${filterDateBeforeLimitRes.status} ${filterDateBeforeLimitRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${res.status} ${res.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
new file mode 100644
index 0000000000..ef87dc6720
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
@@ -0,0 +1,25 @@
+---
+id: 602da04c22201c65d2a019f4
+title: Build a Number Guessing Game
+challengeType: 13
+url: freeCodeCamp/learn-number-guessing-game
+dashedName: lab-number-guessing-game
+---
+
+# --description--
+
+For this lab, you will use Bash scripting, PostgreSQL, and Git to create a number guessing game that runs in the terminal and saves user information.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `number_guess.sql` file, as well as your `number_guess.sh` file, so you can complete step 2. There will be instructions on how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `number_guess.sql`, `number_guess.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
new file mode 100644
index 0000000000..5040e27424
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
@@ -0,0 +1,65 @@
+---
+id: bd7158d8c443edefaeb5bdff
+title: Build a Request Header Parser Microservice
+challengeType: 4
+dashedName: lab-request-header-parser-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://request-header-parser-microservice.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://request-header-parser-microservice.freecodecamp.rocks/</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/request-header-parser-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+A request to `/api/whoami` should return a JSON object with your IP address in the `ipaddress` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.ipaddress && data.ipaddress.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your preferred language in the `language` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.language && data.language.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your software in the `software` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.software && data.software.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
new file mode 100644
index 0000000000..0fbf80a0bf
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
@@ -0,0 +1,107 @@
+---
+id: bd7158d8c443edefaeb5bd0e
+title: URL Shortener Microservice
+challengeType: 4
+dashedName: url-shortener-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://url-shortener-microservice.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://url-shortener-microservice.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+**HINT:** Do not forget to use a body parsing middleware to handle the POST requests. Also, you can use the function `dns.lookup(host, cb)` from the `dns` core module to verify a submitted URL.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/url-shortener-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+You can POST a URL to `/api/shorturl` and get a JSON response with `original_url` and `short_url` properties. Here's an example: `{ original_url : 'https://freeCodeCamp.org', short_url : 1}`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (res.ok) {
+    const { short_url, original_url } = await res.json();
+    assert.isNotNull(short_url);
+    assert.strictEqual(original_url, `${url}/?v=${urlVariable}`);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+When you visit `/api/shorturl/<short_url>`, you will be redirected to the original URL.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  let shortenedUrlVariable;
+  const postResponse = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (postResponse.ok) {
+    const { short_url } = await postResponse.json();
+    shortenedUrlVariable = short_url;
+  } else {
+    throw new Error(`${postResponse.status} ${postResponse.statusText}`);
+  }
+  const getResponse = await fetch(
+    url + '/api/shorturl/' + shortenedUrlVariable
+  );
+  if (getResponse) {
+    const { redirected, url } = getResponse;
+    assert.isTrue(redirected);
+    assert.strictEqual(url,fullUrl);
+  } else {
+    throw new Error(`${getResponse.status} ${getResponse.statusText}`);
+  }
+};
+```
+
+If you pass an invalid URL that doesn't follow the valid `http://www.example.com` format, the JSON response will contain `{ error: 'invalid url' }`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=ftp:/john-doe.invalidTLD`
+  });
+  if (res.ok) {
+    const { error } = await res.json();
+    assert.isNotNull(error);
+    assert.strictEqual(error.toLowerCase(), 'invalid url');
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
new file mode 100644
index 0000000000..d77442a1ba
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
@@ -0,0 +1,25 @@
+---
+id: 5f9771307d4d22b9d2b75a94
+title: Build a World Cup Database
+challengeType: 13
+url: freeCodeCamp/learn-world-cup-database
+dashedName: lab-world-cup-database
+---
+
+# --description--
+
+For this project, you will create a Bash script that enters information from World Cup games into PostgreSQL, then query the database for useful statistics.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `worldcup.sql` file, as well as your `insert_data.sh` and `queries.sh` files, so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `worldcup.sql`, `insert_data.sh`, `queries.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
index 51ea9e3069..753ee1a6bb 100644
--- a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
@@ -7,9 +7,9 @@ dashedName: step-22
 
 # --description--
 
-Add another label with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
+Add another `label` with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
 
-Below the label element, add another checkbox input with the `id`, `name` and `value` attributes set to `"recommendation"`.
+Below the `label` element, add another checkbox `input` with the `id`, `name` and `value` attributes set to `"recommendation"`.
 
 # --hints--
 
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
index 42c425209d..80a23ca86d 100644
--- a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
@@ -11,7 +11,7 @@ Next, add another `label` element with the text of `Location` and the `for` attr
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"location"`.
 
-Below that `input` element, add another `label` element with the text of `Reputation` and the for attribute set to `"reputation"`.
+Below that `input` element, add another `label` element with the text of `Reputation` and the `for` attribute set to `"reputation"`.
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"reputation"`.
 
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
index 69efa4832c..09e3e6e59b 100644
--- a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
@@ -7,7 +7,7 @@ dashedName: step-28
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attributes:**
 
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
index 6549345d45..22b9a707be 100644
--- a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
@@ -7,7 +7,7 @@ dashedName: step-31
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attribute:**
 
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
new file mode 100644
index 0000000000..237515fd88
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
@@ -0,0 +1,71 @@
+---
+id: 66c8ba41a77db20a93f9d7a1
+title: Step 1
+challengeType: 1
+dashedName: step-1
+---
+
+# --description--
+
+In this workshop, you'll review JavaScript conditionals by building a loan qualification checker app.
+
+The app will check whether the user is eligible for a duplex, car, and condo loan based on their annual income and credit score. A credit score is a number that represents how good you are at managing borrowed money.
+
+To get started, create the following variables and values.
+
+| Variable Name             | Value   |
+| ------------------------- | ------- |
+| `minIncomeForDuplex`      | `60000` |
+| `minCreditScoreForDuplex` | `700`   |
+| `minIncomeForCondo`       | `45000` |
+| `minCreditScoreForCondo`  | `680`   |
+| `minIncomeForCar`         | `30000` |
+| `minCreditScoreForCar`    | `650`   |
+
+# --hints--
+
+You should create a `minIncomeForDuplex` variable set to `60000`.
+
+```js
+assert.equal(minIncomeForDuplex, 60000);
+```
+
+You should create a `minCreditScoreForDuplex` set to `700`.
+
+```js
+assert.equal(minCreditScoreForDuplex, 700);
+```
+
+You should create a `minIncomeForCar` variable set to `30000`.
+
+```js
+assert.equal(minIncomeForCar, 30000);
+```
+
+You should create a `minCreditScoreForCar` variable set to `650`.
+
+```js
+assert.equal(minCreditScoreForCar, 650);
+```
+
+You should create a `minIncomeForCondo` variable set to `45000`.
+
+```js
+assert.equal(minIncomeForCondo, 45000);
+```
+
+You should create a `minCreditScoreForCondo` variable set to `680`.
+
+```js
+assert.equal(minCreditScoreForCondo, 680);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
new file mode 100644
index 0000000000..7755f823c4
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
@@ -0,0 +1,53 @@
+---
+id: 66c8ba975ee7230e29f6c4ac
+title: Step 2
+challengeType: 1
+dashedName: step-2
+---
+
+# --description--
+
+When the user is eligible for a loan, you'll want to display a message to them in the console.
+
+For that, you'll build out a function inside which you'll have some checks that'll return what loan the applicant is eligible for.
+
+Create an empty `getLoanMessage` function with an `annualIncome` and `creditScore` parameters.
+
+# --hints--
+
+You should create a `getLoanMessage` function
+
+```js
+assert.isFunction(getLoanMessage)
+```
+
+Your `getLoanMessage` function should have an `annualIncome` and `creditScore` as parameters.
+
+```js
+assert.match(getLoanMessage?.toString(), /\(\s*annualIncome,\s*creditScore\s*\)|\(\s*creditScore,\s*annualIncome\s*\)/);
+```
+
+`getLoanMessage` should be an empty function.
+
+```js
+assert.match(getLoanMessage?.toString(), /\{\s*\}/);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
new file mode 100644
index 0000000000..82a29d7cd9
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
@@ -0,0 +1,55 @@
+---
+id: 66c8ba975ee7230e29f6c4ad
+title: Step 3
+challengeType: 1
+dashedName: step-3
+---
+
+# --description--
+
+To check which loan a user is qualified for based on the `annualIncome` and `creditScore`, you have to use `if/else if` statement or a ternary right inside the `getLoanMessage` function. You'll then return the appropraite message in the block of each condition.
+
+Starting with the duplex loan, check if `annualIncome` is greater than or equal to `minIncomeForDuplex` AND if `creditScore` is greater than `minCreditScoreForDuplex`.
+
+If that condition is true, then the applicant is eligible for a duplex loan and the other loans. So, inside the check, return the string `"You qualify for a car, duplex and Condo loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string.
+
+```js
+assert.isString(getLoanMessage(65000, 750));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a duplex, condo, and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(65000, 750), "You qualify for a duplex, condo, and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a duplex loan.
+
+```js
+assert.strictEqual(getLoanMessage(59000, 700), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+function getLoanMessage(annualIncome, creditScore) {
+
+}
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
new file mode 100644
index 0000000000..638e6291a4
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4af
+title: Step 4
+challengeType: 1
+dashedName: step-4
+---
+
+# --description--
+
+If the applicant's annual income is greater than or equal to `minIncomeForCondo`, AND if their credit score is greater than or equal to `minCreditScoreForCondo`, then they qualify for a condo and car loan.
+
+Check if that's true in the `getLoanMessage` function. If it is, return the string `"You qualify for a condo and car loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a condo and car loan.
+
+```js
+assert.isString(getLoanMessage(45000, 680));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a condo and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 680), "You qualify for a condo and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a condo loan.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 650), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
new file mode 100644
index 0000000000..374ba7b8fe
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4b0
+title: Step 5
+challengeType: 1
+dashedName: step-5
+---
+
+# --description--
+
+Now, you should check if the applicant is qualified for a car loan only. If they're, return the string `"You qualify for a car loan."`.
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a car loan.
+
+```js
+assert.isString(getLoanMessage(30000, 650));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 650), "You qualify for a car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a car loan.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 600), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+--fcc-editable-region--
+  } 
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
new file mode 100644
index 0000000000..16e8c7baca
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
@@ -0,0 +1,54 @@
+---
+id: 66c8ba975ee7230e29f6c4b1
+title: Step 6
+challengeType: 1
+dashedName: step-6
+---
+
+# --description--
+
+If the applicant's annual income and credit score fall below `minIncomeForCar` and `minCreditScoreForCar`, then they don't qualify for any loan. So, return the string `"You don't qualify for any loans."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant doesn't qualify for any loan.
+
+```js
+assert.isString(getLoanMessage(25000, 550));
+```
+
+Your `getLoanMessage` function should return the string `"You don't qualify for any loans."` if the applicant does not meet the requirements for any loan.
+
+```js
+assert.strictEqual(getLoanMessage(15000, 600), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(25000, 550), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(20000, 500), "You don't qualify for any loans.");
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
new file mode 100644
index 0000000000..9d19f9ea4c
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
@@ -0,0 +1,165 @@
+---
+id: 66c8ba975ee7230e29f6c4b2
+title: Step 7
+challengeType: 1
+dashedName: step-7
+---
+
+# --description--
+
+Now, it is time to test out your `getLoanMessage` function.
+
+Use the table below to create `4` variables and their values:
+
+| Variable Name   | Value                        |
+| --------------- | ---------------------------- |
+| `duplexLoanMsg` | `getLoanMessage(85000, 850)` |
+| `condoLoanMsg`  | `getLoanMessage(65000, 690)` |
+| `carLoanMsg`    | `getLoanMessage(45000, 660)` |
+| `noLoanMsg`     | `getLoanMessage(25000, 550)` |
+
+After that, log each variable to the console to see the messages.
+
+With that, your loan qualification checker project is complete!
+
+# --hints--
+
+You should have a variable called `duplexLoanMsg`.
+
+```js
+assert.isNotNull(duplexLoanMsg);
+```
+
+Your `duplexLoanMsg` variable should be set to the result of `getLoanMessage(85000, 850)`.
+
+```js
+assert.equal(duplexLoanMsg, getLoanMessage(85000, 850));
+```
+
+You should log the `duplexLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(duplexLoanMsg\)/)
+```
+
+You should have a variable called `condoLoanMsg`.
+
+```js
+assert.isNotNull(condoLoanMsg);
+```
+
+Your `condoLoanMsg` variable should be set to the result of `getLoanMessage(65000, 690)`.
+
+```js
+assert.equal(condoLoanMsg, getLoanMessage(65000, 690));
+```
+
+You should log the `condoLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(condoLoanMsg\)/)
+```
+
+You should have a variable called `carLoanMsg`.
+
+```js
+assert.isNotNull(carLoanMsg);
+```
+
+Your `carLoanMsg` variable should be set to the result of `getLoanMessage(45000, 660)`.
+
+```js
+assert.equal(carLoanMsg, getLoanMessage(45000, 660));
+```
+
+You should log the `carLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(carLoanMsg\)/)
+```
+
+You should have a variable called `noLoanMsg`.
+
+```js
+assert.isNotNull(noLoanMsg);
+```
+
+Your `noLoanMsg` variable should be set to the result of `getLoanMessage(25000, 550)`.
+
+```js
+assert.equal(noLoanMsg, getLoanMessage(25000, 550));
+```
+
+You should log the `noLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(noLoanMsg\)/)
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
+
+# --solutions--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+const duplexLoanMsg = getLoanMessage(85000, 850)
+console.log(duplexLoanMsg)
+
+const condoLoanMsg = getLoanMessage(65000, 690)
+console.log(condoLoanMsg)
+
+const carLoanMsg = getLoanMessage(45000, 660)
+console.log(carLoanMsg)
+
+const noLoanMsg = getLoanMessage(25000, 550)
+console.log(noLoanMsg)
+```
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
new file mode 100644
index 0000000000..4e11751ca0
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
@@ -0,0 +1,19 @@
+---
+id: 5f2c289f164c29556da632fd
+title: Build a Mario Database
+challengeType: 12
+url: freeCodeCamp/learn-relational-databases-by-building-a-mario-database
+dashedName: build-a-mario-database
+---
+
+# --description--
+
+In this 165-lesson workshop, you will learn the basics of a relational database by creating a PostgreSQL database filled with video game characters.
+
+# --instructions--
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
new file mode 100644
index 0000000000..8d4c90410d
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
@@ -0,0 +1,53 @@
+---
+id: 587d7fb3367417b2b2512bfb
+title: How to Use package.json, the Core of Any Node.js Project or npm Package
+challengeType: 2
+forumTopicId: 301528
+dashedName: how-to-use-package-json-the-core-of-any-node-js-project-or-npm-package
+---
+
+# --description--
+
+Working on these challenges will involve you writing your code using one of the following methods:
+
+- Clone <a href="https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete these challenges locally.
+- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+The `package.json` file is the center of any Node.js project or npm package. It stores information about your project. It consists of a single JSON object where information is stored in key-value pairs. There are only two required fields; `name` and `version`, but it’s good practice to provide additional information.
+
+You can create the `package.json` file from the terminal using the `npm init` command. This will run a guided setup. Using `npm init` with the `-y` flag will generate the file without having it ask any questions, `npm init -y`.
+
+If you look at the file tree of your project, you will find the `package.json` file on the top level of the tree. This is the file that you will be improving in the next couple of challenges.
+
+One of the most common pieces of information in this file is the `author` field. It specifies who created the project, and can consist of a string or an object with contact or other details. An object is recommended for bigger projects, but a simple string like the following example will do for this project.
+
+```json
+"author": "Jane Doe",
+```
+
+# --instructions--
+
+Add your name as the `author` of the project in the `package.json` file.
+
+**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (") and be separated with a comma (,).
+
+If you are using Gitpod, make sure the app is running and the preview window is open. Copy the preview window's URL and paste it into the Solution Link input below.
+
+# --hints--
+
+`package.json` should have a valid "author" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.author, '"author" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
new file mode 100644
index 0000000000..37d15d5261
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb3367417b2b2512bfc
+title: Add a Description to Your package.json
+challengeType: 2
+forumTopicId: 301522
+dashedName: add-a-description-to-your-package-json
+---
+
+# --description--
+
+The next part of a good package.json file is the `description` field; where a short, but informative description about your project belongs.
+
+If some day you plan to publish a package to npm, this is the string that should sell your idea to the user when they decide whether to install your package or not. However, that’s not the only use case for the description, it’s a great way to summarize what a project does. It’s just as important in any Node.js project to help other developers, future maintainers or even your future self understand the project quickly.
+
+Regardless of what you plan for your project, a description is definitely recommended. Here's an example:
+
+```json
+"description": "A project that does something awesome",
+```
+
+# --instructions--
+
+Add a `description` to the package.json file of your project.
+
+**Note:** Remember to use double-quotes for field-names (") and commas (,) to separate fields.
+
+# --hints--
+
+package.json should have a valid "description" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.description, '"description" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
new file mode 100644
index 0000000000..a001cdd477
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
@@ -0,0 +1,75 @@
+---
+id: 587d7fb4367417b2b2512bfd
+title: Add Keywords to Your package.json
+challengeType: 2
+forumTopicId: 301526
+dashedName: add-keywords-to-your-package-json
+---
+
+# --description--
+
+The `keywords` field is where you can describe your project using related keywords. Here's an example:
+
+```json
+"keywords": [ "descriptive", "related", "words" ],
+```
+
+As you can see, this field is structured as an array of double-quoted strings.
+
+# --instructions--
+
+Add an array of suitable strings to the `keywords` field in the package.json file of your project.
+
+One of the keywords should be "freecodecamp".
+
+# --hints--
+
+package.json should have a valid "keywords" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.keywords, '"keywords" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" field should be an Array
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.isArray(packJson.keywords, '"keywords" is not an array');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" should include "freecodecamp"
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.include(
+        packJson.keywords,
+        'freecodecamp',
+        '"keywords" does not include "freecodecamp"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
new file mode 100644
index 0000000000..7b09acd042
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
@@ -0,0 +1,39 @@
+---
+id: 587d7fb4367417b2b2512bfe
+title: Add a License to Your package.json
+challengeType: 2
+forumTopicId: 301523
+dashedName: add-a-license-to-your-package-json
+---
+
+# --description--
+
+The `license` field is where you inform users of what they are allowed to do with your project.
+
+Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do. Here's an example of the license field:
+
+```json
+"license": "MIT",
+```
+
+# --instructions--
+
+Fill the `license` field in the package.json file of your project as you find suitable.
+
+# --hints--
+
+package.json should have a valid "license" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.license, '"license" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
new file mode 100644
index 0000000000..f2e571faed
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
@@ -0,0 +1,37 @@
+---
+id: 587d7fb4367417b2b2512bff
+title: Add a Version to Your package.json
+challengeType: 2
+forumTopicId: 301525
+dashedName: add-a-version-to-your-package-json
+---
+
+# --description--
+
+A `version` is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example:
+
+```json
+"version": "1.2.0",
+```
+
+# --instructions--
+
+Add a `version` to the package.json file of your project.
+
+# --hints--
+
+package.json should have a valid "version" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.version, '"version" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
new file mode 100644
index 0000000000..161c60fe69
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
@@ -0,0 +1,68 @@
+---
+id: 587d7fb4367417b2b2512c00
+title: Expand Your Project with External Packages from npm
+challengeType: 2
+forumTopicId: 301527
+dashedName: expand-your-project-with-external-packages-from-npm
+---
+
+# --description--
+
+One of the biggest reasons to use a package manager, is their powerful dependency management. Instead of manually having to make sure that you get all dependencies whenever you set up a project on a new computer, npm automatically installs everything for you. But how can npm know exactly what your project needs? Meet the `dependencies` section of your package.json file.
+
+In this section, packages your project requires are stored using the following format:
+
+```json
+"dependencies": {
+  "package-name": "version",
+  "express": "4.14.0"
+}
+
+```
+
+# --instructions--
+
+Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file.
+
+**Note:** `@freecodecamp/example` is a faux package used as a learning tool.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.1.0"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^[\^\~]?1\.1\.0/,
+        'Wrong version of "@freecodecamp/example" installed. It should be 1.1.0'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
new file mode 100644
index 0000000000..deda9b82de
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
@@ -0,0 +1,64 @@
+---
+id: 587d7fb5367417b2b2512c01
+title: Manage npm Dependencies By Understanding Semantic Versioning
+challengeType: 2
+forumTopicId: 301529
+dashedName: manage-npm-dependencies-by-understanding-semantic-versioning
+---
+
+# --description--
+
+`Versions` of the npm packages in the dependencies section of your package.json file follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes projects can expect if they update.
+
+Knowing SemVer can be useful when you develop software that uses external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things that worked yesterday suddenly don’t work today. This is how Semantic Versioning works according to the official website:
+
+```json
+"package": "MAJOR.MINOR.PATCH"
+```
+
+The MAJOR version should increment when you make incompatible API changes. The MINOR version should increment when you add functionality in a backwards-compatible manner. The PATCH version should increment when you make backwards-compatible bug fixes. This means that PATCHes are bug fixes and MINORs add new features but neither of them break what worked before. Finally, MAJORs add changes that won’t work with earlier versions.
+
+# --instructions--
+
+In the dependencies section of your `package.json` file, change the version of `@freecodecamp/example` to match MAJOR version 1, MINOR version 2 and PATCH version 13
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.equal(
+        packJson.dependencies["@freecodecamp/example"],
+        '1.2.13',
+        'Wrong version of "@freecodecamp/example". It should be 1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
new file mode 100644
index 0000000000..8eae5f51ee
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c02
+title: Use the Tilde-Character to Always Use the Latest Patch Version of a Dependency
+challengeType: 2
+forumTopicId: 301532
+dashedName: use-the-tilde-character-to-always-use-the-latest-patch-version-of-a-dependency
+---
+
+# --description--
+
+In the last challenge, you told npm to only include a specific version of a package. That’s a useful way to freeze your dependencies if you need to make sure that different parts of your project stay compatible with each other. But in most use cases, you don’t want to miss bug fixes since they often include important security patches and (hopefully) don’t break things in doing so.
+
+To allow an npm dependency to update to the latest PATCH version, you can prefix the dependency’s version with the tilde (`~`) character. Here's an example of how to allow updates to any `1.3.x` version.
+
+```json
+"package": "~1.3.8"
+```
+
+# --instructions--
+
+In the package.json file, your current rule for how npm may upgrade `@freecodecamp/example` is to use a specific version (`1.2.13`). But now, you want to allow the latest `1.2.x` version.
+
+Use the tilde (`~`) character to prefix the version of `@freecodecamp/example` in your dependencies, and allow npm to update it to any new _patch_ release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"~1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\~1\.2\.13/,
+        'Wrong version of "@freecodecamp/example". It should be ~1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
new file mode 100644
index 0000000000..adc3014ea4
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c03
+title: Use the Caret-Character to Use the Latest Minor Version of a Dependency
+challengeType: 2
+forumTopicId: 301531
+dashedName: use-the-caret-character-to-use-the-latest-minor-version-of-a-dependency
+---
+
+# --description--
+
+Similar to how the tilde we learned about in the last challenge allows npm to install the latest PATCH for a dependency, the caret (`^`) allows npm to install future updates as well. The difference is that the caret will allow both MINOR updates and PATCHes.
+
+Your current version of `@freecodecamp/example` should be `~1.2.13` which allows npm to install to the latest `1.2.x` version. If you were to use the caret (^) as a version prefix instead, npm would be allowed to update to any `1.x.x` version.
+
+```json
+"package": "^1.3.8"
+```
+
+This would allow updates to any `1.x.x` version of the package.
+
+# --instructions--
+
+Use the caret (`^`) to prefix the version of `@freecodecamp/example` in your dependencies and allow npm to update it to any new MINOR release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"^1.x.x"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\^1\./,
+        'Wrong version of "@freecodecamp/example". It should be ^1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
new file mode 100644
index 0000000000..5f695eed88
--- /dev/null
+++ b/curriculum/challenges/chinese-traditional/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb5367417b2b2512c04
+title: Remove a Package from Your Dependencies
+challengeType: 2
+forumTopicId: 301530
+dashedName: remove-a-package-from-your-dependencies
+---
+
+# --description--
+
+You have now tested a few ways you can manage dependencies of your project by using the package.json's dependencies section. You have also included external packages by adding them to the file and even told npm what types of versions you want, by using special characters such as the tilde or the caret.
+
+But what if you want to remove an external package that you no longer need? You might already have guessed it, just remove the corresponding key-value pair for that package from your dependencies.
+
+This same method applies to removing other fields in your package.json as well.
+
+# --instructions--
+
+Remove the `@freecodecamp/example` package from your dependencies.
+
+**Note:** Make sure you have the right amount of commas after removing it.
+
+# --hints--
+
+`"dependencies"` should not include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.notProperty(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" still includes "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md b/curriculum/challenges/chinese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
index f5853c146e..50262f5248 100644
--- a/curriculum/challenges/chinese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
+++ b/curriculum/challenges/chinese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
@@ -8,7 +8,7 @@ dashedName: build-a-periodic-table-database
 
 # --description--
 
-这是你获得认证的必做项目之一。 对于此项目，你将创建 Bash 脚本以从元素周期表数据库中获取有关化学元素的信息。
+这是你获得认证的必做项目之一。 For this project, you will create a Bash script to get information about chemical elements from a periodic table database.
 
 # --instructions--
 
diff --git a/curriculum/challenges/chinese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md b/curriculum/challenges/chinese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
index e56eff5b06..548bc0088b 100644
--- a/curriculum/challenges/chinese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
+++ b/curriculum/challenges/chinese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
@@ -9,6 +9,8 @@ dashedName: step-64
 
 在 `footer` 中，添加一个 `p` 元素。 然后，在 `p` 中嵌套一个锚（`a`）元素，链接到 `https://www.freecodecamp.org`，并有文字 `Visit our website`。
 
+Make sure that the link opens in a new tab by adding a `target` attribute with the value `_blank`.
+
 # --hints--
 
 你不应该修改现有的 `footer` 元素。
@@ -43,6 +45,12 @@ assert(document.querySelector("footer > p > a")?.innerText === "Visit our websit
 assert(document.querySelector("footer > p > a")?.href === "https://www.freecodecamp.org/");
 ```
 
+Your new `a` element should have the `target` attribute set to `_blank`.
+
+```js
+assert.equal(document.querySelector("footer > p > a")?.target, "_blank");
+```
+
 # --seed--
 
 ## --seed-contents--
diff --git a/curriculum/challenges/chinese/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md b/curriculum/challenges/chinese/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md
index 7e2d7fc923..f87325c93b 100644
--- a/curriculum/challenges/chinese/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md
+++ b/curriculum/challenges/chinese/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md
@@ -7,7 +7,7 @@ dashedName: step-47
 
 # --description--
 
-Move the right eye into position with a `position` property of `absolute`, a `top` of `54px`, and a `left` of `134px`.
+将右眼移动到位，其 `position` 属性为 `absolute`，`top` 为 `54px`，`left` 为 `134px`。
 
 # --hints--
 
diff --git a/curriculum/challenges/chinese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md b/curriculum/challenges/chinese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
index d2ad72a1ea..1b6ca05444 100644
--- a/curriculum/challenges/chinese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
+++ b/curriculum/challenges/chinese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
@@ -21,12 +21,12 @@ Remove `flex: 1` from `.item` and add `justify-content: space-between` to `.cont
 
 `justify-content` aligns items across the **main axis**. There are a few values that you can use here. You'll learn the rest of them in the reading assignments, but for now try changing it to center, which should center the boxes along the main axis.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see what is possible with the `justify-content` property. Read this [interactive article on MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) and play around with the different values of `justify-content` on the example.
 
+# --question--
+
 ## --text--
 
 How does applying `justify-content: space-between` to a flex container affect the positioning of its items?
diff --git a/curriculum/challenges/chinese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md b/curriculum/challenges/chinese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
index d3137b0af5..59acb55a29 100644
--- a/curriculum/challenges/chinese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
+++ b/curriculum/challenges/chinese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
@@ -17,12 +17,12 @@ To change the placement of items along the cross axis use `align-items`. Try get
 
 Because `justify-content` and `align-items` are based on the main and cross axis of your container, their behavior changes when you change the flex-direction of a flex-container. For example, when you change `flex-direction` to `column`, `justify-content` aligns vertically and `align-items` aligns horizontally. The most common behavior, however, is the default, i.e. `justify-content` aligns items horizontally (because the main axis defaults to horizontal), and `align-items` aligns them vertically. One of the biggest sticking points that beginners have with flexbox is confusion when this behavior changes.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see if you can figure out how `align-items` behaves when you change the `flex-direction` property to `column`.
 
+# --question--
+
 ## --text--
 
 When changing the `flex-direction` property to `column` in a flex container, how does `align-items` behave in relation to the flex items?
diff --git a/curriculum/challenges/chinese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md b/curriculum/challenges/chinese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
index 1adf9ce84f..49edeac0e4 100644
--- a/curriculum/challenges/chinese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
+++ b/curriculum/challenges/chinese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
@@ -9,12 +9,12 @@ dashedName: learn-block-and-inline-lesson-b
 
 Inline elements, however, do not start on a new line. They appear in line with whatever elements they are placed beside. A clear example of an inline element is a link, or `<a>` tag. If you stick one of these in the middle of a paragraph of text, it will behave like a part of the paragraph. <a  href="https://www.freecodecamp.org/" target="_blank">(Like this)</a> The link’s text will sit alongside other words in that paragraph. Additionally, padding and margin behave differently on inline elements. In general, you do not want to try to put extra padding or margin on inline elements.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Search the web for a list of `block` elements and a list of `inline` elements.
 
+# --question--
+
 ## --text--
 
 What is the difference between a `block` element and an `inline` element?
diff --git a/curriculum/challenges/chinese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md b/curriculum/challenges/chinese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
index cdd4d5aa87..e75492e9c1 100644
--- a/curriculum/challenges/chinese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
+++ b/curriculum/challenges/chinese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-block-and-inline-lesson-g
 
 # --description--
 
-Now that you have some basic understanding of `block` and inline `elements`, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
+Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
 
 # --question--
 
diff --git a/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md b/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
index 995073b8a2..a7a2ee9a51 100644
--- a/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
+++ b/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
@@ -21,12 +21,12 @@ New programmers often find problem solving the hardest skill to build. It's not
 
 The best way to improve your problem solving ability is by building experience by making lots and lots of programs. The more practice you have the better you'll be prepared to solve real world problems.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Read <a href="https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/" target="_blank">How to Think Like a Programmer - Lessons in Problem Solving</a> by Richard Reis.
 
+# --question--
+
 ## --text--
 
 According to V. Anton Spraul in "Think Like a Programmer," what is problem solving in programming?
diff --git a/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md b/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
index ae905ecf89..c57a7d43e8 100644
--- a/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
+++ b/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
@@ -25,11 +25,11 @@ Now that you know what you’re aiming to solve, don’t jump into coding just y
 
 The last question is where you will write out an algorithm to solve the problem. You can think of an algorithm as a recipe for solving a particular problem. It defines the steps that need to be taken by the computer to solve a problem in pseudocode.
 
-# --question--
-
-## --assignment--
+# --assignment--
 Watch <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">How to Begin Thinking Like a Programmer</a> by Coding Tech. It’s an hour long but packed full of information and definitely worth your time watching.
 
+# --question--
+
 ## --text--
 
 What should you do before starting to code according to the provided text?
diff --git a/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md b/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
index c837fd9658..082f2d51ae 100644
--- a/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
+++ b/curriculum/challenges/chinese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
@@ -22,12 +22,12 @@ Print the value of the counter variable
 
 This is a basic program to demonstrate how pseudocode looks. There will be more examples of pseudocode included in the assignments.
 
+# --assignment--
 
-# --question--
-
-## --assignment--
 Read this <a href="https://builtin.com/data-science/pseudocode" target="_blank"> Pseudocode: What It Is and How to Write It</a> article from Built In.
 
+# --question--
+
 ## --text--
 
 What are the benefits of using pseudocode according to the linked article?
diff --git a/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md b/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
index 67cd63830c..9e77d699c7 100644
--- a/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
+++ b/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-So far you have learned how to create questions with the verb to be. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
+So far you have learned how to create questions with the verb `to be`. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
 
 `You are a developer` -> `Are you a developer?`
 
diff --git a/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md b/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
index 544d8f1988..8cd311a518 100644
--- a/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
+++ b/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
@@ -21,7 +21,7 @@ Which sentence is correct for describing one place near you?
 
 ### --feedback--
 
-`There are` is used for plural nouns, and `bank` is singular. You’ll learn about there are in the next few lessons.
+`There are` is used for plural nouns, and `bank` is singular. You’ll learn about `there are` in the next few lessons.
 
 ---
 
diff --git a/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md b/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
index 6526b1e95b..10c0845779 100644
--- a/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
+++ b/curriculum/challenges/chinese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
@@ -7,7 +7,7 @@ dashedName: task-112
 
 # --description--
 
-To elaborate a question using `there is` you just need to change the order of the verb to be, like so:
+To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so:
 
 `There is an ATM nearby` -> `Is there an ATM nearby?`
 
diff --git a/curriculum/challenges/chinese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md b/curriculum/challenges/chinese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
new file mode 100644
index 0000000000..7d664a8876
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
@@ -0,0 +1,25 @@
+---
+id: 5f1a4ef5d5d6b5ab580fc6ae
+title: Build a Celestial Bodies Database
+challengeType: 13
+url: freeCodeCamp/learn-celestial-bodies-database
+dashedName: lab-celestial-bodies-database
+---
+
+# --description--
+
+For this project, you will build a database of celestial bodies using PostgreSQL.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `universe.sql` file so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `universe.sql`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/chinese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md b/curriculum/challenges/chinese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
new file mode 100644
index 0000000000..9492b82cb4
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
@@ -0,0 +1,611 @@
+---
+id: 5a8b073d06fa14fcfde687aa
+title: Build an Exercise Tracker
+challengeType: 4
+dashedName: build-an-exercise-tracker
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://exercise-tracker.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://exercise-tracker.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+Your responses should have the following structures.
+
+Exercise:
+
+```js
+{
+  username: "fcc_test",
+  description: "test",
+  duration: 60,
+  date: "Mon Jan 01 1990",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+User:
+
+```js
+{
+  username: "fcc_test",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Log:
+
+```js
+{
+  username: "fcc_test",
+  count: 1,
+  _id: "5fb5853f734231456ccb3b05",
+  log: [{
+    description: "test",
+    duration: 60,
+    date: "Mon Jan 01 1990",
+  }]
+}
+```
+
+**Hint:** For the `date` property, the `toDateString` method of the `Date` API can be used to achieve the expected output.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  const url = getUserInput('url');
+  assert(
+    !/.*\/exercise-tracker\.freecodecamp\.rocks/.test(getUserInput('url'))
+  );
+};
+```
+
+You can `POST` to `/api/users` with form data `username` to create a new user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The returned response from `POST /api/users` with form data `username` will be an object with `username` and `_id` properties.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    assert.exists(_id);
+    assert.exists(username);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users` to get a list of all users.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `GET` request to `/api/users` returns an array.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    assert.isArray(users);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Each element in the array returned from `GET /api/users` is an object literal containing a user's `username` and `_id`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    const user = users[0];
+    assert.exists(user);
+    assert.exists(user.username);
+    assert.exists(user._id);
+    assert.isString(user.username);
+    assert.isString(user._id);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can `POST` to `/api/users/:_id/exercises` with form data `description`, `duration`, and optionally `date`. If no date is supplied, the current date will be used.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+  assert.isTrue(addRes.ok);
+  if(!addRes.ok) {
+    throw new Error(`${addRes.status} ${addRes.statusText}`)
+  };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+The response returned from `POST /api/users/:_id/exercises` will be the user object with the exercise fields added.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    if (addRes.ok) {
+      const actual = await addRes.json();
+      assert.deepEqual(actual, expected);
+      assert.isString(actual.description);
+      assert.isNumber(actual.duration);
+      assert.isString(actual.date);
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users/:_id/logs` to retrieve a full exercise log of any user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+    assert.isTrue(logRes.ok);
+    if(!logRes.ok) {
+      throw new Error(`${logRes.status} ${logRes.statusText}`)
+    };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A request to a user's log `GET /api/users/:_id/logs` returns a user object with a `count` property representing the number of exercises that belong to that user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if (logRes.ok) {
+        const { count } = await logRes.json();
+        assert(count);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A `GET` request to `/api/users/:_id/logs` will return the user object with a `log` array of all the exercises added.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  })
+  if(res.ok){
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok){
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+Each item in the `log` array that is returned from `GET /api/users/:_id/logs` is an object that should have a `description`, `duration`, and `date` properties.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + `/api/users`, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+     const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.exists(exercise);
+        assert.exists(exercise.description);
+        assert.exists(exercise.duration);
+        assert.exists(exercise.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `description` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.description);
+        assert.equal(exercise.description, expected.description);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `duration` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a number.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isNumber(exercise.duration);
+        assert.equal(exercise.duration, expected.duration);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `date` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string. Use the `dateString` format of the `Date` API.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toLocaleDateString("en-US", {
+        timeZone: "UTC", weekday: "short", month: "short",
+        day: "2-digit", year: "numeric"
+      }).replaceAll(',', '')
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.date);
+        assert.equal(exercise.date, expected.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can add `from`, `to` and `limit` parameters to a `GET /api/users/:_id/logs` request to retrieve part of the log of any user. `from` and `to` are dates in `yyyy-mm-dd` format. `limit` is an integer of how many logs to send back.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addExerciseRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    const addExerciseTwoRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-03`
+    });
+    if (addExerciseRes.ok && addExerciseTwoRes.ok) {
+      const logRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1989-12-31&to=1990-01-04`
+      );
+      if (logRes.ok) {
+        const { log } = await logRes.json();
+        assert.isArray(log);
+        assert.equal(2, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+      const limitRes = await fetch(
+        url + `/api/users/${_id}/logs?limit=1`
+      );
+      if (limitRes.ok) {
+        const { log } = await limitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${limitRes.status} ${limitRes.statusText}`);
+      }
+      const filterDateBeforeLimitRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1990-01-02&to=1990-01-04&limit=1`
+      );
+      if (filterDateBeforeLimitRes.ok) {
+        const { log } = await filterDateBeforeLimitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${filterDateBeforeLimitRes.status} ${filterDateBeforeLimitRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${res.status} ${res.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
diff --git a/curriculum/challenges/chinese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md b/curriculum/challenges/chinese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
new file mode 100644
index 0000000000..ef87dc6720
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
@@ -0,0 +1,25 @@
+---
+id: 602da04c22201c65d2a019f4
+title: Build a Number Guessing Game
+challengeType: 13
+url: freeCodeCamp/learn-number-guessing-game
+dashedName: lab-number-guessing-game
+---
+
+# --description--
+
+For this lab, you will use Bash scripting, PostgreSQL, and Git to create a number guessing game that runs in the terminal and saves user information.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `number_guess.sql` file, as well as your `number_guess.sh` file, so you can complete step 2. There will be instructions on how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `number_guess.sql`, `number_guess.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/chinese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md b/curriculum/challenges/chinese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
new file mode 100644
index 0000000000..5040e27424
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
@@ -0,0 +1,65 @@
+---
+id: bd7158d8c443edefaeb5bdff
+title: Build a Request Header Parser Microservice
+challengeType: 4
+dashedName: lab-request-header-parser-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://request-header-parser-microservice.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://request-header-parser-microservice.freecodecamp.rocks/</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/request-header-parser-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+A request to `/api/whoami` should return a JSON object with your IP address in the `ipaddress` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.ipaddress && data.ipaddress.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your preferred language in the `language` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.language && data.language.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your software in the `software` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.software && data.software.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md b/curriculum/challenges/chinese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
new file mode 100644
index 0000000000..0fbf80a0bf
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
@@ -0,0 +1,107 @@
+---
+id: bd7158d8c443edefaeb5bd0e
+title: URL Shortener Microservice
+challengeType: 4
+dashedName: url-shortener-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://url-shortener-microservice.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://url-shortener-microservice.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+**HINT:** Do not forget to use a body parsing middleware to handle the POST requests. Also, you can use the function `dns.lookup(host, cb)` from the `dns` core module to verify a submitted URL.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/url-shortener-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+You can POST a URL to `/api/shorturl` and get a JSON response with `original_url` and `short_url` properties. Here's an example: `{ original_url : 'https://freeCodeCamp.org', short_url : 1}`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (res.ok) {
+    const { short_url, original_url } = await res.json();
+    assert.isNotNull(short_url);
+    assert.strictEqual(original_url, `${url}/?v=${urlVariable}`);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+When you visit `/api/shorturl/<short_url>`, you will be redirected to the original URL.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  let shortenedUrlVariable;
+  const postResponse = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (postResponse.ok) {
+    const { short_url } = await postResponse.json();
+    shortenedUrlVariable = short_url;
+  } else {
+    throw new Error(`${postResponse.status} ${postResponse.statusText}`);
+  }
+  const getResponse = await fetch(
+    url + '/api/shorturl/' + shortenedUrlVariable
+  );
+  if (getResponse) {
+    const { redirected, url } = getResponse;
+    assert.isTrue(redirected);
+    assert.strictEqual(url,fullUrl);
+  } else {
+    throw new Error(`${getResponse.status} ${getResponse.statusText}`);
+  }
+};
+```
+
+If you pass an invalid URL that doesn't follow the valid `http://www.example.com` format, the JSON response will contain `{ error: 'invalid url' }`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=ftp:/john-doe.invalidTLD`
+  });
+  if (res.ok) {
+    const { error } = await res.json();
+    assert.isNotNull(error);
+    assert.strictEqual(error.toLowerCase(), 'invalid url');
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
diff --git a/curriculum/challenges/chinese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md b/curriculum/challenges/chinese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
new file mode 100644
index 0000000000..d77442a1ba
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
@@ -0,0 +1,25 @@
+---
+id: 5f9771307d4d22b9d2b75a94
+title: Build a World Cup Database
+challengeType: 13
+url: freeCodeCamp/learn-world-cup-database
+dashedName: lab-world-cup-database
+---
+
+# --description--
+
+For this project, you will create a Bash script that enters information from World Cup games into PostgreSQL, then query the database for useful statistics.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `worldcup.sql` file, as well as your `insert_data.sh` and `queries.sh` files, so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `worldcup.sql`, `insert_data.sh`, `queries.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md b/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
index 51ea9e3069..753ee1a6bb 100644
--- a/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
@@ -7,9 +7,9 @@ dashedName: step-22
 
 # --description--
 
-Add another label with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
+Add another `label` with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
 
-Below the label element, add another checkbox input with the `id`, `name` and `value` attributes set to `"recommendation"`.
+Below the `label` element, add another checkbox `input` with the `id`, `name` and `value` attributes set to `"recommendation"`.
 
 # --hints--
 
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md b/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
index 42c425209d..80a23ca86d 100644
--- a/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
@@ -11,7 +11,7 @@ Next, add another `label` element with the text of `Location` and the `for` attr
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"location"`.
 
-Below that `input` element, add another `label` element with the text of `Reputation` and the for attribute set to `"reputation"`.
+Below that `input` element, add another `label` element with the text of `Reputation` and the `for` attribute set to `"reputation"`.
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"reputation"`.
 
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md b/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
index 69efa4832c..09e3e6e59b 100644
--- a/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
@@ -7,7 +7,7 @@ dashedName: step-28
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attributes:**
 
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md b/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
index 6549345d45..22b9a707be 100644
--- a/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
@@ -7,7 +7,7 @@ dashedName: step-31
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attribute:**
 
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
new file mode 100644
index 0000000000..237515fd88
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
@@ -0,0 +1,71 @@
+---
+id: 66c8ba41a77db20a93f9d7a1
+title: Step 1
+challengeType: 1
+dashedName: step-1
+---
+
+# --description--
+
+In this workshop, you'll review JavaScript conditionals by building a loan qualification checker app.
+
+The app will check whether the user is eligible for a duplex, car, and condo loan based on their annual income and credit score. A credit score is a number that represents how good you are at managing borrowed money.
+
+To get started, create the following variables and values.
+
+| Variable Name             | Value   |
+| ------------------------- | ------- |
+| `minIncomeForDuplex`      | `60000` |
+| `minCreditScoreForDuplex` | `700`   |
+| `minIncomeForCondo`       | `45000` |
+| `minCreditScoreForCondo`  | `680`   |
+| `minIncomeForCar`         | `30000` |
+| `minCreditScoreForCar`    | `650`   |
+
+# --hints--
+
+You should create a `minIncomeForDuplex` variable set to `60000`.
+
+```js
+assert.equal(minIncomeForDuplex, 60000);
+```
+
+You should create a `minCreditScoreForDuplex` set to `700`.
+
+```js
+assert.equal(minCreditScoreForDuplex, 700);
+```
+
+You should create a `minIncomeForCar` variable set to `30000`.
+
+```js
+assert.equal(minIncomeForCar, 30000);
+```
+
+You should create a `minCreditScoreForCar` variable set to `650`.
+
+```js
+assert.equal(minCreditScoreForCar, 650);
+```
+
+You should create a `minIncomeForCondo` variable set to `45000`.
+
+```js
+assert.equal(minIncomeForCondo, 45000);
+```
+
+You should create a `minCreditScoreForCondo` variable set to `680`.
+
+```js
+assert.equal(minCreditScoreForCondo, 680);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
new file mode 100644
index 0000000000..7755f823c4
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
@@ -0,0 +1,53 @@
+---
+id: 66c8ba975ee7230e29f6c4ac
+title: Step 2
+challengeType: 1
+dashedName: step-2
+---
+
+# --description--
+
+When the user is eligible for a loan, you'll want to display a message to them in the console.
+
+For that, you'll build out a function inside which you'll have some checks that'll return what loan the applicant is eligible for.
+
+Create an empty `getLoanMessage` function with an `annualIncome` and `creditScore` parameters.
+
+# --hints--
+
+You should create a `getLoanMessage` function
+
+```js
+assert.isFunction(getLoanMessage)
+```
+
+Your `getLoanMessage` function should have an `annualIncome` and `creditScore` as parameters.
+
+```js
+assert.match(getLoanMessage?.toString(), /\(\s*annualIncome,\s*creditScore\s*\)|\(\s*creditScore,\s*annualIncome\s*\)/);
+```
+
+`getLoanMessage` should be an empty function.
+
+```js
+assert.match(getLoanMessage?.toString(), /\{\s*\}/);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
new file mode 100644
index 0000000000..82a29d7cd9
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
@@ -0,0 +1,55 @@
+---
+id: 66c8ba975ee7230e29f6c4ad
+title: Step 3
+challengeType: 1
+dashedName: step-3
+---
+
+# --description--
+
+To check which loan a user is qualified for based on the `annualIncome` and `creditScore`, you have to use `if/else if` statement or a ternary right inside the `getLoanMessage` function. You'll then return the appropraite message in the block of each condition.
+
+Starting with the duplex loan, check if `annualIncome` is greater than or equal to `minIncomeForDuplex` AND if `creditScore` is greater than `minCreditScoreForDuplex`.
+
+If that condition is true, then the applicant is eligible for a duplex loan and the other loans. So, inside the check, return the string `"You qualify for a car, duplex and Condo loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string.
+
+```js
+assert.isString(getLoanMessage(65000, 750));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a duplex, condo, and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(65000, 750), "You qualify for a duplex, condo, and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a duplex loan.
+
+```js
+assert.strictEqual(getLoanMessage(59000, 700), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+function getLoanMessage(annualIncome, creditScore) {
+
+}
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
new file mode 100644
index 0000000000..638e6291a4
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4af
+title: Step 4
+challengeType: 1
+dashedName: step-4
+---
+
+# --description--
+
+If the applicant's annual income is greater than or equal to `minIncomeForCondo`, AND if their credit score is greater than or equal to `minCreditScoreForCondo`, then they qualify for a condo and car loan.
+
+Check if that's true in the `getLoanMessage` function. If it is, return the string `"You qualify for a condo and car loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a condo and car loan.
+
+```js
+assert.isString(getLoanMessage(45000, 680));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a condo and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 680), "You qualify for a condo and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a condo loan.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 650), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
new file mode 100644
index 0000000000..374ba7b8fe
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4b0
+title: Step 5
+challengeType: 1
+dashedName: step-5
+---
+
+# --description--
+
+Now, you should check if the applicant is qualified for a car loan only. If they're, return the string `"You qualify for a car loan."`.
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a car loan.
+
+```js
+assert.isString(getLoanMessage(30000, 650));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 650), "You qualify for a car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a car loan.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 600), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+--fcc-editable-region--
+  } 
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
new file mode 100644
index 0000000000..16e8c7baca
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
@@ -0,0 +1,54 @@
+---
+id: 66c8ba975ee7230e29f6c4b1
+title: Step 6
+challengeType: 1
+dashedName: step-6
+---
+
+# --description--
+
+If the applicant's annual income and credit score fall below `minIncomeForCar` and `minCreditScoreForCar`, then they don't qualify for any loan. So, return the string `"You don't qualify for any loans."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant doesn't qualify for any loan.
+
+```js
+assert.isString(getLoanMessage(25000, 550));
+```
+
+Your `getLoanMessage` function should return the string `"You don't qualify for any loans."` if the applicant does not meet the requirements for any loan.
+
+```js
+assert.strictEqual(getLoanMessage(15000, 600), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(25000, 550), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(20000, 500), "You don't qualify for any loans.");
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
new file mode 100644
index 0000000000..9d19f9ea4c
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
@@ -0,0 +1,165 @@
+---
+id: 66c8ba975ee7230e29f6c4b2
+title: Step 7
+challengeType: 1
+dashedName: step-7
+---
+
+# --description--
+
+Now, it is time to test out your `getLoanMessage` function.
+
+Use the table below to create `4` variables and their values:
+
+| Variable Name   | Value                        |
+| --------------- | ---------------------------- |
+| `duplexLoanMsg` | `getLoanMessage(85000, 850)` |
+| `condoLoanMsg`  | `getLoanMessage(65000, 690)` |
+| `carLoanMsg`    | `getLoanMessage(45000, 660)` |
+| `noLoanMsg`     | `getLoanMessage(25000, 550)` |
+
+After that, log each variable to the console to see the messages.
+
+With that, your loan qualification checker project is complete!
+
+# --hints--
+
+You should have a variable called `duplexLoanMsg`.
+
+```js
+assert.isNotNull(duplexLoanMsg);
+```
+
+Your `duplexLoanMsg` variable should be set to the result of `getLoanMessage(85000, 850)`.
+
+```js
+assert.equal(duplexLoanMsg, getLoanMessage(85000, 850));
+```
+
+You should log the `duplexLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(duplexLoanMsg\)/)
+```
+
+You should have a variable called `condoLoanMsg`.
+
+```js
+assert.isNotNull(condoLoanMsg);
+```
+
+Your `condoLoanMsg` variable should be set to the result of `getLoanMessage(65000, 690)`.
+
+```js
+assert.equal(condoLoanMsg, getLoanMessage(65000, 690));
+```
+
+You should log the `condoLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(condoLoanMsg\)/)
+```
+
+You should have a variable called `carLoanMsg`.
+
+```js
+assert.isNotNull(carLoanMsg);
+```
+
+Your `carLoanMsg` variable should be set to the result of `getLoanMessage(45000, 660)`.
+
+```js
+assert.equal(carLoanMsg, getLoanMessage(45000, 660));
+```
+
+You should log the `carLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(carLoanMsg\)/)
+```
+
+You should have a variable called `noLoanMsg`.
+
+```js
+assert.isNotNull(noLoanMsg);
+```
+
+Your `noLoanMsg` variable should be set to the result of `getLoanMessage(25000, 550)`.
+
+```js
+assert.equal(noLoanMsg, getLoanMessage(25000, 550));
+```
+
+You should log the `noLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(noLoanMsg\)/)
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
+
+# --solutions--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+const duplexLoanMsg = getLoanMessage(85000, 850)
+console.log(duplexLoanMsg)
+
+const condoLoanMsg = getLoanMessage(65000, 690)
+console.log(condoLoanMsg)
+
+const carLoanMsg = getLoanMessage(45000, 660)
+console.log(carLoanMsg)
+
+const noLoanMsg = getLoanMessage(25000, 550)
+console.log(noLoanMsg)
+```
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md b/curriculum/challenges/chinese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
new file mode 100644
index 0000000000..4e11751ca0
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
@@ -0,0 +1,19 @@
+---
+id: 5f2c289f164c29556da632fd
+title: Build a Mario Database
+challengeType: 12
+url: freeCodeCamp/learn-relational-databases-by-building-a-mario-database
+dashedName: build-a-mario-database
+---
+
+# --description--
+
+In this 165-lesson workshop, you will learn the basics of a relational database by creating a PostgreSQL database filled with video game characters.
+
+# --instructions--
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
new file mode 100644
index 0000000000..8d4c90410d
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
@@ -0,0 +1,53 @@
+---
+id: 587d7fb3367417b2b2512bfb
+title: How to Use package.json, the Core of Any Node.js Project or npm Package
+challengeType: 2
+forumTopicId: 301528
+dashedName: how-to-use-package-json-the-core-of-any-node-js-project-or-npm-package
+---
+
+# --description--
+
+Working on these challenges will involve you writing your code using one of the following methods:
+
+- Clone <a href="https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete these challenges locally.
+- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+The `package.json` file is the center of any Node.js project or npm package. It stores information about your project. It consists of a single JSON object where information is stored in key-value pairs. There are only two required fields; `name` and `version`, but it’s good practice to provide additional information.
+
+You can create the `package.json` file from the terminal using the `npm init` command. This will run a guided setup. Using `npm init` with the `-y` flag will generate the file without having it ask any questions, `npm init -y`.
+
+If you look at the file tree of your project, you will find the `package.json` file on the top level of the tree. This is the file that you will be improving in the next couple of challenges.
+
+One of the most common pieces of information in this file is the `author` field. It specifies who created the project, and can consist of a string or an object with contact or other details. An object is recommended for bigger projects, but a simple string like the following example will do for this project.
+
+```json
+"author": "Jane Doe",
+```
+
+# --instructions--
+
+Add your name as the `author` of the project in the `package.json` file.
+
+**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (") and be separated with a comma (,).
+
+If you are using Gitpod, make sure the app is running and the preview window is open. Copy the preview window's URL and paste it into the Solution Link input below.
+
+# --hints--
+
+`package.json` should have a valid "author" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.author, '"author" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
new file mode 100644
index 0000000000..37d15d5261
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb3367417b2b2512bfc
+title: Add a Description to Your package.json
+challengeType: 2
+forumTopicId: 301522
+dashedName: add-a-description-to-your-package-json
+---
+
+# --description--
+
+The next part of a good package.json file is the `description` field; where a short, but informative description about your project belongs.
+
+If some day you plan to publish a package to npm, this is the string that should sell your idea to the user when they decide whether to install your package or not. However, that’s not the only use case for the description, it’s a great way to summarize what a project does. It’s just as important in any Node.js project to help other developers, future maintainers or even your future self understand the project quickly.
+
+Regardless of what you plan for your project, a description is definitely recommended. Here's an example:
+
+```json
+"description": "A project that does something awesome",
+```
+
+# --instructions--
+
+Add a `description` to the package.json file of your project.
+
+**Note:** Remember to use double-quotes for field-names (") and commas (,) to separate fields.
+
+# --hints--
+
+package.json should have a valid "description" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.description, '"description" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
new file mode 100644
index 0000000000..a001cdd477
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
@@ -0,0 +1,75 @@
+---
+id: 587d7fb4367417b2b2512bfd
+title: Add Keywords to Your package.json
+challengeType: 2
+forumTopicId: 301526
+dashedName: add-keywords-to-your-package-json
+---
+
+# --description--
+
+The `keywords` field is where you can describe your project using related keywords. Here's an example:
+
+```json
+"keywords": [ "descriptive", "related", "words" ],
+```
+
+As you can see, this field is structured as an array of double-quoted strings.
+
+# --instructions--
+
+Add an array of suitable strings to the `keywords` field in the package.json file of your project.
+
+One of the keywords should be "freecodecamp".
+
+# --hints--
+
+package.json should have a valid "keywords" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.keywords, '"keywords" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" field should be an Array
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.isArray(packJson.keywords, '"keywords" is not an array');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" should include "freecodecamp"
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.include(
+        packJson.keywords,
+        'freecodecamp',
+        '"keywords" does not include "freecodecamp"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
new file mode 100644
index 0000000000..7b09acd042
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
@@ -0,0 +1,39 @@
+---
+id: 587d7fb4367417b2b2512bfe
+title: Add a License to Your package.json
+challengeType: 2
+forumTopicId: 301523
+dashedName: add-a-license-to-your-package-json
+---
+
+# --description--
+
+The `license` field is where you inform users of what they are allowed to do with your project.
+
+Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do. Here's an example of the license field:
+
+```json
+"license": "MIT",
+```
+
+# --instructions--
+
+Fill the `license` field in the package.json file of your project as you find suitable.
+
+# --hints--
+
+package.json should have a valid "license" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.license, '"license" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
new file mode 100644
index 0000000000..f2e571faed
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
@@ -0,0 +1,37 @@
+---
+id: 587d7fb4367417b2b2512bff
+title: Add a Version to Your package.json
+challengeType: 2
+forumTopicId: 301525
+dashedName: add-a-version-to-your-package-json
+---
+
+# --description--
+
+A `version` is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example:
+
+```json
+"version": "1.2.0",
+```
+
+# --instructions--
+
+Add a `version` to the package.json file of your project.
+
+# --hints--
+
+package.json should have a valid "version" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.version, '"version" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
new file mode 100644
index 0000000000..161c60fe69
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
@@ -0,0 +1,68 @@
+---
+id: 587d7fb4367417b2b2512c00
+title: Expand Your Project with External Packages from npm
+challengeType: 2
+forumTopicId: 301527
+dashedName: expand-your-project-with-external-packages-from-npm
+---
+
+# --description--
+
+One of the biggest reasons to use a package manager, is their powerful dependency management. Instead of manually having to make sure that you get all dependencies whenever you set up a project on a new computer, npm automatically installs everything for you. But how can npm know exactly what your project needs? Meet the `dependencies` section of your package.json file.
+
+In this section, packages your project requires are stored using the following format:
+
+```json
+"dependencies": {
+  "package-name": "version",
+  "express": "4.14.0"
+}
+
+```
+
+# --instructions--
+
+Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file.
+
+**Note:** `@freecodecamp/example` is a faux package used as a learning tool.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.1.0"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^[\^\~]?1\.1\.0/,
+        'Wrong version of "@freecodecamp/example" installed. It should be 1.1.0'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
new file mode 100644
index 0000000000..deda9b82de
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
@@ -0,0 +1,64 @@
+---
+id: 587d7fb5367417b2b2512c01
+title: Manage npm Dependencies By Understanding Semantic Versioning
+challengeType: 2
+forumTopicId: 301529
+dashedName: manage-npm-dependencies-by-understanding-semantic-versioning
+---
+
+# --description--
+
+`Versions` of the npm packages in the dependencies section of your package.json file follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes projects can expect if they update.
+
+Knowing SemVer can be useful when you develop software that uses external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things that worked yesterday suddenly don’t work today. This is how Semantic Versioning works according to the official website:
+
+```json
+"package": "MAJOR.MINOR.PATCH"
+```
+
+The MAJOR version should increment when you make incompatible API changes. The MINOR version should increment when you add functionality in a backwards-compatible manner. The PATCH version should increment when you make backwards-compatible bug fixes. This means that PATCHes are bug fixes and MINORs add new features but neither of them break what worked before. Finally, MAJORs add changes that won’t work with earlier versions.
+
+# --instructions--
+
+In the dependencies section of your `package.json` file, change the version of `@freecodecamp/example` to match MAJOR version 1, MINOR version 2 and PATCH version 13
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.equal(
+        packJson.dependencies["@freecodecamp/example"],
+        '1.2.13',
+        'Wrong version of "@freecodecamp/example". It should be 1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
new file mode 100644
index 0000000000..8eae5f51ee
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c02
+title: Use the Tilde-Character to Always Use the Latest Patch Version of a Dependency
+challengeType: 2
+forumTopicId: 301532
+dashedName: use-the-tilde-character-to-always-use-the-latest-patch-version-of-a-dependency
+---
+
+# --description--
+
+In the last challenge, you told npm to only include a specific version of a package. That’s a useful way to freeze your dependencies if you need to make sure that different parts of your project stay compatible with each other. But in most use cases, you don’t want to miss bug fixes since they often include important security patches and (hopefully) don’t break things in doing so.
+
+To allow an npm dependency to update to the latest PATCH version, you can prefix the dependency’s version with the tilde (`~`) character. Here's an example of how to allow updates to any `1.3.x` version.
+
+```json
+"package": "~1.3.8"
+```
+
+# --instructions--
+
+In the package.json file, your current rule for how npm may upgrade `@freecodecamp/example` is to use a specific version (`1.2.13`). But now, you want to allow the latest `1.2.x` version.
+
+Use the tilde (`~`) character to prefix the version of `@freecodecamp/example` in your dependencies, and allow npm to update it to any new _patch_ release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"~1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\~1\.2\.13/,
+        'Wrong version of "@freecodecamp/example". It should be ~1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
new file mode 100644
index 0000000000..adc3014ea4
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c03
+title: Use the Caret-Character to Use the Latest Minor Version of a Dependency
+challengeType: 2
+forumTopicId: 301531
+dashedName: use-the-caret-character-to-use-the-latest-minor-version-of-a-dependency
+---
+
+# --description--
+
+Similar to how the tilde we learned about in the last challenge allows npm to install the latest PATCH for a dependency, the caret (`^`) allows npm to install future updates as well. The difference is that the caret will allow both MINOR updates and PATCHes.
+
+Your current version of `@freecodecamp/example` should be `~1.2.13` which allows npm to install to the latest `1.2.x` version. If you were to use the caret (^) as a version prefix instead, npm would be allowed to update to any `1.x.x` version.
+
+```json
+"package": "^1.3.8"
+```
+
+This would allow updates to any `1.x.x` version of the package.
+
+# --instructions--
+
+Use the caret (`^`) to prefix the version of `@freecodecamp/example` in your dependencies and allow npm to update it to any new MINOR release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"^1.x.x"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\^1\./,
+        'Wrong version of "@freecodecamp/example". It should be ^1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
new file mode 100644
index 0000000000..5f695eed88
--- /dev/null
+++ b/curriculum/challenges/chinese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb5367417b2b2512c04
+title: Remove a Package from Your Dependencies
+challengeType: 2
+forumTopicId: 301530
+dashedName: remove-a-package-from-your-dependencies
+---
+
+# --description--
+
+You have now tested a few ways you can manage dependencies of your project by using the package.json's dependencies section. You have also included external packages by adding them to the file and even told npm what types of versions you want, by using special characters such as the tilde or the caret.
+
+But what if you want to remove an external package that you no longer need? You might already have guessed it, just remove the corresponding key-value pair for that package from your dependencies.
+
+This same method applies to removing other fields in your package.json as well.
+
+# --instructions--
+
+Remove the `@freecodecamp/example` package from your dependencies.
+
+**Note:** Make sure you have the right amount of commas after removing it.
+
+# --hints--
+
+`"dependencies"` should not include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.notProperty(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" still includes "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/espanol/01-responsive-web-design/applied-accessibility/improve-accessibility-of-audio-content-with-the-audio-element.md b/curriculum/challenges/espanol/01-responsive-web-design/applied-accessibility/improve-accessibility-of-audio-content-with-the-audio-element.md
index 7a0ea4c642..7415ec18cf 100644
--- a/curriculum/challenges/espanol/01-responsive-web-design/applied-accessibility/improve-accessibility-of-audio-content-with-the-audio-element.md
+++ b/curriculum/challenges/espanol/01-responsive-web-design/applied-accessibility/improve-accessibility-of-audio-content-with-the-audio-element.md
@@ -26,7 +26,7 @@ Acá tenemos un ejemplo:
 
 # --instructions--
 
-Es hora de salir del Camper Cat y conocer a nuestro compañero Zersiax (@zersiax), un campeón en accesibilidad y un usuario de lector de pantalla. Para escuchar el fragmento de audio de su lector de pantalla en acción, agregue un elemento `audio` después del elemento `p`. Incluye el atributo `controls`. Then place a `source` element inside the `audio` tags with the `src` attribute set to `https://cdn.freecodecamp.org/curriculum/applied-accessibility/screen-reader.mp3` and `type` attribute set to `"audio/mpeg"`.
+Es hora de salir del Camper Cat y conocer a nuestro compañero Zersiax (@zersiax), un campeón en accesibilidad y un usuario de lector de pantalla. Para escuchar el fragmento de audio de su lector de pantalla en acción, agregue un elemento `audio` después del elemento `p`. Incluye el atributo `controls`. Luego ubica un elemento `source` dentro del `audio` etiquetado con el atributo `src` asignado a `https://cdn.freecodecamp.org/curriculum/applied-accessibility/screen-reader.mp3` y el atributo`type` asignado a `"audio/mpeg"`.
 
 **Note:** El clip del audio puede sonar rápido y quizás sea difícil de entender pero esta velocidad es normal para los lectores de pantalla.
 
diff --git a/curriculum/challenges/espanol/01-responsive-web-design/applied-visual-design/create-movement-using-css-animation.md b/curriculum/challenges/espanol/01-responsive-web-design/applied-visual-design/create-movement-using-css-animation.md
index 65baac7481..e0a552c79e 100644
--- a/curriculum/challenges/espanol/01-responsive-web-design/applied-visual-design/create-movement-using-css-animation.md
+++ b/curriculum/challenges/espanol/01-responsive-web-design/applied-visual-design/create-movement-using-css-animation.md
@@ -1,6 +1,6 @@
 ---
 id: 587d78a7367417b2b2512ae1
-title: Crear movimiento usando animación CSS
+title: Crea movimiento usando animación CSS
 challengeType: 0
 videoUrl: 'https://scrimba.com/c/c7amZfW'
 forumTopicId: 301051
diff --git a/curriculum/challenges/espanol/01-responsive-web-design/applied-visual-design/create-visual-direction-by-fading-an-element-from-left-to-right.md b/curriculum/challenges/espanol/01-responsive-web-design/applied-visual-design/create-visual-direction-by-fading-an-element-from-left-to-right.md
index 0e0569db6b..0d4bbb5b04 100644
--- a/curriculum/challenges/espanol/01-responsive-web-design/applied-visual-design/create-visual-direction-by-fading-an-element-from-left-to-right.md
+++ b/curriculum/challenges/espanol/01-responsive-web-design/applied-visual-design/create-visual-direction-by-fading-an-element-from-left-to-right.md
@@ -1,6 +1,6 @@
 ---
 id: 587d78a7367417b2b2512ae2
-title: Crear dirección visual desvaneciendo un elemento de izquierda a derecha
+title: Crea dirección visual desvaneciendo un elemento de izquierda a derecha
 challengeType: 0
 videoUrl: 'https://scrimba.com/c/cGJqqAE'
 forumTopicId: 301054
diff --git a/curriculum/challenges/espanol/01-responsive-web-design/basic-css/style-the-html-body-element.md b/curriculum/challenges/espanol/01-responsive-web-design/basic-css/style-the-html-body-element.md
index 7ba0b2122f..84b47af2f1 100644
--- a/curriculum/challenges/espanol/01-responsive-web-design/basic-css/style-the-html-body-element.md
+++ b/curriculum/challenges/espanol/01-responsive-web-design/basic-css/style-the-html-body-element.md
@@ -41,7 +41,7 @@ assert(
 );
 ```
 
-Your CSS rule should end with a semicolon.
+La regla de CSS debe terminar con un punto y coma.
 
 ```js
 assert(
diff --git a/curriculum/challenges/espanol/01-responsive-web-design/css-grid/add-columns-with-grid-template-columns.md b/curriculum/challenges/espanol/01-responsive-web-design/css-grid/add-columns-with-grid-template-columns.md
index 8632af7175..dd27bb97f8 100644
--- a/curriculum/challenges/espanol/01-responsive-web-design/css-grid/add-columns-with-grid-template-columns.md
+++ b/curriculum/challenges/espanol/01-responsive-web-design/css-grid/add-columns-with-grid-template-columns.md
@@ -9,7 +9,7 @@ dashedName: add-columns-with-grid-template-columns
 
 # --description--
 
-Crear un simple elemento cuadrícula (grid) no te llevará muy lejos. Necesitas también definir su estructura. Para agregar columnas a la cuadrícula, usa la propiedad `grid-template-columns` en el contenedor de la cuadrícula como se demuestra a continuación:
+Crea un simple elemento cuadrícula (grid) no te llevará muy lejos. Necesitas también definir su estructura. Para agregar columnas a la cuadrícula, usa la propiedad `grid-template-columns` en el contenedor de la cuadrícula como se demuestra a continuación:
 
 ```css
 .container {
diff --git a/curriculum/challenges/espanol/02-javascript-algorithms-and-data-structures/basic-javascript/record-collection.md b/curriculum/challenges/espanol/02-javascript-algorithms-and-data-structures/basic-javascript/record-collection.md
index 4a2b16f90f..809137b62c 100644
--- a/curriculum/challenges/espanol/02-javascript-algorithms-and-data-structures/basic-javascript/record-collection.md
+++ b/curriculum/challenges/espanol/02-javascript-algorithms-and-data-structures/basic-javascript/record-collection.md
@@ -22,8 +22,8 @@ Completa la función utilizando las reglas siguientes para modificar el objeto p
 -   Tu función debe devolver siempre el objeto `records` completo.
 -   Si `value` es una cadena vacía, elimina la propiedad `prop` dada del álbum.
 -   Si `prop` no es `tracks` y `value` no es una cadena vacía, asigna el `value` a la `prop` de ese álbum.
--   If `prop` is `tracks` and `value` isn't an empty string, but the album doesn't have a `tracks` property, create an empty array and add `value` to it.
--   If prop is `tracks` and `value` isn't an empty string, add `value` to the end of the album's existing `tracks` array.
+-   Si `prop` es `tracks` y `value` no es una cadena de carácteres vacía, pero el álbum no tiene una propiedad `tracks`, crea un arreglo vacío y agregalo `value` a él.
+-   Si la propiedad es `tracks` y `value` no es una cadena de caracteres vacía, agregalo `value` al final del arreglo existente `tracks` del álbum.
 
 **Nota:** Para las pruebas se utiliza una copia del objeto `recordCollection`. No debes modificar directamente el objeto `recordCollection`.
 
diff --git a/curriculum/challenges/espanol/04-data-visualization/data-visualization-projects/visualize-data-with-a-scatterplot-graph.md b/curriculum/challenges/espanol/04-data-visualization/data-visualization-projects/visualize-data-with-a-scatterplot-graph.md
index 5beac2ba93..aca2e9d070 100644
--- a/curriculum/challenges/espanol/04-data-visualization/data-visualization-projects/visualize-data-with-a-scatterplot-graph.md
+++ b/curriculum/challenges/espanol/04-data-visualization/data-visualization-projects/visualize-data-with-a-scatterplot-graph.md
@@ -12,7 +12,7 @@ dashedName: visualize-data-with-a-scatterplot-graph
 
 Completa las historias de usuario a continuación y obtén todas las pruebas para aprobar. Utiliza cualquier librería o API que necesites. Dale tu propio estilo.
 
-Puedes utilizar HTML, JavaScript, CSS y la librería D3 de visualización basada en svg. Las pruebas requieren que los ejes se generen utilizando la propiedad de eje D3, que genera automáticamente marcas a lo largo del eje. Estas marcas son necesarias para pasar las pruebas de D3, ya que sus posiciones se utilizan para determinar el alineamiento de los elementos gráficos. You will find information about generating axes at <https://d3js.org/d3-axis>. Los elementos DOM necesarios se consultan en el momento de cada prueba. Si usas un framework frontend (como por ejemplo Vue), los resultados de la prueba pueden ser inexactos para el contenido dinámico. Esperamos poder adaptarlos eventualmente, pero por ahora estos frameworks no son soportados por los proyectos con D3.
+Puedes utilizar HTML, JavaScript, CSS y la librería D3 de visualización basada en svg. Las pruebas requieren que los ejes se generen utilizando la propiedad de eje D3, que genera automáticamente marcas a lo largo del eje. Estas marcas son necesarias para pasar las pruebas de D3, ya que sus posiciones se utilizan para determinar el alineamiento de los elementos gráficos. Encontrarás información sobre la generación de ejes en <https://d3js.org/d3-axis>. Los elementos DOM necesarios se consultan en el momento de cada prueba. Si usas un framework frontend (como por ejemplo Vue), los resultados de la prueba pueden ser inexactos para el contenido dinámico. Esperamos poder adaptarlos eventualmente, pero por ahora estos frameworks no son soportados por los proyectos con D3.
 
 **Historia de usuario #1:** Puedo ver un elemento titular que tiene un `id="title"`.
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/advanced-node-and-express/serialization-of-a-user-object.md b/curriculum/challenges/espanol/06-quality-assurance/advanced-node-and-express/serialization-of-a-user-object.md
index 450a519061..5d67bab988 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/advanced-node-and-express/serialization-of-a-user-object.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/advanced-node-and-express/serialization-of-a-user-object.md
@@ -8,7 +8,7 @@ dashedName: serialization-of-a-user-object
 
 # --description--
 
-Serialization and deserialization are important concepts in regard to authentication. Para serializar un objeto significa convertir su contenido en una pequeña *key* que puede ser deserializada en el objeto original. Esto es lo que nos permite saber quién se ha comunicado con el servidor sin tener que enviar los datos de autentificación, como el nombre de usuario y la contraseña, en cada petición de una nueva página.
+La serialización y deserialización son conceptos importantes en lo que respecta a la autenticación. Para serializar un objeto significa convertir su contenido en una pequeña *key* que puede ser deserializada en el objeto original. Esto es lo que nos permite saber quién se ha comunicado con el servidor sin tener que enviar los datos de autentificación, como el nombre de usuario y la contraseña, en cada petición de una nueva página.
 
 Para configurar esto apropiadamente, necesita tener una función serializada y una función deserialización. En Passport, esto puede ser creado con:
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/assert-deep-equality-with-.deepequal-and-.notdeepequal.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/assert-deep-equality-with-.deepequal-and-.notdeepequal.md
index 77576bb4ce..33f194519f 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/assert-deep-equality-with-.deepequal-and-.notdeepequal.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/assert-deep-equality-with-.deepequal-and-.notdeepequal.md
@@ -8,13 +8,13 @@ dashedName: assert-deep-equality-with--deepequal-and--notdeepequal
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>  or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a> o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 `deepEqual()` confirma que dos objetos son iguales en profundidad.
 
 # --instructions--
 
-Within `tests/1_unit-tests.js` under the test labeled `#7` in the `Equality` suite, change each `assert` to either `assert.deepEqual` or `assert.notDeepEqual` to make the test pass (should evaluate to `true`). No modifiques los argumentos pasados ​​a los verificadores.
+Dentro de `tests/1_unit-tests.js` bajo la prueba etiquetada `#7` en el conjunto de pruebas `Equality`, cambia cada `assert` a `assert.deepEqual` o `assert.notDeepEqual` para pasar la prueba (debe evaluarse como `true`). No modifiques los argumentos pasados ​​a los verificadores.
 
 # --hints--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/compare-the-properties-of-two-elements.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/compare-the-properties-of-two-elements.md
index c27ff746ed..53a64853a8 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/compare-the-properties-of-two-elements.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/compare-the-properties-of-two-elements.md
@@ -8,11 +8,11 @@ dashedName: compare-the-properties-of-two-elements
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a> o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 # --instructions--
 
-Within `tests/1_unit-tests.js` under the test labeled `#8` in the `Comparisons` suite, change each `assert` to either `assert.isAbove` or `assert.isAtMost` to make the test pass (should evaluate to `true`). No modifiques los argumentos pasados ​​a los verificadores.
+Dentro de `tests/1_unit-tests.js` bajo la prueba etiquetada como `#8` en el conjunto de pruebas `Comparisons`, cambiar cada `assert` a `assert.isAbove` o `assert.isAtMost` para que el test sea aprovado (debe evaluarse a `true`). No modifiques los argumentos pasados ​​a los verificadores.
 
 # --hints--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/learn-how-javascript-assertions-work.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/learn-how-javascript-assertions-work.md
index a8a800509f..e09b28228a 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/learn-how-javascript-assertions-work.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/learn-how-javascript-assertions-work.md
@@ -11,12 +11,12 @@ dashedName: learn-how-javascript-assertions-work
 Trabajar en estos desafíos implica escribir tu código usando uno de los siguientes métodos:
 
 - Clone este repositorio de <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow"> GitHub</a> y complete estos desafíos localmente.
-- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Utiliza <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">nuestro proyecto inicial en Gitpod</a> para completar estos desafíos.
 - Utiliza un constructor de sitios web de tu elección para completar el proyecto. Asegúrate de incorporar todos los archivos de nuestro repositorio de GitHub.
 
 # --instructions--
 
-Within `tests/1_unit-tests.js` under the test labeled `#1` in the `Basic Assertions` suite, change each `assert` to either `assert.isNull` or `assert.isNotNull` to make the test pass (should evaluate to `true`). No cambies los argumentos pasados a las aserciones.
+Dentro de `tests/1_unit-tests.js`, bajo la prueba etiquetada como `#1` en el conjunto de prueba `Basic Assertions`, cambia cada `assert` a `assert.isNull` o `assert.isNotNull` para pasar la prueba (deber evaluarse como `true`). No cambies los argumentos pasados a las aserciones.
 
 # --hints--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-on-an-api-response-using-chai-http-iii---put-method.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-on-an-api-response-using-chai-http-iii---put-method.md
index 2f3abb3b53..dcd5409ba0 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-on-an-api-response-using-chai-http-iii---put-method.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-on-an-api-response-using-chai-http-iii---put-method.md
@@ -8,7 +8,7 @@ dashedName: run-functional-tests-on-an-api-response-using-chai-http-iii---put-me
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 Cuando se prueba una solicitud `PUT`, a menudo enviarás datos junto con ella. Los datos que incluye con su solicitud `PUT` se llama el body de la petición.
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-on-api-endpoints-using-chai-http.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-on-api-endpoints-using-chai-http.md
index 9c150351fb..3e244eb50c 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-on-api-endpoints-using-chai-http.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-on-api-endpoints-using-chai-http.md
@@ -8,7 +8,7 @@ dashedName: run-functional-tests-on-api-endpoints-using-chai-http
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a> o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 Mocha te permite comprobar operaciones asíncronas como llamadas a los endpoints de la API con un complemento llamado `chai-http`.
 
@@ -42,13 +42,13 @@ Sin embargo, las pruebas que se ejecutan cuando envía el enlace para tu proyect
 
 # --instructions--
 
-Dentro de `tests/2_functional-tests.js`, altera la prueba `'Test GET /hello with no name'` (`// #1`) para afirmar el `status` y el `text` de la respuesta para hacer que la prueba pase. Do not alter the arguments passed to the asserts.
+Dentro de `tests/2_functional-tests.js`, altera la prueba `'Test GET /hello with no name'` (`// #1`) para afirmar el `status` y el `text` de la respuesta para hacer que la prueba pase. No altere los argumentos pasados a las afirmaciones.
 
-There should be no URL query. Without a name URL query, the endpoint responds with `hello Guest`.
+No debe haber ninguna consulta de URL. Sin una consulta de URL de nombre, el extremo responde con `hello Guest`.
 
 # --hints--
 
-All tests should pass
+Todas las pruebas deben pasar
 
 ```js
 (getUserInput) =>
@@ -62,7 +62,7 @@ All tests should pass
   );
 ```
 
-You should test for `res.status` == 200
+Debe probar para `res.status` == 200
 
 ```js
 (getUserInput) =>
@@ -78,7 +78,7 @@ You should test for `res.status` == 200
   );
 ```
 
-You should test for `res.text` == `'hello Guest'`
+Debe probar `res.text` == `'hello Guest'`
 
 ```js
 (getUserInput) =>
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-using-a-headless-browser-ii.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-using-a-headless-browser-ii.md
index ec6bcaedfe..73caa3ce28 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-using-a-headless-browser-ii.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-using-a-headless-browser-ii.md
@@ -8,7 +8,7 @@ dashedName: run-functional-tests-using-a-headless-browser-ii
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a> o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 # --instructions--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-using-a-headless-browser.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-using-a-headless-browser.md
index d5669decee..0829f08653 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-using-a-headless-browser.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-using-a-headless-browser.md
@@ -8,7 +8,7 @@ dashedName: run-functional-tests-using-a-headless-browser
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a> o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 En la página hay un formulario de entrada. Envía datos al endpoint `PUT /travellers` como una solicitud AJAX.
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-for-truthiness.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-for-truthiness.md
index bca07b044f..f2e0ca477a 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-for-truthiness.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-for-truthiness.md
@@ -8,7 +8,7 @@ dashedName: test-for-truthiness
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a> o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 `isTrue()` probará el valor booleano `true` y `isNotTrue()` pasará cuando se le dé cualquier cosa que no sea el valor booleano de `true`.
 
@@ -22,7 +22,7 @@ assert.isTrue(1, 'This will NOT pass with the number value 1');
 
 # --instructions--
 
-Within `tests/1_unit-tests.js` under the test labeled `#4` in the `Basic Assertions` suite, change each `assert` to either `assert.isTrue` or `assert.isNotTrue` to make the test pass (should evaluate to `true`). No modifiques los argumentos pasados ​​a los verificadores.
+Dentro de `tests/1_unit-tests.js` bajo la prueba etiquetada como `#4` en el conjunto de prueba `Basic Assertions`, cambia cada `assert` a `assert.isTrue` o `assert.isNotTrue` para hacer que la prueba pase (debe evaluarse como `true`). No modifiques los argumentos pasados ​​a los verificadores.
 
 # --hints--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-a-value-is-an-array.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-a-value-is-an-array.md
index 321ae654e2..db9c8e4dc4 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-a-value-is-an-array.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-a-value-is-an-array.md
@@ -8,11 +8,11 @@ dashedName: test-if-a-value-is-an-array
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+A modo de recordatorio, este proyecto se está construyendo sobre el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 # --instructions--
 
-Within `tests/1_unit-tests.js` under the test labeled `#11` in the `Arrays` suite, change each `assert` to either `assert.isArray` or `assert.isNotArray` to make the test pass (should evaluate to `true`). No modifiques los argumentos pasados ​​a los verificadores.
+Dentro de `tests/1_unit-tests.js` debajo de la prueba etiquetada `#11` en el `Arrays` suite, cambia cada `assert` por cualquiera, `assert.isArray` o `assert.isNotArray` para pasar la prueba (debe evaluarse como `true`). No modifiques los argumentos pasados ​​a los verificadores.
 
 # --hints--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-an-object-has-a-property.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-an-object-has-a-property.md
index f2c370f3ca..92e55a0df6 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-an-object-has-a-property.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-an-object-has-a-property.md
@@ -8,13 +8,13 @@ dashedName: test-if-an-object-has-a-property
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 `property` verifica que el objeto actual tiene una propiedad determinada.
 
 # --instructions--
 
-Within `tests/1_unit-tests.js` under the test labeled `#16` in the `Objects` suite, change each `assert` to either `assert.property` or `assert.notProperty` to make the test pass (should evaluate to `true`). No modifiques los argumentos pasados ​​a los verificadores.
+Dentro de `tests/1_unit-tests.js` bajo la prueba etiquetada `#16` en la suite `Objects`, cambia cada `assert` a `assert.property` o `assert.notProperty` para pasar la prueba (debe evaluarse como `true`). No modifiques los argumentos pasados ​​a los verificadores.
 
 # --hints--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-an-object-is-an-instance-of-a-constructor.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-an-object-is-an-instance-of-a-constructor.md
index 817e781bd6..5a418e209c 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-an-object-is-an-instance-of-a-constructor.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-an-object-is-an-instance-of-a-constructor.md
@@ -8,13 +8,13 @@ dashedName: test-if-an-object-is-an-instance-of-a-constructor
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 `#instanceOf` verifica que un objeto es una instancia de un constructor.
 
 # --instructions--
 
-Within `tests/1_unit-tests.js` under the test labeled `#18` in the `Objects` suite, change each `assert` to either `assert.instanceOf` or `assert.notInstanceOf` to make the test pass (should evaluate to `true`). No modifiques los argumentos pasados ​​a los verificadores.
+Dentro de `tests/1_unit-tests.js` bajo la prueba etiquetada `#18` en la suite `Objects`, cambia cada `assert` por `assert.instanceOf` o por `assert.notInstanceOf` para pasar la prueba (debe evaluarse como `true`). No modifiques los argumentos pasados ​​a los verificadores.
 
 # --hints--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-one-value-is-below-or-at-least-as-large-as-another.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-one-value-is-below-or-at-least-as-large-as-another.md
index fd1524668e..735fb65327 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-one-value-is-below-or-at-least-as-large-as-another.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/test-if-one-value-is-below-or-at-least-as-large-as-another.md
@@ -8,7 +8,7 @@ dashedName: test-if-one-value-is-below-or-at-least-as-large-as-another
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a> o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 # --instructions--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-assert.isok-and-assert.isnotok.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-assert.isok-and-assert.isnotok.md
index 63a02bd196..ffdbb96ae3 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-assert.isok-and-assert.isnotok.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-assert.isok-and-assert.isnotok.md
@@ -8,7 +8,7 @@ dashedName: use-assert-isok-and-assert-isnotok
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 `isOk()` prueba un valor verdadero y `isNotOk()` prueba un valor falso.
 
@@ -16,7 +16,7 @@ Para aprender más sobre los valores verdaderos y falsos, prueba nuestro desafí
 
 # --instructions--
 
-Within `tests/1_unit-tests.js` under the test labeled `#3` in the `Basic Assertions` suite, change each `assert` to either `assert.isOk()` or `assert.isNotOk()` to make the test pass (should evaluate to `true`). No modifiques los argumentos pasados ​​a los verificadores.
+Dentro de `tests/1_unit-tests.js` bajo la prueba etiquetada `#3` en la suite `Basic Assertions`, cambia cada `assert` a `assert.isOk()` o a `assert.isNotOk()` para hacer que la prueba pase (debe evaluarse como `true`). No modifiques los argumentos pasados ​​a los verificadores.
 
 # --hints--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-regular-expressions-to-test-a-string.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-regular-expressions-to-test-a-string.md
index 92f156577f..ac33f0cd7e 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-regular-expressions-to-test-a-string.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-regular-expressions-to-test-a-string.md
@@ -8,13 +8,13 @@ dashedName: use-regular-expressions-to-test-a-string
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a> o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 `match()` verifica que el valor real coincide con la expresión regular del segundo argumento.
 
 # --instructions--
 
-Within `tests/1_unit-tests.js` under the test labeled `#15` in the `Strings` suite, change each `assert` to either `assert.match` or `assert.notMatch` to make the test pass (should evaluate to `true`). No modifiques los argumentos pasados ​​a los verificadores.
+Dentro de `tests/1_unit-tests.js` bajo la prueba etiquetada `#15` en el suite `Strings`, cambia cada `assert` por `assert.match` o por `assert.notMatch` para pasar la prueba (debe evaluarse a `true`). No modifiques los argumentos pasados ​​a los verificadores.
 
 # --hints--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-the-triple-equals-to-assert-strict-equality.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-the-triple-equals-to-assert-strict-equality.md
index a65210a4f8..dfa8e67842 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-the-triple-equals-to-assert-strict-equality.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-and-testing-with-chai/use-the-triple-equals-to-assert-strict-equality.md
@@ -8,13 +8,13 @@ dashedName: use-the-triple-equals-to-assert-strict-equality
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a> o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 `strictEqual()` compara objetos usando `===`.
 
 # --instructions--
 
-Within `tests/1_unit-tests.js` under the test labeled `#6` in the `Equality` suite, change each `assert` to either `assert.strictEqual` or `assert.notStrictEqual` to make the test pass (should evaluate to `true`). No modifiques los argumentos pasados ​​a los verificadores.
+Dentro de `tests/1_unit-tests.js` bajo la prueba etiquetada `#6` en la suite `Equality`, cambia cada `assert` por `assert.strictEqual` o por `assert.notStrictEqual`, para pasar la prueba (debe evaluarse como `true`). No modifiques los argumentos pasados ​​a los verificadores.
 
 # --hints--
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/american-british-translator.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/american-british-translator.md
index 4b75b8e0c2..c6445b0016 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/american-british-translator.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/american-british-translator.md
@@ -11,7 +11,7 @@ dashedName: american-british-translator
 Crea una aplicación full stack de JavaScript que sea funcionalmente similar a esta: <a href="https://american-british-translator.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://american-british-translator.freecodecamp.rocks/</a>. Trabajar en este proyecto implicará escribir tu código utilizando uno de los siguientes métodos:
 
 -   Clone este repositorio de <a href="https://github.com/freeCodeCamp/boilerplate-project-american-british-english-translator/" target="_blank" rel="noopener noreferrer nofollow"> GitHub</a> y complete estos desafíos localmente.
--   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-american-british-english-translator/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Usa <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-american-british-english-translator/" target="_blank" rel="noopener noreferrer nofollow">nuestro proyecto inicial de Gitpod</a>para completar tu proyecto.
 -   Usa un constructor de sitios de tu elección para completar el proyecto. Asegúrate de incorporar todos los archivos de nuestro repositorio de GitHub.
 
 # --instructions--
@@ -20,7 +20,7 @@ Crea una aplicación full stack de JavaScript que sea funcionalmente similar a e
 -   Completa la ruta `/api/translate` en `/routes/api.js`
 -   Crea todo lo de las pruebas unitarias/funcionales tests en `tests/1_unit-tests.js` y `tests/2_functional-tests.js`
 -   Consulta los archivos JavaScript en `/components` para las diferentes pronunciaciones y terminos que tu aplicación debería traducir
--   To run the tests automatically, set `NODE_ENV` to `test` without quotes in the `.env` file
+-   Para ejecutar las pruebas automáticamente, establece `NODE_ENV` a `test` sin comillas en el `.env`archivo
 -   Para ejecutar las pruebas en la consola, usa el comando: `npm run test`.
 
 Escribe las siguientes pruebas en `tests/1_unit-tests.js`:
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/issue-tracker.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/issue-tracker.md
index ffe60228c5..5c2958430a 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/issue-tracker.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/issue-tracker.md
@@ -11,7 +11,7 @@ dashedName: issue-tracker
 Crea una aplicación full stack de JavaScript que sea funcionalmente similar a esta: <a href="https://issue-tracker.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://issue-tracker.freecodecamp.rocks/</a>. Trabajar en este proyecto implicará escribir tu código utilizando uno de los siguientes métodos:
 
 -   Clone este repositorio de <a href="https://github.com/freeCodeCamp/boilerplate-project-issuetracker/" target="_blank" rel="noopener noreferrer nofollow"> GitHub</a> y complete estos desafíos localmente.
--   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-issuetracker/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Utiliza <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-issuetracker/" target="_blank" rel="noopener noreferrer nofollow">nuestro proyecto inicial en Gitpod</a> para completar tu proyecto.
 -   Usa un constructor de sitios de tu elección para completar el proyecto. Asegúrate de incorporar todos los archivos de nuestro repositorio de GitHub.
 
 # --instructions--
@@ -19,8 +19,8 @@ Crea una aplicación full stack de JavaScript que sea funcionalmente similar a e
 -   Complete las rutas necesarias en `/routes/api.js`
 -   Crea todas las pruebas funcionales en `tests/2_functional-tests.js`
 -   Copie el archivo `sample.env` a `.env` y establezca las variables apropiadamente
--   To run the tests automatically, add `NODE_ENV=test` in your `.env` file
--   To run the tests in the console, use the command `npm run test`
+-   Para ejecutar las pruebas automáticamente, añade `NODE_ENV=test` en tu archivo `.env`
+-   Para ejecutar las pruebas en la consola, use el comando `npm run test`
 
 Escribir las siguientes pruebas en `tests/2_functional-tests.js`:
 
diff --git a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/metric-imperial-converter.md b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/metric-imperial-converter.md
index ab8cdfeb6d..eb2d871365 100644
--- a/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/metric-imperial-converter.md
+++ b/curriculum/challenges/espanol/06-quality-assurance/quality-assurance-projects/metric-imperial-converter.md
@@ -11,45 +11,45 @@ dashedName: metric-imperial-converter
 Crea una aplicación full stack de JavaScript que sea funcionalmente similar a esta: <a href="https://metric-imperial-converter.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://metric-imperial-converter.freecodecamp.rocks/</a>. Trabajar en este proyecto implicará escribir tu código utilizando uno de los siguientes métodos:
 
 - Clone este repositorio de <a href="https://github.com/freeCodeCamp/boilerplate-project-metricimpconverter/" target="_blank" rel="noopener noreferrer nofollow"> GitHub</a> y complete estos desafíos localmente.
-- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-metricimpconverter/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+- Utiliza <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-metricimpconverter/" target="_blank" rel="noopener noreferrer nofollow">nuestro proyecto inicial de Gitpod</a> para completar tu proyecto.
 - Usa un constructor de sitios de tu elección para completar el proyecto. Asegúrate de incorporar todos los archivos de nuestro repositorio de GitHub.
 
-**Note:** This project's tests do not work when using `glitch.com`.
+**Nota:** Las pruebas de este proyecto no funcionan cuando se usa `glitch.com`.
 
 # --instructions--
 
-- Complete the necessary conversion logic in `/controllers/convertHandler.js`
-- Complete the necessary routes in `/routes/api.js`
+- Completa la lógica de conversión necesaria en `/controllers/convertHandler.js`
+- Completa las rutas necesarias en `/routes/api.js`
 - Copie el archivo `sample.env` a `.env` y establezca las variables apropiadamente
-- To run the tests automatically, add `NODE_ENV=test` in your `.env` file
+- Para ejecutar las pruebas automáticamente, añade `NODE_ENV=test` en tu archivo `.env`
 - Para ejecutar las pruebas en la consola, use el comando `npm run test`.
 
-Write the following tests in `tests/1_unit-tests.js`:
-
-- `convertHandler` should correctly read a whole number input.
-- `convertHandler` should correctly read a decimal number input.
-- `convertHandler` should correctly read a fractional input.
-- `convertHandler` should correctly read a fractional input with a decimal.
-- `convertHandler` should correctly return an error on a double-fraction (i.e. `3/2/3`).
-- `convertHandler` should correctly default to a numerical input of `1` when no numerical input is provided.
-- `convertHandler` should correctly read each valid input unit.
-- `convertHandler` should correctly return an error for an invalid input unit.
-- `convertHandler` should return the correct return unit for each valid input unit.
-- `convertHandler` should correctly return the spelled-out string unit for each valid input unit.
-- `convertHandler` should correctly convert `gal` to `L`.
-- `convertHandler` should correctly convert `L` to `gal`.
-- `convertHandler` should correctly convert `mi` to `km`.
-- `convertHandler` should correctly convert `km` to `mi`.
-- `convertHandler` should correctly convert `lbs` to `kg`.
-- `convertHandler` should correctly convert `kg` to `lbs`.
-
-Write the following tests in `tests/2_functional-tests.js`:
-
-- Convert a valid input such as `10L`: `GET` request to `/api/convert`.
-- Convert an invalid input such as `32g`: `GET` request to `/api/convert`.
-- Convert an invalid number such as `3/7.2/4kg`: `GET` request to `/api/convert`.
-- Convert an invalid number AND unit such as `3/7.2/4kilomegagram`: `GET` request to `/api/convert`.
-- Convert with no number such as `kg`: `GET` request to `/api/convert`.
+Escribe las siguientes pruebas en `tests/1_unit-tests.js`:
+
+- `convertHandler` debe leer correctamente una entrada de número entero.
+- `convertHandler` debe leer correctamente una entrada de número decimal.
+- `convertHandler` debe leer correctamente una entrada fraccional.
+- `convertHandler` debe leer correctamente una entrada fraccional con un decimal.
+- `convertHandler` debe devolver correctamente un error en una fracción doble (i.e. `3/2/3`).
+- `convertHandler` debe predeterminar correctamente una entrada numérica de `1` cuando no se proporciona ninguna entrada numérica.
+- `convertHandler` debe leer correctamente cada unidad de las entradas válidas.
+- `convertHandler` debe devolver correctamente un error por cada unidad de entrada no válida.
+- `convertHandler` debe devolver la unidad de retorno correcta para cada unidad de entrada válida.
+- `convertHandler` debe devolver correctamente la unidad de cadena deletreada para cada unidad de entrada válida.
+- `convertHandler` debe convertir correctamente `gal` a `L`.
+- `convertHandler` debe convertir correctamente `L` a `gal`.
+- `convertHandler` debe convertir correctamente `mi` a `km`.
+- `convertHandler` debe convertir correctamente `km` a `mi`.
+- `convertHandler` debe convertir correctamente `lbs` a `kg`.
+- `convertHandler` debe convertir correctamente `kg` a `lbs`.
+
+Escribir las siguientes pruebas en `tests/2_functional-tests.js`:
+
+- Convierte una entrada válida como `10L`: petición `GET` a `/api/convert`.
+- Convierte una entrada inválida como `32g`: petición `GET` a `/api/convert`.
+- Convierte un número inválido como `3/7.2/4kg`: petición `GET` a `/api/convert`.
+- Convierte un número Y una unidad no válidos como `3/7.2/4kilomegagram`: petición `GET` a `/api/convert`.
+- Convierte sin número tal como `kg`: petición `GET` a `/api/convert`.
 
 # --hints--
 
@@ -65,13 +65,13 @@ getUserInput => {
 };
 ```
 
-You can `GET` `/api/convert` with a single parameter containing an accepted number and unit and have it converted. (Hint: Split the input by looking for the index of the first character which will mark the start of the unit)
+Puedes realizar una petición `GET` `/api/convert` con un único parámetro que contenga un número y una unidad aceptados y que lo convierta. (Pista: Divide la entrada buscando el índice del primer carácter que marcará el inicio de la unidad)
 
 ```js
 
 ```
 
-You can convert `'gal'` to `'L'` and vice versa. (1 gal to 3.78541 L)
+Puedes convertir `'gal'` a `'L'` y viceversa. (1 gal a 3.78541 L)
 
 ```js
 async getUserInput => {
@@ -94,7 +94,7 @@ async getUserInput => {
 };
 ```
 
-You can convert `'lbs'` to `'kg'` and vice versa. (1 lbs to 0.453592 kg)
+Puedes convertir `'lbs'` a `'kg'` y viceversa. (1 lbs a 0.453592 kg)
 
 ```js
 async getUserInput => {
@@ -117,7 +117,7 @@ async getUserInput => {
 };
 ```
 
-You can convert `'mi'` to `'km'` and vice versa. (1 mi to 1.60934 km)
+Puedes convertir `'mi'` a `'km'` y viceversa. (1 mi a 1.60934 km)
 
 ```js
 async getUserInput => {
@@ -140,7 +140,7 @@ async getUserInput => {
 };
 ```
 
-All incoming units should be accepted in both upper and lower case, but should be returned in both the `initUnit` and `returnUnit` in lower case, except for liter, which should be represented as an uppercase `'L'`.
+Todas las unidades entrantes deben ser aceptadas en mayúsculas y minúsculas, pero debe ser devuelto en `initUnit` y `returnUnit` en minúsculas excepto por litro, que debe ser representado como una `'L'` mayúscula.
 
 ```js
 async getUserInput => {
@@ -163,7 +163,7 @@ async getUserInput => {
 };
 ```
 
-If the unit of measurement is invalid, returned will be `'invalid unit'`.
+Si la unidad de medida no es válida, se devolverá `'invalid unit'`.
 
 ```js
 async getUserInput => {
@@ -176,7 +176,7 @@ async getUserInput => {
 };
 ```
 
-If the number is invalid, returned will be `'invalid number'`.
+Si el número no es válido, devolverá `'invalid number'`.
 
 ```js
 async getUserInput => {
@@ -191,7 +191,7 @@ async getUserInput => {
 };
 ```
 
-If both the unit and number are invalid, returned will be `'invalid number and unit'`.
+Si tanto la unidad como el número son inválidos, se devolverá `'invalid number and unit'`.
 
 ```js
 async getUserInput => {
@@ -209,7 +209,7 @@ async getUserInput => {
 };
 ```
 
-You can use fractions, decimals or both in the parameter (ie. 5, 1/2, 2.5/6), but if nothing is provided it will default to 1.
+Puedes utilizar fracciones, decimales o ambos en el parámetro (es decir, 5, 1/2, 2.5/6), pero si no se proporciona nada, el valor predeterminado será 1.
 
 ```js
 async getUserInput => {
@@ -240,7 +240,7 @@ async getUserInput => {
 };
 ```
 
-Your return will consist of the `initNum`, `initUnit`, `returnNum`, `returnUnit`, and `string` spelling out units in the format `'{initNum} {initUnitString} converts to {returnNum} {returnUnitString}'` with the result rounded to 5 decimals.
+Tu devolución consistirá en `initNum`, `initUnit`, `returnNum`, `returnUnit`, y `string` detallando unidades en el formato `'{initNum} {initUnitString} converts to {returnNum} {returnUnitString}'` con el resultado redondeado a 5 decimales.
 
 ```js
 async getUserInput => {
@@ -257,7 +257,7 @@ async getUserInput => {
 };
 ```
 
-All 16 unit tests are complete and passing.
+Las 16 pruebas unitarias están completas y aprobadas.
 
 ```js
 async getUserInput => {
@@ -282,7 +282,7 @@ async getUserInput => {
 };
 ```
 
-All 5 functional tests are complete and passing.
+Las 5 pruebas funcionales están completas y aprobadas.
 
 ```js
 async getUserInput => {
diff --git a/curriculum/challenges/espanol/08-data-analysis-with-python/data-analysis-with-python-projects/medical-data-visualizer.md b/curriculum/challenges/espanol/08-data-analysis-with-python/data-analysis-with-python-projects/medical-data-visualizer.md
index 10e5232fe9..decba6b2ef 100644
--- a/curriculum/challenges/espanol/08-data-analysis-with-python/data-analysis-with-python-projects/medical-data-visualizer.md
+++ b/curriculum/challenges/espanol/08-data-analysis-with-python/data-analysis-with-python-projects/medical-data-visualizer.md
@@ -8,7 +8,7 @@ dashedName: medical-data-visualizer
 
 # --description--
 
-You will be <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-medical-data-visualizer/" target="_blank" rel="noopener noreferrer nofollow">working on this project with our Gitpod starter code</a>.
+Estarás <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-medical-data-visualizer/" target="_blank" rel="noopener noreferrer nofollow">trabajando en este proyecto con nuestro código inicial en Gitpod</a>.
 
 Todavía estamos desarrollando la parte interactiva del currículo de Python. Por ahora, aquí hay algunos vídeos en nuestro canal de YouTube freeCodeCamp.org que te enseñará todo lo que necesitas saber para completer este proyecto:
 
@@ -18,7 +18,7 @@ Todavía estamos desarrollando la parte interactiva del currículo de Python. Po
 
 # --instructions--
 
-In this project, you will visualize and make calculations from medical examination data using `matplotlib`, `seaborn`, and `pandas`. Los valores del conjunto de datos (dataset) se recogieron durante los exámenes médicos.
+En este proyecto, visualizarás y realizarás cálculos a partir de datos de exámenes médicos usando `matplotlib`, `seaborn` y `pandas`. Los valores del conjunto de datos (dataset) se recogieron durante los exámenes médicos.
 
 ## Descripción de datos
 
@@ -43,7 +43,7 @@ Nombre del archivo: medical_examination.csv
 
 ## Tareas
 
-Create a chart similar to `examples/Figure_1.png`, where we show the counts of good and bad outcomes for the `cholesterol`, `gluc`, `alco`, `active`, and `smoke` variables for patients with `cardio=1` and `cardio=0` in different panels.
+Crear un gráfico similar a `examples/Figure_1.png`, donde mostramos las cifras de resultados buenos y malos para las variables `cholesterol`, `gluc`, `alco`, `active` y `smoke` en los pacientes con `cardio=1` y `cardio=0` en diferentes paneles.
 
 Utiliza los datos para completar las siguientes tareas en `medical_data_visualizer.py`:
 
diff --git a/curriculum/challenges/espanol/08-data-analysis-with-python/data-analysis-with-python-projects/page-view-time-series-visualizer.md b/curriculum/challenges/espanol/08-data-analysis-with-python/data-analysis-with-python-projects/page-view-time-series-visualizer.md
index 187d7f6946..3dd63361da 100644
--- a/curriculum/challenges/espanol/08-data-analysis-with-python/data-analysis-with-python-projects/page-view-time-series-visualizer.md
+++ b/curriculum/challenges/espanol/08-data-analysis-with-python/data-analysis-with-python-projects/page-view-time-series-visualizer.md
@@ -8,11 +8,11 @@ dashedName: page-view-time-series-visualizer
 
 # --description--
 
-You will be <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-page-view-time-series-visualizer" target="_blank" rel="noopener noreferrer nofollow">working on this project with our Gitpod starter code</a>.
+Estarás <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-page-view-time-series-visualizer" target="_blank" rel="noopener noreferrer nofollow">trabajando en este proyecto con nuestro código inicial en Gitpod</a>.
 
 Todavía estamos desarrollando la parte interactiva del currículo de Python. Por el momento, aquí hay algunos videos en el canal de YouTube de freeCodeCamp.org que te enseñaran todo lo que necesitas saber para completar este proyecto:
 
-- <a href="https://www.freecodecamp.org/news/python-for-everybody/" target="_blank" rel="noopener noreferrer nofollow">Python for Everybody Video Course</a> (14 hours)
+- <a href="https://www.freecodecamp.org/news/python-for-everybody/" target="_blank" rel="noopener noreferrer nofollow">Curso en Vídeo de Python para Todos</a> (Duración: 14 horas)
 
 - <a href="https://www.freecodecamp.org/news/how-to-analyze-data-with-python-pandas/" target="_blank" rel="noopener noreferrer nofollow">How to Analyze Data with Python Pandas</a> (10 horas)
 
@@ -34,11 +34,11 @@ El boilerplate también incluye los comandos para guardar y devolver la imagen.
 
 ## Desarrollo
 
-Write your code in `time_series_visualizer.py`. For development, you can use `main.py` to test your code.
+Escribe tu código en `time_series_visualizer.py`. Para el desarrollo, puedes utilizar `main.py` para probar tu código.
 
 ## Pruebas
 
-The unit tests for this project are in `test_module.py`. Hemos importado las pruebas de `test_module.py` a `main.py` para tu conveniencia.
+Las pruebas unitarias para este proyecto están en `test_module.py`. Hemos importado las pruebas de `test_module.py` a `main.py` para tu conveniencia.
 
 ## Envío
 
diff --git a/curriculum/challenges/espanol/09-information-security/information-security-projects/port-scanner.md b/curriculum/challenges/espanol/09-information-security/information-security-projects/port-scanner.md
index 0dc6df49c5..b0df95899f 100644
--- a/curriculum/challenges/espanol/09-information-security/information-security-projects/port-scanner.md
+++ b/curriculum/challenges/espanol/09-information-security/information-security-projects/port-scanner.md
@@ -9,7 +9,7 @@ dashedName: port-scanner
 
 # --description--
 
-You will be <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-port-scanner" target="_blank" rel="noopener noreferrer nofollow">working on this project with our Gitpod starter code</a>.
+Estarás <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-port-scanner" target="_blank" rel="noopener noreferrer nofollow">trabajando en este proyecto con nuestro código inicial en Gitpod</a>.
 
 Todavía estamos desarrollando la parte interactiva del currículo de Python. Por ahora, aquí hay algunos videos en el canal de YouTube de freeCodeCamp.org que te enseñaran todo lo que necesitas saber para completar este proyecto:
 
diff --git a/curriculum/challenges/espanol/09-information-security/information-security-projects/secure-real-time-multiplayer-game.md b/curriculum/challenges/espanol/09-information-security/information-security-projects/secure-real-time-multiplayer-game.md
index 9d2076bf17..42d0a32aac 100644
--- a/curriculum/challenges/espanol/09-information-security/information-security-projects/secure-real-time-multiplayer-game.md
+++ b/curriculum/challenges/espanol/09-information-security/information-security-projects/secure-real-time-multiplayer-game.md
@@ -11,7 +11,7 @@ dashedName: secure-real-time-multiplayer-game
 Desarrolla un juego multijugador en tiempo real en 2D utilizando HTML Canvas API y Socket.io que sea funcionalmente similar a este: <a href="https://secure-real-time-multiplayer-game.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://secure-real-time-multiplayer-game.freecodecamp.rocks/</a>. Trabajar en este proyecto implicará escribir tu código utilizando uno de los siguientes métodos:
 
 -   Clona <a href="https://github.com/freeCodeCamp/boilerplate-project-secure-real-time-multiplayer-game/" target="_blank" rel="noopener noreferrer nofollow">este repositorio de GitHub</a> y completa tu proyecto localmente.
--   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-secure-real-time-multiplayer-game/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Utiliza <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-secure-real-time-multiplayer-game/" target="_blank" rel="noopener noreferrer nofollow">nuestro proyecto inicial en Gitpod</a> para completar tu proyecto.
 -   Utiliza un constructor de sitios de tu elección para completar el proyecto. Asegúrate de incorporar todos los archivos de nuestro repositorio GitHub.
 
 # --instructions--
diff --git a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/disable-client-side-caching-with-helmet.nocache.md b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/disable-client-side-caching-with-helmet.nocache.md
index 53096fe9f4..a446b5e02c 100644
--- a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/disable-client-side-caching-with-helmet.nocache.md
+++ b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/disable-client-side-caching-with-helmet.nocache.md
@@ -8,7 +8,7 @@ dashedName: disable-client-side-caching-with-helmet-nocache
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 Si esta lanzando una actualización para su sitio web, y quiere que los usuarios siempre descarguen la versión más reciente, puede (intentar) desactivar la cache en el navegador del cliente. Puede ser útil también en desarrollo. El almacenamiento de cache tiene beneficios de rendimiento, los cuales perderás, así que solo usa está opción cuando haya una necesidad real.
 
diff --git a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hash-and-compare-passwords-asynchronously.md b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hash-and-compare-passwords-asynchronously.md
index 06d9894516..357b7801eb 100644
--- a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hash-and-compare-passwords-asynchronously.md
+++ b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hash-and-compare-passwords-asynchronously.md
@@ -8,7 +8,7 @@ dashedName: hash-and-compare-passwords-asynchronously
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-bcrypt/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-bcrypt/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-bcrypt/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-bcrypt/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 Como el As hashing esta diseñado para ser computacionalmente intensivo, es recomendado hacerlo de manera asyncrona en tu servidor para evitar conexiones entrantes mientras se efectúa el hash. Todo lo que debes hacer para hash una contraseña asíncrona es llamar
 
diff --git a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hash-and-compare-passwords-synchronously.md b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hash-and-compare-passwords-synchronously.md
index 2f84ed7575..f62b62bfad 100644
--- a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hash-and-compare-passwords-synchronously.md
+++ b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hash-and-compare-passwords-synchronously.md
@@ -8,7 +8,7 @@ dashedName: hash-and-compare-passwords-synchronously
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-bcrypt/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-bcrypt/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-bcrypt/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-bcrypt/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 Picar sincrónicamente es igual de fácil de hacer, pero puede causar retrasos si se usa en el lado del servidor con un alto costo o si se pica con mucha frecuencia. Picar con este método es tan fácil como llamar
 
diff --git a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hide-potentially-dangerous-information-using-helmet.hidepoweredby.md b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hide-potentially-dangerous-information-using-helmet.hidepoweredby.md
index e45b1fe9c3..43473666b6 100644
--- a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hide-potentially-dangerous-information-using-helmet.hidepoweredby.md
+++ b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/hide-potentially-dangerous-information-using-helmet.hidepoweredby.md
@@ -8,7 +8,7 @@ dashedName: hide-potentially-dangerous-information-using-helmet-hidepoweredby
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 Los Hackers pueden aprovechar la vulnerabalidades conocidas en Express/Node, si ellos ven que tu sitio está siendo alimentado por Express. `X-Powered-By: Express` Se envía por defecto en cualquier solicitud proveniente de Express. Utilice el middleware de `helmet.hidePoweredBy()` para quitar la cabecera X-Powered-By.
 
diff --git a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/install-and-require-helmet.md b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/install-and-require-helmet.md
index 4f3bc72504..38b8711df7 100644
--- a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/install-and-require-helmet.md
+++ b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/install-and-require-helmet.md
@@ -11,7 +11,7 @@ dashedName: install-and-require-helmet
 Trabajar en estos desafíos implica escribir tu código usando uno de los siguientes métodos:
 
 - Clona <a href="https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">este repositorio de GitHub </a> y completa esos retos localmente.
-- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Usa <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">nuestro proyecto inicial de Gitpod</a> para completar estos desafíos.
 - Utilice un constructor de sitios de su elección para completar el proyecto. Asegúrese de incorporar todos los archivos de nuestro repositorio de GitHub.
 
 Helmet ayuda asegurar tus aplicaciones Express apps configurando varios encabezados HTTP.
diff --git a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/mitigate-the-risk-of-cross-site-scripting-xss-attacks-with-helmet.xssfilter.md b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/mitigate-the-risk-of-cross-site-scripting-xss-attacks-with-helmet.xssfilter.md
index c3cfec9442..521f6d92dd 100644
--- a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/mitigate-the-risk-of-cross-site-scripting-xss-attacks-with-helmet.xssfilter.md
+++ b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/mitigate-the-risk-of-cross-site-scripting-xss-attacks-with-helmet.xssfilter.md
@@ -9,11 +9,11 @@ dashedName: mitigate-the-risk-of-cross-site-scripting-xss-attacks-with-helmet-xs
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
 Secuencias de Comando de Sitio-Cruzado (XSS) es un ataque de tipo frecuente donde instrucciones maliciosas son insertadas dentro de páginas vulnerables, con el propósito de robar información sensible como información almacenada de sesión (cookies), o contraseñas.
 
-The basic rule to lower the risk of an XSS attack is simple: "Never trust user's input". Como desarrollador siempre deberías limpiar toda la información que provenga desde el exterior. Esto incluye datos provenientes de formularios, consultas urls GET, e incluso de cuerpos POST. Sanear significa que tu deberías encontrar y los caracteres que puedan ser peligrosos por ej.: &lt;, >.
+La regla básica para disminuir el riesgo de un ataque de XSS es simple: "Nunca confíes en la entrada del usuario". Como desarrollador siempre deberías limpiar toda la información que provenga desde el exterior. Esto incluye datos provenientes de formularios, consultas urls GET, e incluso de cuerpos POST. Sanear significa que tu deberías encontrar y los caracteres que puedan ser peligrosos por ej.: &lt;, >.
 
 Navegadores actuales pueden ayudar a mitigar el riesgo mediante la adopción de mejores estrategias de software. A menudo esto es configurable via cabeceras http.
 
diff --git a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/prevent-ie-from-opening-untrusted-html-with-helmet.ienoopen.md b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/prevent-ie-from-opening-untrusted-html-with-helmet.ienoopen.md
index 7efa4c2e82..d37e7b933f 100644
--- a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/prevent-ie-from-opening-untrusted-html-with-helmet.ienoopen.md
+++ b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/prevent-ie-from-opening-untrusted-html-with-helmet.ienoopen.md
@@ -8,9 +8,9 @@ dashedName: prevent-ie-from-opening-untrusted-html-with-helmet-ienoopen
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
-Algunas aplicaciones web servirán HTML no confiable en la descarga. Algunas versiones de Internet Explorer por defecto abren estos archivos HTML en el contexto de tu sitio web. Esto significa que una página HTML no confiable podría haber empezado a hacer cosas malas en el contenido de tus páginas. Este middleware ajusta la cabecera X-Download-Options en noopen. This will prevent IE users from executing downloads in the trusted site's context.
+Algunas aplicaciones web servirán HTML no confiable en la descarga. Algunas versiones de Internet Explorer por defecto abren estos archivos HTML en el contexto de tu sitio web. Esto significa que una página HTML no confiable podría haber empezado a hacer cosas malas en el contenido de tus páginas. Este middleware ajusta la cabecera X-Download-Options en noopen. Esto evitará que los usuarios de IE ejecuten descargas en el contexto de sitio de confianza.
 
 # --instructions--
 
diff --git a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/set-a-content-security-policy-with-helmet.contentsecuritypolicy.md b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/set-a-content-security-policy-with-helmet.contentsecuritypolicy.md
index 65f95fac35..40c9c80299 100644
--- a/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/set-a-content-security-policy-with-helmet.contentsecuritypolicy.md
+++ b/curriculum/challenges/espanol/09-information-security/information-security-with-helmetjs/set-a-content-security-policy-with-helmet.contentsecuritypolicy.md
@@ -1,6 +1,6 @@
 ---
 id: 587d8249367417b2b2512c3f
-title: Set a Content Security Policy with helmet.contentSecurityPolicy()
+title: Establece una Política de Seguridad de Contenido con helmet.contentSecurityPolicy()
 challengeType: 2
 forumTopicId: 301585
 dashedName: set-a-content-security-policy-with-helmet-contentsecuritypolicy
@@ -8,21 +8,21 @@ dashedName: set-a-content-security-policy-with-helmet-contentsecuritypolicy
 
 # --description--
 
-As a reminder, this project is being built upon the following starter project on <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
+Como recordatorio, este proyecto se está construyendo según el siguiente proyecto inicial en <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">Gitpod</a>, o clonando desde <a href="https://github.com/freeCodeCamp/boilerplate-infosec/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>.
 
-This challenge highlights one promising new defense that can significantly reduce the risk and impact of many type of attacks in modern browsers. By setting and configuring a Content Security Policy you can prevent the injection of anything unintended into your page. This will protect your app from XSS vulnerabilities, undesired tracking, malicious frames, and much more. CSP works by defining an allowed list of content sources which are trusted. You can configure them for each kind of resource a web page may need (scripts, stylesheets, fonts, frames, media, and so on...). There are multiple directives available, so a website owner can have a granular control. See HTML 5 Rocks, KeyCDN for more details. Unfortunately CSP is unsupported by older browsers.
+Este desafío marca una nueva defensa prometedora que puede significativamente reducir el riesgo e impacto de muchos tipos de ataques en navegadores modernos. Estableciendo y configurando una Política de Seguridad de Contenido puedes prevenir la inyección de cualquier no intencionado en tu página. Esto protegerá tu app de vulnerabilidades XSS, seguimientos no deseados, marcos maliciosos, y mucho más. CSP trabaja defendiendo una lista de fuentes de contenido permitidas las cuales son confiables. Puedes configurarlas para cada tipo de recurso que una página web pueda necesitar (scripts, hojas de estilo, fuentes, marcos, medios, etc...). Hay multiples directivas disponibles, entonces un propietario de un sitio web puede tener un control granular. Vea HTML 5 Rocks, KeyCDN para más detalles. Desafortunadamente CSP no está soportado por navegadores antiguos.
 
-By default, directives are wide open, so it’s important to set the defaultSrc directive as a fallback. Helmet supports both defaultSrc and default-src naming styles. The fallback applies for most of the unspecified directives.
+Por defecto, directivas son ampliamente abiertas, entonces es importante la directiva defaultSrc de reserva. Helmet suporta ambos defaultSrc y default-src estilos de nomenclatura. La reserva aplica para la mayoría de directivas no específicadas.
 
 # --instructions--
 
-In this exercise, use `helmet.contentSecurityPolicy()`. Configure it by adding a `directives` object. In the object, set the `defaultSrc` to `["'self'"]` (the list of allowed sources must be in an array), in order to trust only your website address by default. Also set the `scriptSrc` directive so that you only allow scripts to be downloaded from your website (`'self'`), and from the domain `'trusted-cdn.com'`.
+En este ejercicio, usa `helmet.contentSecurityPolicy()`. Configurala agregando un objeto `directives`. En eI objeto, establece el `defaultSrc` a `["'self'"]` (la lista de fuentes permitidas debe ser un arreglo), en orden para confiar solo en la dirección de tu sitio web por defecto. También establece la directiva `scriptSrc` para que permita solo descargar scripts desde tu sitio web (`'self'`), y desde el dominio `'trusted-cdn.com'`.
 
-Hint: in the `'self'` keyword, the single quotes are part of the keyword itself, so it needs to be enclosed in double quotes to be working.
+Pista: en la palabra clave `'self'`, las comillas simples son partes de la misma palabra clave, entonces se necesita ser encerradas entre comillas dobles para funcionar.
 
 # --hints--
 
-helmet.contentSecurityPolicy() middleware should be mounted correctly
+helmet.contentSecurityPolicy() middleware debe ser montado correctamente
 
 ```js
 (getUserInput) =>
@@ -36,7 +36,7 @@ helmet.contentSecurityPolicy() middleware should be mounted correctly
   );
 ```
 
-Your csp config is not correct. defaultSrc should be ["'self'"] and scriptSrc should be ["'self'", 'trusted-cdn.com']
+Tu configuración csp no es correcta. defaultSrc debería ser ["'self'"] y scriptSrc debe ser ["'self'", 'trusted-cdn.com']
 
 ```js
 (getUserInput) =>
diff --git a/curriculum/challenges/espanol/10-coding-interview-prep/data-structures/add-a-new-element-to-a-binary-search-tree.md b/curriculum/challenges/espanol/10-coding-interview-prep/data-structures/add-a-new-element-to-a-binary-search-tree.md
index 5b0e856622..0c00d00611 100644
--- a/curriculum/challenges/espanol/10-coding-interview-prep/data-structures/add-a-new-element-to-a-binary-search-tree.md
+++ b/curriculum/challenges/espanol/10-coding-interview-prep/data-structures/add-a-new-element-to-a-binary-search-tree.md
@@ -14,7 +14,7 @@ Primero, vamos a describir alguna terminología común que encontraremos con los
 
 Para comenzar, trataremos un tipo particular de árbol, el árbol binario. De hecho, en realidad discutiremos un árbol binario en particular, un árbol binario de búsqueda. Describiremos lo que esto significa. Mientras que la estructura de datos de árbol puede tener cualquier número de ramas en un solo nodo, un árbol binario solamente puede tener dos ramas para cada nodo. Además, un árbol binario de búsqueda se ordena respecto a los subárboles hijos, el valor de cada nodo en el subárbol izquierdo es menor o igual que el valor del nodo padre, y el valor de cada nodo en el subárbol derecho es mayor o igual que el valor del nodo padre. Es muy útil visualizar esta relación de orden para entenderla mejor:
 
-<div style='width: 100%; display: flex; justify-content: center; align-items: center;'><img alt="an example of a binary search tree" style='width: 100%; max-width: 350px; background-color: var(--gray-05);' src='https://user-images.githubusercontent.com/18563015/32136009-1e665d98-bbd6-11e7-9133-63184f9f9182.png'></div>
+<div style='width: 100%; display: flex; justify-content: center; align-items: center;'><img alt="un ejemplo de un árbol de búsqueda binario" style='width: 100%; max-width: 350px; background-color: var(--gray-05);' src='https://user-images.githubusercontent.com/18563015/32136009-1e665d98-bbd6-11e7-9133-63184f9f9182.png'></div>
 
 Ahora esta relación de orden es fácil de ver. Observa que cada valor a la izquierda de 8, el nodo raíz, es menor que 8, y cada valor a la derecha es mayor que 8. Además note que esta relación también es aplicada para cada de los subárboles. Por ejemplo, el primer hijo izquierdo es un subárbol. 3 es el nodo padre, y tiene exactamente dos nodos hijos - debido a las reglas de los árboles binarios de búsqueda, sabemos sin siquiera ver que el hijo izquierdo de este nodo ( y cualquiera de sus hijos) será menor que, y el hijo derecho(y cualquiera de sus hijos) será mayor que 3 (pero además menor que el valor de la raíz de la estructura).
 
diff --git a/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/build-a-pong-game.md b/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/build-a-pong-game.md
index d48df3b596..8d731d9c97 100644
--- a/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/build-a-pong-game.md
+++ b/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/build-a-pong-game.md
@@ -16,15 +16,15 @@ dashedName: build-a-pong-game
 
 **User Story:** I can control a paddle.
 
-**User Story:** The computer can control the other paddle.
+**Historia de usuario:** El computador puede controlar la otra paleta.
 
-**User Story:** The computer's paddle is unbeatable. It should never miss the ball.
+**Historia de usuario:** La paleta del computador es imbatible. Nunca debe fallar el balón.
 
-**User Story:** The game keeps track of the player and computer's score.
+**Historia de usuario:** Se mantiene registro de los puntajes del jugador y el computador.
 
 Cuando hayas terminado, incluye un enlace a tu proyecto en CodePen y haz clic en el botón "He completado este desafío".
 
-You can get feedback on your project by sharing it on the <a href="https://forum.freecodecamp.org/c/project-feedback/409" target="_blank" rel="noopener noreferrer nofollow">freeCodeCamp forum</a>.
+Puedes recibir retroalimentación de tu proyecto compartiendolo en el <a href="https://forum.freecodecamp.org/c/project-feedback/409" target="_blank" rel="noopener noreferrer nofollow">foro de freeCodeCamp</a>.
 
 # --solutions--
 
diff --git a/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/build-a-recipe-box.md b/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/build-a-recipe-box.md
index 6f266f91c9..20a52e224d 100644
--- a/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/build-a-recipe-box.md
+++ b/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/build-a-recipe-box.md
@@ -8,23 +8,23 @@ dashedName: build-a-recipe-box
 
 # --description--
 
-**Objective:** Build an app that is functionally similar to this: <a href="https://codepen.io/freeCodeCamp/full/dNVazZ/" target="_blank" rel="noopener noreferrer nofollow">https://codepen.io/freeCodeCamp/full/dNVazZ/</a>.
+**Objetivo:** Construir un aplicación que sea funcionalmente similar a ésta: <a href="https://codepen.io/freeCodeCamp/full/dNVazZ/" target="_blank" rel="noopener noreferrer nofollow">https://codepen.io/freeCodeCamp/full/dNVazZ/</a>.
 
-Fulfill the below user stories and get all of the tests to pass. Utiliza cualquier librería o API que necesites. Dale tu propio estilo personal.
+Completa las historias de los usuarios que están aquí abajo y haz que pasen todas las pruebas. Utiliza cualquier librería o API que necesites. Dale tu propio estilo personal.
 
-**User Story:** I can create recipes that have names and ingredients.
+**Historia de Usuario:** Puedo crear recetas que tienen nombres e ingredientes.
 
-**User Story:** I can see an index view where the names of all the recipes are visible.
+**Historia de Usuario:** Puedo ver un índice donde son visibles los nombres de todas las recetas.
 
-**User Story:** I can click into any of those recipes to view it.
+**Historia de Usuario:** Puedo clickear cualquiera de esas recetas para verla.
 
-**User Story:** I can edit these recipes.
+**Historia de Usuario:** Puedo editar esas recetas.
 
-**User Story:** I can delete these recipes.
+**Historia de Usuario:** Puedo eliminar esas recetas.
 
-**User Story:** All new recipes I add are saved in my browser's local storage. If I refresh the page, these recipes will still be there.
+**Historia de Usuario:** Todas las nuevas recetas que agrego están guardadas en el almacenamiento local (local storage) de mi navegador. Si actualizo la página, estas recetas seguirán ahí.
 
-**Hint:** You should prefix your local storage keys on CodePen, i.e. `_username_recipes`
+**Sugerencia:** Debes prefijar tus claves de almacenamiento local en CodePen, es decir, `_username_recipes`
 
 Cuando hayas terminado, incluye un enlace a tu proyecto en CodePen y haz clic en el botón "He completado este desafío".
 
diff --git a/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/chart-the-stock-market.md b/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/chart-the-stock-market.md
index 650954b6ec..5a5f574d39 100644
--- a/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/chart-the-stock-market.md
+++ b/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/chart-the-stock-market.md
@@ -8,19 +8,19 @@ dashedName: chart-the-stock-market
 
 # --description--
 
-Build a full stack JavaScript app that is functionally similar to this: <a href="https://chart-the-stock-market.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://chart-the-stock-market.freecodecamp.rocks/</a>. Utiliza un constructor de sitios de tu elección para completar el proyecto.
+Construye una aplicación full stack de JavaScript que sea funcionalmente similar a esta: <a href="https://chart-the-stock-market.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://chart-the-stock-market.freecodecamp.rocks/</a>. Utiliza un constructor de sitios de tu elección para completar el proyecto.
 
 Estas son las historias de usuario específicas que debes implementar para este proyecto:
 
-**User Story:** You can view a graph displaying the recent trend lines for each added stock.
+**Historia del usuario:** Puedes ver un gráfico con las recientes líneas de tendencia por cada stock agregado.
 
-**User Story:** You can add new stocks by their symbol name.
+**Historia de Usuario:** Puedes agregar nuevas acciones desde su nombre simbólico.
 
-**User Story:** You can remove stocks.
+**Historia de Usuario:** Puedes eliminar acciones.
 
-**User Story:** You can see changes in real-time when any other user adds or removes a stock. For this you will need to use Web Sockets.
+**Historia de Usuario:** Puedes ver los cambios en tiempo real cuando otro usuario agrega o quita una acción. Para ésto, necesitarás usar Websockets.
 
-Cuando hayas terminado, asegúrate de que un demo funcional de tu proyecto esté alojado en algún lugar público. Then submit the URL to it in the Solution Link field. Optionally, also submit a link to your project's source code in the GitHub Link field.
+Cuando hayas terminado, asegúrate de que un demo funcional de tu proyecto esté alojado en algún lugar público. Luego, envía la URL a éste, en el link del campo Solución. Opcionalmente, también envía un enlace al código fuente de tu proyecto en el campo GitHub Link.
 
 # --solutions--
 
diff --git a/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/use-the-twitch-json-api.md b/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/use-the-twitch-json-api.md
index f32ec9909a..7bf0b374d5 100644
--- a/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/use-the-twitch-json-api.md
+++ b/curriculum/challenges/espanol/10-coding-interview-prep/take-home-projects/use-the-twitch-json-api.md
@@ -8,25 +8,25 @@ dashedName: use-the-twitch-json-api
 
 # --description--
 
-**Objective:** Build an app that is functionally similar to this: <a href="https://codepen.io/freeCodeCamp/full/Myvqmo/" target="_blank" rel="noopener noreferrer nofollow">https://codepen.io/freeCodeCamp/full/Myvqmo/</a>.
+**Objetivo:** Construye una aplicación que sea funcionalmente similar a esta: <a href="https://codepen.io/freeCodeCamp/full/Myvqmo/" target="_blank" rel="noopener noreferrer nofollow">https://codepen.io/freeCodeCamp/full/Myvqmo/</a>.
 
-The Twitch API is a RESTful API that lets developers build creative integrations for the broader Twitch community.
+La API de Twitch es una API RESTful que permite a los desarrolladores construir integraciones creativas para la comunidad de Twitch más amplia.
 
-Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style.
+Completa las siguientes historias de usuario y consigue que todas las pruebas pasen. Utiliza cualquier librería o API que necesites. Dale tu propio estilo.
 
-**User Story:** I can see whether freeCodeCamp is currently streaming on Twitch.tv.
+**Historia del usuario:** Puedo ver si freeCodeCamp está transmitiendo en Twitch.tv.
 
-**User Story:** I can click the status output and be sent directly to the freeCodeCamp's Twitch.tv channel.
+**Historia del usuario:** Puedo hacer clic en la salida del estado y ser enviado directamente al canal Twitch.tv de freeCodeCamp.
 
-**User Story:** If a Twitch user is currently streaming, I can see additional details about what they are streaming.
+**Historia del usuario:** Si un usuario de Twitch está transmitiendo actualmente, puedo ver detalles adicionales sobre lo que está transmitiendo.
 
-**Hint:** Here's an array of the Twitch.tv usernames of people who regularly stream: `["ESL_SC2", "OgamingSC2", "cretetion", "freecodecamp", "storbeck", "habathcx", "RobotCaleb", "noobs2ninjas"]`
+**Sugerencia:** Aquí hay un arreglo de los nombres de usuario Twitch.tv de las personas que regularmente transmiten: `["ESL_SC2", "OgamingSC2", "cretetion", "freecodecamp", "storbeck", "habathcx", "RobotCaleb", "noobs2ninjas"]`
 
-**UPDATE:** Due to a change in conditions on API usage, Twitch.tv requires an API key, but we've built a workaround. Use <a href="https://twitch-proxy.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://twitch-proxy.freecodecamp.rocks/</a> instead of Twitch's API base URL and you'll still be able to get account information, without needing to sign up for an API key.
+**ACTUALIZACIÓN:** Debido a un cambio en las condiciones de uso de la API, Twitch.tv requiere una clave API, pero hemos creado una solución para ello. Usa <a href="https://twitch-proxy.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://twitch-proxy.freecodecamp. ocks/</a> en lugar de la URL base de la API de Twitter y todavía podrá obtener información de la cuenta, sin necesidad de registrarse en una clave API.
 
 Cuando hayas terminado, incluye un enlace a tu proyecto en CodePen y haz clic en el botón "He completado este desafío".
 
-You can get feedback on your project by sharing it on the <a href="https://forum.freecodecamp.org/c/project-feedback/409" target="_blank" rel="noopener noreferrer nofollow">freeCodeCamp forum</a>.
+Puedes obtener opiniones de tu proyecto compartiéndolo en el <a href="https://forum.freecodecamp.org/c/project-feedback/409" target="_blank" rel="noopener noreferrer nofollow">foro freeCodeCamp</a>.
 
 # --solutions--
 
diff --git a/curriculum/challenges/espanol/11-machine-learning-with-python/machine-learning-with-python-projects/neural-network-sms-text-classifier.md b/curriculum/challenges/espanol/11-machine-learning-with-python/machine-learning-with-python-projects/neural-network-sms-text-classifier.md
index f347d6df3b..0091b0425e 100644
--- a/curriculum/challenges/espanol/11-machine-learning-with-python/machine-learning-with-python-projects/neural-network-sms-text-classifier.md
+++ b/curriculum/challenges/espanol/11-machine-learning-with-python/machine-learning-with-python-projects/neural-network-sms-text-classifier.md
@@ -8,7 +8,7 @@ dashedName: neural-network-sms-text-classifier
 
 # --description--
 
-You will be <a href="https://colab.research.google.com/github/freeCodeCamp/boilerplate-neural-network-sms-text-classifier/blob/master/fcc_sms_text_classification.ipynb" target="_blank" rel="noopener noreferrer nofollow">working on this project with Google Colaboratory</a>.
+Estarás <a href="https://colab.research.google.com/github/freeCodeCamp/boilerplate-neural-network-sms-text-classifier/blob/master/fcc_sms_text_classification.ipynb" target="_blank" rel="noopener noreferrer nofollow">trabajando en este proyecto con Google Colaboratory</a>.
 
 Después de acceder al enlace, crea una copia del cuaderno ya sea en tu propia cuenta o de manera local. Una vez hayas completado el proyecto y superes el test (incluido en el enlace), envía el enlace del proyecto a continuación. Si envias un enlace a Google Colaboratory, asegúrate de que activas el uso compartido para "cualquiera con el enlace."
 
@@ -16,17 +16,17 @@ Todavía estamos desarrollando el contenido instructivo interactivo para el plan
 
 # --instructions--
 
-In this challenge, you need to create a machine learning model that will classify SMS messages as either "ham" or "spam". A "ham" message is a normal message sent by a friend. A "spam" message is an advertisement or a message sent by a company.
+En este desafío, necesitas crear un modelo de aprendizaje automático que clasifique los mensajes SMS como "jamón" o "spam". Un mensaje "ham" es un mensaje normal enviado por un amigo. Un mensaje "spam" es un anuncio o un mensaje enviado por una empresa.
 
-You should create a function called `predict_message` that takes a message string as an argument and returns a list. The first element in the list should be a number between zero and one that indicates the likeliness of "ham" (0) or "spam" (1). The second element in the list should be the word "ham" or "spam", depending on which is most likely.
+Debes crear una función llamada `predict_message` que toma una cadena de mensaje como argumento y devuelve una lista. El primer elemento de la lista debe ser un número entre cero y uno que indique la probabilidad de "jamón" (0) o "spam" (1). El segundo elemento de la lista debe ser la palabra "jamón" o "spam", dependiendo de cuál sea más probable.
 
-For this challenge, you will use the <a href="http://www.dt.fee.unicamp.br/~tiago/smsspamcollection/" target="_blank" rel="noopener noreferrer nofollow">SMS Spam Collection</a> dataset. The dataset has already been grouped into train data and test data.
+Para este desafío, usarás el conjunto de datos <a href="http://www.dt.fee.unicamp.br/~tiago/smsspamcollection/" target="_blank" rel="noopener noreferrer nofollow">SMS Spam Collection</a>. El conjunto de datos ya ha sido agrupado en datos de entrenamiento y de pruebas.
 
-The first two cells import the libraries and data. The final cell tests your model and function. Add your code in between these cells.
+Las dos primeras celdas importan las bibliotecas y los datos. La celda final prueba tu modelo y función. Escribe tu código entre esas celdas.
 
 # --hints--
 
-It should pass all Python tests.
+Debes pasar todas las pruebas de Python.
 
 ```js
 
diff --git a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/core-learning-algorithms-hidden-markov-models.md b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/core-learning-algorithms-hidden-markov-models.md
index 2adf4b7055..ba19203ca2 100644
--- a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/core-learning-algorithms-hidden-markov-models.md
+++ b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/core-learning-algorithms-hidden-markov-models.md
@@ -1,6 +1,6 @@
 ---
 id: 5e8f2f13c4cdbe86b5c72d90
-title: 'Core Learning Algorithms: Hidden Markov Models'
+title: 'Algoritmos de Aprendizaje Central: Modelos Markov Ocultos'
 challengeType: 11
 videoId: IZg24y4wEPY
 bilibiliIds:
@@ -14,19 +14,19 @@ dashedName: core-learning-algorithms-hidden-markov-models
 
 ## --text--
 
-What makes a Hidden Markov model different than linear regression or classification?
+¿Qué hace a un modelo de Markov oculto diferente de una regresión o clasificación lineal?
 
 ## --answers--
 
-It uses probability distributions to predict future events or states.
+Usa distribuciones de probabilidades para predecir eventos o estados futuros.
 
 ---
 
-It analyzes the relationship between independent and dependent variables to make predictions.
+Analiza la relación entre entre variables dependientes e independientes para hacer predicciones.
 
 ---
 
-It separates data points into separate categories.
+Separa los puntos de datos en categorías separadas.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/core-learning-algorithms.md b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/core-learning-algorithms.md
index 337151e060..8d8f82f735 100644
--- a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/core-learning-algorithms.md
+++ b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/core-learning-algorithms.md
@@ -12,7 +12,7 @@ dashedName: core-learning-algorithms
 
 # --description--
 
-The next few video lessons will reference [this Colab notebook](https://colab.research.google.com/drive/15Cyy2H7nT40sGR7TBN5wBvgTd57mVKay#forceEdit=true&sandboxMode=true).
+Las próximas videolecciones referenciarán [este cuaderno de Colab](https://colab.research.google.com/drive/15Cyy2H7nT40sGR7TBN5wBvgTd57mVKay#forceEdit=true&sandboxMode=true).
 
 # --question--
 
diff --git a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/introduction-machine-learning-fundamentals.md b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/introduction-machine-learning-fundamentals.md
index 61248b976a..b51f5582ba 100644
--- a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/introduction-machine-learning-fundamentals.md
+++ b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/introduction-machine-learning-fundamentals.md
@@ -1,6 +1,6 @@
 ---
 id: 5e8f2f13c4cdbe86b5c72d87
-title: 'Introduction: Machine Learning Fundamentals'
+title: 'Introducción: Fundamentos del aprendizaje automático'
 challengeType: 11
 videoId: KwL1qTR5MT8
 bilibiliIds:
@@ -14,19 +14,19 @@ dashedName: introduction-machine-learning-fundamentals
 
 ## --text--
 
-Which statement below is **false**?
+¿Qué afirmación es **falso**?
 
 ## --answers--
 
-Neural networks are modeled after the way the human brain works.
+Las redes neurológicas se modelan según la forma en que funciona el cerebro humano.
 
 ---
 
-Computer programs that play tic-tac-toe or chess against human players are examples of simple artificial intelligence.
+Los programas informáticos que juegan con el dedo en la mano o el ajedrez contra jugadores humanos son ejemplos de una simple inteligencia artificial.
 
 ---
 
-Machine learning is a subset of artificial intelligence.
+El aprendizaje automático es un subconjunto de la inteligencia artificial.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/natural-language-processing-with-rnns-training-the-model.md b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/natural-language-processing-with-rnns-training-the-model.md
index a2d0858bab..11bee28515 100644
--- a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/natural-language-processing-with-rnns-training-the-model.md
+++ b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/natural-language-processing-with-rnns-training-the-model.md
@@ -1,6 +1,6 @@
 ---
 id: 5e8f2f13c4cdbe86b5c72da2
-title: 'Natural Language Processing With RNNs: Training the Model'
+title: 'Procesamiento del lenguaje natural con RNNs: Entrenando el modelo'
 challengeType: 11
 videoId: hEUiK7j9UI8
 bilibiliIds:
@@ -14,7 +14,7 @@ dashedName: natural-language-processing-with-rnns-training-the-model
 
 ## --text--
 
-Fill in the blanks below to save your model's checkpoints in the `./checkpoints` directory and call the latest checkpoint for training:
+Rellena los siguientes espacios en blanco para guardar los puntos de control de tu modelo en el directorio `./checkpoints` y llama al último punto de control para el entrenamiento:
 
 ```py
 checkpoint_dir = __A__
diff --git a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/neural-networks-optimizers.md b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/neural-networks-optimizers.md
index c5da846ac0..a6205a8cfd 100644
--- a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/neural-networks-optimizers.md
+++ b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/neural-networks-optimizers.md
@@ -1,6 +1,6 @@
 ---
 id: 5e8f2f13c4cdbe86b5c72d94
-title: 'Neural Networks: Optimizers'
+title: 'Redes Neurales: Optimizadores'
 challengeType: 11
 videoId: hdOtRPQe1o4
 bilibiliIds:
@@ -14,19 +14,19 @@ dashedName: neural-networks-optimizers
 
 ## --text--
 
-What is an optimizer function?
+¿Qué es una función optimizador?
 
 ## --answers--
 
-A function that increases the accuracy of a model's predictions.
+Una función que aumenta la precisión de las predicciones de un modelo.
 
 ---
 
-A function that implements the gradient descent and backpropagation algorithms for you.
+Una función que implementa los algoritmos de descenso y retropropagación degradados para usted.
 
 ---
 
-A function that reduces the time a model needs to train.
+Una función que reduce el tiempo que un modelo necesita entrenar.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/neural-networks-with-tensorflow.md b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/neural-networks-with-tensorflow.md
index 2f2ea5c714..1c6a9ca786 100644
--- a/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/neural-networks-with-tensorflow.md
+++ b/curriculum/challenges/espanol/11-machine-learning-with-python/tensorflow/neural-networks-with-tensorflow.md
@@ -1,6 +1,6 @@
 ---
 id: 5e8f2f13c4cdbe86b5c72d92
-title: Neural Networks with TensorFlow
+title: Redes Neurales con TensorFlow
 challengeType: 11
 videoId: uisdfrNrZW4
 bilibiliIds:
@@ -12,25 +12,25 @@ dashedName: neural-networks-with-tensorflow
 
 # --description--
 
-The next few video lessons will reference [this Colab notebook](https://colab.research.google.com/drive/1m2cg3D1x3j5vrFc-Cu0gMvc48gWyCOuG#forceEdit=true&sandboxMode=true).
+Las próximas videolecciones referenciarán [este cuaderno de Colab](https://colab.research.google.com/drive/1m2cg3D1x3j5vrFc-Cu0gMvc48gWyCOuG#forceEdit=true&sandboxMode=true).
 
 # --question--
 
 ## --text--
 
-A densely connected neural network is one in which...:
+Una red neuronal densamente conectada es aquella en la cual...:
 
 ## --answers--
 
-all the neurons in the current layer are connected to one neuron in the previous layer.
+todas las neuronas de la capa actual están conectadas a una neurona en la capa anterior.
 
 ---
 
-all the neurons in each layer are connected randomly.
+todas las neuronas de cada capa se conectan al azar.
 
 ---
 
-all the neurons in the current layer are connected to every neuron in the previous layer.
+todas las neuronas de la capa actual están conectadas a una neurona en la capa anterior.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/espanol/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md b/curriculum/challenges/espanol/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
index c24cc9ea6d..ebf26c9af2 100644
--- a/curriculum/challenges/espanol/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
+++ b/curriculum/challenges/espanol/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
@@ -8,7 +8,7 @@ dashedName: build-a-periodic-table-database
 
 # --description--
 
-Este es uno de los proyectos necesarios para obtener su certificación. Para este proyecto, creará Bash un script para obtener información sobre elementos químicos de una base de datos de tabla periódica.
+Este es uno de los proyectos necesarios para obtener su certificación. For this project, you will create a Bash script to get information about chemical elements from a periodic table database.
 
 # --instructions--
 
diff --git a/curriculum/challenges/espanol/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md b/curriculum/challenges/espanol/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
index 254763ddd4..e05a2fc106 100644
--- a/curriculum/challenges/espanol/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
+++ b/curriculum/challenges/espanol/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
@@ -9,6 +9,8 @@ dashedName: step-64
 
 Dentro del elemento `footer`, añade un elemento `p`. Después, anida un elemento anchor (`a`) en el elemento `p` que enlace a `https://www.freecodecamp.org` y tenga el texto `Visit our website`.
 
+Make sure that the link opens in a new tab by adding a `target` attribute with the value `_blank`.
+
 # --hints--
 
 No debes modificar el elemento `footer` existente.
@@ -43,6 +45,12 @@ Tu nuevo elemento `a` te debe enlazar a `https://www.freecodecamp.org`. Recuerda
 assert(document.querySelector("footer > p > a")?.href === "https://www.freecodecamp.org/");
 ```
 
+Your new `a` element should have the `target` attribute set to `_blank`.
+
+```js
+assert.equal(document.querySelector("footer > p > a")?.target, "_blank");
+```
+
 # --seed--
 
 ## --seed-contents--
diff --git a/curriculum/challenges/espanol/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md b/curriculum/challenges/espanol/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
index d2ad72a1ea..1b6ca05444 100644
--- a/curriculum/challenges/espanol/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
+++ b/curriculum/challenges/espanol/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
@@ -21,12 +21,12 @@ Remove `flex: 1` from `.item` and add `justify-content: space-between` to `.cont
 
 `justify-content` aligns items across the **main axis**. There are a few values that you can use here. You'll learn the rest of them in the reading assignments, but for now try changing it to center, which should center the boxes along the main axis.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see what is possible with the `justify-content` property. Read this [interactive article on MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) and play around with the different values of `justify-content` on the example.
 
+# --question--
+
 ## --text--
 
 How does applying `justify-content: space-between` to a flex container affect the positioning of its items?
diff --git a/curriculum/challenges/espanol/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md b/curriculum/challenges/espanol/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
index d3137b0af5..59acb55a29 100644
--- a/curriculum/challenges/espanol/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
+++ b/curriculum/challenges/espanol/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
@@ -17,12 +17,12 @@ To change the placement of items along the cross axis use `align-items`. Try get
 
 Because `justify-content` and `align-items` are based on the main and cross axis of your container, their behavior changes when you change the flex-direction of a flex-container. For example, when you change `flex-direction` to `column`, `justify-content` aligns vertically and `align-items` aligns horizontally. The most common behavior, however, is the default, i.e. `justify-content` aligns items horizontally (because the main axis defaults to horizontal), and `align-items` aligns them vertically. One of the biggest sticking points that beginners have with flexbox is confusion when this behavior changes.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see if you can figure out how `align-items` behaves when you change the `flex-direction` property to `column`.
 
+# --question--
+
 ## --text--
 
 When changing the `flex-direction` property to `column` in a flex container, how does `align-items` behave in relation to the flex items?
diff --git a/curriculum/challenges/espanol/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md b/curriculum/challenges/espanol/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
index 1adf9ce84f..49edeac0e4 100644
--- a/curriculum/challenges/espanol/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
+++ b/curriculum/challenges/espanol/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
@@ -9,12 +9,12 @@ dashedName: learn-block-and-inline-lesson-b
 
 Inline elements, however, do not start on a new line. They appear in line with whatever elements they are placed beside. A clear example of an inline element is a link, or `<a>` tag. If you stick one of these in the middle of a paragraph of text, it will behave like a part of the paragraph. <a  href="https://www.freecodecamp.org/" target="_blank">(Like this)</a> The link’s text will sit alongside other words in that paragraph. Additionally, padding and margin behave differently on inline elements. In general, you do not want to try to put extra padding or margin on inline elements.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Search the web for a list of `block` elements and a list of `inline` elements.
 
+# --question--
+
 ## --text--
 
 What is the difference between a `block` element and an `inline` element?
diff --git a/curriculum/challenges/espanol/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md b/curriculum/challenges/espanol/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
index cdd4d5aa87..e75492e9c1 100644
--- a/curriculum/challenges/espanol/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
+++ b/curriculum/challenges/espanol/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-block-and-inline-lesson-g
 
 # --description--
 
-Now that you have some basic understanding of `block` and inline `elements`, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
+Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
 
 # --question--
 
diff --git a/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md b/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
index 995073b8a2..a7a2ee9a51 100644
--- a/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
+++ b/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
@@ -21,12 +21,12 @@ New programmers often find problem solving the hardest skill to build. It's not
 
 The best way to improve your problem solving ability is by building experience by making lots and lots of programs. The more practice you have the better you'll be prepared to solve real world problems.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Read <a href="https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/" target="_blank">How to Think Like a Programmer - Lessons in Problem Solving</a> by Richard Reis.
 
+# --question--
+
 ## --text--
 
 According to V. Anton Spraul in "Think Like a Programmer," what is problem solving in programming?
diff --git a/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md b/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
index ae905ecf89..c57a7d43e8 100644
--- a/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
+++ b/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
@@ -25,11 +25,11 @@ Now that you know what you’re aiming to solve, don’t jump into coding just y
 
 The last question is where you will write out an algorithm to solve the problem. You can think of an algorithm as a recipe for solving a particular problem. It defines the steps that need to be taken by the computer to solve a problem in pseudocode.
 
-# --question--
-
-## --assignment--
+# --assignment--
 Watch <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">How to Begin Thinking Like a Programmer</a> by Coding Tech. It’s an hour long but packed full of information and definitely worth your time watching.
 
+# --question--
+
 ## --text--
 
 What should you do before starting to code according to the provided text?
diff --git a/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md b/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
index c837fd9658..082f2d51ae 100644
--- a/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
+++ b/curriculum/challenges/espanol/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
@@ -22,12 +22,12 @@ Print the value of the counter variable
 
 This is a basic program to demonstrate how pseudocode looks. There will be more examples of pseudocode included in the assignments.
 
+# --assignment--
 
-# --question--
-
-## --assignment--
 Read this <a href="https://builtin.com/data-science/pseudocode" target="_blank"> Pseudocode: What It Is and How to Write It</a> article from Built In.
 
+# --question--
+
 ## --text--
 
 What are the benefits of using pseudocode according to the linked article?
diff --git a/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md b/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
index 60c25af9a5..df1677d813 100644
--- a/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
+++ b/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-So far you have learned how to create questions with the verb to be. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
+So far you have learned how to create questions with the verb `to be`. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
 
 `You are a developer` -> `Are you a developer?`
 
diff --git a/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md b/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
index 9e7122d39d..41846bc67f 100644
--- a/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
+++ b/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
@@ -21,7 +21,7 @@ Which sentence is correct for describing one place near you?
 
 ### --retroalimentación--
 
-`There are` is used for plural nouns, and `bank` is singular. You’ll learn about there are in the next few lessons.
+`There are` is used for plural nouns, and `bank` is singular. You’ll learn about `there are` in the next few lessons.
 
 ---
 
diff --git a/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md b/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
index e8cb7d2947..fe1ca44d6b 100644
--- a/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
+++ b/curriculum/challenges/espanol/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
@@ -7,7 +7,7 @@ dashedName: task-112
 
 # --description--
 
-To elaborate a question using `there is` you just need to change the order of the verb to be, like so:
+To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so:
 
 `There is an ATM nearby` -> `Is there an ATM nearby?`
 
diff --git a/curriculum/challenges/espanol/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md b/curriculum/challenges/espanol/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
new file mode 100644
index 0000000000..7d664a8876
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
@@ -0,0 +1,25 @@
+---
+id: 5f1a4ef5d5d6b5ab580fc6ae
+title: Build a Celestial Bodies Database
+challengeType: 13
+url: freeCodeCamp/learn-celestial-bodies-database
+dashedName: lab-celestial-bodies-database
+---
+
+# --description--
+
+For this project, you will build a database of celestial bodies using PostgreSQL.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `universe.sql` file so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `universe.sql`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/espanol/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md b/curriculum/challenges/espanol/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
new file mode 100644
index 0000000000..9492b82cb4
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
@@ -0,0 +1,611 @@
+---
+id: 5a8b073d06fa14fcfde687aa
+title: Build an Exercise Tracker
+challengeType: 4
+dashedName: build-an-exercise-tracker
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://exercise-tracker.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://exercise-tracker.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+Your responses should have the following structures.
+
+Exercise:
+
+```js
+{
+  username: "fcc_test",
+  description: "test",
+  duration: 60,
+  date: "Mon Jan 01 1990",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+User:
+
+```js
+{
+  username: "fcc_test",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Log:
+
+```js
+{
+  username: "fcc_test",
+  count: 1,
+  _id: "5fb5853f734231456ccb3b05",
+  log: [{
+    description: "test",
+    duration: 60,
+    date: "Mon Jan 01 1990",
+  }]
+}
+```
+
+**Hint:** For the `date` property, the `toDateString` method of the `Date` API can be used to achieve the expected output.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  const url = getUserInput('url');
+  assert(
+    !/.*\/exercise-tracker\.freecodecamp\.rocks/.test(getUserInput('url'))
+  );
+};
+```
+
+You can `POST` to `/api/users` with form data `username` to create a new user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The returned response from `POST /api/users` with form data `username` will be an object with `username` and `_id` properties.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    assert.exists(_id);
+    assert.exists(username);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users` to get a list of all users.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `GET` request to `/api/users` returns an array.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    assert.isArray(users);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Each element in the array returned from `GET /api/users` is an object literal containing a user's `username` and `_id`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    const user = users[0];
+    assert.exists(user);
+    assert.exists(user.username);
+    assert.exists(user._id);
+    assert.isString(user.username);
+    assert.isString(user._id);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can `POST` to `/api/users/:_id/exercises` with form data `description`, `duration`, and optionally `date`. If no date is supplied, the current date will be used.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+  assert.isTrue(addRes.ok);
+  if(!addRes.ok) {
+    throw new Error(`${addRes.status} ${addRes.statusText}`)
+  };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+The response returned from `POST /api/users/:_id/exercises` will be the user object with the exercise fields added.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    if (addRes.ok) {
+      const actual = await addRes.json();
+      assert.deepEqual(actual, expected);
+      assert.isString(actual.description);
+      assert.isNumber(actual.duration);
+      assert.isString(actual.date);
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users/:_id/logs` to retrieve a full exercise log of any user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+    assert.isTrue(logRes.ok);
+    if(!logRes.ok) {
+      throw new Error(`${logRes.status} ${logRes.statusText}`)
+    };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A request to a user's log `GET /api/users/:_id/logs` returns a user object with a `count` property representing the number of exercises that belong to that user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if (logRes.ok) {
+        const { count } = await logRes.json();
+        assert(count);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A `GET` request to `/api/users/:_id/logs` will return the user object with a `log` array of all the exercises added.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  })
+  if(res.ok){
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok){
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+Each item in the `log` array that is returned from `GET /api/users/:_id/logs` is an object that should have a `description`, `duration`, and `date` properties.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + `/api/users`, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+     const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.exists(exercise);
+        assert.exists(exercise.description);
+        assert.exists(exercise.duration);
+        assert.exists(exercise.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `description` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.description);
+        assert.equal(exercise.description, expected.description);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `duration` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a number.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isNumber(exercise.duration);
+        assert.equal(exercise.duration, expected.duration);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `date` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string. Use the `dateString` format of the `Date` API.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toLocaleDateString("en-US", {
+        timeZone: "UTC", weekday: "short", month: "short",
+        day: "2-digit", year: "numeric"
+      }).replaceAll(',', '')
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.date);
+        assert.equal(exercise.date, expected.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can add `from`, `to` and `limit` parameters to a `GET /api/users/:_id/logs` request to retrieve part of the log of any user. `from` and `to` are dates in `yyyy-mm-dd` format. `limit` is an integer of how many logs to send back.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addExerciseRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    const addExerciseTwoRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-03`
+    });
+    if (addExerciseRes.ok && addExerciseTwoRes.ok) {
+      const logRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1989-12-31&to=1990-01-04`
+      );
+      if (logRes.ok) {
+        const { log } = await logRes.json();
+        assert.isArray(log);
+        assert.equal(2, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+      const limitRes = await fetch(
+        url + `/api/users/${_id}/logs?limit=1`
+      );
+      if (limitRes.ok) {
+        const { log } = await limitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${limitRes.status} ${limitRes.statusText}`);
+      }
+      const filterDateBeforeLimitRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1990-01-02&to=1990-01-04&limit=1`
+      );
+      if (filterDateBeforeLimitRes.ok) {
+        const { log } = await filterDateBeforeLimitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${filterDateBeforeLimitRes.status} ${filterDateBeforeLimitRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${res.status} ${res.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
diff --git a/curriculum/challenges/espanol/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md b/curriculum/challenges/espanol/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
new file mode 100644
index 0000000000..ef87dc6720
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
@@ -0,0 +1,25 @@
+---
+id: 602da04c22201c65d2a019f4
+title: Build a Number Guessing Game
+challengeType: 13
+url: freeCodeCamp/learn-number-guessing-game
+dashedName: lab-number-guessing-game
+---
+
+# --description--
+
+For this lab, you will use Bash scripting, PostgreSQL, and Git to create a number guessing game that runs in the terminal and saves user information.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `number_guess.sql` file, as well as your `number_guess.sh` file, so you can complete step 2. There will be instructions on how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `number_guess.sql`, `number_guess.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/espanol/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md b/curriculum/challenges/espanol/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
new file mode 100644
index 0000000000..5040e27424
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
@@ -0,0 +1,65 @@
+---
+id: bd7158d8c443edefaeb5bdff
+title: Build a Request Header Parser Microservice
+challengeType: 4
+dashedName: lab-request-header-parser-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://request-header-parser-microservice.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://request-header-parser-microservice.freecodecamp.rocks/</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/request-header-parser-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+A request to `/api/whoami` should return a JSON object with your IP address in the `ipaddress` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.ipaddress && data.ipaddress.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your preferred language in the `language` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.language && data.language.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your software in the `software` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.software && data.software.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/espanol/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md b/curriculum/challenges/espanol/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
new file mode 100644
index 0000000000..0fbf80a0bf
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
@@ -0,0 +1,107 @@
+---
+id: bd7158d8c443edefaeb5bd0e
+title: URL Shortener Microservice
+challengeType: 4
+dashedName: url-shortener-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://url-shortener-microservice.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://url-shortener-microservice.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+**HINT:** Do not forget to use a body parsing middleware to handle the POST requests. Also, you can use the function `dns.lookup(host, cb)` from the `dns` core module to verify a submitted URL.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/url-shortener-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+You can POST a URL to `/api/shorturl` and get a JSON response with `original_url` and `short_url` properties. Here's an example: `{ original_url : 'https://freeCodeCamp.org', short_url : 1}`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (res.ok) {
+    const { short_url, original_url } = await res.json();
+    assert.isNotNull(short_url);
+    assert.strictEqual(original_url, `${url}/?v=${urlVariable}`);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+When you visit `/api/shorturl/<short_url>`, you will be redirected to the original URL.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  let shortenedUrlVariable;
+  const postResponse = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (postResponse.ok) {
+    const { short_url } = await postResponse.json();
+    shortenedUrlVariable = short_url;
+  } else {
+    throw new Error(`${postResponse.status} ${postResponse.statusText}`);
+  }
+  const getResponse = await fetch(
+    url + '/api/shorturl/' + shortenedUrlVariable
+  );
+  if (getResponse) {
+    const { redirected, url } = getResponse;
+    assert.isTrue(redirected);
+    assert.strictEqual(url,fullUrl);
+  } else {
+    throw new Error(`${getResponse.status} ${getResponse.statusText}`);
+  }
+};
+```
+
+If you pass an invalid URL that doesn't follow the valid `http://www.example.com` format, the JSON response will contain `{ error: 'invalid url' }`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=ftp:/john-doe.invalidTLD`
+  });
+  if (res.ok) {
+    const { error } = await res.json();
+    assert.isNotNull(error);
+    assert.strictEqual(error.toLowerCase(), 'invalid url');
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
diff --git a/curriculum/challenges/espanol/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md b/curriculum/challenges/espanol/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
new file mode 100644
index 0000000000..d77442a1ba
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
@@ -0,0 +1,25 @@
+---
+id: 5f9771307d4d22b9d2b75a94
+title: Build a World Cup Database
+challengeType: 13
+url: freeCodeCamp/learn-world-cup-database
+dashedName: lab-world-cup-database
+---
+
+# --description--
+
+For this project, you will create a Bash script that enters information from World Cup games into PostgreSQL, then query the database for useful statistics.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `worldcup.sql` file, as well as your `insert_data.sh` and `queries.sh` files, so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `worldcup.sql`, `insert_data.sh`, `queries.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md b/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
index 51ea9e3069..753ee1a6bb 100644
--- a/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
@@ -7,9 +7,9 @@ dashedName: step-22
 
 # --description--
 
-Add another label with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
+Add another `label` with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
 
-Below the label element, add another checkbox input with the `id`, `name` and `value` attributes set to `"recommendation"`.
+Below the `label` element, add another checkbox `input` with the `id`, `name` and `value` attributes set to `"recommendation"`.
 
 # --hints--
 
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md b/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
index 42c425209d..80a23ca86d 100644
--- a/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
@@ -11,7 +11,7 @@ Next, add another `label` element with the text of `Location` and the `for` attr
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"location"`.
 
-Below that `input` element, add another `label` element with the text of `Reputation` and the for attribute set to `"reputation"`.
+Below that `input` element, add another `label` element with the text of `Reputation` and the `for` attribute set to `"reputation"`.
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"reputation"`.
 
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md b/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
index 69efa4832c..09e3e6e59b 100644
--- a/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
@@ -7,7 +7,7 @@ dashedName: step-28
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attributes:**
 
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md b/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
index 6549345d45..22b9a707be 100644
--- a/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
@@ -7,7 +7,7 @@ dashedName: step-31
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attribute:**
 
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
new file mode 100644
index 0000000000..237515fd88
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
@@ -0,0 +1,71 @@
+---
+id: 66c8ba41a77db20a93f9d7a1
+title: Step 1
+challengeType: 1
+dashedName: step-1
+---
+
+# --description--
+
+In this workshop, you'll review JavaScript conditionals by building a loan qualification checker app.
+
+The app will check whether the user is eligible for a duplex, car, and condo loan based on their annual income and credit score. A credit score is a number that represents how good you are at managing borrowed money.
+
+To get started, create the following variables and values.
+
+| Variable Name             | Value   |
+| ------------------------- | ------- |
+| `minIncomeForDuplex`      | `60000` |
+| `minCreditScoreForDuplex` | `700`   |
+| `minIncomeForCondo`       | `45000` |
+| `minCreditScoreForCondo`  | `680`   |
+| `minIncomeForCar`         | `30000` |
+| `minCreditScoreForCar`    | `650`   |
+
+# --hints--
+
+You should create a `minIncomeForDuplex` variable set to `60000`.
+
+```js
+assert.equal(minIncomeForDuplex, 60000);
+```
+
+You should create a `minCreditScoreForDuplex` set to `700`.
+
+```js
+assert.equal(minCreditScoreForDuplex, 700);
+```
+
+You should create a `minIncomeForCar` variable set to `30000`.
+
+```js
+assert.equal(minIncomeForCar, 30000);
+```
+
+You should create a `minCreditScoreForCar` variable set to `650`.
+
+```js
+assert.equal(minCreditScoreForCar, 650);
+```
+
+You should create a `minIncomeForCondo` variable set to `45000`.
+
+```js
+assert.equal(minIncomeForCondo, 45000);
+```
+
+You should create a `minCreditScoreForCondo` variable set to `680`.
+
+```js
+assert.equal(minCreditScoreForCondo, 680);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
new file mode 100644
index 0000000000..7755f823c4
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
@@ -0,0 +1,53 @@
+---
+id: 66c8ba975ee7230e29f6c4ac
+title: Step 2
+challengeType: 1
+dashedName: step-2
+---
+
+# --description--
+
+When the user is eligible for a loan, you'll want to display a message to them in the console.
+
+For that, you'll build out a function inside which you'll have some checks that'll return what loan the applicant is eligible for.
+
+Create an empty `getLoanMessage` function with an `annualIncome` and `creditScore` parameters.
+
+# --hints--
+
+You should create a `getLoanMessage` function
+
+```js
+assert.isFunction(getLoanMessage)
+```
+
+Your `getLoanMessage` function should have an `annualIncome` and `creditScore` as parameters.
+
+```js
+assert.match(getLoanMessage?.toString(), /\(\s*annualIncome,\s*creditScore\s*\)|\(\s*creditScore,\s*annualIncome\s*\)/);
+```
+
+`getLoanMessage` should be an empty function.
+
+```js
+assert.match(getLoanMessage?.toString(), /\{\s*\}/);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
new file mode 100644
index 0000000000..82a29d7cd9
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
@@ -0,0 +1,55 @@
+---
+id: 66c8ba975ee7230e29f6c4ad
+title: Step 3
+challengeType: 1
+dashedName: step-3
+---
+
+# --description--
+
+To check which loan a user is qualified for based on the `annualIncome` and `creditScore`, you have to use `if/else if` statement or a ternary right inside the `getLoanMessage` function. You'll then return the appropraite message in the block of each condition.
+
+Starting with the duplex loan, check if `annualIncome` is greater than or equal to `minIncomeForDuplex` AND if `creditScore` is greater than `minCreditScoreForDuplex`.
+
+If that condition is true, then the applicant is eligible for a duplex loan and the other loans. So, inside the check, return the string `"You qualify for a car, duplex and Condo loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string.
+
+```js
+assert.isString(getLoanMessage(65000, 750));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a duplex, condo, and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(65000, 750), "You qualify for a duplex, condo, and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a duplex loan.
+
+```js
+assert.strictEqual(getLoanMessage(59000, 700), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+function getLoanMessage(annualIncome, creditScore) {
+
+}
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
new file mode 100644
index 0000000000..638e6291a4
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4af
+title: Step 4
+challengeType: 1
+dashedName: step-4
+---
+
+# --description--
+
+If the applicant's annual income is greater than or equal to `minIncomeForCondo`, AND if their credit score is greater than or equal to `minCreditScoreForCondo`, then they qualify for a condo and car loan.
+
+Check if that's true in the `getLoanMessage` function. If it is, return the string `"You qualify for a condo and car loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a condo and car loan.
+
+```js
+assert.isString(getLoanMessage(45000, 680));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a condo and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 680), "You qualify for a condo and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a condo loan.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 650), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
new file mode 100644
index 0000000000..374ba7b8fe
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4b0
+title: Step 5
+challengeType: 1
+dashedName: step-5
+---
+
+# --description--
+
+Now, you should check if the applicant is qualified for a car loan only. If they're, return the string `"You qualify for a car loan."`.
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a car loan.
+
+```js
+assert.isString(getLoanMessage(30000, 650));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 650), "You qualify for a car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a car loan.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 600), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+--fcc-editable-region--
+  } 
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
new file mode 100644
index 0000000000..16e8c7baca
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
@@ -0,0 +1,54 @@
+---
+id: 66c8ba975ee7230e29f6c4b1
+title: Step 6
+challengeType: 1
+dashedName: step-6
+---
+
+# --description--
+
+If the applicant's annual income and credit score fall below `minIncomeForCar` and `minCreditScoreForCar`, then they don't qualify for any loan. So, return the string `"You don't qualify for any loans."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant doesn't qualify for any loan.
+
+```js
+assert.isString(getLoanMessage(25000, 550));
+```
+
+Your `getLoanMessage` function should return the string `"You don't qualify for any loans."` if the applicant does not meet the requirements for any loan.
+
+```js
+assert.strictEqual(getLoanMessage(15000, 600), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(25000, 550), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(20000, 500), "You don't qualify for any loans.");
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
new file mode 100644
index 0000000000..9d19f9ea4c
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
@@ -0,0 +1,165 @@
+---
+id: 66c8ba975ee7230e29f6c4b2
+title: Step 7
+challengeType: 1
+dashedName: step-7
+---
+
+# --description--
+
+Now, it is time to test out your `getLoanMessage` function.
+
+Use the table below to create `4` variables and their values:
+
+| Variable Name   | Value                        |
+| --------------- | ---------------------------- |
+| `duplexLoanMsg` | `getLoanMessage(85000, 850)` |
+| `condoLoanMsg`  | `getLoanMessage(65000, 690)` |
+| `carLoanMsg`    | `getLoanMessage(45000, 660)` |
+| `noLoanMsg`     | `getLoanMessage(25000, 550)` |
+
+After that, log each variable to the console to see the messages.
+
+With that, your loan qualification checker project is complete!
+
+# --hints--
+
+You should have a variable called `duplexLoanMsg`.
+
+```js
+assert.isNotNull(duplexLoanMsg);
+```
+
+Your `duplexLoanMsg` variable should be set to the result of `getLoanMessage(85000, 850)`.
+
+```js
+assert.equal(duplexLoanMsg, getLoanMessage(85000, 850));
+```
+
+You should log the `duplexLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(duplexLoanMsg\)/)
+```
+
+You should have a variable called `condoLoanMsg`.
+
+```js
+assert.isNotNull(condoLoanMsg);
+```
+
+Your `condoLoanMsg` variable should be set to the result of `getLoanMessage(65000, 690)`.
+
+```js
+assert.equal(condoLoanMsg, getLoanMessage(65000, 690));
+```
+
+You should log the `condoLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(condoLoanMsg\)/)
+```
+
+You should have a variable called `carLoanMsg`.
+
+```js
+assert.isNotNull(carLoanMsg);
+```
+
+Your `carLoanMsg` variable should be set to the result of `getLoanMessage(45000, 660)`.
+
+```js
+assert.equal(carLoanMsg, getLoanMessage(45000, 660));
+```
+
+You should log the `carLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(carLoanMsg\)/)
+```
+
+You should have a variable called `noLoanMsg`.
+
+```js
+assert.isNotNull(noLoanMsg);
+```
+
+Your `noLoanMsg` variable should be set to the result of `getLoanMessage(25000, 550)`.
+
+```js
+assert.equal(noLoanMsg, getLoanMessage(25000, 550));
+```
+
+You should log the `noLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(noLoanMsg\)/)
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
+
+# --solutions--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+const duplexLoanMsg = getLoanMessage(85000, 850)
+console.log(duplexLoanMsg)
+
+const condoLoanMsg = getLoanMessage(65000, 690)
+console.log(condoLoanMsg)
+
+const carLoanMsg = getLoanMessage(45000, 660)
+console.log(carLoanMsg)
+
+const noLoanMsg = getLoanMessage(25000, 550)
+console.log(noLoanMsg)
+```
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md b/curriculum/challenges/espanol/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
new file mode 100644
index 0000000000..4e11751ca0
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
@@ -0,0 +1,19 @@
+---
+id: 5f2c289f164c29556da632fd
+title: Build a Mario Database
+challengeType: 12
+url: freeCodeCamp/learn-relational-databases-by-building-a-mario-database
+dashedName: build-a-mario-database
+---
+
+# --description--
+
+In this 165-lesson workshop, you will learn the basics of a relational database by creating a PostgreSQL database filled with video game characters.
+
+# --instructions--
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
new file mode 100644
index 0000000000..8d4c90410d
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
@@ -0,0 +1,53 @@
+---
+id: 587d7fb3367417b2b2512bfb
+title: How to Use package.json, the Core of Any Node.js Project or npm Package
+challengeType: 2
+forumTopicId: 301528
+dashedName: how-to-use-package-json-the-core-of-any-node-js-project-or-npm-package
+---
+
+# --description--
+
+Working on these challenges will involve you writing your code using one of the following methods:
+
+- Clone <a href="https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete these challenges locally.
+- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+The `package.json` file is the center of any Node.js project or npm package. It stores information about your project. It consists of a single JSON object where information is stored in key-value pairs. There are only two required fields; `name` and `version`, but it’s good practice to provide additional information.
+
+You can create the `package.json` file from the terminal using the `npm init` command. This will run a guided setup. Using `npm init` with the `-y` flag will generate the file without having it ask any questions, `npm init -y`.
+
+If you look at the file tree of your project, you will find the `package.json` file on the top level of the tree. This is the file that you will be improving in the next couple of challenges.
+
+One of the most common pieces of information in this file is the `author` field. It specifies who created the project, and can consist of a string or an object with contact or other details. An object is recommended for bigger projects, but a simple string like the following example will do for this project.
+
+```json
+"author": "Jane Doe",
+```
+
+# --instructions--
+
+Add your name as the `author` of the project in the `package.json` file.
+
+**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (") and be separated with a comma (,).
+
+If you are using Gitpod, make sure the app is running and the preview window is open. Copy the preview window's URL and paste it into the Solution Link input below.
+
+# --hints--
+
+`package.json` should have a valid "author" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.author, '"author" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
new file mode 100644
index 0000000000..37d15d5261
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb3367417b2b2512bfc
+title: Add a Description to Your package.json
+challengeType: 2
+forumTopicId: 301522
+dashedName: add-a-description-to-your-package-json
+---
+
+# --description--
+
+The next part of a good package.json file is the `description` field; where a short, but informative description about your project belongs.
+
+If some day you plan to publish a package to npm, this is the string that should sell your idea to the user when they decide whether to install your package or not. However, that’s not the only use case for the description, it’s a great way to summarize what a project does. It’s just as important in any Node.js project to help other developers, future maintainers or even your future self understand the project quickly.
+
+Regardless of what you plan for your project, a description is definitely recommended. Here's an example:
+
+```json
+"description": "A project that does something awesome",
+```
+
+# --instructions--
+
+Add a `description` to the package.json file of your project.
+
+**Note:** Remember to use double-quotes for field-names (") and commas (,) to separate fields.
+
+# --hints--
+
+package.json should have a valid "description" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.description, '"description" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
new file mode 100644
index 0000000000..a001cdd477
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
@@ -0,0 +1,75 @@
+---
+id: 587d7fb4367417b2b2512bfd
+title: Add Keywords to Your package.json
+challengeType: 2
+forumTopicId: 301526
+dashedName: add-keywords-to-your-package-json
+---
+
+# --description--
+
+The `keywords` field is where you can describe your project using related keywords. Here's an example:
+
+```json
+"keywords": [ "descriptive", "related", "words" ],
+```
+
+As you can see, this field is structured as an array of double-quoted strings.
+
+# --instructions--
+
+Add an array of suitable strings to the `keywords` field in the package.json file of your project.
+
+One of the keywords should be "freecodecamp".
+
+# --hints--
+
+package.json should have a valid "keywords" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.keywords, '"keywords" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" field should be an Array
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.isArray(packJson.keywords, '"keywords" is not an array');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" should include "freecodecamp"
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.include(
+        packJson.keywords,
+        'freecodecamp',
+        '"keywords" does not include "freecodecamp"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
new file mode 100644
index 0000000000..7b09acd042
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
@@ -0,0 +1,39 @@
+---
+id: 587d7fb4367417b2b2512bfe
+title: Add a License to Your package.json
+challengeType: 2
+forumTopicId: 301523
+dashedName: add-a-license-to-your-package-json
+---
+
+# --description--
+
+The `license` field is where you inform users of what they are allowed to do with your project.
+
+Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do. Here's an example of the license field:
+
+```json
+"license": "MIT",
+```
+
+# --instructions--
+
+Fill the `license` field in the package.json file of your project as you find suitable.
+
+# --hints--
+
+package.json should have a valid "license" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.license, '"license" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
new file mode 100644
index 0000000000..f2e571faed
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
@@ -0,0 +1,37 @@
+---
+id: 587d7fb4367417b2b2512bff
+title: Add a Version to Your package.json
+challengeType: 2
+forumTopicId: 301525
+dashedName: add-a-version-to-your-package-json
+---
+
+# --description--
+
+A `version` is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example:
+
+```json
+"version": "1.2.0",
+```
+
+# --instructions--
+
+Add a `version` to the package.json file of your project.
+
+# --hints--
+
+package.json should have a valid "version" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.version, '"version" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
new file mode 100644
index 0000000000..161c60fe69
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
@@ -0,0 +1,68 @@
+---
+id: 587d7fb4367417b2b2512c00
+title: Expand Your Project with External Packages from npm
+challengeType: 2
+forumTopicId: 301527
+dashedName: expand-your-project-with-external-packages-from-npm
+---
+
+# --description--
+
+One of the biggest reasons to use a package manager, is their powerful dependency management. Instead of manually having to make sure that you get all dependencies whenever you set up a project on a new computer, npm automatically installs everything for you. But how can npm know exactly what your project needs? Meet the `dependencies` section of your package.json file.
+
+In this section, packages your project requires are stored using the following format:
+
+```json
+"dependencies": {
+  "package-name": "version",
+  "express": "4.14.0"
+}
+
+```
+
+# --instructions--
+
+Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file.
+
+**Note:** `@freecodecamp/example` is a faux package used as a learning tool.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.1.0"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^[\^\~]?1\.1\.0/,
+        'Wrong version of "@freecodecamp/example" installed. It should be 1.1.0'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
new file mode 100644
index 0000000000..deda9b82de
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
@@ -0,0 +1,64 @@
+---
+id: 587d7fb5367417b2b2512c01
+title: Manage npm Dependencies By Understanding Semantic Versioning
+challengeType: 2
+forumTopicId: 301529
+dashedName: manage-npm-dependencies-by-understanding-semantic-versioning
+---
+
+# --description--
+
+`Versions` of the npm packages in the dependencies section of your package.json file follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes projects can expect if they update.
+
+Knowing SemVer can be useful when you develop software that uses external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things that worked yesterday suddenly don’t work today. This is how Semantic Versioning works according to the official website:
+
+```json
+"package": "MAJOR.MINOR.PATCH"
+```
+
+The MAJOR version should increment when you make incompatible API changes. The MINOR version should increment when you add functionality in a backwards-compatible manner. The PATCH version should increment when you make backwards-compatible bug fixes. This means that PATCHes are bug fixes and MINORs add new features but neither of them break what worked before. Finally, MAJORs add changes that won’t work with earlier versions.
+
+# --instructions--
+
+In the dependencies section of your `package.json` file, change the version of `@freecodecamp/example` to match MAJOR version 1, MINOR version 2 and PATCH version 13
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.equal(
+        packJson.dependencies["@freecodecamp/example"],
+        '1.2.13',
+        'Wrong version of "@freecodecamp/example". It should be 1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
new file mode 100644
index 0000000000..8eae5f51ee
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c02
+title: Use the Tilde-Character to Always Use the Latest Patch Version of a Dependency
+challengeType: 2
+forumTopicId: 301532
+dashedName: use-the-tilde-character-to-always-use-the-latest-patch-version-of-a-dependency
+---
+
+# --description--
+
+In the last challenge, you told npm to only include a specific version of a package. That’s a useful way to freeze your dependencies if you need to make sure that different parts of your project stay compatible with each other. But in most use cases, you don’t want to miss bug fixes since they often include important security patches and (hopefully) don’t break things in doing so.
+
+To allow an npm dependency to update to the latest PATCH version, you can prefix the dependency’s version with the tilde (`~`) character. Here's an example of how to allow updates to any `1.3.x` version.
+
+```json
+"package": "~1.3.8"
+```
+
+# --instructions--
+
+In the package.json file, your current rule for how npm may upgrade `@freecodecamp/example` is to use a specific version (`1.2.13`). But now, you want to allow the latest `1.2.x` version.
+
+Use the tilde (`~`) character to prefix the version of `@freecodecamp/example` in your dependencies, and allow npm to update it to any new _patch_ release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"~1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\~1\.2\.13/,
+        'Wrong version of "@freecodecamp/example". It should be ~1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
new file mode 100644
index 0000000000..adc3014ea4
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c03
+title: Use the Caret-Character to Use the Latest Minor Version of a Dependency
+challengeType: 2
+forumTopicId: 301531
+dashedName: use-the-caret-character-to-use-the-latest-minor-version-of-a-dependency
+---
+
+# --description--
+
+Similar to how the tilde we learned about in the last challenge allows npm to install the latest PATCH for a dependency, the caret (`^`) allows npm to install future updates as well. The difference is that the caret will allow both MINOR updates and PATCHes.
+
+Your current version of `@freecodecamp/example` should be `~1.2.13` which allows npm to install to the latest `1.2.x` version. If you were to use the caret (^) as a version prefix instead, npm would be allowed to update to any `1.x.x` version.
+
+```json
+"package": "^1.3.8"
+```
+
+This would allow updates to any `1.x.x` version of the package.
+
+# --instructions--
+
+Use the caret (`^`) to prefix the version of `@freecodecamp/example` in your dependencies and allow npm to update it to any new MINOR release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"^1.x.x"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\^1\./,
+        'Wrong version of "@freecodecamp/example". It should be ^1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
new file mode 100644
index 0000000000..5f695eed88
--- /dev/null
+++ b/curriculum/challenges/espanol/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb5367417b2b2512c04
+title: Remove a Package from Your Dependencies
+challengeType: 2
+forumTopicId: 301530
+dashedName: remove-a-package-from-your-dependencies
+---
+
+# --description--
+
+You have now tested a few ways you can manage dependencies of your project by using the package.json's dependencies section. You have also included external packages by adding them to the file and even told npm what types of versions you want, by using special characters such as the tilde or the caret.
+
+But what if you want to remove an external package that you no longer need? You might already have guessed it, just remove the corresponding key-value pair for that package from your dependencies.
+
+This same method applies to removing other fields in your package.json as well.
+
+# --instructions--
+
+Remove the `@freecodecamp/example` package from your dependencies.
+
+**Note:** Make sure you have the right amount of commas after removing it.
+
+# --hints--
+
+`"dependencies"` should not include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.notProperty(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" still includes "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/german/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md b/curriculum/challenges/german/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
index fa2065c819..6667174c95 100644
--- a/curriculum/challenges/german/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
+++ b/curriculum/challenges/german/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
@@ -8,7 +8,7 @@ dashedName: build-a-periodic-table-database
 
 # --description--
 
-Dies ist eines der Projekte, die für den Erhalt der Zertifizierung erforderlich sind. In diesem Projekt erstellst du mit Bash ein Skript, das Informationen über chemische Elemente aus einer Datenbank des Periodensystems abruft.
+Dies ist eines der Projekte, die für den Erhalt der Zertifizierung erforderlich sind. For this project, you will create a Bash script to get information about chemical elements from a periodic table database.
 
 # --instructions--
 
diff --git a/curriculum/challenges/german/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md b/curriculum/challenges/german/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
index 55cc92c8d3..2fceb78181 100644
--- a/curriculum/challenges/german/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
+++ b/curriculum/challenges/german/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
@@ -9,6 +9,8 @@ dashedName: step-64
 
 Füge innerhalb des `footer` ein `p`-Element hinzu. Bette anschließend ein Ankerelement (`a`) im `p` ein, das mit `https://www.freecodecamp.org` verlinkt ist und den Text `Visit our website` enthält.
 
+Make sure that the link opens in a new tab by adding a `target` attribute with the value `_blank`.
+
 # --hints--
 
 Du solltest nicht das vorhandene `footer`-Element ändern.
@@ -43,6 +45,12 @@ Dein neues `a`-Element sollte zu `https://www.freecodecamp.org` verlinkt sein. D
 assert(document.querySelector("footer > p > a")?.href === "https://www.freecodecamp.org/");
 ```
 
+Your new `a` element should have the `target` attribute set to `_blank`.
+
+```js
+assert.equal(document.querySelector("footer > p > a")?.target, "_blank");
+```
+
 # --seed--
 
 ## --seed-contents--
diff --git a/curriculum/challenges/german/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md b/curriculum/challenges/german/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
index d2ad72a1ea..1b6ca05444 100644
--- a/curriculum/challenges/german/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
+++ b/curriculum/challenges/german/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
@@ -21,12 +21,12 @@ Remove `flex: 1` from `.item` and add `justify-content: space-between` to `.cont
 
 `justify-content` aligns items across the **main axis**. There are a few values that you can use here. You'll learn the rest of them in the reading assignments, but for now try changing it to center, which should center the boxes along the main axis.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see what is possible with the `justify-content` property. Read this [interactive article on MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) and play around with the different values of `justify-content` on the example.
 
+# --question--
+
 ## --text--
 
 How does applying `justify-content: space-between` to a flex container affect the positioning of its items?
diff --git a/curriculum/challenges/german/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md b/curriculum/challenges/german/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
index d3137b0af5..59acb55a29 100644
--- a/curriculum/challenges/german/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
+++ b/curriculum/challenges/german/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
@@ -17,12 +17,12 @@ To change the placement of items along the cross axis use `align-items`. Try get
 
 Because `justify-content` and `align-items` are based on the main and cross axis of your container, their behavior changes when you change the flex-direction of a flex-container. For example, when you change `flex-direction` to `column`, `justify-content` aligns vertically and `align-items` aligns horizontally. The most common behavior, however, is the default, i.e. `justify-content` aligns items horizontally (because the main axis defaults to horizontal), and `align-items` aligns them vertically. One of the biggest sticking points that beginners have with flexbox is confusion when this behavior changes.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see if you can figure out how `align-items` behaves when you change the `flex-direction` property to `column`.
 
+# --question--
+
 ## --text--
 
 When changing the `flex-direction` property to `column` in a flex container, how does `align-items` behave in relation to the flex items?
diff --git a/curriculum/challenges/german/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md b/curriculum/challenges/german/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
index 1adf9ce84f..49edeac0e4 100644
--- a/curriculum/challenges/german/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
+++ b/curriculum/challenges/german/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
@@ -9,12 +9,12 @@ dashedName: learn-block-and-inline-lesson-b
 
 Inline elements, however, do not start on a new line. They appear in line with whatever elements they are placed beside. A clear example of an inline element is a link, or `<a>` tag. If you stick one of these in the middle of a paragraph of text, it will behave like a part of the paragraph. <a  href="https://www.freecodecamp.org/" target="_blank">(Like this)</a> The link’s text will sit alongside other words in that paragraph. Additionally, padding and margin behave differently on inline elements. In general, you do not want to try to put extra padding or margin on inline elements.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Search the web for a list of `block` elements and a list of `inline` elements.
 
+# --question--
+
 ## --text--
 
 What is the difference between a `block` element and an `inline` element?
diff --git a/curriculum/challenges/german/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md b/curriculum/challenges/german/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
index cdd4d5aa87..e75492e9c1 100644
--- a/curriculum/challenges/german/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
+++ b/curriculum/challenges/german/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-block-and-inline-lesson-g
 
 # --description--
 
-Now that you have some basic understanding of `block` and inline `elements`, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
+Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
 
 # --question--
 
diff --git a/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md b/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
index 995073b8a2..a7a2ee9a51 100644
--- a/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
+++ b/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
@@ -21,12 +21,12 @@ New programmers often find problem solving the hardest skill to build. It's not
 
 The best way to improve your problem solving ability is by building experience by making lots and lots of programs. The more practice you have the better you'll be prepared to solve real world problems.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Read <a href="https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/" target="_blank">How to Think Like a Programmer - Lessons in Problem Solving</a> by Richard Reis.
 
+# --question--
+
 ## --text--
 
 According to V. Anton Spraul in "Think Like a Programmer," what is problem solving in programming?
diff --git a/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md b/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
index ae905ecf89..c57a7d43e8 100644
--- a/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
+++ b/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
@@ -25,11 +25,11 @@ Now that you know what you’re aiming to solve, don’t jump into coding just y
 
 The last question is where you will write out an algorithm to solve the problem. You can think of an algorithm as a recipe for solving a particular problem. It defines the steps that need to be taken by the computer to solve a problem in pseudocode.
 
-# --question--
-
-## --assignment--
+# --assignment--
 Watch <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">How to Begin Thinking Like a Programmer</a> by Coding Tech. It’s an hour long but packed full of information and definitely worth your time watching.
 
+# --question--
+
 ## --text--
 
 What should you do before starting to code according to the provided text?
diff --git a/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md b/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
index c837fd9658..082f2d51ae 100644
--- a/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
+++ b/curriculum/challenges/german/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
@@ -22,12 +22,12 @@ Print the value of the counter variable
 
 This is a basic program to demonstrate how pseudocode looks. There will be more examples of pseudocode included in the assignments.
 
+# --assignment--
 
-# --question--
-
-## --assignment--
 Read this <a href="https://builtin.com/data-science/pseudocode" target="_blank"> Pseudocode: What It Is and How to Write It</a> article from Built In.
 
+# --question--
+
 ## --text--
 
 What are the benefits of using pseudocode according to the linked article?
diff --git a/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md b/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
index bdc2416567..4a8f5d2d91 100644
--- a/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
+++ b/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-Bisher hast du gelernt, wie man Fragen mit dem Verb to be bildet. In Sätzen mit dem Verb `to be` (am, is, are) muss man nur die Reihenfolge von Substantiv und Verb ändern, um eine Frage zu bilden. Like this:
+So far you have learned how to create questions with the verb `to be`. In Sätzen mit dem Verb `to be` (am, is, are) muss man nur die Reihenfolge von Substantiv und Verb ändern, um eine Frage zu bilden. Like this:
 
 `You are a developer` -> `Are you a developer?`
 
diff --git a/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md b/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
index a890d35b9a..679acbfe32 100644
--- a/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
+++ b/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
@@ -21,7 +21,7 @@ Which sentence is correct for describing one place near you?
 
 ### --Feedback--
 
-`There are` is used for plural nouns, and `bank` is singular. You’ll learn about there are in the next few lessons.
+`There are` is used for plural nouns, and `bank` is singular. You’ll learn about `there are` in the next few lessons.
 
 ---
 
diff --git a/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md b/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
index 919eb64a7c..247b605d84 100644
--- a/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
+++ b/curriculum/challenges/german/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
@@ -7,7 +7,7 @@ dashedName: task-112
 
 # --description--
 
-To elaborate a question using `there is` you just need to change the order of the verb to be, like so:
+To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so:
 
 `There is an ATM nearby` -> `Is there an ATM nearby?`
 
diff --git a/curriculum/challenges/german/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md b/curriculum/challenges/german/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
new file mode 100644
index 0000000000..7d664a8876
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
@@ -0,0 +1,25 @@
+---
+id: 5f1a4ef5d5d6b5ab580fc6ae
+title: Build a Celestial Bodies Database
+challengeType: 13
+url: freeCodeCamp/learn-celestial-bodies-database
+dashedName: lab-celestial-bodies-database
+---
+
+# --description--
+
+For this project, you will build a database of celestial bodies using PostgreSQL.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `universe.sql` file so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `universe.sql`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/german/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md b/curriculum/challenges/german/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
new file mode 100644
index 0000000000..9492b82cb4
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
@@ -0,0 +1,611 @@
+---
+id: 5a8b073d06fa14fcfde687aa
+title: Build an Exercise Tracker
+challengeType: 4
+dashedName: build-an-exercise-tracker
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://exercise-tracker.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://exercise-tracker.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+Your responses should have the following structures.
+
+Exercise:
+
+```js
+{
+  username: "fcc_test",
+  description: "test",
+  duration: 60,
+  date: "Mon Jan 01 1990",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+User:
+
+```js
+{
+  username: "fcc_test",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Log:
+
+```js
+{
+  username: "fcc_test",
+  count: 1,
+  _id: "5fb5853f734231456ccb3b05",
+  log: [{
+    description: "test",
+    duration: 60,
+    date: "Mon Jan 01 1990",
+  }]
+}
+```
+
+**Hint:** For the `date` property, the `toDateString` method of the `Date` API can be used to achieve the expected output.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  const url = getUserInput('url');
+  assert(
+    !/.*\/exercise-tracker\.freecodecamp\.rocks/.test(getUserInput('url'))
+  );
+};
+```
+
+You can `POST` to `/api/users` with form data `username` to create a new user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The returned response from `POST /api/users` with form data `username` will be an object with `username` and `_id` properties.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    assert.exists(_id);
+    assert.exists(username);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users` to get a list of all users.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `GET` request to `/api/users` returns an array.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    assert.isArray(users);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Each element in the array returned from `GET /api/users` is an object literal containing a user's `username` and `_id`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    const user = users[0];
+    assert.exists(user);
+    assert.exists(user.username);
+    assert.exists(user._id);
+    assert.isString(user.username);
+    assert.isString(user._id);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can `POST` to `/api/users/:_id/exercises` with form data `description`, `duration`, and optionally `date`. If no date is supplied, the current date will be used.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+  assert.isTrue(addRes.ok);
+  if(!addRes.ok) {
+    throw new Error(`${addRes.status} ${addRes.statusText}`)
+  };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+The response returned from `POST /api/users/:_id/exercises` will be the user object with the exercise fields added.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    if (addRes.ok) {
+      const actual = await addRes.json();
+      assert.deepEqual(actual, expected);
+      assert.isString(actual.description);
+      assert.isNumber(actual.duration);
+      assert.isString(actual.date);
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users/:_id/logs` to retrieve a full exercise log of any user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+    assert.isTrue(logRes.ok);
+    if(!logRes.ok) {
+      throw new Error(`${logRes.status} ${logRes.statusText}`)
+    };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A request to a user's log `GET /api/users/:_id/logs` returns a user object with a `count` property representing the number of exercises that belong to that user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if (logRes.ok) {
+        const { count } = await logRes.json();
+        assert(count);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A `GET` request to `/api/users/:_id/logs` will return the user object with a `log` array of all the exercises added.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  })
+  if(res.ok){
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok){
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+Each item in the `log` array that is returned from `GET /api/users/:_id/logs` is an object that should have a `description`, `duration`, and `date` properties.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + `/api/users`, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+     const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.exists(exercise);
+        assert.exists(exercise.description);
+        assert.exists(exercise.duration);
+        assert.exists(exercise.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `description` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.description);
+        assert.equal(exercise.description, expected.description);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `duration` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a number.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isNumber(exercise.duration);
+        assert.equal(exercise.duration, expected.duration);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `date` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string. Use the `dateString` format of the `Date` API.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toLocaleDateString("en-US", {
+        timeZone: "UTC", weekday: "short", month: "short",
+        day: "2-digit", year: "numeric"
+      }).replaceAll(',', '')
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.date);
+        assert.equal(exercise.date, expected.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can add `from`, `to` and `limit` parameters to a `GET /api/users/:_id/logs` request to retrieve part of the log of any user. `from` and `to` are dates in `yyyy-mm-dd` format. `limit` is an integer of how many logs to send back.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addExerciseRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    const addExerciseTwoRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-03`
+    });
+    if (addExerciseRes.ok && addExerciseTwoRes.ok) {
+      const logRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1989-12-31&to=1990-01-04`
+      );
+      if (logRes.ok) {
+        const { log } = await logRes.json();
+        assert.isArray(log);
+        assert.equal(2, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+      const limitRes = await fetch(
+        url + `/api/users/${_id}/logs?limit=1`
+      );
+      if (limitRes.ok) {
+        const { log } = await limitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${limitRes.status} ${limitRes.statusText}`);
+      }
+      const filterDateBeforeLimitRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1990-01-02&to=1990-01-04&limit=1`
+      );
+      if (filterDateBeforeLimitRes.ok) {
+        const { log } = await filterDateBeforeLimitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${filterDateBeforeLimitRes.status} ${filterDateBeforeLimitRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${res.status} ${res.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
diff --git a/curriculum/challenges/german/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md b/curriculum/challenges/german/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
new file mode 100644
index 0000000000..ef87dc6720
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
@@ -0,0 +1,25 @@
+---
+id: 602da04c22201c65d2a019f4
+title: Build a Number Guessing Game
+challengeType: 13
+url: freeCodeCamp/learn-number-guessing-game
+dashedName: lab-number-guessing-game
+---
+
+# --description--
+
+For this lab, you will use Bash scripting, PostgreSQL, and Git to create a number guessing game that runs in the terminal and saves user information.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `number_guess.sql` file, as well as your `number_guess.sh` file, so you can complete step 2. There will be instructions on how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `number_guess.sql`, `number_guess.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/german/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md b/curriculum/challenges/german/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
new file mode 100644
index 0000000000..5040e27424
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
@@ -0,0 +1,65 @@
+---
+id: bd7158d8c443edefaeb5bdff
+title: Build a Request Header Parser Microservice
+challengeType: 4
+dashedName: lab-request-header-parser-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://request-header-parser-microservice.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://request-header-parser-microservice.freecodecamp.rocks/</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/request-header-parser-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+A request to `/api/whoami` should return a JSON object with your IP address in the `ipaddress` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.ipaddress && data.ipaddress.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your preferred language in the `language` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.language && data.language.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your software in the `software` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.software && data.software.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/german/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md b/curriculum/challenges/german/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
new file mode 100644
index 0000000000..0fbf80a0bf
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
@@ -0,0 +1,107 @@
+---
+id: bd7158d8c443edefaeb5bd0e
+title: URL Shortener Microservice
+challengeType: 4
+dashedName: url-shortener-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://url-shortener-microservice.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://url-shortener-microservice.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+**HINT:** Do not forget to use a body parsing middleware to handle the POST requests. Also, you can use the function `dns.lookup(host, cb)` from the `dns` core module to verify a submitted URL.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/url-shortener-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+You can POST a URL to `/api/shorturl` and get a JSON response with `original_url` and `short_url` properties. Here's an example: `{ original_url : 'https://freeCodeCamp.org', short_url : 1}`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (res.ok) {
+    const { short_url, original_url } = await res.json();
+    assert.isNotNull(short_url);
+    assert.strictEqual(original_url, `${url}/?v=${urlVariable}`);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+When you visit `/api/shorturl/<short_url>`, you will be redirected to the original URL.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  let shortenedUrlVariable;
+  const postResponse = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (postResponse.ok) {
+    const { short_url } = await postResponse.json();
+    shortenedUrlVariable = short_url;
+  } else {
+    throw new Error(`${postResponse.status} ${postResponse.statusText}`);
+  }
+  const getResponse = await fetch(
+    url + '/api/shorturl/' + shortenedUrlVariable
+  );
+  if (getResponse) {
+    const { redirected, url } = getResponse;
+    assert.isTrue(redirected);
+    assert.strictEqual(url,fullUrl);
+  } else {
+    throw new Error(`${getResponse.status} ${getResponse.statusText}`);
+  }
+};
+```
+
+If you pass an invalid URL that doesn't follow the valid `http://www.example.com` format, the JSON response will contain `{ error: 'invalid url' }`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=ftp:/john-doe.invalidTLD`
+  });
+  if (res.ok) {
+    const { error } = await res.json();
+    assert.isNotNull(error);
+    assert.strictEqual(error.toLowerCase(), 'invalid url');
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
diff --git a/curriculum/challenges/german/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md b/curriculum/challenges/german/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
new file mode 100644
index 0000000000..d77442a1ba
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
@@ -0,0 +1,25 @@
+---
+id: 5f9771307d4d22b9d2b75a94
+title: Build a World Cup Database
+challengeType: 13
+url: freeCodeCamp/learn-world-cup-database
+dashedName: lab-world-cup-database
+---
+
+# --description--
+
+For this project, you will create a Bash script that enters information from World Cup games into PostgreSQL, then query the database for useful statistics.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `worldcup.sql` file, as well as your `insert_data.sh` and `queries.sh` files, so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `worldcup.sql`, `insert_data.sh`, `queries.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md b/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
index 51ea9e3069..753ee1a6bb 100644
--- a/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
+++ b/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
@@ -7,9 +7,9 @@ dashedName: step-22
 
 # --description--
 
-Add another label with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
+Add another `label` with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
 
-Below the label element, add another checkbox input with the `id`, `name` and `value` attributes set to `"recommendation"`.
+Below the `label` element, add another checkbox `input` with the `id`, `name` and `value` attributes set to `"recommendation"`.
 
 # --hints--
 
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md b/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
index 42c425209d..80a23ca86d 100644
--- a/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
+++ b/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
@@ -11,7 +11,7 @@ Next, add another `label` element with the text of `Location` and the `for` attr
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"location"`.
 
-Below that `input` element, add another `label` element with the text of `Reputation` and the for attribute set to `"reputation"`.
+Below that `input` element, add another `label` element with the text of `Reputation` and the `for` attribute set to `"reputation"`.
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"reputation"`.
 
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md b/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
index 69efa4832c..09e3e6e59b 100644
--- a/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
+++ b/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
@@ -7,7 +7,7 @@ dashedName: step-28
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attributes:**
 
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md b/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
index 6549345d45..22b9a707be 100644
--- a/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
+++ b/curriculum/challenges/german/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
@@ -7,7 +7,7 @@ dashedName: step-31
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attribute:**
 
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
new file mode 100644
index 0000000000..237515fd88
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
@@ -0,0 +1,71 @@
+---
+id: 66c8ba41a77db20a93f9d7a1
+title: Step 1
+challengeType: 1
+dashedName: step-1
+---
+
+# --description--
+
+In this workshop, you'll review JavaScript conditionals by building a loan qualification checker app.
+
+The app will check whether the user is eligible for a duplex, car, and condo loan based on their annual income and credit score. A credit score is a number that represents how good you are at managing borrowed money.
+
+To get started, create the following variables and values.
+
+| Variable Name             | Value   |
+| ------------------------- | ------- |
+| `minIncomeForDuplex`      | `60000` |
+| `minCreditScoreForDuplex` | `700`   |
+| `minIncomeForCondo`       | `45000` |
+| `minCreditScoreForCondo`  | `680`   |
+| `minIncomeForCar`         | `30000` |
+| `minCreditScoreForCar`    | `650`   |
+
+# --hints--
+
+You should create a `minIncomeForDuplex` variable set to `60000`.
+
+```js
+assert.equal(minIncomeForDuplex, 60000);
+```
+
+You should create a `minCreditScoreForDuplex` set to `700`.
+
+```js
+assert.equal(minCreditScoreForDuplex, 700);
+```
+
+You should create a `minIncomeForCar` variable set to `30000`.
+
+```js
+assert.equal(minIncomeForCar, 30000);
+```
+
+You should create a `minCreditScoreForCar` variable set to `650`.
+
+```js
+assert.equal(minCreditScoreForCar, 650);
+```
+
+You should create a `minIncomeForCondo` variable set to `45000`.
+
+```js
+assert.equal(minIncomeForCondo, 45000);
+```
+
+You should create a `minCreditScoreForCondo` variable set to `680`.
+
+```js
+assert.equal(minCreditScoreForCondo, 680);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
new file mode 100644
index 0000000000..7755f823c4
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
@@ -0,0 +1,53 @@
+---
+id: 66c8ba975ee7230e29f6c4ac
+title: Step 2
+challengeType: 1
+dashedName: step-2
+---
+
+# --description--
+
+When the user is eligible for a loan, you'll want to display a message to them in the console.
+
+For that, you'll build out a function inside which you'll have some checks that'll return what loan the applicant is eligible for.
+
+Create an empty `getLoanMessage` function with an `annualIncome` and `creditScore` parameters.
+
+# --hints--
+
+You should create a `getLoanMessage` function
+
+```js
+assert.isFunction(getLoanMessage)
+```
+
+Your `getLoanMessage` function should have an `annualIncome` and `creditScore` as parameters.
+
+```js
+assert.match(getLoanMessage?.toString(), /\(\s*annualIncome,\s*creditScore\s*\)|\(\s*creditScore,\s*annualIncome\s*\)/);
+```
+
+`getLoanMessage` should be an empty function.
+
+```js
+assert.match(getLoanMessage?.toString(), /\{\s*\}/);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
new file mode 100644
index 0000000000..82a29d7cd9
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
@@ -0,0 +1,55 @@
+---
+id: 66c8ba975ee7230e29f6c4ad
+title: Step 3
+challengeType: 1
+dashedName: step-3
+---
+
+# --description--
+
+To check which loan a user is qualified for based on the `annualIncome` and `creditScore`, you have to use `if/else if` statement or a ternary right inside the `getLoanMessage` function. You'll then return the appropraite message in the block of each condition.
+
+Starting with the duplex loan, check if `annualIncome` is greater than or equal to `minIncomeForDuplex` AND if `creditScore` is greater than `minCreditScoreForDuplex`.
+
+If that condition is true, then the applicant is eligible for a duplex loan and the other loans. So, inside the check, return the string `"You qualify for a car, duplex and Condo loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string.
+
+```js
+assert.isString(getLoanMessage(65000, 750));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a duplex, condo, and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(65000, 750), "You qualify for a duplex, condo, and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a duplex loan.
+
+```js
+assert.strictEqual(getLoanMessage(59000, 700), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+function getLoanMessage(annualIncome, creditScore) {
+
+}
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
new file mode 100644
index 0000000000..638e6291a4
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4af
+title: Step 4
+challengeType: 1
+dashedName: step-4
+---
+
+# --description--
+
+If the applicant's annual income is greater than or equal to `minIncomeForCondo`, AND if their credit score is greater than or equal to `minCreditScoreForCondo`, then they qualify for a condo and car loan.
+
+Check if that's true in the `getLoanMessage` function. If it is, return the string `"You qualify for a condo and car loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a condo and car loan.
+
+```js
+assert.isString(getLoanMessage(45000, 680));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a condo and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 680), "You qualify for a condo and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a condo loan.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 650), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
new file mode 100644
index 0000000000..374ba7b8fe
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4b0
+title: Step 5
+challengeType: 1
+dashedName: step-5
+---
+
+# --description--
+
+Now, you should check if the applicant is qualified for a car loan only. If they're, return the string `"You qualify for a car loan."`.
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a car loan.
+
+```js
+assert.isString(getLoanMessage(30000, 650));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 650), "You qualify for a car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a car loan.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 600), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+--fcc-editable-region--
+  } 
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
new file mode 100644
index 0000000000..16e8c7baca
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
@@ -0,0 +1,54 @@
+---
+id: 66c8ba975ee7230e29f6c4b1
+title: Step 6
+challengeType: 1
+dashedName: step-6
+---
+
+# --description--
+
+If the applicant's annual income and credit score fall below `minIncomeForCar` and `minCreditScoreForCar`, then they don't qualify for any loan. So, return the string `"You don't qualify for any loans."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant doesn't qualify for any loan.
+
+```js
+assert.isString(getLoanMessage(25000, 550));
+```
+
+Your `getLoanMessage` function should return the string `"You don't qualify for any loans."` if the applicant does not meet the requirements for any loan.
+
+```js
+assert.strictEqual(getLoanMessage(15000, 600), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(25000, 550), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(20000, 500), "You don't qualify for any loans.");
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
new file mode 100644
index 0000000000..9d19f9ea4c
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
@@ -0,0 +1,165 @@
+---
+id: 66c8ba975ee7230e29f6c4b2
+title: Step 7
+challengeType: 1
+dashedName: step-7
+---
+
+# --description--
+
+Now, it is time to test out your `getLoanMessage` function.
+
+Use the table below to create `4` variables and their values:
+
+| Variable Name   | Value                        |
+| --------------- | ---------------------------- |
+| `duplexLoanMsg` | `getLoanMessage(85000, 850)` |
+| `condoLoanMsg`  | `getLoanMessage(65000, 690)` |
+| `carLoanMsg`    | `getLoanMessage(45000, 660)` |
+| `noLoanMsg`     | `getLoanMessage(25000, 550)` |
+
+After that, log each variable to the console to see the messages.
+
+With that, your loan qualification checker project is complete!
+
+# --hints--
+
+You should have a variable called `duplexLoanMsg`.
+
+```js
+assert.isNotNull(duplexLoanMsg);
+```
+
+Your `duplexLoanMsg` variable should be set to the result of `getLoanMessage(85000, 850)`.
+
+```js
+assert.equal(duplexLoanMsg, getLoanMessage(85000, 850));
+```
+
+You should log the `duplexLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(duplexLoanMsg\)/)
+```
+
+You should have a variable called `condoLoanMsg`.
+
+```js
+assert.isNotNull(condoLoanMsg);
+```
+
+Your `condoLoanMsg` variable should be set to the result of `getLoanMessage(65000, 690)`.
+
+```js
+assert.equal(condoLoanMsg, getLoanMessage(65000, 690));
+```
+
+You should log the `condoLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(condoLoanMsg\)/)
+```
+
+You should have a variable called `carLoanMsg`.
+
+```js
+assert.isNotNull(carLoanMsg);
+```
+
+Your `carLoanMsg` variable should be set to the result of `getLoanMessage(45000, 660)`.
+
+```js
+assert.equal(carLoanMsg, getLoanMessage(45000, 660));
+```
+
+You should log the `carLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(carLoanMsg\)/)
+```
+
+You should have a variable called `noLoanMsg`.
+
+```js
+assert.isNotNull(noLoanMsg);
+```
+
+Your `noLoanMsg` variable should be set to the result of `getLoanMessage(25000, 550)`.
+
+```js
+assert.equal(noLoanMsg, getLoanMessage(25000, 550));
+```
+
+You should log the `noLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(noLoanMsg\)/)
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
+
+# --solutions--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+const duplexLoanMsg = getLoanMessage(85000, 850)
+console.log(duplexLoanMsg)
+
+const condoLoanMsg = getLoanMessage(65000, 690)
+console.log(condoLoanMsg)
+
+const carLoanMsg = getLoanMessage(45000, 660)
+console.log(carLoanMsg)
+
+const noLoanMsg = getLoanMessage(25000, 550)
+console.log(noLoanMsg)
+```
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md b/curriculum/challenges/german/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
new file mode 100644
index 0000000000..4e11751ca0
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
@@ -0,0 +1,19 @@
+---
+id: 5f2c289f164c29556da632fd
+title: Build a Mario Database
+challengeType: 12
+url: freeCodeCamp/learn-relational-databases-by-building-a-mario-database
+dashedName: build-a-mario-database
+---
+
+# --description--
+
+In this 165-lesson workshop, you will learn the basics of a relational database by creating a PostgreSQL database filled with video game characters.
+
+# --instructions--
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
new file mode 100644
index 0000000000..8d4c90410d
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
@@ -0,0 +1,53 @@
+---
+id: 587d7fb3367417b2b2512bfb
+title: How to Use package.json, the Core of Any Node.js Project or npm Package
+challengeType: 2
+forumTopicId: 301528
+dashedName: how-to-use-package-json-the-core-of-any-node-js-project-or-npm-package
+---
+
+# --description--
+
+Working on these challenges will involve you writing your code using one of the following methods:
+
+- Clone <a href="https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete these challenges locally.
+- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+The `package.json` file is the center of any Node.js project or npm package. It stores information about your project. It consists of a single JSON object where information is stored in key-value pairs. There are only two required fields; `name` and `version`, but it’s good practice to provide additional information.
+
+You can create the `package.json` file from the terminal using the `npm init` command. This will run a guided setup. Using `npm init` with the `-y` flag will generate the file without having it ask any questions, `npm init -y`.
+
+If you look at the file tree of your project, you will find the `package.json` file on the top level of the tree. This is the file that you will be improving in the next couple of challenges.
+
+One of the most common pieces of information in this file is the `author` field. It specifies who created the project, and can consist of a string or an object with contact or other details. An object is recommended for bigger projects, but a simple string like the following example will do for this project.
+
+```json
+"author": "Jane Doe",
+```
+
+# --instructions--
+
+Add your name as the `author` of the project in the `package.json` file.
+
+**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (") and be separated with a comma (,).
+
+If you are using Gitpod, make sure the app is running and the preview window is open. Copy the preview window's URL and paste it into the Solution Link input below.
+
+# --hints--
+
+`package.json` should have a valid "author" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.author, '"author" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
new file mode 100644
index 0000000000..37d15d5261
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb3367417b2b2512bfc
+title: Add a Description to Your package.json
+challengeType: 2
+forumTopicId: 301522
+dashedName: add-a-description-to-your-package-json
+---
+
+# --description--
+
+The next part of a good package.json file is the `description` field; where a short, but informative description about your project belongs.
+
+If some day you plan to publish a package to npm, this is the string that should sell your idea to the user when they decide whether to install your package or not. However, that’s not the only use case for the description, it’s a great way to summarize what a project does. It’s just as important in any Node.js project to help other developers, future maintainers or even your future self understand the project quickly.
+
+Regardless of what you plan for your project, a description is definitely recommended. Here's an example:
+
+```json
+"description": "A project that does something awesome",
+```
+
+# --instructions--
+
+Add a `description` to the package.json file of your project.
+
+**Note:** Remember to use double-quotes for field-names (") and commas (,) to separate fields.
+
+# --hints--
+
+package.json should have a valid "description" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.description, '"description" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
new file mode 100644
index 0000000000..a001cdd477
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
@@ -0,0 +1,75 @@
+---
+id: 587d7fb4367417b2b2512bfd
+title: Add Keywords to Your package.json
+challengeType: 2
+forumTopicId: 301526
+dashedName: add-keywords-to-your-package-json
+---
+
+# --description--
+
+The `keywords` field is where you can describe your project using related keywords. Here's an example:
+
+```json
+"keywords": [ "descriptive", "related", "words" ],
+```
+
+As you can see, this field is structured as an array of double-quoted strings.
+
+# --instructions--
+
+Add an array of suitable strings to the `keywords` field in the package.json file of your project.
+
+One of the keywords should be "freecodecamp".
+
+# --hints--
+
+package.json should have a valid "keywords" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.keywords, '"keywords" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" field should be an Array
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.isArray(packJson.keywords, '"keywords" is not an array');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" should include "freecodecamp"
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.include(
+        packJson.keywords,
+        'freecodecamp',
+        '"keywords" does not include "freecodecamp"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
new file mode 100644
index 0000000000..7b09acd042
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
@@ -0,0 +1,39 @@
+---
+id: 587d7fb4367417b2b2512bfe
+title: Add a License to Your package.json
+challengeType: 2
+forumTopicId: 301523
+dashedName: add-a-license-to-your-package-json
+---
+
+# --description--
+
+The `license` field is where you inform users of what they are allowed to do with your project.
+
+Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do. Here's an example of the license field:
+
+```json
+"license": "MIT",
+```
+
+# --instructions--
+
+Fill the `license` field in the package.json file of your project as you find suitable.
+
+# --hints--
+
+package.json should have a valid "license" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.license, '"license" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
new file mode 100644
index 0000000000..f2e571faed
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
@@ -0,0 +1,37 @@
+---
+id: 587d7fb4367417b2b2512bff
+title: Add a Version to Your package.json
+challengeType: 2
+forumTopicId: 301525
+dashedName: add-a-version-to-your-package-json
+---
+
+# --description--
+
+A `version` is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example:
+
+```json
+"version": "1.2.0",
+```
+
+# --instructions--
+
+Add a `version` to the package.json file of your project.
+
+# --hints--
+
+package.json should have a valid "version" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.version, '"version" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
new file mode 100644
index 0000000000..161c60fe69
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
@@ -0,0 +1,68 @@
+---
+id: 587d7fb4367417b2b2512c00
+title: Expand Your Project with External Packages from npm
+challengeType: 2
+forumTopicId: 301527
+dashedName: expand-your-project-with-external-packages-from-npm
+---
+
+# --description--
+
+One of the biggest reasons to use a package manager, is their powerful dependency management. Instead of manually having to make sure that you get all dependencies whenever you set up a project on a new computer, npm automatically installs everything for you. But how can npm know exactly what your project needs? Meet the `dependencies` section of your package.json file.
+
+In this section, packages your project requires are stored using the following format:
+
+```json
+"dependencies": {
+  "package-name": "version",
+  "express": "4.14.0"
+}
+
+```
+
+# --instructions--
+
+Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file.
+
+**Note:** `@freecodecamp/example` is a faux package used as a learning tool.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.1.0"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^[\^\~]?1\.1\.0/,
+        'Wrong version of "@freecodecamp/example" installed. It should be 1.1.0'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
new file mode 100644
index 0000000000..deda9b82de
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
@@ -0,0 +1,64 @@
+---
+id: 587d7fb5367417b2b2512c01
+title: Manage npm Dependencies By Understanding Semantic Versioning
+challengeType: 2
+forumTopicId: 301529
+dashedName: manage-npm-dependencies-by-understanding-semantic-versioning
+---
+
+# --description--
+
+`Versions` of the npm packages in the dependencies section of your package.json file follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes projects can expect if they update.
+
+Knowing SemVer can be useful when you develop software that uses external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things that worked yesterday suddenly don’t work today. This is how Semantic Versioning works according to the official website:
+
+```json
+"package": "MAJOR.MINOR.PATCH"
+```
+
+The MAJOR version should increment when you make incompatible API changes. The MINOR version should increment when you add functionality in a backwards-compatible manner. The PATCH version should increment when you make backwards-compatible bug fixes. This means that PATCHes are bug fixes and MINORs add new features but neither of them break what worked before. Finally, MAJORs add changes that won’t work with earlier versions.
+
+# --instructions--
+
+In the dependencies section of your `package.json` file, change the version of `@freecodecamp/example` to match MAJOR version 1, MINOR version 2 and PATCH version 13
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.equal(
+        packJson.dependencies["@freecodecamp/example"],
+        '1.2.13',
+        'Wrong version of "@freecodecamp/example". It should be 1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
new file mode 100644
index 0000000000..8eae5f51ee
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c02
+title: Use the Tilde-Character to Always Use the Latest Patch Version of a Dependency
+challengeType: 2
+forumTopicId: 301532
+dashedName: use-the-tilde-character-to-always-use-the-latest-patch-version-of-a-dependency
+---
+
+# --description--
+
+In the last challenge, you told npm to only include a specific version of a package. That’s a useful way to freeze your dependencies if you need to make sure that different parts of your project stay compatible with each other. But in most use cases, you don’t want to miss bug fixes since they often include important security patches and (hopefully) don’t break things in doing so.
+
+To allow an npm dependency to update to the latest PATCH version, you can prefix the dependency’s version with the tilde (`~`) character. Here's an example of how to allow updates to any `1.3.x` version.
+
+```json
+"package": "~1.3.8"
+```
+
+# --instructions--
+
+In the package.json file, your current rule for how npm may upgrade `@freecodecamp/example` is to use a specific version (`1.2.13`). But now, you want to allow the latest `1.2.x` version.
+
+Use the tilde (`~`) character to prefix the version of `@freecodecamp/example` in your dependencies, and allow npm to update it to any new _patch_ release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"~1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\~1\.2\.13/,
+        'Wrong version of "@freecodecamp/example". It should be ~1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
new file mode 100644
index 0000000000..adc3014ea4
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c03
+title: Use the Caret-Character to Use the Latest Minor Version of a Dependency
+challengeType: 2
+forumTopicId: 301531
+dashedName: use-the-caret-character-to-use-the-latest-minor-version-of-a-dependency
+---
+
+# --description--
+
+Similar to how the tilde we learned about in the last challenge allows npm to install the latest PATCH for a dependency, the caret (`^`) allows npm to install future updates as well. The difference is that the caret will allow both MINOR updates and PATCHes.
+
+Your current version of `@freecodecamp/example` should be `~1.2.13` which allows npm to install to the latest `1.2.x` version. If you were to use the caret (^) as a version prefix instead, npm would be allowed to update to any `1.x.x` version.
+
+```json
+"package": "^1.3.8"
+```
+
+This would allow updates to any `1.x.x` version of the package.
+
+# --instructions--
+
+Use the caret (`^`) to prefix the version of `@freecodecamp/example` in your dependencies and allow npm to update it to any new MINOR release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"^1.x.x"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\^1\./,
+        'Wrong version of "@freecodecamp/example". It should be ^1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
new file mode 100644
index 0000000000..5f695eed88
--- /dev/null
+++ b/curriculum/challenges/german/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb5367417b2b2512c04
+title: Remove a Package from Your Dependencies
+challengeType: 2
+forumTopicId: 301530
+dashedName: remove-a-package-from-your-dependencies
+---
+
+# --description--
+
+You have now tested a few ways you can manage dependencies of your project by using the package.json's dependencies section. You have also included external packages by adding them to the file and even told npm what types of versions you want, by using special characters such as the tilde or the caret.
+
+But what if you want to remove an external package that you no longer need? You might already have guessed it, just remove the corresponding key-value pair for that package from your dependencies.
+
+This same method applies to removing other fields in your package.json as well.
+
+# --instructions--
+
+Remove the `@freecodecamp/example` package from your dependencies.
+
+**Note:** Make sure you have the right amount of commas after removing it.
+
+# --hints--
+
+`"dependencies"` should not include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.notProperty(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" still includes "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/italian/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md b/curriculum/challenges/italian/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
index b284ce61c9..92943db202 100644
--- a/curriculum/challenges/italian/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
+++ b/curriculum/challenges/italian/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
@@ -8,7 +8,7 @@ dashedName: build-a-periodic-table-database
 
 # --description--
 
-Questo è uno dei progetti richiesti per completare la certificazione. Per questo progetto, creerai uno script Bash per ottenere informazioni sugli elementi chimici da un database della tavola periodica.
+Questo è uno dei progetti richiesti per completare la certificazione. For this project, you will create a Bash script to get information about chemical elements from a periodic table database.
 
 # --instructions--
 
diff --git a/curriculum/challenges/italian/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md b/curriculum/challenges/italian/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
index 81b4ccebac..6b33708d31 100644
--- a/curriculum/challenges/italian/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
+++ b/curriculum/challenges/italian/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
@@ -9,6 +9,8 @@ dashedName: step-64
 
 Aggiungi un elemento `p` all'interno del `footer`. Poi, annida un elemento di ancoraggio (`a`) nell'elemento `p` contenente il link `https://www.freecodecamp.org` e il testo `Visit our website`.
 
+Make sure that the link opens in a new tab by adding a `target` attribute with the value `_blank`.
+
 # --hints--
 
 Non dovresti modificare l'elemento `footer` esistente.
@@ -43,6 +45,12 @@ Il nuovo elemento `a` dovrebbe contenere il link `https://www.freecodecamp.org`.
 assert(document.querySelector("footer > p > a")?.href === "https://www.freecodecamp.org/");
 ```
 
+Your new `a` element should have the `target` attribute set to `_blank`.
+
+```js
+assert.equal(document.querySelector("footer > p > a")?.target, "_blank");
+```
+
 # --seed--
 
 ## --seed-contents--
diff --git a/curriculum/challenges/italian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md b/curriculum/challenges/italian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
index d2ad72a1ea..1b6ca05444 100644
--- a/curriculum/challenges/italian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
+++ b/curriculum/challenges/italian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
@@ -21,12 +21,12 @@ Remove `flex: 1` from `.item` and add `justify-content: space-between` to `.cont
 
 `justify-content` aligns items across the **main axis**. There are a few values that you can use here. You'll learn the rest of them in the reading assignments, but for now try changing it to center, which should center the boxes along the main axis.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see what is possible with the `justify-content` property. Read this [interactive article on MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) and play around with the different values of `justify-content` on the example.
 
+# --question--
+
 ## --text--
 
 How does applying `justify-content: space-between` to a flex container affect the positioning of its items?
diff --git a/curriculum/challenges/italian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md b/curriculum/challenges/italian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
index d3137b0af5..59acb55a29 100644
--- a/curriculum/challenges/italian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
+++ b/curriculum/challenges/italian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
@@ -17,12 +17,12 @@ To change the placement of items along the cross axis use `align-items`. Try get
 
 Because `justify-content` and `align-items` are based on the main and cross axis of your container, their behavior changes when you change the flex-direction of a flex-container. For example, when you change `flex-direction` to `column`, `justify-content` aligns vertically and `align-items` aligns horizontally. The most common behavior, however, is the default, i.e. `justify-content` aligns items horizontally (because the main axis defaults to horizontal), and `align-items` aligns them vertically. One of the biggest sticking points that beginners have with flexbox is confusion when this behavior changes.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see if you can figure out how `align-items` behaves when you change the `flex-direction` property to `column`.
 
+# --question--
+
 ## --text--
 
 When changing the `flex-direction` property to `column` in a flex container, how does `align-items` behave in relation to the flex items?
diff --git a/curriculum/challenges/italian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md b/curriculum/challenges/italian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
index 1adf9ce84f..49edeac0e4 100644
--- a/curriculum/challenges/italian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
+++ b/curriculum/challenges/italian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
@@ -9,12 +9,12 @@ dashedName: learn-block-and-inline-lesson-b
 
 Inline elements, however, do not start on a new line. They appear in line with whatever elements they are placed beside. A clear example of an inline element is a link, or `<a>` tag. If you stick one of these in the middle of a paragraph of text, it will behave like a part of the paragraph. <a  href="https://www.freecodecamp.org/" target="_blank">(Like this)</a> The link’s text will sit alongside other words in that paragraph. Additionally, padding and margin behave differently on inline elements. In general, you do not want to try to put extra padding or margin on inline elements.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Search the web for a list of `block` elements and a list of `inline` elements.
 
+# --question--
+
 ## --text--
 
 What is the difference between a `block` element and an `inline` element?
diff --git a/curriculum/challenges/italian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md b/curriculum/challenges/italian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
index cdd4d5aa87..e75492e9c1 100644
--- a/curriculum/challenges/italian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
+++ b/curriculum/challenges/italian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-block-and-inline-lesson-g
 
 # --description--
 
-Now that you have some basic understanding of `block` and inline `elements`, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
+Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
 
 # --question--
 
diff --git a/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md b/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
index 995073b8a2..a7a2ee9a51 100644
--- a/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
+++ b/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
@@ -21,12 +21,12 @@ New programmers often find problem solving the hardest skill to build. It's not
 
 The best way to improve your problem solving ability is by building experience by making lots and lots of programs. The more practice you have the better you'll be prepared to solve real world problems.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Read <a href="https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/" target="_blank">How to Think Like a Programmer - Lessons in Problem Solving</a> by Richard Reis.
 
+# --question--
+
 ## --text--
 
 According to V. Anton Spraul in "Think Like a Programmer," what is problem solving in programming?
diff --git a/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md b/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
index ae905ecf89..c57a7d43e8 100644
--- a/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
+++ b/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
@@ -25,11 +25,11 @@ Now that you know what you’re aiming to solve, don’t jump into coding just y
 
 The last question is where you will write out an algorithm to solve the problem. You can think of an algorithm as a recipe for solving a particular problem. It defines the steps that need to be taken by the computer to solve a problem in pseudocode.
 
-# --question--
-
-## --assignment--
+# --assignment--
 Watch <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">How to Begin Thinking Like a Programmer</a> by Coding Tech. It’s an hour long but packed full of information and definitely worth your time watching.
 
+# --question--
+
 ## --text--
 
 What should you do before starting to code according to the provided text?
diff --git a/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md b/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
index c837fd9658..082f2d51ae 100644
--- a/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
+++ b/curriculum/challenges/italian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
@@ -22,12 +22,12 @@ Print the value of the counter variable
 
 This is a basic program to demonstrate how pseudocode looks. There will be more examples of pseudocode included in the assignments.
 
+# --assignment--
 
-# --question--
-
-## --assignment--
 Read this <a href="https://builtin.com/data-science/pseudocode" target="_blank"> Pseudocode: What It Is and How to Write It</a> article from Built In.
 
+# --question--
+
 ## --text--
 
 What are the benefits of using pseudocode according to the linked article?
diff --git a/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md b/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
index de8a8a3f51..567708f620 100644
--- a/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
+++ b/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-So far you have learned how to create questions with the verb to be. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
+So far you have learned how to create questions with the verb `to be`. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
 
 `You are a developer` -> `Are you a developer?`
 
diff --git a/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md b/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
index 544d8f1988..8cd311a518 100644
--- a/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
+++ b/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
@@ -21,7 +21,7 @@ Which sentence is correct for describing one place near you?
 
 ### --feedback--
 
-`There are` is used for plural nouns, and `bank` is singular. You’ll learn about there are in the next few lessons.
+`There are` is used for plural nouns, and `bank` is singular. You’ll learn about `there are` in the next few lessons.
 
 ---
 
diff --git a/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md b/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
index 6526b1e95b..10c0845779 100644
--- a/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
+++ b/curriculum/challenges/italian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
@@ -7,7 +7,7 @@ dashedName: task-112
 
 # --description--
 
-To elaborate a question using `there is` you just need to change the order of the verb to be, like so:
+To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so:
 
 `There is an ATM nearby` -> `Is there an ATM nearby?`
 
diff --git a/curriculum/challenges/italian/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md b/curriculum/challenges/italian/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
new file mode 100644
index 0000000000..7d664a8876
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
@@ -0,0 +1,25 @@
+---
+id: 5f1a4ef5d5d6b5ab580fc6ae
+title: Build a Celestial Bodies Database
+challengeType: 13
+url: freeCodeCamp/learn-celestial-bodies-database
+dashedName: lab-celestial-bodies-database
+---
+
+# --description--
+
+For this project, you will build a database of celestial bodies using PostgreSQL.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `universe.sql` file so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `universe.sql`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/italian/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md b/curriculum/challenges/italian/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
new file mode 100644
index 0000000000..9492b82cb4
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
@@ -0,0 +1,611 @@
+---
+id: 5a8b073d06fa14fcfde687aa
+title: Build an Exercise Tracker
+challengeType: 4
+dashedName: build-an-exercise-tracker
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://exercise-tracker.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://exercise-tracker.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+Your responses should have the following structures.
+
+Exercise:
+
+```js
+{
+  username: "fcc_test",
+  description: "test",
+  duration: 60,
+  date: "Mon Jan 01 1990",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+User:
+
+```js
+{
+  username: "fcc_test",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Log:
+
+```js
+{
+  username: "fcc_test",
+  count: 1,
+  _id: "5fb5853f734231456ccb3b05",
+  log: [{
+    description: "test",
+    duration: 60,
+    date: "Mon Jan 01 1990",
+  }]
+}
+```
+
+**Hint:** For the `date` property, the `toDateString` method of the `Date` API can be used to achieve the expected output.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  const url = getUserInput('url');
+  assert(
+    !/.*\/exercise-tracker\.freecodecamp\.rocks/.test(getUserInput('url'))
+  );
+};
+```
+
+You can `POST` to `/api/users` with form data `username` to create a new user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The returned response from `POST /api/users` with form data `username` will be an object with `username` and `_id` properties.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    assert.exists(_id);
+    assert.exists(username);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users` to get a list of all users.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `GET` request to `/api/users` returns an array.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    assert.isArray(users);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Each element in the array returned from `GET /api/users` is an object literal containing a user's `username` and `_id`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    const user = users[0];
+    assert.exists(user);
+    assert.exists(user.username);
+    assert.exists(user._id);
+    assert.isString(user.username);
+    assert.isString(user._id);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can `POST` to `/api/users/:_id/exercises` with form data `description`, `duration`, and optionally `date`. If no date is supplied, the current date will be used.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+  assert.isTrue(addRes.ok);
+  if(!addRes.ok) {
+    throw new Error(`${addRes.status} ${addRes.statusText}`)
+  };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+The response returned from `POST /api/users/:_id/exercises` will be the user object with the exercise fields added.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    if (addRes.ok) {
+      const actual = await addRes.json();
+      assert.deepEqual(actual, expected);
+      assert.isString(actual.description);
+      assert.isNumber(actual.duration);
+      assert.isString(actual.date);
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users/:_id/logs` to retrieve a full exercise log of any user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+    assert.isTrue(logRes.ok);
+    if(!logRes.ok) {
+      throw new Error(`${logRes.status} ${logRes.statusText}`)
+    };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A request to a user's log `GET /api/users/:_id/logs` returns a user object with a `count` property representing the number of exercises that belong to that user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if (logRes.ok) {
+        const { count } = await logRes.json();
+        assert(count);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A `GET` request to `/api/users/:_id/logs` will return the user object with a `log` array of all the exercises added.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  })
+  if(res.ok){
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok){
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+Each item in the `log` array that is returned from `GET /api/users/:_id/logs` is an object that should have a `description`, `duration`, and `date` properties.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + `/api/users`, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+     const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.exists(exercise);
+        assert.exists(exercise.description);
+        assert.exists(exercise.duration);
+        assert.exists(exercise.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `description` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.description);
+        assert.equal(exercise.description, expected.description);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `duration` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a number.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isNumber(exercise.duration);
+        assert.equal(exercise.duration, expected.duration);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `date` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string. Use the `dateString` format of the `Date` API.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toLocaleDateString("en-US", {
+        timeZone: "UTC", weekday: "short", month: "short",
+        day: "2-digit", year: "numeric"
+      }).replaceAll(',', '')
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.date);
+        assert.equal(exercise.date, expected.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can add `from`, `to` and `limit` parameters to a `GET /api/users/:_id/logs` request to retrieve part of the log of any user. `from` and `to` are dates in `yyyy-mm-dd` format. `limit` is an integer of how many logs to send back.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addExerciseRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    const addExerciseTwoRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-03`
+    });
+    if (addExerciseRes.ok && addExerciseTwoRes.ok) {
+      const logRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1989-12-31&to=1990-01-04`
+      );
+      if (logRes.ok) {
+        const { log } = await logRes.json();
+        assert.isArray(log);
+        assert.equal(2, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+      const limitRes = await fetch(
+        url + `/api/users/${_id}/logs?limit=1`
+      );
+      if (limitRes.ok) {
+        const { log } = await limitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${limitRes.status} ${limitRes.statusText}`);
+      }
+      const filterDateBeforeLimitRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1990-01-02&to=1990-01-04&limit=1`
+      );
+      if (filterDateBeforeLimitRes.ok) {
+        const { log } = await filterDateBeforeLimitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${filterDateBeforeLimitRes.status} ${filterDateBeforeLimitRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${res.status} ${res.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
diff --git a/curriculum/challenges/italian/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md b/curriculum/challenges/italian/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
new file mode 100644
index 0000000000..ef87dc6720
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
@@ -0,0 +1,25 @@
+---
+id: 602da04c22201c65d2a019f4
+title: Build a Number Guessing Game
+challengeType: 13
+url: freeCodeCamp/learn-number-guessing-game
+dashedName: lab-number-guessing-game
+---
+
+# --description--
+
+For this lab, you will use Bash scripting, PostgreSQL, and Git to create a number guessing game that runs in the terminal and saves user information.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `number_guess.sql` file, as well as your `number_guess.sh` file, so you can complete step 2. There will be instructions on how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `number_guess.sql`, `number_guess.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/italian/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md b/curriculum/challenges/italian/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
new file mode 100644
index 0000000000..5040e27424
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
@@ -0,0 +1,65 @@
+---
+id: bd7158d8c443edefaeb5bdff
+title: Build a Request Header Parser Microservice
+challengeType: 4
+dashedName: lab-request-header-parser-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://request-header-parser-microservice.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://request-header-parser-microservice.freecodecamp.rocks/</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/request-header-parser-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+A request to `/api/whoami` should return a JSON object with your IP address in the `ipaddress` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.ipaddress && data.ipaddress.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your preferred language in the `language` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.language && data.language.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your software in the `software` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.software && data.software.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/italian/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md b/curriculum/challenges/italian/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
new file mode 100644
index 0000000000..0fbf80a0bf
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
@@ -0,0 +1,107 @@
+---
+id: bd7158d8c443edefaeb5bd0e
+title: URL Shortener Microservice
+challengeType: 4
+dashedName: url-shortener-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://url-shortener-microservice.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://url-shortener-microservice.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+**HINT:** Do not forget to use a body parsing middleware to handle the POST requests. Also, you can use the function `dns.lookup(host, cb)` from the `dns` core module to verify a submitted URL.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/url-shortener-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+You can POST a URL to `/api/shorturl` and get a JSON response with `original_url` and `short_url` properties. Here's an example: `{ original_url : 'https://freeCodeCamp.org', short_url : 1}`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (res.ok) {
+    const { short_url, original_url } = await res.json();
+    assert.isNotNull(short_url);
+    assert.strictEqual(original_url, `${url}/?v=${urlVariable}`);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+When you visit `/api/shorturl/<short_url>`, you will be redirected to the original URL.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  let shortenedUrlVariable;
+  const postResponse = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (postResponse.ok) {
+    const { short_url } = await postResponse.json();
+    shortenedUrlVariable = short_url;
+  } else {
+    throw new Error(`${postResponse.status} ${postResponse.statusText}`);
+  }
+  const getResponse = await fetch(
+    url + '/api/shorturl/' + shortenedUrlVariable
+  );
+  if (getResponse) {
+    const { redirected, url } = getResponse;
+    assert.isTrue(redirected);
+    assert.strictEqual(url,fullUrl);
+  } else {
+    throw new Error(`${getResponse.status} ${getResponse.statusText}`);
+  }
+};
+```
+
+If you pass an invalid URL that doesn't follow the valid `http://www.example.com` format, the JSON response will contain `{ error: 'invalid url' }`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=ftp:/john-doe.invalidTLD`
+  });
+  if (res.ok) {
+    const { error } = await res.json();
+    assert.isNotNull(error);
+    assert.strictEqual(error.toLowerCase(), 'invalid url');
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
diff --git a/curriculum/challenges/italian/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md b/curriculum/challenges/italian/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
new file mode 100644
index 0000000000..d77442a1ba
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
@@ -0,0 +1,25 @@
+---
+id: 5f9771307d4d22b9d2b75a94
+title: Build a World Cup Database
+challengeType: 13
+url: freeCodeCamp/learn-world-cup-database
+dashedName: lab-world-cup-database
+---
+
+# --description--
+
+For this project, you will create a Bash script that enters information from World Cup games into PostgreSQL, then query the database for useful statistics.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `worldcup.sql` file, as well as your `insert_data.sh` and `queries.sh` files, so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `worldcup.sql`, `insert_data.sh`, `queries.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md b/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
index 51ea9e3069..753ee1a6bb 100644
--- a/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
@@ -7,9 +7,9 @@ dashedName: step-22
 
 # --description--
 
-Add another label with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
+Add another `label` with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
 
-Below the label element, add another checkbox input with the `id`, `name` and `value` attributes set to `"recommendation"`.
+Below the `label` element, add another checkbox `input` with the `id`, `name` and `value` attributes set to `"recommendation"`.
 
 # --hints--
 
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md b/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
index 42c425209d..80a23ca86d 100644
--- a/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
@@ -11,7 +11,7 @@ Next, add another `label` element with the text of `Location` and the `for` attr
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"location"`.
 
-Below that `input` element, add another `label` element with the text of `Reputation` and the for attribute set to `"reputation"`.
+Below that `input` element, add another `label` element with the text of `Reputation` and the `for` attribute set to `"reputation"`.
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"reputation"`.
 
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md b/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
index 69efa4832c..09e3e6e59b 100644
--- a/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
@@ -7,7 +7,7 @@ dashedName: step-28
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attributes:**
 
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md b/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
index 6549345d45..22b9a707be 100644
--- a/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
@@ -7,7 +7,7 @@ dashedName: step-31
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attribute:**
 
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
new file mode 100644
index 0000000000..237515fd88
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
@@ -0,0 +1,71 @@
+---
+id: 66c8ba41a77db20a93f9d7a1
+title: Step 1
+challengeType: 1
+dashedName: step-1
+---
+
+# --description--
+
+In this workshop, you'll review JavaScript conditionals by building a loan qualification checker app.
+
+The app will check whether the user is eligible for a duplex, car, and condo loan based on their annual income and credit score. A credit score is a number that represents how good you are at managing borrowed money.
+
+To get started, create the following variables and values.
+
+| Variable Name             | Value   |
+| ------------------------- | ------- |
+| `minIncomeForDuplex`      | `60000` |
+| `minCreditScoreForDuplex` | `700`   |
+| `minIncomeForCondo`       | `45000` |
+| `minCreditScoreForCondo`  | `680`   |
+| `minIncomeForCar`         | `30000` |
+| `minCreditScoreForCar`    | `650`   |
+
+# --hints--
+
+You should create a `minIncomeForDuplex` variable set to `60000`.
+
+```js
+assert.equal(minIncomeForDuplex, 60000);
+```
+
+You should create a `minCreditScoreForDuplex` set to `700`.
+
+```js
+assert.equal(minCreditScoreForDuplex, 700);
+```
+
+You should create a `minIncomeForCar` variable set to `30000`.
+
+```js
+assert.equal(minIncomeForCar, 30000);
+```
+
+You should create a `minCreditScoreForCar` variable set to `650`.
+
+```js
+assert.equal(minCreditScoreForCar, 650);
+```
+
+You should create a `minIncomeForCondo` variable set to `45000`.
+
+```js
+assert.equal(minIncomeForCondo, 45000);
+```
+
+You should create a `minCreditScoreForCondo` variable set to `680`.
+
+```js
+assert.equal(minCreditScoreForCondo, 680);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
new file mode 100644
index 0000000000..7755f823c4
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
@@ -0,0 +1,53 @@
+---
+id: 66c8ba975ee7230e29f6c4ac
+title: Step 2
+challengeType: 1
+dashedName: step-2
+---
+
+# --description--
+
+When the user is eligible for a loan, you'll want to display a message to them in the console.
+
+For that, you'll build out a function inside which you'll have some checks that'll return what loan the applicant is eligible for.
+
+Create an empty `getLoanMessage` function with an `annualIncome` and `creditScore` parameters.
+
+# --hints--
+
+You should create a `getLoanMessage` function
+
+```js
+assert.isFunction(getLoanMessage)
+```
+
+Your `getLoanMessage` function should have an `annualIncome` and `creditScore` as parameters.
+
+```js
+assert.match(getLoanMessage?.toString(), /\(\s*annualIncome,\s*creditScore\s*\)|\(\s*creditScore,\s*annualIncome\s*\)/);
+```
+
+`getLoanMessage` should be an empty function.
+
+```js
+assert.match(getLoanMessage?.toString(), /\{\s*\}/);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
new file mode 100644
index 0000000000..82a29d7cd9
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
@@ -0,0 +1,55 @@
+---
+id: 66c8ba975ee7230e29f6c4ad
+title: Step 3
+challengeType: 1
+dashedName: step-3
+---
+
+# --description--
+
+To check which loan a user is qualified for based on the `annualIncome` and `creditScore`, you have to use `if/else if` statement or a ternary right inside the `getLoanMessage` function. You'll then return the appropraite message in the block of each condition.
+
+Starting with the duplex loan, check if `annualIncome` is greater than or equal to `minIncomeForDuplex` AND if `creditScore` is greater than `minCreditScoreForDuplex`.
+
+If that condition is true, then the applicant is eligible for a duplex loan and the other loans. So, inside the check, return the string `"You qualify for a car, duplex and Condo loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string.
+
+```js
+assert.isString(getLoanMessage(65000, 750));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a duplex, condo, and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(65000, 750), "You qualify for a duplex, condo, and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a duplex loan.
+
+```js
+assert.strictEqual(getLoanMessage(59000, 700), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+function getLoanMessage(annualIncome, creditScore) {
+
+}
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
new file mode 100644
index 0000000000..638e6291a4
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4af
+title: Step 4
+challengeType: 1
+dashedName: step-4
+---
+
+# --description--
+
+If the applicant's annual income is greater than or equal to `minIncomeForCondo`, AND if their credit score is greater than or equal to `minCreditScoreForCondo`, then they qualify for a condo and car loan.
+
+Check if that's true in the `getLoanMessage` function. If it is, return the string `"You qualify for a condo and car loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a condo and car loan.
+
+```js
+assert.isString(getLoanMessage(45000, 680));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a condo and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 680), "You qualify for a condo and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a condo loan.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 650), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
new file mode 100644
index 0000000000..374ba7b8fe
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4b0
+title: Step 5
+challengeType: 1
+dashedName: step-5
+---
+
+# --description--
+
+Now, you should check if the applicant is qualified for a car loan only. If they're, return the string `"You qualify for a car loan."`.
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a car loan.
+
+```js
+assert.isString(getLoanMessage(30000, 650));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 650), "You qualify for a car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a car loan.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 600), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+--fcc-editable-region--
+  } 
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
new file mode 100644
index 0000000000..16e8c7baca
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
@@ -0,0 +1,54 @@
+---
+id: 66c8ba975ee7230e29f6c4b1
+title: Step 6
+challengeType: 1
+dashedName: step-6
+---
+
+# --description--
+
+If the applicant's annual income and credit score fall below `minIncomeForCar` and `minCreditScoreForCar`, then they don't qualify for any loan. So, return the string `"You don't qualify for any loans."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant doesn't qualify for any loan.
+
+```js
+assert.isString(getLoanMessage(25000, 550));
+```
+
+Your `getLoanMessage` function should return the string `"You don't qualify for any loans."` if the applicant does not meet the requirements for any loan.
+
+```js
+assert.strictEqual(getLoanMessage(15000, 600), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(25000, 550), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(20000, 500), "You don't qualify for any loans.");
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
new file mode 100644
index 0000000000..9d19f9ea4c
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
@@ -0,0 +1,165 @@
+---
+id: 66c8ba975ee7230e29f6c4b2
+title: Step 7
+challengeType: 1
+dashedName: step-7
+---
+
+# --description--
+
+Now, it is time to test out your `getLoanMessage` function.
+
+Use the table below to create `4` variables and their values:
+
+| Variable Name   | Value                        |
+| --------------- | ---------------------------- |
+| `duplexLoanMsg` | `getLoanMessage(85000, 850)` |
+| `condoLoanMsg`  | `getLoanMessage(65000, 690)` |
+| `carLoanMsg`    | `getLoanMessage(45000, 660)` |
+| `noLoanMsg`     | `getLoanMessage(25000, 550)` |
+
+After that, log each variable to the console to see the messages.
+
+With that, your loan qualification checker project is complete!
+
+# --hints--
+
+You should have a variable called `duplexLoanMsg`.
+
+```js
+assert.isNotNull(duplexLoanMsg);
+```
+
+Your `duplexLoanMsg` variable should be set to the result of `getLoanMessage(85000, 850)`.
+
+```js
+assert.equal(duplexLoanMsg, getLoanMessage(85000, 850));
+```
+
+You should log the `duplexLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(duplexLoanMsg\)/)
+```
+
+You should have a variable called `condoLoanMsg`.
+
+```js
+assert.isNotNull(condoLoanMsg);
+```
+
+Your `condoLoanMsg` variable should be set to the result of `getLoanMessage(65000, 690)`.
+
+```js
+assert.equal(condoLoanMsg, getLoanMessage(65000, 690));
+```
+
+You should log the `condoLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(condoLoanMsg\)/)
+```
+
+You should have a variable called `carLoanMsg`.
+
+```js
+assert.isNotNull(carLoanMsg);
+```
+
+Your `carLoanMsg` variable should be set to the result of `getLoanMessage(45000, 660)`.
+
+```js
+assert.equal(carLoanMsg, getLoanMessage(45000, 660));
+```
+
+You should log the `carLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(carLoanMsg\)/)
+```
+
+You should have a variable called `noLoanMsg`.
+
+```js
+assert.isNotNull(noLoanMsg);
+```
+
+Your `noLoanMsg` variable should be set to the result of `getLoanMessage(25000, 550)`.
+
+```js
+assert.equal(noLoanMsg, getLoanMessage(25000, 550));
+```
+
+You should log the `noLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(noLoanMsg\)/)
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
+
+# --solutions--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+const duplexLoanMsg = getLoanMessage(85000, 850)
+console.log(duplexLoanMsg)
+
+const condoLoanMsg = getLoanMessage(65000, 690)
+console.log(condoLoanMsg)
+
+const carLoanMsg = getLoanMessage(45000, 660)
+console.log(carLoanMsg)
+
+const noLoanMsg = getLoanMessage(25000, 550)
+console.log(noLoanMsg)
+```
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md b/curriculum/challenges/italian/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
new file mode 100644
index 0000000000..4e11751ca0
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
@@ -0,0 +1,19 @@
+---
+id: 5f2c289f164c29556da632fd
+title: Build a Mario Database
+challengeType: 12
+url: freeCodeCamp/learn-relational-databases-by-building-a-mario-database
+dashedName: build-a-mario-database
+---
+
+# --description--
+
+In this 165-lesson workshop, you will learn the basics of a relational database by creating a PostgreSQL database filled with video game characters.
+
+# --instructions--
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
new file mode 100644
index 0000000000..8d4c90410d
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
@@ -0,0 +1,53 @@
+---
+id: 587d7fb3367417b2b2512bfb
+title: How to Use package.json, the Core of Any Node.js Project or npm Package
+challengeType: 2
+forumTopicId: 301528
+dashedName: how-to-use-package-json-the-core-of-any-node-js-project-or-npm-package
+---
+
+# --description--
+
+Working on these challenges will involve you writing your code using one of the following methods:
+
+- Clone <a href="https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete these challenges locally.
+- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+The `package.json` file is the center of any Node.js project or npm package. It stores information about your project. It consists of a single JSON object where information is stored in key-value pairs. There are only two required fields; `name` and `version`, but it’s good practice to provide additional information.
+
+You can create the `package.json` file from the terminal using the `npm init` command. This will run a guided setup. Using `npm init` with the `-y` flag will generate the file without having it ask any questions, `npm init -y`.
+
+If you look at the file tree of your project, you will find the `package.json` file on the top level of the tree. This is the file that you will be improving in the next couple of challenges.
+
+One of the most common pieces of information in this file is the `author` field. It specifies who created the project, and can consist of a string or an object with contact or other details. An object is recommended for bigger projects, but a simple string like the following example will do for this project.
+
+```json
+"author": "Jane Doe",
+```
+
+# --instructions--
+
+Add your name as the `author` of the project in the `package.json` file.
+
+**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (") and be separated with a comma (,).
+
+If you are using Gitpod, make sure the app is running and the preview window is open. Copy the preview window's URL and paste it into the Solution Link input below.
+
+# --hints--
+
+`package.json` should have a valid "author" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.author, '"author" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
new file mode 100644
index 0000000000..37d15d5261
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb3367417b2b2512bfc
+title: Add a Description to Your package.json
+challengeType: 2
+forumTopicId: 301522
+dashedName: add-a-description-to-your-package-json
+---
+
+# --description--
+
+The next part of a good package.json file is the `description` field; where a short, but informative description about your project belongs.
+
+If some day you plan to publish a package to npm, this is the string that should sell your idea to the user when they decide whether to install your package or not. However, that’s not the only use case for the description, it’s a great way to summarize what a project does. It’s just as important in any Node.js project to help other developers, future maintainers or even your future self understand the project quickly.
+
+Regardless of what you plan for your project, a description is definitely recommended. Here's an example:
+
+```json
+"description": "A project that does something awesome",
+```
+
+# --instructions--
+
+Add a `description` to the package.json file of your project.
+
+**Note:** Remember to use double-quotes for field-names (") and commas (,) to separate fields.
+
+# --hints--
+
+package.json should have a valid "description" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.description, '"description" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
new file mode 100644
index 0000000000..a001cdd477
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
@@ -0,0 +1,75 @@
+---
+id: 587d7fb4367417b2b2512bfd
+title: Add Keywords to Your package.json
+challengeType: 2
+forumTopicId: 301526
+dashedName: add-keywords-to-your-package-json
+---
+
+# --description--
+
+The `keywords` field is where you can describe your project using related keywords. Here's an example:
+
+```json
+"keywords": [ "descriptive", "related", "words" ],
+```
+
+As you can see, this field is structured as an array of double-quoted strings.
+
+# --instructions--
+
+Add an array of suitable strings to the `keywords` field in the package.json file of your project.
+
+One of the keywords should be "freecodecamp".
+
+# --hints--
+
+package.json should have a valid "keywords" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.keywords, '"keywords" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" field should be an Array
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.isArray(packJson.keywords, '"keywords" is not an array');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" should include "freecodecamp"
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.include(
+        packJson.keywords,
+        'freecodecamp',
+        '"keywords" does not include "freecodecamp"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
new file mode 100644
index 0000000000..7b09acd042
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
@@ -0,0 +1,39 @@
+---
+id: 587d7fb4367417b2b2512bfe
+title: Add a License to Your package.json
+challengeType: 2
+forumTopicId: 301523
+dashedName: add-a-license-to-your-package-json
+---
+
+# --description--
+
+The `license` field is where you inform users of what they are allowed to do with your project.
+
+Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do. Here's an example of the license field:
+
+```json
+"license": "MIT",
+```
+
+# --instructions--
+
+Fill the `license` field in the package.json file of your project as you find suitable.
+
+# --hints--
+
+package.json should have a valid "license" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.license, '"license" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
new file mode 100644
index 0000000000..f2e571faed
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
@@ -0,0 +1,37 @@
+---
+id: 587d7fb4367417b2b2512bff
+title: Add a Version to Your package.json
+challengeType: 2
+forumTopicId: 301525
+dashedName: add-a-version-to-your-package-json
+---
+
+# --description--
+
+A `version` is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example:
+
+```json
+"version": "1.2.0",
+```
+
+# --instructions--
+
+Add a `version` to the package.json file of your project.
+
+# --hints--
+
+package.json should have a valid "version" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.version, '"version" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
new file mode 100644
index 0000000000..161c60fe69
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
@@ -0,0 +1,68 @@
+---
+id: 587d7fb4367417b2b2512c00
+title: Expand Your Project with External Packages from npm
+challengeType: 2
+forumTopicId: 301527
+dashedName: expand-your-project-with-external-packages-from-npm
+---
+
+# --description--
+
+One of the biggest reasons to use a package manager, is their powerful dependency management. Instead of manually having to make sure that you get all dependencies whenever you set up a project on a new computer, npm automatically installs everything for you. But how can npm know exactly what your project needs? Meet the `dependencies` section of your package.json file.
+
+In this section, packages your project requires are stored using the following format:
+
+```json
+"dependencies": {
+  "package-name": "version",
+  "express": "4.14.0"
+}
+
+```
+
+# --instructions--
+
+Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file.
+
+**Note:** `@freecodecamp/example` is a faux package used as a learning tool.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.1.0"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^[\^\~]?1\.1\.0/,
+        'Wrong version of "@freecodecamp/example" installed. It should be 1.1.0'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
new file mode 100644
index 0000000000..deda9b82de
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
@@ -0,0 +1,64 @@
+---
+id: 587d7fb5367417b2b2512c01
+title: Manage npm Dependencies By Understanding Semantic Versioning
+challengeType: 2
+forumTopicId: 301529
+dashedName: manage-npm-dependencies-by-understanding-semantic-versioning
+---
+
+# --description--
+
+`Versions` of the npm packages in the dependencies section of your package.json file follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes projects can expect if they update.
+
+Knowing SemVer can be useful when you develop software that uses external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things that worked yesterday suddenly don’t work today. This is how Semantic Versioning works according to the official website:
+
+```json
+"package": "MAJOR.MINOR.PATCH"
+```
+
+The MAJOR version should increment when you make incompatible API changes. The MINOR version should increment when you add functionality in a backwards-compatible manner. The PATCH version should increment when you make backwards-compatible bug fixes. This means that PATCHes are bug fixes and MINORs add new features but neither of them break what worked before. Finally, MAJORs add changes that won’t work with earlier versions.
+
+# --instructions--
+
+In the dependencies section of your `package.json` file, change the version of `@freecodecamp/example` to match MAJOR version 1, MINOR version 2 and PATCH version 13
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.equal(
+        packJson.dependencies["@freecodecamp/example"],
+        '1.2.13',
+        'Wrong version of "@freecodecamp/example". It should be 1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
new file mode 100644
index 0000000000..8eae5f51ee
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c02
+title: Use the Tilde-Character to Always Use the Latest Patch Version of a Dependency
+challengeType: 2
+forumTopicId: 301532
+dashedName: use-the-tilde-character-to-always-use-the-latest-patch-version-of-a-dependency
+---
+
+# --description--
+
+In the last challenge, you told npm to only include a specific version of a package. That’s a useful way to freeze your dependencies if you need to make sure that different parts of your project stay compatible with each other. But in most use cases, you don’t want to miss bug fixes since they often include important security patches and (hopefully) don’t break things in doing so.
+
+To allow an npm dependency to update to the latest PATCH version, you can prefix the dependency’s version with the tilde (`~`) character. Here's an example of how to allow updates to any `1.3.x` version.
+
+```json
+"package": "~1.3.8"
+```
+
+# --instructions--
+
+In the package.json file, your current rule for how npm may upgrade `@freecodecamp/example` is to use a specific version (`1.2.13`). But now, you want to allow the latest `1.2.x` version.
+
+Use the tilde (`~`) character to prefix the version of `@freecodecamp/example` in your dependencies, and allow npm to update it to any new _patch_ release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"~1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\~1\.2\.13/,
+        'Wrong version of "@freecodecamp/example". It should be ~1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
new file mode 100644
index 0000000000..adc3014ea4
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c03
+title: Use the Caret-Character to Use the Latest Minor Version of a Dependency
+challengeType: 2
+forumTopicId: 301531
+dashedName: use-the-caret-character-to-use-the-latest-minor-version-of-a-dependency
+---
+
+# --description--
+
+Similar to how the tilde we learned about in the last challenge allows npm to install the latest PATCH for a dependency, the caret (`^`) allows npm to install future updates as well. The difference is that the caret will allow both MINOR updates and PATCHes.
+
+Your current version of `@freecodecamp/example` should be `~1.2.13` which allows npm to install to the latest `1.2.x` version. If you were to use the caret (^) as a version prefix instead, npm would be allowed to update to any `1.x.x` version.
+
+```json
+"package": "^1.3.8"
+```
+
+This would allow updates to any `1.x.x` version of the package.
+
+# --instructions--
+
+Use the caret (`^`) to prefix the version of `@freecodecamp/example` in your dependencies and allow npm to update it to any new MINOR release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"^1.x.x"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\^1\./,
+        'Wrong version of "@freecodecamp/example". It should be ^1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
new file mode 100644
index 0000000000..5f695eed88
--- /dev/null
+++ b/curriculum/challenges/italian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb5367417b2b2512c04
+title: Remove a Package from Your Dependencies
+challengeType: 2
+forumTopicId: 301530
+dashedName: remove-a-package-from-your-dependencies
+---
+
+# --description--
+
+You have now tested a few ways you can manage dependencies of your project by using the package.json's dependencies section. You have also included external packages by adding them to the file and even told npm what types of versions you want, by using special characters such as the tilde or the caret.
+
+But what if you want to remove an external package that you no longer need? You might already have guessed it, just remove the corresponding key-value pair for that package from your dependencies.
+
+This same method applies to removing other fields in your package.json as well.
+
+# --instructions--
+
+Remove the `@freecodecamp/example` package from your dependencies.
+
+**Note:** Make sure you have the right amount of commas after removing it.
+
+# --hints--
+
+`"dependencies"` should not include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.notProperty(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" still includes "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/japanese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md b/curriculum/challenges/japanese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
index 959761b914..6efd95e6d2 100644
--- a/curriculum/challenges/japanese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
+++ b/curriculum/challenges/japanese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
@@ -8,7 +8,7 @@ dashedName: build-a-periodic-table-database
 
 # --description--
 
-これは認定証を獲得するために必須のプロジェクトの 1 つです。 このプロジェクトでは、周期表データベースから化学元素の情報を取得する、Bash スクリプトを作成します。
+これは認定証を獲得するために必須のプロジェクトの 1 つです。 For this project, you will create a Bash script to get information about chemical elements from a periodic table database.
 
 # --instructions--
 
diff --git a/curriculum/challenges/japanese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md b/curriculum/challenges/japanese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
index 163d37a75e..b88a481061 100644
--- a/curriculum/challenges/japanese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
+++ b/curriculum/challenges/japanese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
@@ -9,6 +9,8 @@ dashedName: step-64
 
 `footer` の中に、`p` 要素を 1 つ追加してください。 次に、リンク先が `https://www.freecodecamp.org` でテキストが `Visit our website` のアンカー (`a`) 要素を、`p` 要素の中にネストしてください。
 
+Make sure that the link opens in a new tab by adding a `target` attribute with the value `_blank`.
+
 # --hints--
 
 既存の `footer` 要素を変更しないでください。
@@ -43,6 +45,12 @@ assert(document.querySelector("footer > p > a")?.innerText === "Visit our websit
 assert(document.querySelector("footer > p > a")?.href === "https://www.freecodecamp.org/");
 ```
 
+Your new `a` element should have the `target` attribute set to `_blank`.
+
+```js
+assert.equal(document.querySelector("footer > p > a")?.target, "_blank");
+```
+
 # --seed--
 
 ## --seed-contents--
diff --git a/curriculum/challenges/japanese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md b/curriculum/challenges/japanese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
index d2ad72a1ea..1b6ca05444 100644
--- a/curriculum/challenges/japanese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
+++ b/curriculum/challenges/japanese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
@@ -21,12 +21,12 @@ Remove `flex: 1` from `.item` and add `justify-content: space-between` to `.cont
 
 `justify-content` aligns items across the **main axis**. There are a few values that you can use here. You'll learn the rest of them in the reading assignments, but for now try changing it to center, which should center the boxes along the main axis.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see what is possible with the `justify-content` property. Read this [interactive article on MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) and play around with the different values of `justify-content` on the example.
 
+# --question--
+
 ## --text--
 
 How does applying `justify-content: space-between` to a flex container affect the positioning of its items?
diff --git a/curriculum/challenges/japanese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md b/curriculum/challenges/japanese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
index d3137b0af5..59acb55a29 100644
--- a/curriculum/challenges/japanese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
+++ b/curriculum/challenges/japanese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
@@ -17,12 +17,12 @@ To change the placement of items along the cross axis use `align-items`. Try get
 
 Because `justify-content` and `align-items` are based on the main and cross axis of your container, their behavior changes when you change the flex-direction of a flex-container. For example, when you change `flex-direction` to `column`, `justify-content` aligns vertically and `align-items` aligns horizontally. The most common behavior, however, is the default, i.e. `justify-content` aligns items horizontally (because the main axis defaults to horizontal), and `align-items` aligns them vertically. One of the biggest sticking points that beginners have with flexbox is confusion when this behavior changes.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see if you can figure out how `align-items` behaves when you change the `flex-direction` property to `column`.
 
+# --question--
+
 ## --text--
 
 When changing the `flex-direction` property to `column` in a flex container, how does `align-items` behave in relation to the flex items?
diff --git a/curriculum/challenges/japanese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md b/curriculum/challenges/japanese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
index 1adf9ce84f..49edeac0e4 100644
--- a/curriculum/challenges/japanese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
+++ b/curriculum/challenges/japanese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
@@ -9,12 +9,12 @@ dashedName: learn-block-and-inline-lesson-b
 
 Inline elements, however, do not start on a new line. They appear in line with whatever elements they are placed beside. A clear example of an inline element is a link, or `<a>` tag. If you stick one of these in the middle of a paragraph of text, it will behave like a part of the paragraph. <a  href="https://www.freecodecamp.org/" target="_blank">(Like this)</a> The link’s text will sit alongside other words in that paragraph. Additionally, padding and margin behave differently on inline elements. In general, you do not want to try to put extra padding or margin on inline elements.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Search the web for a list of `block` elements and a list of `inline` elements.
 
+# --question--
+
 ## --text--
 
 What is the difference between a `block` element and an `inline` element?
diff --git a/curriculum/challenges/japanese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md b/curriculum/challenges/japanese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
index cdd4d5aa87..e75492e9c1 100644
--- a/curriculum/challenges/japanese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
+++ b/curriculum/challenges/japanese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-block-and-inline-lesson-g
 
 # --description--
 
-Now that you have some basic understanding of `block` and inline `elements`, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
+Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
 
 # --question--
 
diff --git a/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md b/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
index 995073b8a2..a7a2ee9a51 100644
--- a/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
+++ b/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
@@ -21,12 +21,12 @@ New programmers often find problem solving the hardest skill to build. It's not
 
 The best way to improve your problem solving ability is by building experience by making lots and lots of programs. The more practice you have the better you'll be prepared to solve real world problems.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Read <a href="https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/" target="_blank">How to Think Like a Programmer - Lessons in Problem Solving</a> by Richard Reis.
 
+# --question--
+
 ## --text--
 
 According to V. Anton Spraul in "Think Like a Programmer," what is problem solving in programming?
diff --git a/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md b/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
index ae905ecf89..c57a7d43e8 100644
--- a/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
+++ b/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
@@ -25,11 +25,11 @@ Now that you know what you’re aiming to solve, don’t jump into coding just y
 
 The last question is where you will write out an algorithm to solve the problem. You can think of an algorithm as a recipe for solving a particular problem. It defines the steps that need to be taken by the computer to solve a problem in pseudocode.
 
-# --question--
-
-## --assignment--
+# --assignment--
 Watch <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">How to Begin Thinking Like a Programmer</a> by Coding Tech. It’s an hour long but packed full of information and definitely worth your time watching.
 
+# --question--
+
 ## --text--
 
 What should you do before starting to code according to the provided text?
diff --git a/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md b/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
index c837fd9658..082f2d51ae 100644
--- a/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
+++ b/curriculum/challenges/japanese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
@@ -22,12 +22,12 @@ Print the value of the counter variable
 
 This is a basic program to demonstrate how pseudocode looks. There will be more examples of pseudocode included in the assignments.
 
+# --assignment--
 
-# --question--
-
-## --assignment--
 Read this <a href="https://builtin.com/data-science/pseudocode" target="_blank"> Pseudocode: What It Is and How to Write It</a> article from Built In.
 
+# --question--
+
 ## --text--
 
 What are the benefits of using pseudocode according to the linked article?
diff --git a/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md b/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
index fcc8d61952..bd690bae21 100644
--- a/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
+++ b/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-So far you have learned how to create questions with the verb to be. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
+So far you have learned how to create questions with the verb `to be`. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
 
 `You are a developer` -> `Are you a developer?`
 
diff --git a/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md b/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
index 544d8f1988..8cd311a518 100644
--- a/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
+++ b/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
@@ -21,7 +21,7 @@ Which sentence is correct for describing one place near you?
 
 ### --feedback--
 
-`There are` is used for plural nouns, and `bank` is singular. You’ll learn about there are in the next few lessons.
+`There are` is used for plural nouns, and `bank` is singular. You’ll learn about `there are` in the next few lessons.
 
 ---
 
diff --git a/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md b/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
index 6526b1e95b..10c0845779 100644
--- a/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
+++ b/curriculum/challenges/japanese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
@@ -7,7 +7,7 @@ dashedName: task-112
 
 # --description--
 
-To elaborate a question using `there is` you just need to change the order of the verb to be, like so:
+To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so:
 
 `There is an ATM nearby` -> `Is there an ATM nearby?`
 
diff --git a/curriculum/challenges/japanese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md b/curriculum/challenges/japanese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
new file mode 100644
index 0000000000..7d664a8876
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
@@ -0,0 +1,25 @@
+---
+id: 5f1a4ef5d5d6b5ab580fc6ae
+title: Build a Celestial Bodies Database
+challengeType: 13
+url: freeCodeCamp/learn-celestial-bodies-database
+dashedName: lab-celestial-bodies-database
+---
+
+# --description--
+
+For this project, you will build a database of celestial bodies using PostgreSQL.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `universe.sql` file so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `universe.sql`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/japanese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md b/curriculum/challenges/japanese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
new file mode 100644
index 0000000000..9492b82cb4
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
@@ -0,0 +1,611 @@
+---
+id: 5a8b073d06fa14fcfde687aa
+title: Build an Exercise Tracker
+challengeType: 4
+dashedName: build-an-exercise-tracker
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://exercise-tracker.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://exercise-tracker.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+Your responses should have the following structures.
+
+Exercise:
+
+```js
+{
+  username: "fcc_test",
+  description: "test",
+  duration: 60,
+  date: "Mon Jan 01 1990",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+User:
+
+```js
+{
+  username: "fcc_test",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Log:
+
+```js
+{
+  username: "fcc_test",
+  count: 1,
+  _id: "5fb5853f734231456ccb3b05",
+  log: [{
+    description: "test",
+    duration: 60,
+    date: "Mon Jan 01 1990",
+  }]
+}
+```
+
+**Hint:** For the `date` property, the `toDateString` method of the `Date` API can be used to achieve the expected output.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  const url = getUserInput('url');
+  assert(
+    !/.*\/exercise-tracker\.freecodecamp\.rocks/.test(getUserInput('url'))
+  );
+};
+```
+
+You can `POST` to `/api/users` with form data `username` to create a new user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The returned response from `POST /api/users` with form data `username` will be an object with `username` and `_id` properties.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    assert.exists(_id);
+    assert.exists(username);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users` to get a list of all users.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `GET` request to `/api/users` returns an array.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    assert.isArray(users);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Each element in the array returned from `GET /api/users` is an object literal containing a user's `username` and `_id`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    const user = users[0];
+    assert.exists(user);
+    assert.exists(user.username);
+    assert.exists(user._id);
+    assert.isString(user.username);
+    assert.isString(user._id);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can `POST` to `/api/users/:_id/exercises` with form data `description`, `duration`, and optionally `date`. If no date is supplied, the current date will be used.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+  assert.isTrue(addRes.ok);
+  if(!addRes.ok) {
+    throw new Error(`${addRes.status} ${addRes.statusText}`)
+  };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+The response returned from `POST /api/users/:_id/exercises` will be the user object with the exercise fields added.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    if (addRes.ok) {
+      const actual = await addRes.json();
+      assert.deepEqual(actual, expected);
+      assert.isString(actual.description);
+      assert.isNumber(actual.duration);
+      assert.isString(actual.date);
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users/:_id/logs` to retrieve a full exercise log of any user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+    assert.isTrue(logRes.ok);
+    if(!logRes.ok) {
+      throw new Error(`${logRes.status} ${logRes.statusText}`)
+    };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A request to a user's log `GET /api/users/:_id/logs` returns a user object with a `count` property representing the number of exercises that belong to that user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if (logRes.ok) {
+        const { count } = await logRes.json();
+        assert(count);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A `GET` request to `/api/users/:_id/logs` will return the user object with a `log` array of all the exercises added.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  })
+  if(res.ok){
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok){
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+Each item in the `log` array that is returned from `GET /api/users/:_id/logs` is an object that should have a `description`, `duration`, and `date` properties.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + `/api/users`, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+     const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.exists(exercise);
+        assert.exists(exercise.description);
+        assert.exists(exercise.duration);
+        assert.exists(exercise.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `description` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.description);
+        assert.equal(exercise.description, expected.description);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `duration` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a number.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isNumber(exercise.duration);
+        assert.equal(exercise.duration, expected.duration);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `date` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string. Use the `dateString` format of the `Date` API.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toLocaleDateString("en-US", {
+        timeZone: "UTC", weekday: "short", month: "short",
+        day: "2-digit", year: "numeric"
+      }).replaceAll(',', '')
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.date);
+        assert.equal(exercise.date, expected.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can add `from`, `to` and `limit` parameters to a `GET /api/users/:_id/logs` request to retrieve part of the log of any user. `from` and `to` are dates in `yyyy-mm-dd` format. `limit` is an integer of how many logs to send back.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addExerciseRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    const addExerciseTwoRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-03`
+    });
+    if (addExerciseRes.ok && addExerciseTwoRes.ok) {
+      const logRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1989-12-31&to=1990-01-04`
+      );
+      if (logRes.ok) {
+        const { log } = await logRes.json();
+        assert.isArray(log);
+        assert.equal(2, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+      const limitRes = await fetch(
+        url + `/api/users/${_id}/logs?limit=1`
+      );
+      if (limitRes.ok) {
+        const { log } = await limitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${limitRes.status} ${limitRes.statusText}`);
+      }
+      const filterDateBeforeLimitRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1990-01-02&to=1990-01-04&limit=1`
+      );
+      if (filterDateBeforeLimitRes.ok) {
+        const { log } = await filterDateBeforeLimitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${filterDateBeforeLimitRes.status} ${filterDateBeforeLimitRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${res.status} ${res.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
diff --git a/curriculum/challenges/japanese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md b/curriculum/challenges/japanese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
new file mode 100644
index 0000000000..ef87dc6720
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
@@ -0,0 +1,25 @@
+---
+id: 602da04c22201c65d2a019f4
+title: Build a Number Guessing Game
+challengeType: 13
+url: freeCodeCamp/learn-number-guessing-game
+dashedName: lab-number-guessing-game
+---
+
+# --description--
+
+For this lab, you will use Bash scripting, PostgreSQL, and Git to create a number guessing game that runs in the terminal and saves user information.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `number_guess.sql` file, as well as your `number_guess.sh` file, so you can complete step 2. There will be instructions on how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `number_guess.sql`, `number_guess.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/japanese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md b/curriculum/challenges/japanese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
new file mode 100644
index 0000000000..5040e27424
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
@@ -0,0 +1,65 @@
+---
+id: bd7158d8c443edefaeb5bdff
+title: Build a Request Header Parser Microservice
+challengeType: 4
+dashedName: lab-request-header-parser-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://request-header-parser-microservice.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://request-header-parser-microservice.freecodecamp.rocks/</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/request-header-parser-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+A request to `/api/whoami` should return a JSON object with your IP address in the `ipaddress` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.ipaddress && data.ipaddress.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your preferred language in the `language` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.language && data.language.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your software in the `software` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.software && data.software.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/japanese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md b/curriculum/challenges/japanese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
new file mode 100644
index 0000000000..0fbf80a0bf
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
@@ -0,0 +1,107 @@
+---
+id: bd7158d8c443edefaeb5bd0e
+title: URL Shortener Microservice
+challengeType: 4
+dashedName: url-shortener-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://url-shortener-microservice.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://url-shortener-microservice.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+**HINT:** Do not forget to use a body parsing middleware to handle the POST requests. Also, you can use the function `dns.lookup(host, cb)` from the `dns` core module to verify a submitted URL.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/url-shortener-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+You can POST a URL to `/api/shorturl` and get a JSON response with `original_url` and `short_url` properties. Here's an example: `{ original_url : 'https://freeCodeCamp.org', short_url : 1}`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (res.ok) {
+    const { short_url, original_url } = await res.json();
+    assert.isNotNull(short_url);
+    assert.strictEqual(original_url, `${url}/?v=${urlVariable}`);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+When you visit `/api/shorturl/<short_url>`, you will be redirected to the original URL.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  let shortenedUrlVariable;
+  const postResponse = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (postResponse.ok) {
+    const { short_url } = await postResponse.json();
+    shortenedUrlVariable = short_url;
+  } else {
+    throw new Error(`${postResponse.status} ${postResponse.statusText}`);
+  }
+  const getResponse = await fetch(
+    url + '/api/shorturl/' + shortenedUrlVariable
+  );
+  if (getResponse) {
+    const { redirected, url } = getResponse;
+    assert.isTrue(redirected);
+    assert.strictEqual(url,fullUrl);
+  } else {
+    throw new Error(`${getResponse.status} ${getResponse.statusText}`);
+  }
+};
+```
+
+If you pass an invalid URL that doesn't follow the valid `http://www.example.com` format, the JSON response will contain `{ error: 'invalid url' }`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=ftp:/john-doe.invalidTLD`
+  });
+  if (res.ok) {
+    const { error } = await res.json();
+    assert.isNotNull(error);
+    assert.strictEqual(error.toLowerCase(), 'invalid url');
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
diff --git a/curriculum/challenges/japanese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md b/curriculum/challenges/japanese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
new file mode 100644
index 0000000000..d77442a1ba
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
@@ -0,0 +1,25 @@
+---
+id: 5f9771307d4d22b9d2b75a94
+title: Build a World Cup Database
+challengeType: 13
+url: freeCodeCamp/learn-world-cup-database
+dashedName: lab-world-cup-database
+---
+
+# --description--
+
+For this project, you will create a Bash script that enters information from World Cup games into PostgreSQL, then query the database for useful statistics.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `worldcup.sql` file, as well as your `insert_data.sh` and `queries.sh` files, so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `worldcup.sql`, `insert_data.sh`, `queries.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md b/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
index 51ea9e3069..753ee1a6bb 100644
--- a/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
@@ -7,9 +7,9 @@ dashedName: step-22
 
 # --description--
 
-Add another label with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
+Add another `label` with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
 
-Below the label element, add another checkbox input with the `id`, `name` and `value` attributes set to `"recommendation"`.
+Below the `label` element, add another checkbox `input` with the `id`, `name` and `value` attributes set to `"recommendation"`.
 
 # --hints--
 
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md b/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
index 42c425209d..80a23ca86d 100644
--- a/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
@@ -11,7 +11,7 @@ Next, add another `label` element with the text of `Location` and the `for` attr
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"location"`.
 
-Below that `input` element, add another `label` element with the text of `Reputation` and the for attribute set to `"reputation"`.
+Below that `input` element, add another `label` element with the text of `Reputation` and the `for` attribute set to `"reputation"`.
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"reputation"`.
 
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md b/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
index 69efa4832c..09e3e6e59b 100644
--- a/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
@@ -7,7 +7,7 @@ dashedName: step-28
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attributes:**
 
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md b/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
index 6549345d45..22b9a707be 100644
--- a/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
@@ -7,7 +7,7 @@ dashedName: step-31
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attribute:**
 
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
new file mode 100644
index 0000000000..237515fd88
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
@@ -0,0 +1,71 @@
+---
+id: 66c8ba41a77db20a93f9d7a1
+title: Step 1
+challengeType: 1
+dashedName: step-1
+---
+
+# --description--
+
+In this workshop, you'll review JavaScript conditionals by building a loan qualification checker app.
+
+The app will check whether the user is eligible for a duplex, car, and condo loan based on their annual income and credit score. A credit score is a number that represents how good you are at managing borrowed money.
+
+To get started, create the following variables and values.
+
+| Variable Name             | Value   |
+| ------------------------- | ------- |
+| `minIncomeForDuplex`      | `60000` |
+| `minCreditScoreForDuplex` | `700`   |
+| `minIncomeForCondo`       | `45000` |
+| `minCreditScoreForCondo`  | `680`   |
+| `minIncomeForCar`         | `30000` |
+| `minCreditScoreForCar`    | `650`   |
+
+# --hints--
+
+You should create a `minIncomeForDuplex` variable set to `60000`.
+
+```js
+assert.equal(minIncomeForDuplex, 60000);
+```
+
+You should create a `minCreditScoreForDuplex` set to `700`.
+
+```js
+assert.equal(minCreditScoreForDuplex, 700);
+```
+
+You should create a `minIncomeForCar` variable set to `30000`.
+
+```js
+assert.equal(minIncomeForCar, 30000);
+```
+
+You should create a `minCreditScoreForCar` variable set to `650`.
+
+```js
+assert.equal(minCreditScoreForCar, 650);
+```
+
+You should create a `minIncomeForCondo` variable set to `45000`.
+
+```js
+assert.equal(minIncomeForCondo, 45000);
+```
+
+You should create a `minCreditScoreForCondo` variable set to `680`.
+
+```js
+assert.equal(minCreditScoreForCondo, 680);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
new file mode 100644
index 0000000000..7755f823c4
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
@@ -0,0 +1,53 @@
+---
+id: 66c8ba975ee7230e29f6c4ac
+title: Step 2
+challengeType: 1
+dashedName: step-2
+---
+
+# --description--
+
+When the user is eligible for a loan, you'll want to display a message to them in the console.
+
+For that, you'll build out a function inside which you'll have some checks that'll return what loan the applicant is eligible for.
+
+Create an empty `getLoanMessage` function with an `annualIncome` and `creditScore` parameters.
+
+# --hints--
+
+You should create a `getLoanMessage` function
+
+```js
+assert.isFunction(getLoanMessage)
+```
+
+Your `getLoanMessage` function should have an `annualIncome` and `creditScore` as parameters.
+
+```js
+assert.match(getLoanMessage?.toString(), /\(\s*annualIncome,\s*creditScore\s*\)|\(\s*creditScore,\s*annualIncome\s*\)/);
+```
+
+`getLoanMessage` should be an empty function.
+
+```js
+assert.match(getLoanMessage?.toString(), /\{\s*\}/);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
new file mode 100644
index 0000000000..82a29d7cd9
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
@@ -0,0 +1,55 @@
+---
+id: 66c8ba975ee7230e29f6c4ad
+title: Step 3
+challengeType: 1
+dashedName: step-3
+---
+
+# --description--
+
+To check which loan a user is qualified for based on the `annualIncome` and `creditScore`, you have to use `if/else if` statement or a ternary right inside the `getLoanMessage` function. You'll then return the appropraite message in the block of each condition.
+
+Starting with the duplex loan, check if `annualIncome` is greater than or equal to `minIncomeForDuplex` AND if `creditScore` is greater than `minCreditScoreForDuplex`.
+
+If that condition is true, then the applicant is eligible for a duplex loan and the other loans. So, inside the check, return the string `"You qualify for a car, duplex and Condo loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string.
+
+```js
+assert.isString(getLoanMessage(65000, 750));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a duplex, condo, and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(65000, 750), "You qualify for a duplex, condo, and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a duplex loan.
+
+```js
+assert.strictEqual(getLoanMessage(59000, 700), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+function getLoanMessage(annualIncome, creditScore) {
+
+}
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
new file mode 100644
index 0000000000..638e6291a4
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4af
+title: Step 4
+challengeType: 1
+dashedName: step-4
+---
+
+# --description--
+
+If the applicant's annual income is greater than or equal to `minIncomeForCondo`, AND if their credit score is greater than or equal to `minCreditScoreForCondo`, then they qualify for a condo and car loan.
+
+Check if that's true in the `getLoanMessage` function. If it is, return the string `"You qualify for a condo and car loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a condo and car loan.
+
+```js
+assert.isString(getLoanMessage(45000, 680));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a condo and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 680), "You qualify for a condo and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a condo loan.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 650), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
new file mode 100644
index 0000000000..374ba7b8fe
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4b0
+title: Step 5
+challengeType: 1
+dashedName: step-5
+---
+
+# --description--
+
+Now, you should check if the applicant is qualified for a car loan only. If they're, return the string `"You qualify for a car loan."`.
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a car loan.
+
+```js
+assert.isString(getLoanMessage(30000, 650));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 650), "You qualify for a car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a car loan.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 600), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+--fcc-editable-region--
+  } 
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
new file mode 100644
index 0000000000..16e8c7baca
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
@@ -0,0 +1,54 @@
+---
+id: 66c8ba975ee7230e29f6c4b1
+title: Step 6
+challengeType: 1
+dashedName: step-6
+---
+
+# --description--
+
+If the applicant's annual income and credit score fall below `minIncomeForCar` and `minCreditScoreForCar`, then they don't qualify for any loan. So, return the string `"You don't qualify for any loans."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant doesn't qualify for any loan.
+
+```js
+assert.isString(getLoanMessage(25000, 550));
+```
+
+Your `getLoanMessage` function should return the string `"You don't qualify for any loans."` if the applicant does not meet the requirements for any loan.
+
+```js
+assert.strictEqual(getLoanMessage(15000, 600), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(25000, 550), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(20000, 500), "You don't qualify for any loans.");
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
new file mode 100644
index 0000000000..9d19f9ea4c
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
@@ -0,0 +1,165 @@
+---
+id: 66c8ba975ee7230e29f6c4b2
+title: Step 7
+challengeType: 1
+dashedName: step-7
+---
+
+# --description--
+
+Now, it is time to test out your `getLoanMessage` function.
+
+Use the table below to create `4` variables and their values:
+
+| Variable Name   | Value                        |
+| --------------- | ---------------------------- |
+| `duplexLoanMsg` | `getLoanMessage(85000, 850)` |
+| `condoLoanMsg`  | `getLoanMessage(65000, 690)` |
+| `carLoanMsg`    | `getLoanMessage(45000, 660)` |
+| `noLoanMsg`     | `getLoanMessage(25000, 550)` |
+
+After that, log each variable to the console to see the messages.
+
+With that, your loan qualification checker project is complete!
+
+# --hints--
+
+You should have a variable called `duplexLoanMsg`.
+
+```js
+assert.isNotNull(duplexLoanMsg);
+```
+
+Your `duplexLoanMsg` variable should be set to the result of `getLoanMessage(85000, 850)`.
+
+```js
+assert.equal(duplexLoanMsg, getLoanMessage(85000, 850));
+```
+
+You should log the `duplexLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(duplexLoanMsg\)/)
+```
+
+You should have a variable called `condoLoanMsg`.
+
+```js
+assert.isNotNull(condoLoanMsg);
+```
+
+Your `condoLoanMsg` variable should be set to the result of `getLoanMessage(65000, 690)`.
+
+```js
+assert.equal(condoLoanMsg, getLoanMessage(65000, 690));
+```
+
+You should log the `condoLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(condoLoanMsg\)/)
+```
+
+You should have a variable called `carLoanMsg`.
+
+```js
+assert.isNotNull(carLoanMsg);
+```
+
+Your `carLoanMsg` variable should be set to the result of `getLoanMessage(45000, 660)`.
+
+```js
+assert.equal(carLoanMsg, getLoanMessage(45000, 660));
+```
+
+You should log the `carLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(carLoanMsg\)/)
+```
+
+You should have a variable called `noLoanMsg`.
+
+```js
+assert.isNotNull(noLoanMsg);
+```
+
+Your `noLoanMsg` variable should be set to the result of `getLoanMessage(25000, 550)`.
+
+```js
+assert.equal(noLoanMsg, getLoanMessage(25000, 550));
+```
+
+You should log the `noLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(noLoanMsg\)/)
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
+
+# --solutions--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+const duplexLoanMsg = getLoanMessage(85000, 850)
+console.log(duplexLoanMsg)
+
+const condoLoanMsg = getLoanMessage(65000, 690)
+console.log(condoLoanMsg)
+
+const carLoanMsg = getLoanMessage(45000, 660)
+console.log(carLoanMsg)
+
+const noLoanMsg = getLoanMessage(25000, 550)
+console.log(noLoanMsg)
+```
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md b/curriculum/challenges/japanese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
new file mode 100644
index 0000000000..4e11751ca0
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
@@ -0,0 +1,19 @@
+---
+id: 5f2c289f164c29556da632fd
+title: Build a Mario Database
+challengeType: 12
+url: freeCodeCamp/learn-relational-databases-by-building-a-mario-database
+dashedName: build-a-mario-database
+---
+
+# --description--
+
+In this 165-lesson workshop, you will learn the basics of a relational database by creating a PostgreSQL database filled with video game characters.
+
+# --instructions--
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
new file mode 100644
index 0000000000..8d4c90410d
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
@@ -0,0 +1,53 @@
+---
+id: 587d7fb3367417b2b2512bfb
+title: How to Use package.json, the Core of Any Node.js Project or npm Package
+challengeType: 2
+forumTopicId: 301528
+dashedName: how-to-use-package-json-the-core-of-any-node-js-project-or-npm-package
+---
+
+# --description--
+
+Working on these challenges will involve you writing your code using one of the following methods:
+
+- Clone <a href="https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete these challenges locally.
+- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+The `package.json` file is the center of any Node.js project or npm package. It stores information about your project. It consists of a single JSON object where information is stored in key-value pairs. There are only two required fields; `name` and `version`, but it’s good practice to provide additional information.
+
+You can create the `package.json` file from the terminal using the `npm init` command. This will run a guided setup. Using `npm init` with the `-y` flag will generate the file without having it ask any questions, `npm init -y`.
+
+If you look at the file tree of your project, you will find the `package.json` file on the top level of the tree. This is the file that you will be improving in the next couple of challenges.
+
+One of the most common pieces of information in this file is the `author` field. It specifies who created the project, and can consist of a string or an object with contact or other details. An object is recommended for bigger projects, but a simple string like the following example will do for this project.
+
+```json
+"author": "Jane Doe",
+```
+
+# --instructions--
+
+Add your name as the `author` of the project in the `package.json` file.
+
+**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (") and be separated with a comma (,).
+
+If you are using Gitpod, make sure the app is running and the preview window is open. Copy the preview window's URL and paste it into the Solution Link input below.
+
+# --hints--
+
+`package.json` should have a valid "author" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.author, '"author" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
new file mode 100644
index 0000000000..37d15d5261
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb3367417b2b2512bfc
+title: Add a Description to Your package.json
+challengeType: 2
+forumTopicId: 301522
+dashedName: add-a-description-to-your-package-json
+---
+
+# --description--
+
+The next part of a good package.json file is the `description` field; where a short, but informative description about your project belongs.
+
+If some day you plan to publish a package to npm, this is the string that should sell your idea to the user when they decide whether to install your package or not. However, that’s not the only use case for the description, it’s a great way to summarize what a project does. It’s just as important in any Node.js project to help other developers, future maintainers or even your future self understand the project quickly.
+
+Regardless of what you plan for your project, a description is definitely recommended. Here's an example:
+
+```json
+"description": "A project that does something awesome",
+```
+
+# --instructions--
+
+Add a `description` to the package.json file of your project.
+
+**Note:** Remember to use double-quotes for field-names (") and commas (,) to separate fields.
+
+# --hints--
+
+package.json should have a valid "description" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.description, '"description" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
new file mode 100644
index 0000000000..a001cdd477
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
@@ -0,0 +1,75 @@
+---
+id: 587d7fb4367417b2b2512bfd
+title: Add Keywords to Your package.json
+challengeType: 2
+forumTopicId: 301526
+dashedName: add-keywords-to-your-package-json
+---
+
+# --description--
+
+The `keywords` field is where you can describe your project using related keywords. Here's an example:
+
+```json
+"keywords": [ "descriptive", "related", "words" ],
+```
+
+As you can see, this field is structured as an array of double-quoted strings.
+
+# --instructions--
+
+Add an array of suitable strings to the `keywords` field in the package.json file of your project.
+
+One of the keywords should be "freecodecamp".
+
+# --hints--
+
+package.json should have a valid "keywords" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.keywords, '"keywords" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" field should be an Array
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.isArray(packJson.keywords, '"keywords" is not an array');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" should include "freecodecamp"
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.include(
+        packJson.keywords,
+        'freecodecamp',
+        '"keywords" does not include "freecodecamp"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
new file mode 100644
index 0000000000..7b09acd042
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
@@ -0,0 +1,39 @@
+---
+id: 587d7fb4367417b2b2512bfe
+title: Add a License to Your package.json
+challengeType: 2
+forumTopicId: 301523
+dashedName: add-a-license-to-your-package-json
+---
+
+# --description--
+
+The `license` field is where you inform users of what they are allowed to do with your project.
+
+Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do. Here's an example of the license field:
+
+```json
+"license": "MIT",
+```
+
+# --instructions--
+
+Fill the `license` field in the package.json file of your project as you find suitable.
+
+# --hints--
+
+package.json should have a valid "license" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.license, '"license" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
new file mode 100644
index 0000000000..f2e571faed
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
@@ -0,0 +1,37 @@
+---
+id: 587d7fb4367417b2b2512bff
+title: Add a Version to Your package.json
+challengeType: 2
+forumTopicId: 301525
+dashedName: add-a-version-to-your-package-json
+---
+
+# --description--
+
+A `version` is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example:
+
+```json
+"version": "1.2.0",
+```
+
+# --instructions--
+
+Add a `version` to the package.json file of your project.
+
+# --hints--
+
+package.json should have a valid "version" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.version, '"version" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
new file mode 100644
index 0000000000..161c60fe69
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
@@ -0,0 +1,68 @@
+---
+id: 587d7fb4367417b2b2512c00
+title: Expand Your Project with External Packages from npm
+challengeType: 2
+forumTopicId: 301527
+dashedName: expand-your-project-with-external-packages-from-npm
+---
+
+# --description--
+
+One of the biggest reasons to use a package manager, is their powerful dependency management. Instead of manually having to make sure that you get all dependencies whenever you set up a project on a new computer, npm automatically installs everything for you. But how can npm know exactly what your project needs? Meet the `dependencies` section of your package.json file.
+
+In this section, packages your project requires are stored using the following format:
+
+```json
+"dependencies": {
+  "package-name": "version",
+  "express": "4.14.0"
+}
+
+```
+
+# --instructions--
+
+Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file.
+
+**Note:** `@freecodecamp/example` is a faux package used as a learning tool.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.1.0"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^[\^\~]?1\.1\.0/,
+        'Wrong version of "@freecodecamp/example" installed. It should be 1.1.0'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
new file mode 100644
index 0000000000..deda9b82de
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
@@ -0,0 +1,64 @@
+---
+id: 587d7fb5367417b2b2512c01
+title: Manage npm Dependencies By Understanding Semantic Versioning
+challengeType: 2
+forumTopicId: 301529
+dashedName: manage-npm-dependencies-by-understanding-semantic-versioning
+---
+
+# --description--
+
+`Versions` of the npm packages in the dependencies section of your package.json file follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes projects can expect if they update.
+
+Knowing SemVer can be useful when you develop software that uses external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things that worked yesterday suddenly don’t work today. This is how Semantic Versioning works according to the official website:
+
+```json
+"package": "MAJOR.MINOR.PATCH"
+```
+
+The MAJOR version should increment when you make incompatible API changes. The MINOR version should increment when you add functionality in a backwards-compatible manner. The PATCH version should increment when you make backwards-compatible bug fixes. This means that PATCHes are bug fixes and MINORs add new features but neither of them break what worked before. Finally, MAJORs add changes that won’t work with earlier versions.
+
+# --instructions--
+
+In the dependencies section of your `package.json` file, change the version of `@freecodecamp/example` to match MAJOR version 1, MINOR version 2 and PATCH version 13
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.equal(
+        packJson.dependencies["@freecodecamp/example"],
+        '1.2.13',
+        'Wrong version of "@freecodecamp/example". It should be 1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
new file mode 100644
index 0000000000..8eae5f51ee
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c02
+title: Use the Tilde-Character to Always Use the Latest Patch Version of a Dependency
+challengeType: 2
+forumTopicId: 301532
+dashedName: use-the-tilde-character-to-always-use-the-latest-patch-version-of-a-dependency
+---
+
+# --description--
+
+In the last challenge, you told npm to only include a specific version of a package. That’s a useful way to freeze your dependencies if you need to make sure that different parts of your project stay compatible with each other. But in most use cases, you don’t want to miss bug fixes since they often include important security patches and (hopefully) don’t break things in doing so.
+
+To allow an npm dependency to update to the latest PATCH version, you can prefix the dependency’s version with the tilde (`~`) character. Here's an example of how to allow updates to any `1.3.x` version.
+
+```json
+"package": "~1.3.8"
+```
+
+# --instructions--
+
+In the package.json file, your current rule for how npm may upgrade `@freecodecamp/example` is to use a specific version (`1.2.13`). But now, you want to allow the latest `1.2.x` version.
+
+Use the tilde (`~`) character to prefix the version of `@freecodecamp/example` in your dependencies, and allow npm to update it to any new _patch_ release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"~1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\~1\.2\.13/,
+        'Wrong version of "@freecodecamp/example". It should be ~1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
new file mode 100644
index 0000000000..adc3014ea4
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c03
+title: Use the Caret-Character to Use the Latest Minor Version of a Dependency
+challengeType: 2
+forumTopicId: 301531
+dashedName: use-the-caret-character-to-use-the-latest-minor-version-of-a-dependency
+---
+
+# --description--
+
+Similar to how the tilde we learned about in the last challenge allows npm to install the latest PATCH for a dependency, the caret (`^`) allows npm to install future updates as well. The difference is that the caret will allow both MINOR updates and PATCHes.
+
+Your current version of `@freecodecamp/example` should be `~1.2.13` which allows npm to install to the latest `1.2.x` version. If you were to use the caret (^) as a version prefix instead, npm would be allowed to update to any `1.x.x` version.
+
+```json
+"package": "^1.3.8"
+```
+
+This would allow updates to any `1.x.x` version of the package.
+
+# --instructions--
+
+Use the caret (`^`) to prefix the version of `@freecodecamp/example` in your dependencies and allow npm to update it to any new MINOR release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"^1.x.x"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\^1\./,
+        'Wrong version of "@freecodecamp/example". It should be ^1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
new file mode 100644
index 0000000000..5f695eed88
--- /dev/null
+++ b/curriculum/challenges/japanese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb5367417b2b2512c04
+title: Remove a Package from Your Dependencies
+challengeType: 2
+forumTopicId: 301530
+dashedName: remove-a-package-from-your-dependencies
+---
+
+# --description--
+
+You have now tested a few ways you can manage dependencies of your project by using the package.json's dependencies section. You have also included external packages by adding them to the file and even told npm what types of versions you want, by using special characters such as the tilde or the caret.
+
+But what if you want to remove an external package that you no longer need? You might already have guessed it, just remove the corresponding key-value pair for that package from your dependencies.
+
+This same method applies to removing other fields in your package.json as well.
+
+# --instructions--
+
+Remove the `@freecodecamp/example` package from your dependencies.
+
+**Note:** Make sure you have the right amount of commas after removing it.
+
+# --hints--
+
+`"dependencies"` should not include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.notProperty(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" still includes "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/chunky-monkey.md b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/chunky-monkey.md
index 98b950c4ac..efee31a555 100644
--- a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/chunky-monkey.md
+++ b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/chunky-monkey.md
@@ -8,11 +8,11 @@ dashedName: chunky-monkey
 
 # --description--
 
-Write a function that splits an array (first argument) into groups the length of `size` (second argument) and returns them as a two-dimensional array.
+배열(첫 번째 인자)을 배열 `size`의 길이(두 번째 인자)만큼의 그룹으로 쪼개고 이를 2차원 배열로 반환하세요.
 
 # --hints--
 
-`chunkArrayInGroups(["a", "b", "c", "d"], 2)` should return `[["a", "b"], ["c", "d"]]`.
+`chunkArrayInGroups(["a", "b", "c", "d"], 2)`는 `[["a", "b"], ["c", "d"]]`를 반환해야 합니다.
 
 ```js
 assert.deepEqual(chunkArrayInGroups(['a', 'b', 'c', 'd'], 2), [
@@ -21,7 +21,7 @@ assert.deepEqual(chunkArrayInGroups(['a', 'b', 'c', 'd'], 2), [
 ]);
 ```
 
-`chunkArrayInGroups([0, 1, 2, 3, 4, 5], 3)` should return `[[0, 1, 2], [3, 4, 5]]`.
+`chunkArrayInGroups([0, 1, 2, 3, 4, 5], 3)`는 `[[0, 1, 2], [3, 4, 5]]`를 반환해야 합니다.
 
 ```js
 assert.deepEqual(chunkArrayInGroups([0, 1, 2, 3, 4, 5], 3), [
@@ -30,7 +30,7 @@ assert.deepEqual(chunkArrayInGroups([0, 1, 2, 3, 4, 5], 3), [
 ]);
 ```
 
-`chunkArrayInGroups([0, 1, 2, 3, 4, 5], 2)` should return `[[0, 1], [2, 3], [4, 5]]`.
+`chunkArrayInGroups([0, 1, 2, 3, 4, 5], 2)`는 `[[0, 1], [2, 3], [4, 5]]`를 반환해야 합니다.
 
 ```js
 assert.deepEqual(chunkArrayInGroups([0, 1, 2, 3, 4, 5], 2), [
@@ -40,7 +40,7 @@ assert.deepEqual(chunkArrayInGroups([0, 1, 2, 3, 4, 5], 2), [
 ]);
 ```
 
-`chunkArrayInGroups([0, 1, 2, 3, 4, 5], 4)` should return `[[0, 1, 2, 3], [4, 5]]`.
+`chunkArrayInGroups([0, 1, 2, 3, 4, 5], 4)`는 `[[0, 1, 2, 3], [4, 5]]`를 반환해야 합니다.
 
 ```js
 assert.deepEqual(chunkArrayInGroups([0, 1, 2, 3, 4, 5], 4), [
@@ -49,7 +49,7 @@ assert.deepEqual(chunkArrayInGroups([0, 1, 2, 3, 4, 5], 4), [
 ]);
 ```
 
-`chunkArrayInGroups([0, 1, 2, 3, 4, 5, 6], 3)` should return `[[0, 1, 2], [3, 4, 5], [6]]`.
+`chunkArrayInGroups([0, 1, 2, 3, 4, 5, 6], 3)`는 `[[0, 1, 2], [3, 4, 5], [6]]`를 반환해야 합니다.
 
 ```js
 assert.deepEqual(chunkArrayInGroups([0, 1, 2, 3, 4, 5, 6], 3), [
@@ -59,7 +59,7 @@ assert.deepEqual(chunkArrayInGroups([0, 1, 2, 3, 4, 5, 6], 3), [
 ]);
 ```
 
-`chunkArrayInGroups([0, 1, 2, 3, 4, 5, 6, 7, 8], 4)` should return `[[0, 1, 2, 3], [4, 5, 6, 7], [8]]`.
+`chunkArrayInGroups([0, 1, 2, 3, 4, 5, 6, 7, 8], 4)`는 `[[0, 1, 2, 3], [4, 5, 6, 7], [8]]`를 반환해야 합니다.
 
 ```js
 assert.deepEqual(chunkArrayInGroups([0, 1, 2, 3, 4, 5, 6, 7, 8], 4), [
@@ -69,7 +69,7 @@ assert.deepEqual(chunkArrayInGroups([0, 1, 2, 3, 4, 5, 6, 7, 8], 4), [
 ]);
 ```
 
-`chunkArrayInGroups([0, 1, 2, 3, 4, 5, 6, 7, 8], 2)` should return `[[0, 1], [2, 3], [4, 5], [6, 7], [8]]`.
+`chunkArrayInGroups([0, 1, 2, 3, 4, 5, 6, 7, 8], 2)`는 `[[0, 1], [2, 3], [4, 5], [6, 7], [8]]`를 반환해야 합니다.
 
 ```js
 assert.deepEqual(chunkArrayInGroups([0, 1, 2, 3, 4, 5, 6, 7, 8], 2), [
diff --git a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/factorialize-a-number.md b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/factorialize-a-number.md
index 9121612847..5b689a5c1a 100644
--- a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/factorialize-a-number.md
+++ b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/factorialize-a-number.md
@@ -1,6 +1,6 @@
 ---
 id: a302f7aae1aa3152a5b413bc
-title: Factorialize a Number
+title: 숫자 계승화(Factorialize) 하기
 challengeType: 1
 forumTopicId: 16013
 dashedName: factorialize-a-number
@@ -8,43 +8,43 @@ dashedName: factorialize-a-number
 
 # --description--
 
-Return the factorial of the provided integer.
+주어진 정수의 계승을 반환하세요.
 
-If the integer is represented with the letter `n`, a factorial is the product of all positive integers less than or equal to `n`.
+정수 `n`이 주어졌을 때, 계승은 `n`보다 작거나 같은 모든 양수의 곱입니다.
 
-Factorials are often represented with the shorthand notation `n!`
+계승은 주로 `n!`으로 표기합니다.
 
-For example: `5! = 1 * 2 * 3 * 4 * 5 = 120`
+예시: `5! = 1 * 2 * 3 * 4 * 5 = 120`
 
-Only integers greater than or equal to zero will be supplied to the function.
+함수에는 오직 0보다 크거나 같은 정수만 제공됩니다.
 
 # --hints--
 
-`factorialize(5)` should return a number.
+`factorialize(5)`는 숫자를 반환해야 합니다.
 
 ```js
 assert(typeof factorialize(5) === 'number');
 ```
 
-`factorialize(5)` should return `120`.
+`factorialize(5)`는 `120`을 반환해야 합니다.
 
 ```js
 assert(factorialize(5) === 120);
 ```
 
-`factorialize(10)` should return `3628800`.
+`factorialize(10)`는 `3628800`을 반환해야 합니다.
 
 ```js
 assert(factorialize(10) === 3628800);
 ```
 
-`factorialize(20)` should return `2432902008176640000`.
+`factorialize(20)`는 `2432902008176640000`을 반환해야 합니다.
 
 ```js
 assert(factorialize(20) === 2432902008176640000);
 ```
 
-`factorialize(0)` should return `1`.
+`factorialize(0)`는 `1`을 반환해야 합니다.
 
 ```js
 assert(factorialize(0) === 1);
diff --git a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/find-the-longest-word-in-a-string.md b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/find-the-longest-word-in-a-string.md
index cebe978a7b..aa3f1ad368 100644
--- a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/find-the-longest-word-in-a-string.md
+++ b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/find-the-longest-word-in-a-string.md
@@ -1,6 +1,6 @@
 ---
 id: a26cbbe9ad8655a977e1ceb5
-title: Find the Longest Word in a String
+title: 문자열에서 가장 긴 단어 찾기
 challengeType: 1
 forumTopicId: 16015
 dashedName: find-the-longest-word-in-a-string
@@ -8,13 +8,13 @@ dashedName: find-the-longest-word-in-a-string
 
 # --description--
 
-Return the length of the longest word in the provided sentence.
+주어진 문장에서 가장 긴 단어의 길이를 반환하세요.
 
-Your response should be a number.
+숫자를 반환해야 합니다.
 
 # --hints--
 
-`findLongestWordLength("The quick brown fox jumped over the lazy dog")` should return a number.
+`findLongestWordLength("The quick brown fox jumped over the lazy dog")`는 숫자를 반환해야 합니다.
 
 ```js
 assert(
@@ -24,7 +24,7 @@ assert(
 );
 ```
 
-`findLongestWordLength("The quick brown fox jumped over the lazy dog")` should return `6`.
+`findLongestWordLength("The quick brown fox jumped over the lazy dog")`는 `6`을 반환해야 합니다.
 
 ```js
 assert(
@@ -32,19 +32,19 @@ assert(
 );
 ```
 
-`findLongestWordLength("May the force be with you")` should return `5`.
+`findLongestWordLength("May the force be with you")`는 `5`를 반환해야 합니다.
 
 ```js
 assert(findLongestWordLength('May the force be with you') === 5);
 ```
 
-`findLongestWordLength("Google do a barrel roll")` should return `6`.
+`findLongestWordLength("Google do a barrel roll")`는 `6`을 반환해야 합니다.
 
 ```js
 assert(findLongestWordLength('Google do a barrel roll') === 6);
 ```
 
-`findLongestWordLength("What is the average airspeed velocity of an unladen swallow")` should return `8`.
+`findLongestWordLength("What is the average airspeed velocity of an unladen swallow")`는 `8`을 반환해야 합니다.
 
 ```js
 assert(
@@ -54,7 +54,7 @@ assert(
 );
 ```
 
-`findLongestWordLength("What if we try a super-long word such as otorhinolaryngology")` should return `19`.
+`findLongestWordLength("What if we try a super-long word such as otorhinolaryngology")`는 `19`를 반환해야 합니다.
 
 ```js
 assert(
diff --git a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/finders-keepers.md b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/finders-keepers.md
index 171510f165..44624c8b0a 100644
--- a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/finders-keepers.md
+++ b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/finders-keepers.md
@@ -1,6 +1,6 @@
 ---
 id: a6e40f1041b06c996f7b2406
-title: Finders Keepers
+title: 파인더 키퍼(Finders Keepers)
 challengeType: 1
 forumTopicId: 16016
 dashedName: finders-keepers
@@ -8,11 +8,11 @@ dashedName: finders-keepers
 
 # --description--
 
-Create a function that looks through an array `arr` and returns the first element in it that passes a 'truth test'. This means that given an element `x`, the 'truth test' is passed if `func(x)` is `true`. If no element passes the test, return `undefined`.
+배열 `arr`에서 '참값 테스트'(truth test)를 통과하는 첫 번째 요소를 반환하는 함수를 작성하세요. '참값 테스트'는 주어진 요소 `x`에 대해, `func(x)`가 `true`면 통과한다는 것을 의미합니다. 어떤 요소도 이 테스트를 통과하지 못한다면 `undefined`를 반환하세요.
 
 # --hints--
 
-`findElement([1, 3, 5, 8, 9, 10], function(num) { return num % 2 === 0; })` should return `8`.
+`findElement([1, 3, 5, 8, 9, 10], function(num) { return num % 2 === 0; })`는 `8`을 반환해야 합니다.
 
 ```js
 assert.strictEqual(
@@ -23,7 +23,7 @@ assert.strictEqual(
 );
 ```
 
-`findElement([1, 3, 5, 9], function(num) { return num % 2 === 0; })` should return `undefined`.
+`findElement([1, 3, 5, 9], function(num) { return num % 2 === 0; })`는 `undefined`를 반환해야 합니다.
 
 ```js
 assert.strictEqual(
diff --git a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/mutations.md b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/mutations.md
index 0a17138f1c..4090eca0c1 100644
--- a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/mutations.md
+++ b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/mutations.md
@@ -1,6 +1,6 @@
 ---
 id: af2170cad53daa0770fabdea
-title: Mutations
+title: 변이(Mutations)
 challengeType: 1
 forumTopicId: 16025
 dashedName: mutations
@@ -8,83 +8,83 @@ dashedName: mutations
 
 # --description--
 
-Return `true` if the string in the first element of the array contains all of the letters of the string in the second element of the array.
+배열의 첫 번째 요소에 있는 문자열이 두 번째 요소에 있는 문자열의 모든 글자를 포함하면 `true`를 반환하세요.
 
-For example, `["hello", "Hello"]`, should return `true` because all of the letters in the second string are present in the first, ignoring case.
+예를 들어, `["hello", "Hello"]`는 대/소문자 구분을 하지 않는다면 첫 번째 문자열에 두 번째 문자열의 모든 글자가 있으므로 `true`를 반환해야 합니다.
 
-The arguments `["hello", "hey"]` should return `false` because the string `hello` does not contain a `y`.
+`["hello", "hey"]`는 `hello`가 `y`를 포함하지 않기 때문에 `false`를 반환해야 합니다.
 
-Lastly, `["Alien", "line"]`, should return `true` because all of the letters in `line` are present in `Alien`.
+마지막으로 `["Alien", "line"]`는 `line`의 모든 글자가 `Alien`에 있으므로 `true`를 반환해야 합니다.
 
 # --hints--
 
-`mutation(["hello", "hey"])` should return `false`.
+`mutation(["hello", "hey"])`은 `false`를 반환해야 합니다.
 
 ```js
 assert(mutation(['hello', 'hey']) === false);
 ```
 
-`mutation(["hello", "Hello"])` should return `true`.
+`mutation(["hello", "Hello"])`은 `true`를 반환해야 합니다.
 
 ```js
 assert(mutation(['hello', 'Hello']) === true);
 ```
 
-`mutation(["zyxwvutsrqponmlkjihgfedcba", "qrstu"])` should return `true`.
+`mutation(["zyxwvutsrqponmlkjihgfedcba", "qrstu"])`은 `true`를 반환해야 합니다.
 
 ```js
 assert(mutation(['zyxwvutsrqponmlkjihgfedcba', 'qrstu']) === true);
 ```
 
-`mutation(["Mary", "Army"])` should return `true`.
+`mutation(["Mary", "Army"])`은 `true`를 반환해야 합니다.
 
 ```js
 assert(mutation(['Mary', 'Army']) === true);
 ```
 
-`mutation(["Mary", "Aarmy"])` should return `true`.
+`mutation(["Mary", "Aarmy"])`은 `true`를 반환해야 합니다.
 
 ```js
 assert(mutation(['Mary', 'Aarmy']) === true);
 ```
 
-`mutation(["Alien", "line"])` should return `true`.
+`mutation(["Alien", "line"])`은 `true`를 반환해야 합니다.
 
 ```js
 assert(mutation(['Alien', 'line']) === true);
 ```
 
-`mutation(["floor", "for"])` should return `true`.
+`mutation(["floor", "for"])`은 `true`를 반환해야 합니다.
 
 ```js
 assert(mutation(['floor', 'for']) === true);
 ```
 
-`mutation(["hello", "neo"])` should return `false`.
+`mutation(["hello", "neo"])`은 `false`를 반환해야 합니다.
 
 ```js
 assert(mutation(['hello', 'neo']) === false);
 ```
 
-`mutation(["voodoo", "no"])` should return `false`.
+`mutation(["voodoo", "no"])`은 `false`를 반환해야 합니다.
 
 ```js
 assert(mutation(['voodoo', 'no']) === false);
 ```
 
-`mutation(["ate", "date"])` should return `false`.
+`mutation(["ate", "date"])`은 `false`를 반환해야 합니다.
 
 ```js
 assert(mutation(['ate', 'date']) === false);
 ```
 
-`mutation(["Tiger", "Zebra"])` should return `false`.
+`mutation(["Tiger", "Zebra"])`은 `false`를 반환해야 합니다.
 
 ```js
 assert(mutation(['Tiger', 'Zebra']) === false);
 ```
 
-`mutation(["Noel", "Ole"])` should return `true`.
+`mutation(["Noel", "Ole"])`은 `true`를 반환해야 합니다.
 
 ```js
 assert(mutation(['Noel', 'Ole']) === true);
diff --git a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/repeat-a-string-repeat-a-string.md b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/repeat-a-string-repeat-a-string.md
index dbae3dde01..6540224ae6 100644
--- a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/repeat-a-string-repeat-a-string.md
+++ b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/repeat-a-string-repeat-a-string.md
@@ -1,6 +1,6 @@
 ---
 id: afcc8d540bea9ea2669306b6
-title: Repeat a String Repeat a String
+title: 문자열 반복하기
 challengeType: 1
 forumTopicId: 16041
 dashedName: repeat-a-string-repeat-a-string
@@ -8,53 +8,53 @@ dashedName: repeat-a-string-repeat-a-string
 
 # --description--
 
-Repeat a given string `str` (first argument) for `num` times (second argument). Return an empty string if `num` is not a positive number. For the purpose of this challenge, do *not* use the built-in `.repeat()` method.
+주어진 문자열 `str`(첫 번째 인자)을 `num`(두 번째 인자) 회 반복하세요. `num`이 양수가 아니면 빈 문자열을 반환하세요. 이 문제의 목적을 위해, 내장 메서드 `.repeat()`를 사용하지 *않습니다*.
 
 # --hints--
 
-`repeatStringNumTimes("*", 3)` should return the string `***`.
+`repeatStringNumTimes("*", 3)`는 문자열 `***`을 반환해야 합니다.
 
 ```js
 assert(repeatStringNumTimes('*', 3) === '***');
 ```
 
-`repeatStringNumTimes("abc", 3)` should return the string `abcabcabc`.
+`repeatStringNumTimes("abc", 3)`는 문자열 `abcabcabc`를 반환해야 합니다.
 
 ```js
 assert(repeatStringNumTimes('abc', 3) === 'abcabcabc');
 ```
 
-`repeatStringNumTimes("abc", 4)` should return the string `abcabcabcabc`.
+`repeatStringNumTimes("abc", 4)`는 문자열 `abcabcabcabc`를 반환해야 합니다.
 
 ```js
 assert(repeatStringNumTimes('abc', 4) === 'abcabcabcabc');
 ```
 
-`repeatStringNumTimes("abc", 1)` should return the string `abc`.
+`repeatStringNumTimes("abc", 1)`는 문자열 `abc`를 반환해야 합니다.
 
 ```js
 assert(repeatStringNumTimes('abc', 1) === 'abc');
 ```
 
-`repeatStringNumTimes("*", 8)` should return the string `********`.
+`repeatStringNumTimes("*", 8)`는 문자열 `********`을 반환해야 합니다.
 
 ```js
 assert(repeatStringNumTimes('*', 8) === '********');
 ```
 
-`repeatStringNumTimes("abc", -2)` should return an empty string (`""`).
+`repeatStringNumTimes("abc", -2)`는 빈 문자열(`""`)을 반환해야 합니다.
 
 ```js
 assert(repeatStringNumTimes('abc', -2) === '');
 ```
 
-The built-in `repeat()` method should not be used.
+내장 메서드 `repeat()`는 사용하지 않습니다.
 
 ```js
 assert(!/\.repeat/g.test(__helpers.removeJSComments(code)));
 ```
 
-`repeatStringNumTimes("abc", 0)` should return `""`.
+`repeatStringNumTimes("abc", 0)`는 `""`를 반환해야 합니다.
 
 ```js
 assert(repeatStringNumTimes('abc', 0) === '');
diff --git a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/return-largest-numbers-in-arrays.md b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/return-largest-numbers-in-arrays.md
index 7f8b6a84a2..bfbc39c942 100644
--- a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/return-largest-numbers-in-arrays.md
+++ b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/return-largest-numbers-in-arrays.md
@@ -1,6 +1,6 @@
 ---
 id: a789b3483989747d63b0e427
-title: Return Largest Numbers in Arrays
+title: 배열들로부터 가장 큰 수들 반환하기
 challengeType: 1
 forumTopicId: 16042
 dashedName: return-largest-numbers-in-arrays
@@ -8,13 +8,13 @@ dashedName: return-largest-numbers-in-arrays
 
 # --description--
 
-Return an array consisting of the largest number from each provided sub-array. For simplicity, the provided array will contain exactly 4 sub-arrays.
+주어진 각 하위 배열로부터 얻은 가장 큰 수들을 담은 배열을 반환하세요. 간편한 풀이를 위해 주어진 배열은 정확하게 4개의 하위 배열을 가지게 됩니다.
 
-Remember, you can iterate through an array with a simple for loop, and access each member with array syntax `arr[i]`.
+간단한 for 루프로 배열의 요소를 하나씩 순회할 수 있고 `arr[i]` 문법을 통해 각 요소에 접근할 수 있다는 점을 기억하세요.
 
 # --hints--
 
-`largestOfFour([[4, 5, 1, 3], [13, 27, 18, 26], [32, 35, 37, 39], [1000, 1001, 857, 1]])` should return an array.
+`largestOfFour([[4, 5, 1, 3], [13, 27, 18, 26], [32, 35, 37, 39], [1000, 1001, 857, 1]])`는 배열을 반환해야 합니다.
 
 ```js
 assert(
@@ -27,7 +27,7 @@ assert(
 );
 ```
 
-`largestOfFour([[13, 27, 18, 26], [4, 5, 1, 3], [32, 35, 37, 39], [1000, 1001, 857, 1]])` should return `[27, 5, 39, 1001]`.
+`largestOfFour([[13, 27, 18, 26], [4, 5, 1, 3], [32, 35, 37, 39], [1000, 1001, 857, 1]])`는 `[27, 5, 39, 1001]`을 반환해야 합니다.
 
 ```js
 assert.deepEqual(
@@ -41,7 +41,7 @@ assert.deepEqual(
 );
 ```
 
-`largestOfFour([[4, 9, 1, 3], [13, 35, 18, 26], [32, 35, 97, 39], [1000000, 1001, 857, 1]])` should return `[9, 35, 97, 1000000]`.
+`largestOfFour([[4, 9, 1, 3], [13, 35, 18, 26], [32, 35, 97, 39], [1000000, 1001, 857, 1]])`는 `[9, 35, 97, 1000000]`을 반환해야 합니다.
 
 ```js
 assert.deepEqual(
@@ -55,7 +55,7 @@ assert.deepEqual(
 );
 ```
 
-`largestOfFour([[17, 23, 25, 12], [25, 7, 34, 48], [4, -10, 18, 21], [-72, -3, -17, -10]])` should return `[25, 48, 21, -3]`.
+`largestOfFour([[17, 23, 25, 12], [25, 7, 34, 48], [4, -10, 18, 21], [-72, -3, -17, -10]])`는 `[25, 48, 21, -3]`을 반환해야 합니다.
 
 ```js
 assert.deepEqual(
diff --git a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/reverse-a-string.md b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/reverse-a-string.md
index bca8cb7bd6..30b1b9d682 100644
--- a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/reverse-a-string.md
+++ b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/reverse-a-string.md
@@ -1,6 +1,6 @@
 ---
 id: a202eed8fc186c8434cb6d61
-title: Reverse a String
+title: 문자열 뒤집기
 challengeType: 1
 forumTopicId: 16043
 dashedName: reverse-a-string
@@ -8,31 +8,31 @@ dashedName: reverse-a-string
 
 # --description--
 
-Reverse the provided string and return the reversed string.
+주어진 문자열을 역순으로 나열하고 그 나열된 문자열을 반환하세요.
 
-For example, `"hello"` should become `"olleh"`.
+예를 들어, `"hello"`는 `"olleh"`를 반환해야 합니다.
 
 # --hints--
 
-`reverseString("hello")` should return a string.
+`reverseString("hello")`은 문자열을 반환해야 합니다.
 
 ```js
 assert(typeof reverseString('hello') === 'string');
 ```
 
-`reverseString("hello")` should return the string `olleh`.
+`reverseString("hello")`은 문자열 `olleh`를 반환해야 합니다.
 
 ```js
 assert(reverseString('hello') === 'olleh');
 ```
 
-`reverseString("Howdy")` should return the string `ydwoH`.
+`reverseString("Howdy")`은 문자열 `ydwoH`을 반환해야 합니다.
 
 ```js
 assert(reverseString('Howdy') === 'ydwoH');
 ```
 
-`reverseString("Greetings from Earth")` should return the string `htraE morf sgniteerG`.
+`reverseString("Greetings from Earth")`은 문자열 `htraE morf sgniteerG`을 반환해야 합니다.
 
 ```js
 assert(reverseString('Greetings from Earth') === 'htraE morf sgniteerG');
diff --git a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/slice-and-splice.md b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/slice-and-splice.md
index f336149eae..13586f8b5c 100644
--- a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/slice-and-splice.md
+++ b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/slice-and-splice.md
@@ -1,6 +1,6 @@
 ---
 id: 579e2a2c335b9d72dd32e05c
-title: Slice and Splice
+title: Slice와 Splice
 challengeType: 1
 forumTopicId: 301148
 dashedName: slice-and-splice
@@ -8,29 +8,29 @@ dashedName: slice-and-splice
 
 # --description--
 
-You are given two arrays and an index.
+두 배열과 인덱스가 주어집니다.
 
-Copy each element of the first array into the second array, in order.
+첫 번째 배열의 모든 요소를 두 번째 배열에 순서대로 복사합니다.
 
-Begin inserting elements at index `n` of the second array.
+두 번째 배열의 인덱스 `n`에 요소를 삽입하기 시작합니다.
 
-Return the resulting array. The input arrays should remain the same after the function runs.
+결과 배열을 반환하세요. 입력 배열들은 함수가 실행되고 난 후에도 변함이 없어야 합니다.
 
 # --hints--
 
-`frankenSplice([1, 2, 3], [4, 5], 1)` should return `[4, 1, 2, 3, 5]`.
+`frankenSplice([1, 2, 3], [4, 5], 1)`는 `[4, 1, 2, 3, 5]`를 반환해야 합니다.
 
 ```js
 assert.deepEqual(frankenSplice([1, 2, 3], [4, 5], 1), [4, 1, 2, 3, 5]);
 ```
 
-`frankenSplice([1, 2], ["a", "b"], 1)` should return `["a", 1, 2, "b"]`.
+`frankenSplice([1, 2], ["a", "b"], 1)`는 `["a", 1, 2, "b"]`를 반환해야 합니다.
 
 ```js
 assert.deepEqual(frankenSplice(testArr1, testArr2, 1), ['a', 1, 2, 'b']);
 ```
 
-`frankenSplice(["claw", "tentacle"], ["head", "shoulders", "knees", "toes"], 2)` should return `["head", "shoulders", "claw", "tentacle", "knees", "toes"]`.
+`frankenSplice(["claw", "tentacle"], ["head", "shoulders", "knees", "toes"], 2)`는 `["head", "shoulders", "claw", "tentacle", "knees", "toes"]`를 반환해야 합니다.
 
 ```js
 assert.deepEqual(
@@ -43,20 +43,20 @@ assert.deepEqual(
 );
 ```
 
-All elements from the first array should be added to the second array in their original order. `frankenSplice([1, 2, 3, 4], [], 0)` should return `[1, 2, 3, 4]`.
+첫 번째 배열의 모든 요소는 기존 순서대로 두 번째 배열에 추가되어야 합니다. `frankenSplice([1, 2, 3, 4], [], 0)`는 `[1, 2, 3, 4]`를 반환해야 합니다.
 
 ```js
 assert.deepEqual(frankenSplice([1, 2, 3, 4], [], 0), [1, 2, 3, 4]);
 ```
 
-The first array should remain the same after the function runs.
+첫 번째 배열은 함수가 실행되고 난 후에도 변함이 없어야 합니다.
 
 ```js
 frankenSplice(testArr1, testArr2, 1);
 assert.deepEqual(testArr1, [1, 2]);
 ```
 
-The second array should remain the same after the function runs.
+두 번째 배열은 함수가 실행되고 난 후에도 변함이 없어야 합니다.
 
 ```js
 frankenSplice(testArr1, testArr2, 1);
diff --git a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/truncate-a-string.md b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/truncate-a-string.md
index 855fe03144..dcd96a75e7 100644
--- a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/truncate-a-string.md
+++ b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/truncate-a-string.md
@@ -1,6 +1,6 @@
 ---
 id: ac6993d51946422351508a41
-title: Truncate a String
+title: 문자열 자르기
 challengeType: 1
 forumTopicId: 16089
 dashedName: truncate-a-string
@@ -8,11 +8,11 @@ dashedName: truncate-a-string
 
 # --description--
 
-Truncate a string (first argument) if it is longer than the given maximum string length (second argument). Return the truncated string with a `...` ending.
+주어진 최대 문자열 길이(두 번째 인수)보다 문자열(첫 번째 인수)이 긴 경우 문자열을 자르세요. 잘린 문자열은 끝에 `...`와 함께 반환되어야 합니다.
 
 # --hints--
 
-`truncateString("A-tisket a-tasket A green and yellow basket", 8)` should return the string `A-tisket...`.
+`truncateString("A-tisket a-tasket A green and yellow basket", 8)`은 문자열 `A-tisket...`을 반환해야 합니다.
 
 ```js
 assert(
@@ -21,7 +21,7 @@ assert(
 );
 ```
 
-`truncateString("Peter Piper picked a peck of pickled peppers", 11)` should return the string `Peter Piper...`.
+`truncateString("Peter Piper picked a peck of pickled peppers", 11)`은 문자열 `Peter Piper...`을 반환해야 합니다.
 
 ```js
 assert(
@@ -30,7 +30,7 @@ assert(
 );
 ```
 
-`truncateString("A-tisket a-tasket A green and yellow basket", "A-tisket a-tasket A green and yellow basket".length)` should return the string `A-tisket a-tasket A green and yellow basket`.
+`truncateString("A-tisket a-tasket A green and yellow basket", "A-tisket a-tasket A green and yellow basket".length)`은 문자열 `A-tisket a-tasket A green and yellow basket`을 반환해야 합니다.
 
 ```js
 assert(
@@ -41,7 +41,7 @@ assert(
 );
 ```
 
-`truncateString("A-tisket a-tasket A green and yellow basket", "A-tisket a-tasket A green and yellow basket".length + 2)` should return the string `A-tisket a-tasket A green and yellow basket`.
+`truncateString("A-tisket a-tasket A green and yellow basket", "A-tisket a-tasket A green and yellow basket".length + 2)`은 문자열 `A-tisket a-tasket A green and yellow basket`을 반환해야 합니다.
 
 ```js
 assert(
@@ -52,13 +52,13 @@ assert(
 );
 ```
 
-`truncateString("A-", 1)` should return the string `A...`.
+`truncateString("A-", 1)`은 문자열 `A...`을 반환해야 합니다.
 
 ```js
 assert(truncateString('A-', 1) === 'A...');
 ```
 
-`truncateString("Absolutely Longer", 2)` should return the string `Ab...`.
+`truncateString("Absolutely Longer", 2)`은 문자열 `Ab...`을 반환해야 합니다.
 
 ```js
 assert(truncateString('Absolutely Longer', 2) === 'Ab...');
diff --git a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/where-do-i-belong.md b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/where-do-i-belong.md
index 9d32433792..5f596c753f 100644
--- a/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/where-do-i-belong.md
+++ b/curriculum/challenges/korean/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting/where-do-i-belong.md
@@ -1,6 +1,6 @@
 ---
 id: a24c1a4622e3c05097f71d67
-title: Where do I Belong
+title: 나는 어디에 속할까요
 challengeType: 1
 forumTopicId: 16094
 dashedName: where-do-i-belong
@@ -8,105 +8,105 @@ dashedName: where-do-i-belong
 
 # --description--
 
-Return the lowest index at which a value (second argument) should be inserted into an array (first argument) once it has been sorted. The returned value should be a number.
+배열 (첫 번째 인수)이 정렬된 후에 값(두 번째 인수)이 삽입되어야 하는 가장 낮은 인덱스를 반환합니다. 반환된 값은 숫자여야 합니다.
 
-For example, `getIndexToIns([1,2,3,4], 1.5)` should return `1` because it is greater than `1` (index 0), but less than `2` (index 1).
+예를 들어, `getIndexToIns([1,2,3,4], 1.5)`는 `1`을 반환해야 합니다. 왜냐하면 1.5가 `1`(인덱스 0)보다 크지만 `2`(인덱스 1)보다 작기 때문입니다.
 
-Likewise, `getIndexToIns([20,3,5], 19)` should return `2` because once the array has been sorted it will look like `[3,5,20]` and `19` is less than `20` (index 2) and greater than `5` (index 1).
+마찬가지로, `getIndexToIns([20,3,5], 19)`는 `2`를 반환해야 합니다. 배열이 정렬되면 `[3,5,20]`이 되고 `19`는 `20`(인덱스 2)보다 작지만 `5`(인덱스 1)보다 크기 때문입니다.
 
 # --hints--
 
-`getIndexToIns([10, 20, 30, 40, 50], 35)` should return `3`.
+`getIndexToIns([10, 20, 30, 40, 50], 35)`는 `3`을 반환해야 합니다.
 
 ```js
 assert(getIndexToIns([10, 20, 30, 40, 50], 35) === 3);
 ```
 
-`getIndexToIns([10, 20, 30, 40, 50], 35)` should return a number.
+`getIndexToIns([10, 20, 30, 40, 50], 35)`는 숫자를 반환해야 합니다.
 
 ```js
 assert(typeof getIndexToIns([10, 20, 30, 40, 50], 35) === 'number');
 ```
 
-`getIndexToIns([10, 20, 30, 40, 50], 30)` should return `2`.
+`getIndexToIns([10, 20, 30, 40, 50], 30)`는 `2`를 반환해야 합니다.
 
 ```js
 assert(getIndexToIns([10, 20, 30, 40, 50], 30) === 2);
 ```
 
-`getIndexToIns([10, 20, 30, 40, 50], 30)` should return a number.
+`getIndexToIns([10, 20, 30, 40, 50], 30)`는 숫자를 반환해야 합니다.
 
 ```js
 assert(typeof getIndexToIns([10, 20, 30, 40, 50], 30) === 'number');
 ```
 
-`getIndexToIns([40, 60], 50)` should return `1`.
+`getIndexToIns([40, 60], 50)`는 `1`을 반환해야 합니다.
 
 ```js
 assert(getIndexToIns([40, 60], 50) === 1);
 ```
 
-`getIndexToIns([40, 60], 50)` should return a number.
+`getIndexToIns([40, 60], 50)`는 숫자를 반환해야 합니다.
 
 ```js
 assert(typeof getIndexToIns([40, 60], 50) === 'number');
 ```
 
-`getIndexToIns([3, 10, 5], 3)` should return `0`.
+`getIndexToIns([3, 10, 5], 3)`는 `0`을 반환해야 합니다.
 
 ```js
 assert(getIndexToIns([3, 10, 5], 3) === 0);
 ```
 
-`getIndexToIns([3, 10, 5], 3)` should return a number.
+`getIndexToIns([3, 10, 5], 3)`는 숫자를 반환해야 합니다.
 
 ```js
 assert(typeof getIndexToIns([3, 10, 5], 3) === 'number');
 ```
 
-`getIndexToIns([5, 3, 20, 3], 5)` should return `2`.
+`getIndexToIns([5, 3, 20, 3], 5)`는 `2`를 반환해야 합니다.
 
 ```js
 assert(getIndexToIns([5, 3, 20, 3], 5) === 2);
 ```
 
-`getIndexToIns([5, 3, 20, 3], 5)` should return a number.
+`getIndexToIns([5, 3, 20, 3], 5)`는 숫자를 반환해야 합니다.
 
 ```js
 assert(typeof getIndexToIns([5, 3, 20, 3], 5) === 'number');
 ```
 
-`getIndexToIns([2, 20, 10], 19)` should return `2`.
+`getIndexToIns([2, 20, 10], 19)`는 `2`를 반환해야 합니다.
 
 ```js
 assert(getIndexToIns([2, 20, 10], 19) === 2);
 ```
 
-`getIndexToIns([2, 20, 10], 19)` should return a number.
+`getIndexToIns([2, 20, 10], 19)`는 숫자를 반환해야 합니다.
 
 ```js
 assert(typeof getIndexToIns([2, 20, 10], 19) === 'number');
 ```
 
-`getIndexToIns([2, 5, 10], 15)` should return `3`.
+`getIndexToIns([2, 5, 10], 15)`는 `3`을 반환해야 합니다.
 
 ```js
 assert(getIndexToIns([2, 5, 10], 15) === 3);
 ```
 
-`getIndexToIns([2, 5, 10], 15)` should return a number.
+`getIndexToIns([2, 5, 10], 15)`는 숫자를 반환해야 합니다.
 
 ```js
 assert(typeof getIndexToIns([2, 5, 10], 15) === 'number');
 ```
 
-`getIndexToIns([], 1)` should return `0`.
+`getIndexToIns([], 1)`는 `0`을 반환해야 합니다.
 
 ```js
 assert(getIndexToIns([], 1) === 0);
 ```
 
-`getIndexToIns([], 1)` should return a number.
+`getIndexToIns([], 1)`는 숫자를 반환해야 합니다.
 
 ```js
 assert(typeof getIndexToIns([], 1) === 'number');
diff --git a/curriculum/challenges/korean/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md b/curriculum/challenges/korean/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
index db5b0c61e0..5608918f2f 100644
--- a/curriculum/challenges/korean/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
+++ b/curriculum/challenges/korean/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
@@ -8,7 +8,7 @@ dashedName: build-a-periodic-table-database
 
 # --description--
 
-This is one of the required projects to earn your certification. For this project, you will create Bash a script to get information about chemical elements from a periodic table database.
+This is one of the required projects to earn your certification. For this project, you will create a Bash script to get information about chemical elements from a periodic table database.
 
 # --instructions--
 
diff --git a/curriculum/challenges/korean/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md b/curriculum/challenges/korean/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
index 7d83aef878..2227b3b670 100644
--- a/curriculum/challenges/korean/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
+++ b/curriculum/challenges/korean/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
@@ -9,6 +9,8 @@ dashedName: step-64
 
 Inside the `footer`, add a `p` element. Then, nest an anchor (`a`) element in the `p` that links to `https://www.freecodecamp.org` and has the text `Visit our website`.
 
+Make sure that the link opens in a new tab by adding a `target` attribute with the value `_blank`.
+
 # --hints--
 
 You should not modify the existing `footer` element.
@@ -43,6 +45,12 @@ Your new `a` element should link to `https://www.freecodecamp.org`. Remember tha
 assert(document.querySelector("footer > p > a")?.href === "https://www.freecodecamp.org/");
 ```
 
+Your new `a` element should have the `target` attribute set to `_blank`.
+
+```js
+assert.equal(document.querySelector("footer > p > a")?.target, "_blank");
+```
+
 # --seed--
 
 ## --seed-contents--
diff --git a/curriculum/challenges/korean/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md b/curriculum/challenges/korean/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
index d2ad72a1ea..1b6ca05444 100644
--- a/curriculum/challenges/korean/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
+++ b/curriculum/challenges/korean/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
@@ -21,12 +21,12 @@ Remove `flex: 1` from `.item` and add `justify-content: space-between` to `.cont
 
 `justify-content` aligns items across the **main axis**. There are a few values that you can use here. You'll learn the rest of them in the reading assignments, but for now try changing it to center, which should center the boxes along the main axis.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see what is possible with the `justify-content` property. Read this [interactive article on MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) and play around with the different values of `justify-content` on the example.
 
+# --question--
+
 ## --text--
 
 How does applying `justify-content: space-between` to a flex container affect the positioning of its items?
diff --git a/curriculum/challenges/korean/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md b/curriculum/challenges/korean/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
index d3137b0af5..59acb55a29 100644
--- a/curriculum/challenges/korean/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
+++ b/curriculum/challenges/korean/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
@@ -17,12 +17,12 @@ To change the placement of items along the cross axis use `align-items`. Try get
 
 Because `justify-content` and `align-items` are based on the main and cross axis of your container, their behavior changes when you change the flex-direction of a flex-container. For example, when you change `flex-direction` to `column`, `justify-content` aligns vertically and `align-items` aligns horizontally. The most common behavior, however, is the default, i.e. `justify-content` aligns items horizontally (because the main axis defaults to horizontal), and `align-items` aligns them vertically. One of the biggest sticking points that beginners have with flexbox is confusion when this behavior changes.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see if you can figure out how `align-items` behaves when you change the `flex-direction` property to `column`.
 
+# --question--
+
 ## --text--
 
 When changing the `flex-direction` property to `column` in a flex container, how does `align-items` behave in relation to the flex items?
diff --git a/curriculum/challenges/korean/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md b/curriculum/challenges/korean/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
index 1adf9ce84f..49edeac0e4 100644
--- a/curriculum/challenges/korean/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
+++ b/curriculum/challenges/korean/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
@@ -9,12 +9,12 @@ dashedName: learn-block-and-inline-lesson-b
 
 Inline elements, however, do not start on a new line. They appear in line with whatever elements they are placed beside. A clear example of an inline element is a link, or `<a>` tag. If you stick one of these in the middle of a paragraph of text, it will behave like a part of the paragraph. <a  href="https://www.freecodecamp.org/" target="_blank">(Like this)</a> The link’s text will sit alongside other words in that paragraph. Additionally, padding and margin behave differently on inline elements. In general, you do not want to try to put extra padding or margin on inline elements.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Search the web for a list of `block` elements and a list of `inline` elements.
 
+# --question--
+
 ## --text--
 
 What is the difference between a `block` element and an `inline` element?
diff --git a/curriculum/challenges/korean/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md b/curriculum/challenges/korean/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
index cdd4d5aa87..e75492e9c1 100644
--- a/curriculum/challenges/korean/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
+++ b/curriculum/challenges/korean/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-block-and-inline-lesson-g
 
 # --description--
 
-Now that you have some basic understanding of `block` and inline `elements`, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
+Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
 
 # --question--
 
diff --git a/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md b/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
index 995073b8a2..a7a2ee9a51 100644
--- a/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
+++ b/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
@@ -21,12 +21,12 @@ New programmers often find problem solving the hardest skill to build. It's not
 
 The best way to improve your problem solving ability is by building experience by making lots and lots of programs. The more practice you have the better you'll be prepared to solve real world problems.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Read <a href="https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/" target="_blank">How to Think Like a Programmer - Lessons in Problem Solving</a> by Richard Reis.
 
+# --question--
+
 ## --text--
 
 According to V. Anton Spraul in "Think Like a Programmer," what is problem solving in programming?
diff --git a/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md b/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
index ae905ecf89..c57a7d43e8 100644
--- a/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
+++ b/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
@@ -25,11 +25,11 @@ Now that you know what you’re aiming to solve, don’t jump into coding just y
 
 The last question is where you will write out an algorithm to solve the problem. You can think of an algorithm as a recipe for solving a particular problem. It defines the steps that need to be taken by the computer to solve a problem in pseudocode.
 
-# --question--
-
-## --assignment--
+# --assignment--
 Watch <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">How to Begin Thinking Like a Programmer</a> by Coding Tech. It’s an hour long but packed full of information and definitely worth your time watching.
 
+# --question--
+
 ## --text--
 
 What should you do before starting to code according to the provided text?
diff --git a/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md b/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
index c837fd9658..082f2d51ae 100644
--- a/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
+++ b/curriculum/challenges/korean/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
@@ -22,12 +22,12 @@ Print the value of the counter variable
 
 This is a basic program to demonstrate how pseudocode looks. There will be more examples of pseudocode included in the assignments.
 
+# --assignment--
 
-# --question--
-
-## --assignment--
 Read this <a href="https://builtin.com/data-science/pseudocode" target="_blank"> Pseudocode: What It Is and How to Write It</a> article from Built In.
 
+# --question--
+
 ## --text--
 
 What are the benefits of using pseudocode according to the linked article?
diff --git a/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md b/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
index 3ba0e41199..cfc7c8de5b 100644
--- a/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
+++ b/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-So far you have learned how to create questions with the verb to be. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
+So far you have learned how to create questions with the verb `to be`. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
 
 `You are a developer` -> `Are you a developer?`
 
diff --git a/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md b/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
index 544d8f1988..8cd311a518 100644
--- a/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
+++ b/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
@@ -21,7 +21,7 @@ Which sentence is correct for describing one place near you?
 
 ### --feedback--
 
-`There are` is used for plural nouns, and `bank` is singular. You’ll learn about there are in the next few lessons.
+`There are` is used for plural nouns, and `bank` is singular. You’ll learn about `there are` in the next few lessons.
 
 ---
 
diff --git a/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md b/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
index 6526b1e95b..10c0845779 100644
--- a/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
+++ b/curriculum/challenges/korean/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
@@ -7,7 +7,7 @@ dashedName: task-112
 
 # --description--
 
-To elaborate a question using `there is` you just need to change the order of the verb to be, like so:
+To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so:
 
 `There is an ATM nearby` -> `Is there an ATM nearby?`
 
diff --git a/curriculum/challenges/korean/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md b/curriculum/challenges/korean/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
new file mode 100644
index 0000000000..7d664a8876
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
@@ -0,0 +1,25 @@
+---
+id: 5f1a4ef5d5d6b5ab580fc6ae
+title: Build a Celestial Bodies Database
+challengeType: 13
+url: freeCodeCamp/learn-celestial-bodies-database
+dashedName: lab-celestial-bodies-database
+---
+
+# --description--
+
+For this project, you will build a database of celestial bodies using PostgreSQL.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `universe.sql` file so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `universe.sql`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/korean/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md b/curriculum/challenges/korean/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
new file mode 100644
index 0000000000..9492b82cb4
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
@@ -0,0 +1,611 @@
+---
+id: 5a8b073d06fa14fcfde687aa
+title: Build an Exercise Tracker
+challengeType: 4
+dashedName: build-an-exercise-tracker
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://exercise-tracker.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://exercise-tracker.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+Your responses should have the following structures.
+
+Exercise:
+
+```js
+{
+  username: "fcc_test",
+  description: "test",
+  duration: 60,
+  date: "Mon Jan 01 1990",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+User:
+
+```js
+{
+  username: "fcc_test",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Log:
+
+```js
+{
+  username: "fcc_test",
+  count: 1,
+  _id: "5fb5853f734231456ccb3b05",
+  log: [{
+    description: "test",
+    duration: 60,
+    date: "Mon Jan 01 1990",
+  }]
+}
+```
+
+**Hint:** For the `date` property, the `toDateString` method of the `Date` API can be used to achieve the expected output.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  const url = getUserInput('url');
+  assert(
+    !/.*\/exercise-tracker\.freecodecamp\.rocks/.test(getUserInput('url'))
+  );
+};
+```
+
+You can `POST` to `/api/users` with form data `username` to create a new user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The returned response from `POST /api/users` with form data `username` will be an object with `username` and `_id` properties.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    assert.exists(_id);
+    assert.exists(username);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users` to get a list of all users.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `GET` request to `/api/users` returns an array.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    assert.isArray(users);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Each element in the array returned from `GET /api/users` is an object literal containing a user's `username` and `_id`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    const user = users[0];
+    assert.exists(user);
+    assert.exists(user.username);
+    assert.exists(user._id);
+    assert.isString(user.username);
+    assert.isString(user._id);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can `POST` to `/api/users/:_id/exercises` with form data `description`, `duration`, and optionally `date`. If no date is supplied, the current date will be used.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+  assert.isTrue(addRes.ok);
+  if(!addRes.ok) {
+    throw new Error(`${addRes.status} ${addRes.statusText}`)
+  };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+The response returned from `POST /api/users/:_id/exercises` will be the user object with the exercise fields added.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    if (addRes.ok) {
+      const actual = await addRes.json();
+      assert.deepEqual(actual, expected);
+      assert.isString(actual.description);
+      assert.isNumber(actual.duration);
+      assert.isString(actual.date);
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users/:_id/logs` to retrieve a full exercise log of any user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+    assert.isTrue(logRes.ok);
+    if(!logRes.ok) {
+      throw new Error(`${logRes.status} ${logRes.statusText}`)
+    };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A request to a user's log `GET /api/users/:_id/logs` returns a user object with a `count` property representing the number of exercises that belong to that user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if (logRes.ok) {
+        const { count } = await logRes.json();
+        assert(count);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A `GET` request to `/api/users/:_id/logs` will return the user object with a `log` array of all the exercises added.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  })
+  if(res.ok){
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok){
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+Each item in the `log` array that is returned from `GET /api/users/:_id/logs` is an object that should have a `description`, `duration`, and `date` properties.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + `/api/users`, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+     const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.exists(exercise);
+        assert.exists(exercise.description);
+        assert.exists(exercise.duration);
+        assert.exists(exercise.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `description` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.description);
+        assert.equal(exercise.description, expected.description);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `duration` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a number.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isNumber(exercise.duration);
+        assert.equal(exercise.duration, expected.duration);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `date` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string. Use the `dateString` format of the `Date` API.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toLocaleDateString("en-US", {
+        timeZone: "UTC", weekday: "short", month: "short",
+        day: "2-digit", year: "numeric"
+      }).replaceAll(',', '')
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.date);
+        assert.equal(exercise.date, expected.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can add `from`, `to` and `limit` parameters to a `GET /api/users/:_id/logs` request to retrieve part of the log of any user. `from` and `to` are dates in `yyyy-mm-dd` format. `limit` is an integer of how many logs to send back.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addExerciseRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    const addExerciseTwoRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-03`
+    });
+    if (addExerciseRes.ok && addExerciseTwoRes.ok) {
+      const logRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1989-12-31&to=1990-01-04`
+      );
+      if (logRes.ok) {
+        const { log } = await logRes.json();
+        assert.isArray(log);
+        assert.equal(2, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+      const limitRes = await fetch(
+        url + `/api/users/${_id}/logs?limit=1`
+      );
+      if (limitRes.ok) {
+        const { log } = await limitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${limitRes.status} ${limitRes.statusText}`);
+      }
+      const filterDateBeforeLimitRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1990-01-02&to=1990-01-04&limit=1`
+      );
+      if (filterDateBeforeLimitRes.ok) {
+        const { log } = await filterDateBeforeLimitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${filterDateBeforeLimitRes.status} ${filterDateBeforeLimitRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${res.status} ${res.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
diff --git a/curriculum/challenges/korean/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md b/curriculum/challenges/korean/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
new file mode 100644
index 0000000000..ef87dc6720
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
@@ -0,0 +1,25 @@
+---
+id: 602da04c22201c65d2a019f4
+title: Build a Number Guessing Game
+challengeType: 13
+url: freeCodeCamp/learn-number-guessing-game
+dashedName: lab-number-guessing-game
+---
+
+# --description--
+
+For this lab, you will use Bash scripting, PostgreSQL, and Git to create a number guessing game that runs in the terminal and saves user information.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `number_guess.sql` file, as well as your `number_guess.sh` file, so you can complete step 2. There will be instructions on how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `number_guess.sql`, `number_guess.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/korean/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md b/curriculum/challenges/korean/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
new file mode 100644
index 0000000000..5040e27424
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
@@ -0,0 +1,65 @@
+---
+id: bd7158d8c443edefaeb5bdff
+title: Build a Request Header Parser Microservice
+challengeType: 4
+dashedName: lab-request-header-parser-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://request-header-parser-microservice.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://request-header-parser-microservice.freecodecamp.rocks/</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/request-header-parser-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+A request to `/api/whoami` should return a JSON object with your IP address in the `ipaddress` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.ipaddress && data.ipaddress.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your preferred language in the `language` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.language && data.language.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your software in the `software` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.software && data.software.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/korean/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md b/curriculum/challenges/korean/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
new file mode 100644
index 0000000000..0fbf80a0bf
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
@@ -0,0 +1,107 @@
+---
+id: bd7158d8c443edefaeb5bd0e
+title: URL Shortener Microservice
+challengeType: 4
+dashedName: url-shortener-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://url-shortener-microservice.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://url-shortener-microservice.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+**HINT:** Do not forget to use a body parsing middleware to handle the POST requests. Also, you can use the function `dns.lookup(host, cb)` from the `dns` core module to verify a submitted URL.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/url-shortener-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+You can POST a URL to `/api/shorturl` and get a JSON response with `original_url` and `short_url` properties. Here's an example: `{ original_url : 'https://freeCodeCamp.org', short_url : 1}`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (res.ok) {
+    const { short_url, original_url } = await res.json();
+    assert.isNotNull(short_url);
+    assert.strictEqual(original_url, `${url}/?v=${urlVariable}`);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+When you visit `/api/shorturl/<short_url>`, you will be redirected to the original URL.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  let shortenedUrlVariable;
+  const postResponse = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (postResponse.ok) {
+    const { short_url } = await postResponse.json();
+    shortenedUrlVariable = short_url;
+  } else {
+    throw new Error(`${postResponse.status} ${postResponse.statusText}`);
+  }
+  const getResponse = await fetch(
+    url + '/api/shorturl/' + shortenedUrlVariable
+  );
+  if (getResponse) {
+    const { redirected, url } = getResponse;
+    assert.isTrue(redirected);
+    assert.strictEqual(url,fullUrl);
+  } else {
+    throw new Error(`${getResponse.status} ${getResponse.statusText}`);
+  }
+};
+```
+
+If you pass an invalid URL that doesn't follow the valid `http://www.example.com` format, the JSON response will contain `{ error: 'invalid url' }`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=ftp:/john-doe.invalidTLD`
+  });
+  if (res.ok) {
+    const { error } = await res.json();
+    assert.isNotNull(error);
+    assert.strictEqual(error.toLowerCase(), 'invalid url');
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
diff --git a/curriculum/challenges/korean/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md b/curriculum/challenges/korean/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
new file mode 100644
index 0000000000..d77442a1ba
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
@@ -0,0 +1,25 @@
+---
+id: 5f9771307d4d22b9d2b75a94
+title: Build a World Cup Database
+challengeType: 13
+url: freeCodeCamp/learn-world-cup-database
+dashedName: lab-world-cup-database
+---
+
+# --description--
+
+For this project, you will create a Bash script that enters information from World Cup games into PostgreSQL, then query the database for useful statistics.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `worldcup.sql` file, as well as your `insert_data.sh` and `queries.sh` files, so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `worldcup.sql`, `insert_data.sh`, `queries.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md b/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
index 51ea9e3069..753ee1a6bb 100644
--- a/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
@@ -7,9 +7,9 @@ dashedName: step-22
 
 # --description--
 
-Add another label with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
+Add another `label` with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
 
-Below the label element, add another checkbox input with the `id`, `name` and `value` attributes set to `"recommendation"`.
+Below the `label` element, add another checkbox `input` with the `id`, `name` and `value` attributes set to `"recommendation"`.
 
 # --hints--
 
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md b/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
index 42c425209d..80a23ca86d 100644
--- a/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
@@ -11,7 +11,7 @@ Next, add another `label` element with the text of `Location` and the `for` attr
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"location"`.
 
-Below that `input` element, add another `label` element with the text of `Reputation` and the for attribute set to `"reputation"`.
+Below that `input` element, add another `label` element with the text of `Reputation` and the `for` attribute set to `"reputation"`.
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"reputation"`.
 
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md b/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
index 69efa4832c..09e3e6e59b 100644
--- a/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
@@ -7,7 +7,7 @@ dashedName: step-28
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attributes:**
 
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md b/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
index 6549345d45..22b9a707be 100644
--- a/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
@@ -7,7 +7,7 @@ dashedName: step-31
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attribute:**
 
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
new file mode 100644
index 0000000000..237515fd88
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
@@ -0,0 +1,71 @@
+---
+id: 66c8ba41a77db20a93f9d7a1
+title: Step 1
+challengeType: 1
+dashedName: step-1
+---
+
+# --description--
+
+In this workshop, you'll review JavaScript conditionals by building a loan qualification checker app.
+
+The app will check whether the user is eligible for a duplex, car, and condo loan based on their annual income and credit score. A credit score is a number that represents how good you are at managing borrowed money.
+
+To get started, create the following variables and values.
+
+| Variable Name             | Value   |
+| ------------------------- | ------- |
+| `minIncomeForDuplex`      | `60000` |
+| `minCreditScoreForDuplex` | `700`   |
+| `minIncomeForCondo`       | `45000` |
+| `minCreditScoreForCondo`  | `680`   |
+| `minIncomeForCar`         | `30000` |
+| `minCreditScoreForCar`    | `650`   |
+
+# --hints--
+
+You should create a `minIncomeForDuplex` variable set to `60000`.
+
+```js
+assert.equal(minIncomeForDuplex, 60000);
+```
+
+You should create a `minCreditScoreForDuplex` set to `700`.
+
+```js
+assert.equal(minCreditScoreForDuplex, 700);
+```
+
+You should create a `minIncomeForCar` variable set to `30000`.
+
+```js
+assert.equal(minIncomeForCar, 30000);
+```
+
+You should create a `minCreditScoreForCar` variable set to `650`.
+
+```js
+assert.equal(minCreditScoreForCar, 650);
+```
+
+You should create a `minIncomeForCondo` variable set to `45000`.
+
+```js
+assert.equal(minIncomeForCondo, 45000);
+```
+
+You should create a `minCreditScoreForCondo` variable set to `680`.
+
+```js
+assert.equal(minCreditScoreForCondo, 680);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
new file mode 100644
index 0000000000..7755f823c4
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
@@ -0,0 +1,53 @@
+---
+id: 66c8ba975ee7230e29f6c4ac
+title: Step 2
+challengeType: 1
+dashedName: step-2
+---
+
+# --description--
+
+When the user is eligible for a loan, you'll want to display a message to them in the console.
+
+For that, you'll build out a function inside which you'll have some checks that'll return what loan the applicant is eligible for.
+
+Create an empty `getLoanMessage` function with an `annualIncome` and `creditScore` parameters.
+
+# --hints--
+
+You should create a `getLoanMessage` function
+
+```js
+assert.isFunction(getLoanMessage)
+```
+
+Your `getLoanMessage` function should have an `annualIncome` and `creditScore` as parameters.
+
+```js
+assert.match(getLoanMessage?.toString(), /\(\s*annualIncome,\s*creditScore\s*\)|\(\s*creditScore,\s*annualIncome\s*\)/);
+```
+
+`getLoanMessage` should be an empty function.
+
+```js
+assert.match(getLoanMessage?.toString(), /\{\s*\}/);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
new file mode 100644
index 0000000000..82a29d7cd9
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
@@ -0,0 +1,55 @@
+---
+id: 66c8ba975ee7230e29f6c4ad
+title: Step 3
+challengeType: 1
+dashedName: step-3
+---
+
+# --description--
+
+To check which loan a user is qualified for based on the `annualIncome` and `creditScore`, you have to use `if/else if` statement or a ternary right inside the `getLoanMessage` function. You'll then return the appropraite message in the block of each condition.
+
+Starting with the duplex loan, check if `annualIncome` is greater than or equal to `minIncomeForDuplex` AND if `creditScore` is greater than `minCreditScoreForDuplex`.
+
+If that condition is true, then the applicant is eligible for a duplex loan and the other loans. So, inside the check, return the string `"You qualify for a car, duplex and Condo loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string.
+
+```js
+assert.isString(getLoanMessage(65000, 750));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a duplex, condo, and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(65000, 750), "You qualify for a duplex, condo, and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a duplex loan.
+
+```js
+assert.strictEqual(getLoanMessage(59000, 700), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+function getLoanMessage(annualIncome, creditScore) {
+
+}
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
new file mode 100644
index 0000000000..638e6291a4
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4af
+title: Step 4
+challengeType: 1
+dashedName: step-4
+---
+
+# --description--
+
+If the applicant's annual income is greater than or equal to `minIncomeForCondo`, AND if their credit score is greater than or equal to `minCreditScoreForCondo`, then they qualify for a condo and car loan.
+
+Check if that's true in the `getLoanMessage` function. If it is, return the string `"You qualify for a condo and car loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a condo and car loan.
+
+```js
+assert.isString(getLoanMessage(45000, 680));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a condo and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 680), "You qualify for a condo and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a condo loan.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 650), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
new file mode 100644
index 0000000000..374ba7b8fe
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4b0
+title: Step 5
+challengeType: 1
+dashedName: step-5
+---
+
+# --description--
+
+Now, you should check if the applicant is qualified for a car loan only. If they're, return the string `"You qualify for a car loan."`.
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a car loan.
+
+```js
+assert.isString(getLoanMessage(30000, 650));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 650), "You qualify for a car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a car loan.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 600), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+--fcc-editable-region--
+  } 
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
new file mode 100644
index 0000000000..16e8c7baca
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
@@ -0,0 +1,54 @@
+---
+id: 66c8ba975ee7230e29f6c4b1
+title: Step 6
+challengeType: 1
+dashedName: step-6
+---
+
+# --description--
+
+If the applicant's annual income and credit score fall below `minIncomeForCar` and `minCreditScoreForCar`, then they don't qualify for any loan. So, return the string `"You don't qualify for any loans."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant doesn't qualify for any loan.
+
+```js
+assert.isString(getLoanMessage(25000, 550));
+```
+
+Your `getLoanMessage` function should return the string `"You don't qualify for any loans."` if the applicant does not meet the requirements for any loan.
+
+```js
+assert.strictEqual(getLoanMessage(15000, 600), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(25000, 550), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(20000, 500), "You don't qualify for any loans.");
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
new file mode 100644
index 0000000000..9d19f9ea4c
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
@@ -0,0 +1,165 @@
+---
+id: 66c8ba975ee7230e29f6c4b2
+title: Step 7
+challengeType: 1
+dashedName: step-7
+---
+
+# --description--
+
+Now, it is time to test out your `getLoanMessage` function.
+
+Use the table below to create `4` variables and their values:
+
+| Variable Name   | Value                        |
+| --------------- | ---------------------------- |
+| `duplexLoanMsg` | `getLoanMessage(85000, 850)` |
+| `condoLoanMsg`  | `getLoanMessage(65000, 690)` |
+| `carLoanMsg`    | `getLoanMessage(45000, 660)` |
+| `noLoanMsg`     | `getLoanMessage(25000, 550)` |
+
+After that, log each variable to the console to see the messages.
+
+With that, your loan qualification checker project is complete!
+
+# --hints--
+
+You should have a variable called `duplexLoanMsg`.
+
+```js
+assert.isNotNull(duplexLoanMsg);
+```
+
+Your `duplexLoanMsg` variable should be set to the result of `getLoanMessage(85000, 850)`.
+
+```js
+assert.equal(duplexLoanMsg, getLoanMessage(85000, 850));
+```
+
+You should log the `duplexLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(duplexLoanMsg\)/)
+```
+
+You should have a variable called `condoLoanMsg`.
+
+```js
+assert.isNotNull(condoLoanMsg);
+```
+
+Your `condoLoanMsg` variable should be set to the result of `getLoanMessage(65000, 690)`.
+
+```js
+assert.equal(condoLoanMsg, getLoanMessage(65000, 690));
+```
+
+You should log the `condoLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(condoLoanMsg\)/)
+```
+
+You should have a variable called `carLoanMsg`.
+
+```js
+assert.isNotNull(carLoanMsg);
+```
+
+Your `carLoanMsg` variable should be set to the result of `getLoanMessage(45000, 660)`.
+
+```js
+assert.equal(carLoanMsg, getLoanMessage(45000, 660));
+```
+
+You should log the `carLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(carLoanMsg\)/)
+```
+
+You should have a variable called `noLoanMsg`.
+
+```js
+assert.isNotNull(noLoanMsg);
+```
+
+Your `noLoanMsg` variable should be set to the result of `getLoanMessage(25000, 550)`.
+
+```js
+assert.equal(noLoanMsg, getLoanMessage(25000, 550));
+```
+
+You should log the `noLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(noLoanMsg\)/)
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
+
+# --solutions--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+const duplexLoanMsg = getLoanMessage(85000, 850)
+console.log(duplexLoanMsg)
+
+const condoLoanMsg = getLoanMessage(65000, 690)
+console.log(condoLoanMsg)
+
+const carLoanMsg = getLoanMessage(45000, 660)
+console.log(carLoanMsg)
+
+const noLoanMsg = getLoanMessage(25000, 550)
+console.log(noLoanMsg)
+```
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md b/curriculum/challenges/korean/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
new file mode 100644
index 0000000000..4e11751ca0
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
@@ -0,0 +1,19 @@
+---
+id: 5f2c289f164c29556da632fd
+title: Build a Mario Database
+challengeType: 12
+url: freeCodeCamp/learn-relational-databases-by-building-a-mario-database
+dashedName: build-a-mario-database
+---
+
+# --description--
+
+In this 165-lesson workshop, you will learn the basics of a relational database by creating a PostgreSQL database filled with video game characters.
+
+# --instructions--
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
new file mode 100644
index 0000000000..8d4c90410d
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
@@ -0,0 +1,53 @@
+---
+id: 587d7fb3367417b2b2512bfb
+title: How to Use package.json, the Core of Any Node.js Project or npm Package
+challengeType: 2
+forumTopicId: 301528
+dashedName: how-to-use-package-json-the-core-of-any-node-js-project-or-npm-package
+---
+
+# --description--
+
+Working on these challenges will involve you writing your code using one of the following methods:
+
+- Clone <a href="https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete these challenges locally.
+- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+The `package.json` file is the center of any Node.js project or npm package. It stores information about your project. It consists of a single JSON object where information is stored in key-value pairs. There are only two required fields; `name` and `version`, but it’s good practice to provide additional information.
+
+You can create the `package.json` file from the terminal using the `npm init` command. This will run a guided setup. Using `npm init` with the `-y` flag will generate the file without having it ask any questions, `npm init -y`.
+
+If you look at the file tree of your project, you will find the `package.json` file on the top level of the tree. This is the file that you will be improving in the next couple of challenges.
+
+One of the most common pieces of information in this file is the `author` field. It specifies who created the project, and can consist of a string or an object with contact or other details. An object is recommended for bigger projects, but a simple string like the following example will do for this project.
+
+```json
+"author": "Jane Doe",
+```
+
+# --instructions--
+
+Add your name as the `author` of the project in the `package.json` file.
+
+**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (") and be separated with a comma (,).
+
+If you are using Gitpod, make sure the app is running and the preview window is open. Copy the preview window's URL and paste it into the Solution Link input below.
+
+# --hints--
+
+`package.json` should have a valid "author" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.author, '"author" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
new file mode 100644
index 0000000000..37d15d5261
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb3367417b2b2512bfc
+title: Add a Description to Your package.json
+challengeType: 2
+forumTopicId: 301522
+dashedName: add-a-description-to-your-package-json
+---
+
+# --description--
+
+The next part of a good package.json file is the `description` field; where a short, but informative description about your project belongs.
+
+If some day you plan to publish a package to npm, this is the string that should sell your idea to the user when they decide whether to install your package or not. However, that’s not the only use case for the description, it’s a great way to summarize what a project does. It’s just as important in any Node.js project to help other developers, future maintainers or even your future self understand the project quickly.
+
+Regardless of what you plan for your project, a description is definitely recommended. Here's an example:
+
+```json
+"description": "A project that does something awesome",
+```
+
+# --instructions--
+
+Add a `description` to the package.json file of your project.
+
+**Note:** Remember to use double-quotes for field-names (") and commas (,) to separate fields.
+
+# --hints--
+
+package.json should have a valid "description" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.description, '"description" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
new file mode 100644
index 0000000000..a001cdd477
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
@@ -0,0 +1,75 @@
+---
+id: 587d7fb4367417b2b2512bfd
+title: Add Keywords to Your package.json
+challengeType: 2
+forumTopicId: 301526
+dashedName: add-keywords-to-your-package-json
+---
+
+# --description--
+
+The `keywords` field is where you can describe your project using related keywords. Here's an example:
+
+```json
+"keywords": [ "descriptive", "related", "words" ],
+```
+
+As you can see, this field is structured as an array of double-quoted strings.
+
+# --instructions--
+
+Add an array of suitable strings to the `keywords` field in the package.json file of your project.
+
+One of the keywords should be "freecodecamp".
+
+# --hints--
+
+package.json should have a valid "keywords" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.keywords, '"keywords" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" field should be an Array
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.isArray(packJson.keywords, '"keywords" is not an array');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" should include "freecodecamp"
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.include(
+        packJson.keywords,
+        'freecodecamp',
+        '"keywords" does not include "freecodecamp"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
new file mode 100644
index 0000000000..7b09acd042
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
@@ -0,0 +1,39 @@
+---
+id: 587d7fb4367417b2b2512bfe
+title: Add a License to Your package.json
+challengeType: 2
+forumTopicId: 301523
+dashedName: add-a-license-to-your-package-json
+---
+
+# --description--
+
+The `license` field is where you inform users of what they are allowed to do with your project.
+
+Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do. Here's an example of the license field:
+
+```json
+"license": "MIT",
+```
+
+# --instructions--
+
+Fill the `license` field in the package.json file of your project as you find suitable.
+
+# --hints--
+
+package.json should have a valid "license" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.license, '"license" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
new file mode 100644
index 0000000000..f2e571faed
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
@@ -0,0 +1,37 @@
+---
+id: 587d7fb4367417b2b2512bff
+title: Add a Version to Your package.json
+challengeType: 2
+forumTopicId: 301525
+dashedName: add-a-version-to-your-package-json
+---
+
+# --description--
+
+A `version` is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example:
+
+```json
+"version": "1.2.0",
+```
+
+# --instructions--
+
+Add a `version` to the package.json file of your project.
+
+# --hints--
+
+package.json should have a valid "version" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.version, '"version" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
new file mode 100644
index 0000000000..161c60fe69
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
@@ -0,0 +1,68 @@
+---
+id: 587d7fb4367417b2b2512c00
+title: Expand Your Project with External Packages from npm
+challengeType: 2
+forumTopicId: 301527
+dashedName: expand-your-project-with-external-packages-from-npm
+---
+
+# --description--
+
+One of the biggest reasons to use a package manager, is their powerful dependency management. Instead of manually having to make sure that you get all dependencies whenever you set up a project on a new computer, npm automatically installs everything for you. But how can npm know exactly what your project needs? Meet the `dependencies` section of your package.json file.
+
+In this section, packages your project requires are stored using the following format:
+
+```json
+"dependencies": {
+  "package-name": "version",
+  "express": "4.14.0"
+}
+
+```
+
+# --instructions--
+
+Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file.
+
+**Note:** `@freecodecamp/example` is a faux package used as a learning tool.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.1.0"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^[\^\~]?1\.1\.0/,
+        'Wrong version of "@freecodecamp/example" installed. It should be 1.1.0'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
new file mode 100644
index 0000000000..deda9b82de
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
@@ -0,0 +1,64 @@
+---
+id: 587d7fb5367417b2b2512c01
+title: Manage npm Dependencies By Understanding Semantic Versioning
+challengeType: 2
+forumTopicId: 301529
+dashedName: manage-npm-dependencies-by-understanding-semantic-versioning
+---
+
+# --description--
+
+`Versions` of the npm packages in the dependencies section of your package.json file follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes projects can expect if they update.
+
+Knowing SemVer can be useful when you develop software that uses external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things that worked yesterday suddenly don’t work today. This is how Semantic Versioning works according to the official website:
+
+```json
+"package": "MAJOR.MINOR.PATCH"
+```
+
+The MAJOR version should increment when you make incompatible API changes. The MINOR version should increment when you add functionality in a backwards-compatible manner. The PATCH version should increment when you make backwards-compatible bug fixes. This means that PATCHes are bug fixes and MINORs add new features but neither of them break what worked before. Finally, MAJORs add changes that won’t work with earlier versions.
+
+# --instructions--
+
+In the dependencies section of your `package.json` file, change the version of `@freecodecamp/example` to match MAJOR version 1, MINOR version 2 and PATCH version 13
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.equal(
+        packJson.dependencies["@freecodecamp/example"],
+        '1.2.13',
+        'Wrong version of "@freecodecamp/example". It should be 1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
new file mode 100644
index 0000000000..8eae5f51ee
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c02
+title: Use the Tilde-Character to Always Use the Latest Patch Version of a Dependency
+challengeType: 2
+forumTopicId: 301532
+dashedName: use-the-tilde-character-to-always-use-the-latest-patch-version-of-a-dependency
+---
+
+# --description--
+
+In the last challenge, you told npm to only include a specific version of a package. That’s a useful way to freeze your dependencies if you need to make sure that different parts of your project stay compatible with each other. But in most use cases, you don’t want to miss bug fixes since they often include important security patches and (hopefully) don’t break things in doing so.
+
+To allow an npm dependency to update to the latest PATCH version, you can prefix the dependency’s version with the tilde (`~`) character. Here's an example of how to allow updates to any `1.3.x` version.
+
+```json
+"package": "~1.3.8"
+```
+
+# --instructions--
+
+In the package.json file, your current rule for how npm may upgrade `@freecodecamp/example` is to use a specific version (`1.2.13`). But now, you want to allow the latest `1.2.x` version.
+
+Use the tilde (`~`) character to prefix the version of `@freecodecamp/example` in your dependencies, and allow npm to update it to any new _patch_ release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"~1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\~1\.2\.13/,
+        'Wrong version of "@freecodecamp/example". It should be ~1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
new file mode 100644
index 0000000000..adc3014ea4
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c03
+title: Use the Caret-Character to Use the Latest Minor Version of a Dependency
+challengeType: 2
+forumTopicId: 301531
+dashedName: use-the-caret-character-to-use-the-latest-minor-version-of-a-dependency
+---
+
+# --description--
+
+Similar to how the tilde we learned about in the last challenge allows npm to install the latest PATCH for a dependency, the caret (`^`) allows npm to install future updates as well. The difference is that the caret will allow both MINOR updates and PATCHes.
+
+Your current version of `@freecodecamp/example` should be `~1.2.13` which allows npm to install to the latest `1.2.x` version. If you were to use the caret (^) as a version prefix instead, npm would be allowed to update to any `1.x.x` version.
+
+```json
+"package": "^1.3.8"
+```
+
+This would allow updates to any `1.x.x` version of the package.
+
+# --instructions--
+
+Use the caret (`^`) to prefix the version of `@freecodecamp/example` in your dependencies and allow npm to update it to any new MINOR release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"^1.x.x"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\^1\./,
+        'Wrong version of "@freecodecamp/example". It should be ^1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
new file mode 100644
index 0000000000..5f695eed88
--- /dev/null
+++ b/curriculum/challenges/korean/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb5367417b2b2512c04
+title: Remove a Package from Your Dependencies
+challengeType: 2
+forumTopicId: 301530
+dashedName: remove-a-package-from-your-dependencies
+---
+
+# --description--
+
+You have now tested a few ways you can manage dependencies of your project by using the package.json's dependencies section. You have also included external packages by adding them to the file and even told npm what types of versions you want, by using special characters such as the tilde or the caret.
+
+But what if you want to remove an external package that you no longer need? You might already have guessed it, just remove the corresponding key-value pair for that package from your dependencies.
+
+This same method applies to removing other fields in your package.json as well.
+
+# --instructions--
+
+Remove the `@freecodecamp/example` package from your dependencies.
+
+**Note:** Make sure you have the right amount of commas after removing it.
+
+# --hints--
+
+`"dependencies"` should not include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.notProperty(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" still includes "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md b/curriculum/challenges/portuguese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
index 71ebaa41d5..6297c12cea 100644
--- a/curriculum/challenges/portuguese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
+++ b/curriculum/challenges/portuguese/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
@@ -8,7 +8,7 @@ dashedName: build-a-periodic-table-database
 
 # --description--
 
-Este é um dos projetos necessários para obter sua certificação. Para este projeto, você criará um script no Bash para obter informações sobre elementos químicos de um banco de dados de tabela periódica.
+Este é um dos projetos necessários para obter sua certificação. Para este projeto, você criará um script do Bash para obter informações sobre elementos químicos de um banco de dados de tabela periódica.
 
 # --instructions--
 
diff --git a/curriculum/challenges/portuguese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md b/curriculum/challenges/portuguese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
index 8a6a387f29..a655787ba5 100644
--- a/curriculum/challenges/portuguese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
+++ b/curriculum/challenges/portuguese/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
@@ -9,6 +9,8 @@ dashedName: step-64
 
 Dentro do `footer`, adicione um elemento `p`. Então, aninhe um elemento de âncora (`a`) no `p` que encaminhe para `https://www.freecodecamp.org` e tenha o texto `Visit our website`.
 
+Make sure that the link opens in a new tab by adding a `target` attribute with the value `_blank`.
+
 # --hints--
 
 O elemento preexistente `footer` deve permanecer o mesmo.
@@ -43,6 +45,12 @@ O novo elemento de âncora (`a`) deve fazer um link para `https://www.freecodeca
 assert(document.querySelector("footer > p > a")?.href === "https://www.freecodecamp.org/");
 ```
 
+Your new `a` element should have the `target` attribute set to `_blank`.
+
+```js
+assert.equal(document.querySelector("footer > p > a")?.target, "_blank");
+```
+
 # --seed--
 
 ## --seed-contents--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-a.md b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-a.md
index e89ae1c17d..5e27afd190 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-a.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-a.md
@@ -7,53 +7,53 @@ dashedName: introduction-flexbox-lesson-a
 
 # --description--
 
-## Before we get started
+## Antes de começarmos
 
-Flexbox layouts can get a little complicated. Em uma lição anterior, você aprendeu como inspecionar e depurar coisas usando as ferramentas de desenvolvedor do seu navegador. Those tools will be crucial for you in the following lessons. If something isn’t behaving the way you expect, inspecting it in the developer tools should be your first step every time.
+Os layouts do Flexbox podem ficar um pouco complicados. Em uma lição anterior, você aprendeu como inspecionar e depurar coisas usando as ferramentas de desenvolvedor do seu navegador. Essas ferramentas serão cruciais para você nas próximas lições. Se algo não está se comportando do modo esperado, inspecionar nas ferramentas de desenvolvedor deve ser seu primeiro passo sempre.
 
-Flexbox isn’t necessarily any more difficult than the other concepts that we’ve covered so far, but it does have a few more moving parts. Vai ser um pouco difícil usar qualquer uma das coisas que você está aprendendo nestas primeiras lições até chegar ao fim e conseguir juntar tudo. As we go, do yourself a favor and <strong>play with all of the code examples.</strong>
+O Flexbox não é necessariamente mais difícil do que os outros conceitos que cobrimos até agora, mas tem algumas partes que requerem um pouco mais de atenção. Vai ser um pouco difícil usar qualquer uma das coisas que você está aprendendo nestas primeiras lições até chegar ao fim e conseguir juntar tudo. À medida que avançamos, aproveite o tempo e <strong>brinque bastante com todos os exemplos de código.</strong>
 
 Você quase definitivamente precisará voltar e se referir a essas lições (ou a alguns dos recursos que compartilhamos com você) quando chegar às atividades no final da seção, mas se você levar seu tempo e experimentar todos os exemplos de código que fornecemos, saberá melhor onde procurar quando esse momento chegar.
 
-## Let’s flex
+## Vamos usar o flex
 
-Flexbox is a way to arrange items into rows or columns. These items will flex (i.e. grow or shrink) based on some simple rules that you can define. To get started, let’s look at a simple demonstration.
+O Flexbox é uma maneira de dispor itens em linhas ou colunas. Esses itens "flexionar" (ou seja, crescer ou encolher) com base em algumas regras simples que você pode definir. Para começar, vamos olhar para uma demonstração simples.
 
-> We’ve embedded a lot of interactive examples in these lessons. Take your time to experiment with them as you go to cement the concepts in your mind!
+> Inserimos muitos exemplos interativos nessas lições. Passe um tempo experimentando com eles à medida que avança para fixar os conceitos em sua mente!
 
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true"  frameborder="0" height="400" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/QWgNxrp?height=400&amp;default-tab=html%2Cresult&amp;slug-hash=QWgNxrp&amp;editable=true&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy"></iframe>
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true"  frameborder="0" height="400" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/QWgNxrp?height=400&amp;default-tab=html%2Cresult&amp;slug-hash=QWgNxrp&amp;editable=true&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy"></iframe>
 
-We’ll get into exactly what’s going on here soon enough. But for now, let’s uncomment the two flex related CSS declarations in the above Codepen by removing the `/*` and `*/` tags surrounding them, then check out the result.
+Falaremos sobre o que está acontecendo aqui em breve. Por enquanto, vamos descomentar as duas declarações do CSS relacionadas ao flex no Codepen acima removendo as tags `/*` e `*/` que as envolvem. Depois, conferimos o resultado.
 
-> Comments prevent the browser from interpreting lines as code, and are wrapped between specific tags. CSS uses `/*` as an opening comment tag and `*/` as a closing comment tag, while HTML and JavaScript have their own syntax. Commented out lines of code can be re-enabled simply by removing the comment tags surrounding the code.
+> Comentários impedem que o navegador interprete linhas como código e são envoltos entre tags específicas. O CSS usa `/*` como tag de abertura do comentário e `*/` como tag de fechamento do comentário. O HTML e o JavaScript têm sua própria sintaxe. Linhas de código comentadas podem ser reabilitadas simplesmente removendo as tags de comentário que as cercam.
 
-All 3 divs should now be arranged horizontally. If you resize the results frame with the `1x`, `.5x` and `.25x` buttons you’ll also see that the `div` elements will "flex". They will fill the available area and will each have equal width.
+Todas as 3 divs devem agora estar dispostas horizontalmente. Se você redimensionar a janela de resultados com os botões `1x`, `.5x` e `.25x` você também verá que os elementos `div` vão "flexionar". Eles preencherão a área disponível e terão largura igual.
 
-If you add another `div` to the HTML, inside of `.flex-container`, it will show up alongside the others, and everything will flex to fit within the available area.
+Se você adicionar outra `div` ao HTML, dentro de `.flex-container`, ela aparecerá ao lado dos outras. Tudo se ajustará para caber dentro da área disponível.
 
-> If it’s hard to see what's going on in the small embedded CodePen, feel free to click the "Edit on CodePen" or "Fork on CodePen" button. This will bring the example into a full-sized environment. Some of the later examples might especially benefit from doing this.
+> Se for difícil ver o que está acontecendo no pequeno CodePen incorporado, sinta-se à vontade para clicar no botão "Edit on CodePen" ou "Fork on CodePen". Isso trará o exemplo para um ambiente de tamanho completo. Ao fazer isso, será possível visualizar melhor alguns dos exemplos posteriores.
 
 # --question--
 
 ## --text--
 
-What happens when the two flex related CSS declarations in the CodePen are uncommented?
+O que acontece quando as duas declarações do CSS relacionadas ao flex no CodePen são descomentadas?
 
 ## --answers--
 
-The `div` elements become hidden from view, losing their visibility within the container.
+Os elementos `div` ficam escondidos da vista, perdendo sua visibilidade dentro do contêiner.
 
 ---
 
-All 3 `div` elements are arranged horizontally, and they flex to fill the available area with equal width.
+Os 3 elementos `div` são dispostos horizontalmente e se flexionam para preencher a área disponível com largura igual.
 
 ---
 
-Each `div` element enlarges and covers the entire container, overlapping each other.
+Cada elemento `div` se amplia e cobre todo o contêiner, sobrepondo-se uns aos outros.
 
 ---
 
-The `div` elements align vertically in a single column, ignoring the flex-related CSS declarations.
+Os elementos `div` se alinham verticalmente em uma única coluna, ignorando as declarações do CSS relacionadas ao flex.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-c.md b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-c.md
index 0b7a8d3948..aa83757e28 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-c.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-c.md
@@ -7,21 +7,21 @@ dashedName: introduction-flexbox-lesson-c
 
 # --description--
 
-Somewhat confusingly, any element can be both a flex container and a flex item. Said another way, you can also put `display: flex` on a flex item and then use flexbox to arrange its children.
+Pode parecer um pouco confuso, mas qualquer elemento pode ser tanto um contêiner flex quanto um item flexível. Dito de outra forma, você também pode colocar `display: flex` em um flex item e usar o flexbox para organizar seus filhos.
 
-<img src="https://cdn.freecodecamp.org/curriculum/odin-project/flex-box/flexbox-03.png" style="width: 95%; height: 95%;" alt="a flex container that has multiple flex items, within those flex items are nested flex items as well. Making the parent of those nested flex items also a flex container." />
+<img src="https://cdn.freecodecamp.org/curriculum/odin-project/flex-box/flexbox-03.png" style="width: 95%; height: 95%;" alt="um flex contêiner que tem múltiplos flex itens, dentro desses flex itens estão aninhados flex itens também. Isso também torna o pai desses flex itens aninhados um flex contêiner." />
 
-Creating and nesting multiple flex containers and items is the primary way you will be building up complex layouts. The following image was achieved using only flexbox to arrange, size, and place the various elements. Flexbox is a very powerful tool.
+Criar e aninhar múltiplos contêineres flex e itens flex é a principal forma de você construir layouts complexos. A imagem a seguir foi obtida utilizando apenas flexbox para organizar, dimensionar e posicionar os diversos elementos. Flexbox é uma ferramenta muito poderosa.
 
-<img src="https://cdn.freecodecamp.org/curriculum/odin-project/flex-box/flexbox-02.png" alt="a complex layout of flex items and flex containers. There are multiple flex containers nested into each other, thus making them flex items as well" />
+<img src="https://cdn.freecodecamp.org/curriculum/odin-project/flex-box/flexbox-02.png" alt="um layout complexo de itens flex e contêineres flex. Há múltiplos contêineres flex aninhados uns nos outros, portanto tornando-os também itens flex" />
 
-Certainly, the image features a representation of a CSS Flexbox layout with nested flex containers. The outer container is denoted as "ALSO a flex container" highlighted in blue, and within it is another container marked as "with flex items" in red. Inside the red container, there are three items labeled as "flex items" in peach. This demonstrates that a flex container can be nested within another flex container and contain its own flex items, showcasing the recursive nature of Flexbox layout structures.
+Certamente, a imagem apresenta uma representação de um layout Flexbox CSS com contêineres flex aninhados. O contêiner externo é marcado como "ALSO a flex container" destacado em azul, e dentro dele há outro contêiner marcado como "with flex items" em vermelho. Dentro do contêiner vermelho, há três itens rotulados como "flex items" na cor pêssego. Isso demonstra que um contêiner flex pode ser aninhado dentro de outro contêiner flex e conter seus próprios itens flex, mostrando a natureza recursiva das estruturas de layout Flexbox.
 
 # --question--
 
 ## --text--
 
-Which CSS property is applied to elements to make them flex containers?
+Qual propriedade CSS é aplicada aos elementos para torná-los contêineres flex?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-d.md b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-d.md
index f7e458c52d..c5dd53213c 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-d.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-d.md
@@ -1,35 +1,35 @@
 ---
 id: 6571b2ffcc1de61d7b4dd382
-title: Introduction to Flexbox Lesson D
+title: Lição D de Introdução ao Flexbox
 challengeType: 15
 dashedName: introduction-flexbox-lesson-d
 ---
 
 # --description--
 
-Now that you have a basic understanding of how flexbox works, what is the primairy role of a flex item in a `flexbox` layout? Try and answer the question below.
+Agora que você tem um entendimento básico de como o flexbox funciona, qual é o papel primário de um item flex em um layout do `flexbox`? Tente responder a pergunta abaixo.
 
 # --question--
 
 ## --text--
 
-What role does a flex item play within a flex container?
+Qual papel um item flex desempenha dentro de um contêiner flex?
 
 ## --answers--
 
-Flex items define the overall layout structure.
+Itens flex definem a estrutura geral do layout.
 
 ---
 
-Flex items set the background colors of flex containers.
+Itens flex definem as cores de fundo dos contêineres flex.
 
 ---
 
-Flex items allow the flex container to resize based on content.
+Itens flex permitem que o contêiner flex seja redimensionado com base no conteúdo.
 
 ---
 
-Flex items are elements that reside directly within a flex container.
+Itens flex são elementos que residem diretamente dentro de um contêiner flex.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-e.md b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-e.md
index 366cd6d942..a9307e7d8d 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-e.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-e.md
@@ -7,39 +7,39 @@ dashedName: introduction-flexbox-lesson-e
 
 # --description--
 
-The `flex` declaration is actually a shorthand for 3 properties that you can set on a flex item. These properties affect how flex items size themselves within their container. You've seen some shorthand properties before, but you haven't officially defined them yet.
+A declaração `flex` é na verdade uma abreviação para 3 propriedades que você pode definir em um item flex. Essas propriedades afetam como os itens flex dimensionam a si mesmos dentro de seu contêiner. Você já viu algumas propriedades abreviadas antes, mas ainda não as definiu oficialmente.
 
-> Shorthand properties are CSS properties that let you set the values of multiple other CSS properties simultaneously. Using a shorthand property, you can write more concise (and often more readable) stylesheets, saving time and energy.
+> Propriedades abreviadas são propriedades do CSS que permitem definir os valores de múltiplas outras propriedades do CSS simultaneamente. Usando uma propriedade abreviada, você pode escrever folhas de estilo mais concisas (e muitas vezes mais legíveis), economizando tempo e energia.
 
-In this case, `flex` is actually a shorthand for `flex-grow`, `flex-shrink` and `flex-basis`.
+Neste caso, `flex` é, na verdade, uma abreviação para `flex-grow`, `flex-shrink` e `flex-basis`.
 
-<img src="https://cdn.freecodecamp.org/curriculum/odin-project/flex-box/flexbox-04.png" alt="CSS code setting the flex property to 1 for a div element." />
+<img src="https://cdn.freecodecamp.org/curriculum/odin-project/flex-box/flexbox-04.png" alt="Código em CSS definindo a propriedade flex para 1 em um elemento div." />
 
-In the above screenshot, `flex: 1` equates to: `flex-grow: 1`, `flex-shrink: 1`, `flex-basis: 0`.
+Na captura de tela acima, `flex: 1` equivale a: `flex-grow: 1`, `flex-shrink: 1`, `flex-basis: 0`.
 
-Very often, you see the flex shorthand defined with only one value. In that case, that value is applied to `flex-grow`. So when you put `flex: 1` on our divs, you were actually specifying a shorthand of `flex: 1 1 0`.
+Muito frequentemente, você vê a abreviação de flex definida com apenas um valor. Nesse caso, esse valor é aplicado a `flex-grow`. Então, quando você colocou `flex: 1` nas divs, você estava, na verdade, especificando uma abreviação de `flex: 1 1 0`.
 
 # --question--
 
 ## --text--
 
-Which properties are set by the `flex` shorthand?
+Quais propriedades são definidas pela abreviação `flex`?
 
 ## --answers--
 
-`flex-grow`, `flex-shrink`, and `flex`
+`flex-grow`, `flex-shrink` e `flex`
 
 ---
 
-`flex-basis`, `flex-wrap`, and `flex-direction`
+`flex-basis`, `flex-wrap` e `flex-direction`
 
 ---
 
-`flex-grow`, `flex-shrink`, and `flex-basis`
+`flex-grow`, `flex-shrink` e `flex-basis`
 
 ---
 
-`flex-direction`, `flex`, and `flex-wrap`
+`flex-direction`, `flex` e `flex-wrap`
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-i.md b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-i.md
index daeb69cd8a..1a7f412baa 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-i.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-i.md
@@ -7,37 +7,37 @@ dashedName: introduction-flexbox-lesson-i
 
 # --description--
 
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="400" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/BaZKPdw?height=400&amp;default-tab=html%2Cresult&amp;slug-hash=BaZKPdw&amp;editable=true&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_BaZKPdw"></iframe>
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="400" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/BaZKPdw?height=400&amp;default-tab=html%2Cresult&amp;slug-hash=BaZKPdw&amp;editable=true&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_BaZKPdw"></iframe>
 
-One thing to note is that in this example, `flex-direction: column` would not work as expected if you used the shorthand `flex: 1`. Try it out now (i.e. go change the flex value on the `flex: 1 1 auto;` line). Can you figure out why it does not work if `flex: 1` is used? The divs collapse, even though they clearly have a height defined there.
+Uma coisa a observar é que, neste exemplo, `flex-direction: column` não funcionaria como esperado se você usasse a abreviação `flex: 1`. Tente agora (ou seja, vá mudar o valor do flex na linha `flex: 1 1 auto;`). Você pode descobrir por que não funciona se `flex: 1` for usado? As divs colapsam, embora claramente tenham uma altura definida ali.
 
-The reason for this is that the flex shorthand expands `flex-basis` to `0`, which means that all `flex-growing` and `flex-shrinking` would begin their calculations from 0. Empty divs by default have 0 height, so for our flex items to fill up the height of their container, they don't actually need to have any height at all.
+A razão para isso é que a forma abreviada de flex expande `flex-basis` para `0`, o que significa que todo o `flex-growing` e `flex-shrinking` começaria seus cálculos a partir de 0. Divs vazias, por padrão, têm altura 0, então para nossos itens de flex ocuparem a altura de seu contêiner, eles, na verdade, não precisariam ter qualquer altura.
 
-The example above fixed this by specifying `flex: 1 1 auto`, telling the flex items to default to their given height. You could also have fixed it by putting a `height` on the parent `.flex-container`, or by using `flex-grow: 1` instead of the shorthand.
+O exemplo acima corrigiu isso especificando `flex: 1 1 auto`, dizendo aos itens flex para adotarem a altura fornecida. Você também poderia ter corrigido isso colocando uma `height` no `.flex-container` pai, ou usando `flex-grow: 1` invés da forma abreviada.
 
-Another detail to notice: when you changed the `flex-direction` to `column`, `flex-basis` refers to `height` instead of `width`. Given the context this may be obvious, but it's something to be aware of.
+Outro detalhe a ser observado: quando você alterou a `flex-direction` para `column`, `flex-basis` refere-se a `height` em vez de `width`. Dado o contexto, isso pode ser óbvio, mas é algo a se ter em mente.
 
 # --question--
 
 ## --text--
 
-Why does using `flex: 1` shorthand with `flex-direction: column` lead to collapsed divs in the example described?
+Por que usar a forma abreviada `flex: 1` com `flex-direction: column` leva a divs colapsadas no exemplo descrito?
 
 ## --answers--
 
-The `flex` shorthand defaults `flex-basis` to 0, disregarding the defined height of the divs.
+A forma abreviada do `flex` define `flex-basis` como 0, desconsiderando a altura definida das divs.
 
 ---
 
-The `flex` shorthand overrides the specified `flex-direction`, causing collapsing.
+A forma abreviada do `flex` sobrepõe a `flex-direction` especificada, causando o colapso.
 
 ---
 
-`flex: 1` only works in a row-based layout, not in a column-based one.
+`flex: 1` só funciona com base em layout de linhas, não com base em colunas.
 
 ---
 
-The `flex-basis` property becomes fixed to the width, ignoring the height in column layout.
+A propriedade `flex-basis` torna-se fixa na largura, ignorando a altura no layout de coluna.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
index 0ac30fef8c..b000c7801c 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
@@ -7,45 +7,45 @@ dashedName: introduction-flexbox-lesson-j
 
 # --description--
 
-Let's look at an example.
+Dê uma olhada no exemplo.
 
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="400" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/MWoyBzR?height=400&amp;default-tab=html%2Cresult&amp;slug-hash=MWoyBzR&amp;editable=true&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_MWoyBzR"></iframe>
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="400" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/MWoyBzR?height=400&amp;default-tab=html%2Cresult&amp;slug-hash=MWoyBzR&amp;editable=true&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_MWoyBzR"></iframe>
 
-You should be able to predict what happens if you put `flex: 1` on the `.item` by now. Give it a shot before you move on!
+Agora você deve ser capaz de prever o que acontece se você colocar `flex: 1` no `.item`. Tente antes de continuar!
 
-Adding `flex: 1` to `.item` makes each of the items grow to fill the available space, but what if you wanted them to stay the same width, but distribute themselves differently inside the container? You can do this!
+Adicionar `flex: 1` ao `.item` faz com que cada um dos itens cresça para preencher o espaço disponível, mas o que você poderia fazer se quisesse que eles mantivessem a mesma largura, embora se distribuíssem de modo diferente dentro do contêiner? Você pode fazer isso!
 
-Remove `flex: 1` from `.item` and add `justify-content: space-between` to `.container`. Doing so should give you something like this:
+Remova `flex: 1` do `.item` e adicione `justify-content: space-between` ao `.container`. Fazendo isso, você deve obter algo assim:
 
-<img src="https://cdn.freecodecamp.org/curriculum/odin-project/flex-box/flexbox-05.png" alt="Three small boxes within a much larger rectangle. The boxes are arranged in a single row, one close to the left edge of the container, one close to the right edge of the container, and the last directly in the middle of the container, placing as much space as possible between each box." />
+<img src="https://cdn.freecodecamp.org/curriculum/odin-project/flex-box/flexbox-05.png" alt="Três pequenas caixas dentro de um retângulo muito maior. As caixas são dispostas em uma única linha, uma próxima à borda esquerda do contêiner, outra próxima à borda direita do contêiner e a última diretamente no meio do contêiner, colocando o máximo de espaço possível entre cada caixa." />
 
-`justify-content` aligns items across the **main axis**. There are a few values that you can use here. You'll learn the rest of them in the reading assignments, but for now try changing it to center, which should center the boxes along the main axis.
+`justify-content` alinha itens ao longo do **eixo principal**. Existem alguns valores que você pode usar aqui. Você aprenderá o restante nas leituras indicadas. Por enquanto, tente mudar para center, o que deve centralizar as caixas ao longo do eixo principal.
 
-# --question--
+# --assignment--
 
-## --assignment--
+Antes de passar para a próxima lição, veja o que é possível com a propriedade `justify-content`. Leia este [artigo interativo na MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) e experimente com os diferentes valores de `justify-content` no exemplo.
 
-Antes de passar para a próxima lição, veja o que é possível com a propriedade `justify-content`. Read this [interactive article on MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) and play around with the different values of `justify-content` on the example.
+# --question--
 
 ## --text--
 
-How does applying `justify-content: space-between` to a flex container affect the positioning of its items?
+Como aplicar `justify-content: space-between` a um contêiner flex afeta o posicionamento dos seus itens?
 
 ## --answers--
 
-It evenly distributes space between items, pushing the first and last items to the edges.
+Distribui o espaço uniformemente entre os itens, empurrando o primeiro e o último itens para as bordas.
 
 ---
 
-It centers all items within the container.
+Centraliza todos os itens dentro do contêiner.
 
 ---
 
-It causes the items to grow to fill available space.
+Faz com que os itens cresçam para preencher o espaço disponível.
 
 ---
 
-It aligns items to the left side while leaving excessive space on the right side.
+Alinha os itens ao lado esquerdo enquanto deixa espaço excessivo no lado direito.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
index 7456af7346..c1385b2770 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
@@ -17,12 +17,12 @@ Para mudar o posicionamento dos itens ao longo do eixo transversal, use `align-i
 
 Como `justify-content` e `align-items` são baseados no eixo principal e no eixo transversal do seu contêiner, o comportamento muda quando você muda a flex-direction de um contêiner flexível. Por exemplo, quando você altera `flex-direction` para `column`, `justify-content` alinha verticalmente e `align-items` alinha horizontalmente. O comportamento mais comum, no entanto, é o padrão, ou seja, `justify-content` alinha os itens na horizontal (pois o eixo principal é o horizontal por padrão) e `align-items` os alinha na vertical. Um dos maiores pontos de confusão para iniciantes com flexbox é quando esse comportamento muda.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Antes de passar para a próxima lição, veja se você consegue entender como `align-items` se comporta quando você muda a propriedade `flex-direction` para `column`.
 
+# --question--
+
 ## --text--
 
 Ao mudar a propriedade `flex-direction` para `column` em um contêiner flexível, como `align-items` se comporta em relação aos itens flexíveis?
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-a.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-a.md
index e10900ecdf..24ffbd8f43 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-a.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-a.md
@@ -7,11 +7,11 @@ dashedName: learn-arrays-and-loops-lesson-a
 
 # --description--
 
-Strings and numbers may be our building blocks, but as your scripts get more complex, you're going to need a way to deal with large quantities of them. Luckily, JavaScript has a couple of data types that are used for just that. An Array is an ordered collection of items (Strings, numbers, or other things).
+Strings e números podem ser nossos blocos de construção, mas à medida que seus scripts se tornam mais complexos, você vai precisar de uma maneira de lidar com grandes quantidades deles. Felizmente, o JavaScript possui alguns tipos de dados que são utilizados exatamente para isso. Um array é uma coleção ordenada de itens (strings, números ou outras coisas).
 
-Arrays are a way to store multiple values in a single variable. They are a special type of object that has a length property and a series of numbered properties. Each numbered property is called an element, and each element can store a value of any type.
+Arrays são uma maneira de armazenar múltiplos valores em uma única variável. Eles são um tipo especial de objeto que possui uma propriedade length e uma série de propriedades numeradas. Cada propriedade numerada é chamada de elemento. Cada elemento pode armazenar um valor de qualquer tipo.
 
-An Example of an array is:
+Um exemplo de um array é:
 
 ```javascript
 const fruits = ['apple', 'banana', 'orange'];
@@ -21,23 +21,23 @@ const fruits = ['apple', 'banana', 'orange'];
 
 ## --text--
 
-What is an array in JavaScript?
+O que é um array no JavaScript?
 
 ## --answers--
 
-A function that stores multiple strings and numbers.
+Uma função que armazena múltiplos strings e números.
 
 ---
 
-A data type used exclusively for numerical operations.
+Um tipo de dado usado exclusivamente para operações numéricas.
 
 ---
 
-An ordered collection of items that can store values of any type, including strings and numbers.
+Uma coleção ordenada de itens que pode armazenar valores de qualquer tipo, incluindo strings e números.
 
 ---
 
-A variable that can only store string values.
+Uma variável que só pode armazenar valores de string.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-c.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-c.md
index 77689a7e3b..9ac95b743d 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-c.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-c.md
@@ -1,15 +1,15 @@
 ---
 id: 661e27578602567c118451d3
-title: Learn Arrays and Loops Lesson C
+title: Lição C de Aprenda arrays e laços
 challengeType: 15
 dashedName: learn-arrays-and-loops-lesson-c
 ---
 
 # --description--
 
-One of the most common ways to add a new element to an array is by using the `push()` method. The `push()` method adds one or more elements to the end of an array and returns the new length of the array.
+Uma das maneiras mais comuns de adicionar um novo elemento a um array é usando o método `push()`. O método `push()` adiciona um ou mais elementos ao final de um array e retorna o novo comprimento do array.
 
-For example, to add a new element to the `pet` array, you can use the following code:
+Por exemplo, para adicionar um novo elemento ao array `pet`, você pode usar o seguinte código:
 
 ```javascript
 const pet = ['cat', 'dog', 'bunny'];
@@ -17,9 +17,9 @@ pet.push('parrot');
 console.log(pet); // Output: ['cat', 'dog', 'bunny', 'parrot']
 ```
 
-To remove the last element of an array, you can use the `pop()` method. The `pop()` method removes the last element from an array and returns that element.
+Para remover o último elemento de um array, você pode usar o método `pop()`. O método `pop()` remove o último elemento de um array e retorna aquele elemento.
 
-For example, to remove the last element from the `pet` array, you can use the following code:
+Por exemplo, para remover o último elemento do array `pet`, você pode usar o seguinte código:
 
 ```javascript
 const pet = ['cat', 'dog', 'tiger'];
@@ -32,7 +32,7 @@ console.log(pet); // Output: ['cat', 'dog']
 
 ## --text--
 
-Given the following JavaScript code, what will be the output after executing the code snippet?
+Dado o seguinte código em JavaScript, qual será a saída após a execução do trecho de código?
 
 ```javascript
 const animals = ['deer', 'whale', 'frog'];
@@ -45,19 +45,19 @@ console.log(removed);
 
 ## --answers--
 
-`['deer', 'whale', 'frog', 'shark', 'bear']` and `'bear'`
+`['deer', 'whale', 'frog', 'shark', 'bear']` e `'bear'`
 
 ---
 
-`['deer', 'whale', 'frog', 'shark']` and `'bear'`
+`['deer', 'whale', 'frog', 'shark']` e `'bear'`
 
 ---
 
-`['deer', 'whale', 'frog', 'shark', 'bear']` and `null`
+`['deer', 'whale', 'frog', 'shark', 'bear']` e `null`
 
 ---
 
-`['deer', 'whale', 'frog', 'shark', 'bear']` and `['deer', 'whale', 'frog', 'shark']`
+`['deer', 'whale', 'frog', 'shark', 'bear']` e `['deer', 'whale', 'frog', 'shark']`
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-d.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-d.md
index 3954469401..762c29fc5e 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-d.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-d.md
@@ -1,15 +1,15 @@
 ---
 id: 661e27588602567c118451d4
-title: Learn Arrays and Loops Lesson D
+title: Lição D de Aprenda arrays e laços
 challengeType: 15
 dashedName: learn-arrays-and-loops-lesson-d
 ---
 
 # --description--
 
-One of the more complex methods used with arrays are the `splice()` and `slice()` methods. The `splice()` method changes the contents of an array by removing or replacing an element in the array. The `slice()` method returns a shallow copy of a portion of an array into a new array object selected from `begin` to `end` (`end` not included). The original array will not be modified.
+Entre os métodos mais complexos usados com arrays estão os métodos `splice()` e `slice()`. O método `splice()` altera o conteúdo de um array removendo ou substituindo um elemento no array. O método `slice()` retorna uma cópia rasa de uma porção de um array em um novo objeto de array selecionado de `begin` até `end` (não incluindo `end`). O array original não será modificado.
 
-For example, to remove the second element from the `characters` array, you can use the following code:
+Por exemplo, para remover o segundo elemento do array `characters`, você pode usar o seguinte código:
 
 ```javascript
 const characters = ['Harry', 'Ron', 'Hermione'];
@@ -17,10 +17,10 @@ characters.splice(1, 1);
 console.log(characters); // Output: ['Harry', 'Hermione']
 ```
 
-The above element removes the second element from the `characters` array. The `splice()` method takes two arguments: the index of the element to remove and the number of elements to remove.
+O elemento acima remove o segundo elemento do array `characters`. O método `splice()` recebe dois argumentos: o índice do elemento a ser removido e o número de elementos a remover.
 
 
-To create a new array with the second element from the `character` array, you can use the following code:
+Para criar um array com o segundo elemento do array `character`, você pode usar o seguinte código:
 
 ```javascript
 const characters = ['Harry', 'Ron', 'Hermione'];
@@ -28,13 +28,13 @@ const newCharacters = characters.slice(1, 2);
 console.log(newCharacters); // Output: ['Ron']
 ```
 
-The above code creates a new array `newCharacters` with the second element from the `characters` array. The `slice()` method takes two arguments: the index of the element to start the slice and the index of the element to end the slice (not included).
+O código acima cria um array `newCharacters` com o segundo elemento do array `characters`. O método `slice()` recebe dois argumentos: o índice do elemento para iniciar o corte e o índice do elemento para terminar o corte (não incluído).
 
 # --question--
 
 ## --text--
 
-What will be the output of the following JavaScript code snippet?
+Qual será a saída do seguinte trecho de código em JavaScript?
 
 
 ```javascript
@@ -48,19 +48,19 @@ console.log(slicedNumbers);
 
 ## --answers--
 
-`numbers` output: `[10, 20, 30, 50]` and `slicedNumbers` output: `[30, 50]`
+Saída de `numbers`: `[10, 20, 30, 50]`. Saída de `slicedNumbers`: `[30, 50]`
 
 ---
 
-`numbers` output: `[10, 20, 30, 40]` and `slicedNumbers` output: `[30, 40]`
+Saída de `numbers`: `[10, 20, 30, 40]`. Saída de `slicedNumbers`: `[30, 40]`
 
 ---
 
-`numbers` output: `[10, 20, 50, 40]` and `slicedNumbers` output: `[20, 50]`
+Saída de `numbers`: `[10, 20, 50, 40]`. Saída de `slicedNumbers`: `[20, 50]`
 
 ---
 
-`numbers` output: `[10, 20, 30, 50, 40]` and `slicedNumbers` output: `[30, 50]`
+Saída de `numbers`: `[10, 20, 30, 50, 40]`. Saída de `slicedNumbers`: `[30, 50]`
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-e.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-e.md
index 28382318c1..1dfe0f83b8 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-e.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-e.md
@@ -1,13 +1,13 @@
 ---
 id: 661e27588602567c118451d5
-title: Learn Arrays and Loops Lesson E
+title: Lição E de Aprenda arrays e laços
 challengeType: 15
 dashedName: learn-arrays-and-loops-lesson-e
 ---
 
 # --description--
 
-Now that you have a basic understanding about arrays, let's talk about loops. Loops are used to execute a block of code multiple times. One of those loops is the `while` loop. The `while` loop executes a block of code as long as the condition is true. The syntax of the `while` loop is as follows:
+Agora que você tem um entendimento básico sobre arrays, vamos falar sobre laços. Laços são usados para executar um bloco de código várias vezes. Um desses laços é o laço `while`. O laço `while` executa um bloco de código enquanto a condição for verdadeira. A sintaxe do laço `while` é a seguinte:
 
 ```javascript
 while (condition) {
@@ -15,7 +15,7 @@ while (condition) {
 }
 ```
 
-For example, the following code snippet prints the numbers from 1 to 5:
+Por exemplo, o seguinte trecho de código imprime os números de 1 a 5:
 
 ```javascript
 let i = 1;
@@ -25,13 +25,13 @@ while (i <= 5) {
 }
 ```
 
-The above code snippet initializes a variable `i` with the value `1`. The `while` loop executes the block of code as long as the value of `i` is less than or equal to `5`. The value of `i` is incremented by `1` in each iteration.
+O trecho de código acima inicializa uma variável `i` com o valor `1`. O laço `while` executa o bloco de código enquanto o valor de `i` for menor ou igual a `5`. O valor de `i` é incrementado em `1` em cada iteração.
 
 # --question--
 
 ## --text--
 
-What will be the output of the following JavaScript code snippet?
+Qual será a saída do seguinte trecho de código JavaScript?
 
 ```javascript
 let i = 5;
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-f.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-f.md
index 3556f1aa5b..30d7083dfa 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-f.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-arrays-and-loops/learn-arrays-and-loops-lesson-f.md
@@ -7,7 +7,7 @@ dashedName: learn-arrays-and-loops-lesson-f
 
 # --description--
 
-The `for` loop is another type of loop that is used to execute a block of code multiple times. The `for` loop is used when the number of iterations is known. The syntax of the `for` loop is as follows:
+O laço `for` é outro tipo de laço usado para executar um bloco de código várias vezes. O laço `for` é usado quando o número de iterações é conhecido. A sintaxe do laço `for` é a seguinte:
 
 ```javascript
 for (initialization; condition; increment/decrement) {
@@ -15,7 +15,7 @@ for (initialization; condition; increment/decrement) {
 }
 ```
 
-For example, the following code snippet prints the numbers from 1 to 5:
+Por exemplo, o seguinte trecho de código imprime os números de 1 a 5:
 
 ```javascript
 for (let i = 1; i <= 5; i++) {
@@ -23,7 +23,7 @@ for (let i = 1; i <= 5; i++) {
 }
 ```
 
-To iterate over an array using a `for` loop, you can use the array's length property. For example, the following code snippet prints the elements of an array:
+Para iterar sobre um array usando um laço `for`, você pode usar a propriedade length do array. Por exemplo, o seguinte trecho de código imprime os elementos de um array:
 
 ```javascript
 const arr = [1, 2, 3, 4, 5];
@@ -36,7 +36,7 @@ for (let i = 0; i < arr.length; i++) {
 
 ## --text--
 
-What will be the output of the following JavaScript code snippet?
+Qual será a saída do seguinte trecho de código JavaScript?
 
 ```javascript
 const items = ['apple', 'banana', 'cherry', 'date'];
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
index c61646de36..904a46be25 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
@@ -9,12 +9,12 @@ dashedName: learn-block-and-inline-lesson-b
 
 Elementos inline, no entanto, não começam em uma nova linha. Eles aparecem na linha com quaisquer elementos ao lado dos quais são colocados. Um exemplo claro de um elemento inline é um link, ou tag `<a>`. Se você inserir um desses no meio de um parágrafo de texto, ele se comportará como parte do parágrafo. <a  href="https://www.freecodecamp.org/" target="_blank">(assim)</a> O texto do link ficará ao lado de outras palavras nesse parágrafo. Além disso, padding e margem se comportam de maneira diferente em elementos inline. Em geral, você não deve tentar adicionar padding ou margem extra em elementos inline.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Procure na web uma lista de elementos `block` e uma lista de elementos `inline`.
 
+# --question--
+
 ## --text--
 
 Qual é a diferença entre um elemento `block` e um elemento `inline`?
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-d.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-d.md
index 948f34ccd1..2ea301d885 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-d.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-d.md
@@ -7,29 +7,29 @@ dashedName: learn-block-and-inline-lesson-d
 
 # --description--
 
-Now that you have a basic understanding on how adding width and height to `inline` elements works, what happens when you add a top margin to an `inline` element?
+Agora que você tem uma compreensão básica de como adicionar largura e altura a elementos `inline` funciona, o que acontece quando você adiciona uma margem superior a um elemento `inline`?
 
 # --question--
 
 ## --text--
 
-How does `margin-top` affect `inline` elements?
+Como `margin-top` afeta elementos `inline`?
 
 ## --answers--
 
-`margin-top` has no impact on the layout of `inline` elements
+`margin-top` não tem impacto no layout de elementos `inline`
 
 ---
 
-`margin-top` increases the height of `inline` elements.
+`margin-top` aumenta a altura dos elementos `inline`.
 
 ---
 
-`margin-top` adds space above the `inline` element.
+`margin-top` adiciona espaço acima do elemento `inline`.
 
 ---
 
-`margin-top` only affects the horizontal spacing of `inline` elements.
+`margin-top` afeta apenas o espaçamento horizontal de elementos `inline`.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-e.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-e.md
index edd07ca149..ec9f5efd1d 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-e.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-e.md
@@ -1,35 +1,35 @@
 ---
 id: 6570447fe7b02272663824e3
-title: Learn Block and Inline Lesson E
+title: Lição E de Aprenda sobre block e inline
 challengeType: 15
 dashedName: learn-block-and-inline-lesson-e
 ---
 
 # --description--
 
-Inline-block elements behave like inline elements, but with block-style padding and margin. `display: inline-block` is a useful tool to know about, but in practice, you'll probably end up reaching for flexbox more often if you're trying to line up a bunch of boxes. Flexbox will be covered in-depth in the next lesson.
+Elementos de inline-block se comportam como elementos inline, mas com preenchimento e margem em estilo de bloco. `display: inline-block` é uma ferramenta útil de se conhecer, mas na prática, você provavelmente acabará recorrendo ao flexbox com mais frequência se estiver tentando alinhar um monte de caixas. Flexbox será tratado em mais detalhes na próxima lição.
 
 # --question--
 
 ## --text--
 
-What is the difference between an `inline` element and an `inline-block` element?
+Qual é a diferença entre um elemento `inline` e um elemento `inline-block`?
 
 ## --answers--
 
-`inline` elements are displayed without line breaks, while `inline-block` elements are displayed with line breaks.
+Elementos `inline` são exibidos sem quebras de linha, enquanto elementos `inline-block` são exibidos com quebras de linha.
 
 ---
 
-`inline` elements do not allow setting width and height, while `inline-block` elements allow setting width and height.
+Elementos `inline` não permitem estabelecer largura e altura, enquanto elementos `inline-block` permitem estabelecer largura e altura.
 
 ---
 
-`inline` elements are always positioned horizontally, while `inline-block` elements are positioned vertically.
+Elementos `inline` estão sempre posicionados horizontalmente, enquanto elementos `inline-block` estão posicionados verticalmente.
 
 ---
 
-`inline` elements can contain block-level elements, while `inline-block` elements cannot contain other elements.
+Elementos `inline` podem conter elementos de nível de bloco, enquanto elementos `inline-block` não podem conter outros elementos.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-f.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-f.md
index 4a04c7adaa..1ebb1d8f24 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-f.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-f.md
@@ -7,29 +7,29 @@ dashedName: learn-block-and-inline-lesson-f
 
 # --description--
 
-The concept of “Normal flow” is implied in the box-model resources, but isn’t laid out very specifically. Read <a href="https://developer.mozilla.org/en-US/docs/Learn/CSS/CSS_layout/Normal_Flow" target="_blank">Normal Flow</a> from MDN to make sure you understand how elements lay themselves out by default.
+O conceito de “Fluxo normal” é implícito nos recursos do modelo de caixas, mas não é apresentado de modo muito específico. Leia <a href="https://developer.mozilla.org/en-US/docs/Learn/CSS/CSS_layout/Normal_Flow" target="_blank">Fluxo Normal</a> do MDN para garantir que você compreende como os elementos se dispõem por padrão.
 
 # --question--
 
 ## --text--
 
-What is the "Normal flow" in CSS layouts?
+O que é o "Fluxo normal" em layouts do CSS?
 
 ## --answers--
 
-Normal flow refers to the process of animating elements in a CSS layout.
+Fluxo normal refere-se ao processo de animação de elementos em um layout do CSS.
 
 ---
 
-Normal flow is a CSS property used to control the visibility of elements in a layout.
+Fluxo normal é uma propriedade do CSS usada para controlar a visibilidade dos elementos em um layout.
 
 ---
 
-Normal flow is a CSS rule that defines the order of media queries for responsive design.
+Fluxo normal é uma regra do CSS que define a ordem das media queries para design responsivo.
 
 ---
 
-Normal flow in CSS layouts refers to the default positioning of elements on a webpage.
+Fluxo normal em layouts do CSS refere-se ao posicionamento padrão dos elementos em uma página da web.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
index 1fb356f0bd..a280a254f8 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-block-and-inline-lesson-g
 
 # --description--
 
-Agora que você tem algum entendimento básico de elementos `block` e `inline`, pegue sua lista de elementos `block` e `inline` de algumas perguntas atrás e veja se consegue identificar quais dos elementos a seguir são elementos `block` e quais são elementos `inline`.
+Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
 
 # --question--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-i.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-i.md
index 5c73752ebf..c2399c4508 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-i.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-i.md
@@ -7,25 +7,25 @@ dashedName: learn-block-and-inline-lesson-i
 
 # --description--
 
-You can't talk about `block` and `inline` elements without discussing `div`s and `span`s. All the other HTML elements you have encountered so far give meaning to their content. For example, paragraph elements tell the browser to display the text it contains as a paragraph. Strong elements tell the browser which texts within are important and so on. Yet, `div`s and `span`s give no particular meaning to their content. They are just generic boxes that can contain anything.
+Você não pode falar sobre elementos `block` e `inline` sem discutir `div`s e `span`s. Todos os outros elementos HTML que você encontrou até agora dão significado ao seu conteúdo. Por exemplo, elementos de parágrafo informam ao navegador para exibir o texto que contém como um parágrafo. Elementos strong informam ao navegador quais textos dentro deles são importantes e assim por diante. Ainda assim, `div`s e `span`s não dão nenhum significado particular ao seu conteúdo. Eles são apenas caixas genéricas que podem conter qualquer coisa.
 
 # --question--
 
 ## --text--
 
-What is the primary difference of `span` and `div` elements from other elements?
+Qual é a diferença principal dos elementos `span` e `div` de outros elementos?
 
 ## --answers--
 
-Unlike specific HTML elements that carry inherent meanings, `span` and `div` elements are versatile and are primarily used for styling and layout purposes.
+Ao contrário de elementos do HTML específicos que carregam significados inerentes, os elementos `span` e `div` são versáteis e são usados principalmente para fins de estilo e layout.
 
 ---
 
-`span` and `div` elements do not impart any specific semantic meaning to the content they contain, unlike other HTML elements such as paragraphs or headings.
+Os elementos `span` e `div` não transmitem nenhum significado semântico específico ao conteúdo que contêm, ao contrário de outros elementos HTML, como parágrafos ou cabeçalhos.
 
 ---
 
-`span` and `div` elements are generic containers that allow developers to apply CSS styles and structure content without any particular semantic significance.
+Os elementos `span` e `div` são contêineres genéricos que permitem aos desenvolvedores aplicar estilos CSS e estruturar conteúdo sem qualquer significado semântico particular.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-j.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-j.md
index 5f6cd8f963..f545d0353f 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-j.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-j.md
@@ -1,35 +1,35 @@
 ---
 id: 65704485e7b02272663824e8
-title: Learn Block and Inline Lesson J
+title: Lição J de Aprenda sobre block e inline
 challengeType: 15
 dashedName: learn-block-and-inline-lesson-j
 ---
 
 # --description--
 
-Now that you have a basic understanding on how adding width and height to `inline` elements works, what happens when you add a top padding of 10 pixels to a `span` element?
+Agora que você tem um entendimento básico de como adicionar largura e altura a elementos `inline` funciona, o que acontece quando você adiciona um padding superior de 10 pixels a um elemento `span`?
 
 # --question--
 
 ## --text--
 
-What happens when you add `padding-top: 10px;` to a `span` element?
+O que acontece quando você adiciona `padding-top: 10px;` a um elemento `span`?
 
 ## --answers--
 
-The `span` element's content will shift downward by 10 pixels.
+O conteúdo do elemento `span` se moverá para baixo por 10 pixels.
 
 ---
 
-The `span` element will gain additional space above its content.
+O elemento `span` ganhará espaço adicional acima do seu conteúdo.
 
 ---
 
-The `span` element's width will increase by 10 pixels.
+A largura do elemento `span` aumentará em 10 pixels.
 
 ---
 
-Padding has no effect on the layout of a `span` element.
+O padding não tem efeito no layout de um elemento `span`.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-k.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-k.md
index 8a395de16e..37b79b9b72 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-k.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-k.md
@@ -1,35 +1,35 @@
 ---
 id: 65704486e7b02272663824e9
-title: Learn Block and Inline Lesson K
+title: Lição K de Aprenda sobre block e inline
 challengeType: 15
 dashedName: learn-block-and-inline-lesson-k
 ---
 
 # --description--
 
-Now that you have a basic understanding on how adding width and height to `inline` elements works.
+Agora que você tem uma compreensão básica de como adicionar largura e altura aos elementos `inline` funciona.
 
 # --question--
 
 ## --text--
 
-What happens when you add a bottom padding of 15 pixels to a `span` element with display set to `inline-block`?
+O que acontece quando você adiciona um padding inferior de 15 pixels a um elemento `span` com exibição definida como `inline-block`?
 
 ## --answers--
 
-The `span` element's content will shift upward by 15 pixels.
+O conteúdo do elemento `span` será deslocado para cima em 15 pixels.
 
 ---
 
-The `span` element's width will increase by 15 pixels.
+A largura do elemento `span` aumentará em 15 pixels.
 
 ---
 
-The `span` element will gain additional space below its content.
+O elemento `span` ganhará espaço adicional abaixo de seu conteúdo.
 
 ---
 
-Padding has no effect on the layout of an `inline-block` `span` element.
+Padding não tem efeito no layout de um elemento `span` `inline-block`.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-a.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-a.md
index d24d018275..81c02bb299 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-a.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-a.md
@@ -8,7 +8,7 @@ dashedName: css-foundations-lesson-a
 
 # --description--
 
-A type selector (or element selector) will select all elements of the given element type, and the syntax is just the name of the element:
+Um seletor de tipo (ou seletor de elemento) selecionará todos os elementos do tipo de elemento dado. A sintaxe é apenas o nome do elemento:
 
 ```html
 <!-- index.html -->
@@ -27,25 +27,25 @@ div {
 }
 ```
 
-Here, all three `<div>` elements would be selected, while the `<p>` element wouldn’t be.
+Aqui, todos os três elementos `<div>` seriam selecionados, enquanto o elemento `<p>` não seria.
 
 # --question--
 
 ## --text--
 
-Which of the following best describes the CSS code given above?
+Qual das seguintes opções melhor descreve o código em CSS fornecido acima?
 
 ## --answers--
 
-The code applies a `white` color to all elements in the HTML file.
+O código aplica uma cor `white` a todos os elementos do arquivo HTML.
 
 ---
 
-The code applies a `white` color to all `div` elements in the HTML file.
+O código aplica uma cor `white` a todos os elementos `div` do arquivo HTML.
 
 ---
 
-The code applies a `white` color to all `p` elements in the HTML file.
+O código aplica uma cor `white` a todos os elementos `p` do arquivo HTML.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-d.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-d.md
index 9dc6044c89..09684c76e9 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-d.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-d.md
@@ -1,14 +1,14 @@
 ---
 id: 63ee35300d8d4841c3a7091d
 videoId: LGQuIIv2RVA
-title: CSS Foundations Lesson D
+title: Lição D sobre Fundamentos de CSS
 challengeType: 15
 dashedName: css-foundations-lesson-d
 ---
 
 # --description--
 
-Another way to use selectors is to chain them as a list without any separation. Let’s say you had the following HTML:
+Outra forma de usar seletores é encadeá-los como uma lista sem separação. Vamos dizer que você tem o seguinte HTML:
 
 ```html
 <div>
@@ -17,7 +17,7 @@ Another way to use selectors is to chain them as a list without any separation.
 </div>
 ```
 
-You have two elements with the `subsection` class that have some sort of unique styles, but what if you only want to apply a separate rule to the element that also has `header` as a second class? Well, you could chain both the `class` selectors together in your CSS like so:
+Você tem dois elementos com a classe `subsection` que têm algum tipo de estilo único, mas o que você pode fazer se quiser apenas aplicar uma regra separada para o elemento que também tem `header` como uma segunda classe? Bem, você pode encadear ambos os seletores `class` no CSS assim:
 
 ```css
 .subsection.header {
@@ -25,9 +25,9 @@ You have two elements with the `subsection` class that have some sort of unique
 }
 ```
 
-What `.subsection.header` does is it selects any element that has both the `subsection` and `header` classes. Notice how there isn’t any space between the `.subsection` and `.header` `class` selectors. This syntax basically works for chaining any combination of selectors, except for chaining more than one type selector.
+O que `.subsection.header` faz é selecionar qualquer elemento que tenha as classes `subsection` e `header`. Observe como não há espaço entre os seletores `class` `.subsection` e `.header`. Essa sintaxe basicamente funciona para encadear qualquer combinação de seletores, exceto para encadear mais de um seletor de tipos.
 
-This can also be used to chain a class and an ID, as shown below:
+Isso também pode ser usado para encadear uma classe e um id, como mostrado abaixo:
 
 ```html
 <div>
@@ -36,7 +36,7 @@ This can also be used to chain a class and an ID, as shown below:
 </div>
 ```
 
-You can take the two elements above and combine them with the following:
+Você pode pegar os dois elementos acima e combiná-los assim:
 
 ```css
 .subsection.header {
@@ -48,13 +48,13 @@ You can take the two elements above and combine them with the following:
 }
 ```
 
-In general, you can’t chain more than one type selector since an element can’t be two different types at once. For example, chaining two type selectors like `div` and `p` would give us the selector `divp`, which wouldn’t work since the selector would try to find a literal `<divp>` element, which doesn’t exist.
+Geralmente, você não pode encadear mais de um tipo de seletor, já que um elemento não pode ter dois tipos diferentes de uma vez. Por exemplo, encadear dois seletores de tipo como `div` e `p` nos daria o seletor `divp`, que não funcionaria porque o seletor tentaria encontrar um elemento literal, `<divp>`, que não existe.
 
 # --question--
 
 ## --text--
 
-Given an element that has an `id` of `title` and a `class` of `primary`, how would you use both attributes for a single rule?
+Dado o elemento que tem um `id` `title` e uma `class` `primary`, como você usaria os dois atributos em uma única regra?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-e.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-e.md
index f813f0f3f4..77b57c8c94 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-e.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-e.md
@@ -1,16 +1,16 @@
 ---
 id: 63ee35370d8d4841c3a7091e
 videoId: LGQuIIv2RVA
-title: CSS Foundations Lesson E
+title: Lição E de Fundamentos de CSS
 challengeType: 15
 dashedName: css-foundations-lesson-e
 ---
 
 # --description--
 
-Combinators allow us to combine multiple selectors differently than either grouping or chaining them, as they show a relationship between the selectors. There are four types of combinators in total, but for right now we’re going to only show you the descendant combinator, which is represented in CSS by a single space between selectors. A descendant combinator will only cause elements that match the last selector to be selected if they also have an ancestor (parent, grandparent, etc) that matches the previous selector.
+Combinadores nos permitem combinar vários seletores de modo diferente do que por agrupamento ou encadeamento, pois mostram uma relação entre os seletores. Existem quatro tipos de combinadores no total, mas, por enquanto, mostraremos apenas o combinador descendente, que é representado no CSS por um espaço único entre seletores. Um combinador de descendente fará com que elementos que coincidam com o último seletor sejam selecionados se também tiverem um ancestral (pai, avô etc.) que corresponda ao seletor anterior.
 
-So something like `.ancestor .child` would select an element with the class `child` if it has an ancestor with the class `ancestor`. Another way to think of it is child will only be selected if it is nested inside of `ancestor`, no matter how deep. Take a quick look at the example below and see if you can tell which elements would be selected based on the CSS rule provided:
+Então, algo como `.ancestor .child` selecionaria um elemento com a classe `child` se tiver um ancestral com a classe `ancestor`. Outro modo de pensar isso é imaginar que o filho só será selecionado se estiver aninhado dentro do `ancestor`, não importando o nível de aninhamento dentro desse ancestral. Dê uma olhada rápida no exemplo abaixo e veja se pode dizer quais elementos serão selecionados com base na regra de CSS fornecida:
 
 ```html
 <!-- index.html -->
@@ -33,27 +33,27 @@ So something like `.ancestor .child` would select an element with the class `chi
 }
 ```
 
-In the above example, the first two elements with the `contents` class (`B` and `C`) would be selected, but that last element (`D`) won’t be. Was your guess correct?
+No exemplo acima, os dois primeiros elementos com a classe `contents` (`B` e `C`) seriam selecionados, mas o último elemento (`D`) não seria. Seu palpite estava correto?
 
-There’s really no limit to how many combinators you can add to a rule, so `.one .two .three .four` would be totally valid. This would just select an element that has a class of `four` if it has an ancestor with a class of `three`, and if that ancestor has its own ancestor with a class of `two`, and so on. You generally want to avoid trying to select elements that need this level of nesting, though, as it can get pretty confusing and long, and it can cause issues when it comes to specificity.
+Não há limite para quantos combinadores você pode adicionar a uma regra. `.one .two .three .four` seria totalmente válido. Isso apenas selecionaria um elemento que tem uma classe `four` se tiver um ancestral com uma classe de `three` e se aquele ancestral tiver seu próprio ancestral com a classe `two` e assim por diante. No entanto, você geralmente vai quer evitar tentar selecionar elementos que precisam deste nível de aninhamento, pois pode ficar muito confuso e longo, além de causar problemas quando se trata de especificidade.
 
 # --question--
 
 ## --text--
 
-What does the descendant combinator do?
+O que faz o combinador de descendente?
 
 ## --answers--
 
-It groups certain classes together which share the same declarations.
+Ele agrupa certas classes que partilhem das mesmas declarações.
 
 ---
 
-It gives the ability to select an element that shares the same `class` and `id`.
+Ele dá a capacidade de selecionar um elemento que compartilhe a mesma `class` e o mesmo `id`.
 
 ---
 
-It allows you to select an element based on its relationship with its ancestor (parent, grandparent, and so on).
+Ele permite selecionar um elemento com base na sua relação com seu ancestral (pai, avô e assim por diante).
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-f.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-f.md
index 512036b1ab..71232a9a6c 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-f.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-f.md
@@ -1,45 +1,45 @@
 ---
 id: 63ee353e0d8d4841c3a7091f
 videoId: LGQuIIv2RVA
-title: CSS Foundations Lesson F
+title: Lição F sobre Fundamentos de CSS
 challengeType: 15
 dashedName: css-foundations-lesson-f
 ---
 
 # --description--
 
-Okay, you went over quite a bit so far. The only thing left for now is to go over how to add all this CSS to your HTML. There are three methods to do so.
+Tudo bem, você já passou por um bocado até aqui. A única coisa que falta por enquanto é ver como adicionar esse CSS ao HTML. Existem três métodos para se fazer isso.
 
-External CSS is the most common method you will come across, and it involves creating a separate file for the CSS and linking it inside of an HTML’s opening and closing `<head>` tags with a self-closing `<link>` element:
+O CSS externo é o método mais comum que você encontrará. Ele envolve a criação de um arquivo separado para o CSS e a vinculação desse arquivo dentro das tags de abertura e fechamento de um elemento `<head>` do HTML na forma de um elemento `<link>` de fechamento próprio:
 
-First, you add a self-closing `<link>` element inside of the opening and closing `<head>` tags of the HTML file. The `href` attribute is the location of the CSS file, either an absolute URL or, what you’ll be utilizing, a URL relative to the location of the HTML file. In the example above, you are assuming both files are located in the same directory. The `rel` attribute is required, and it specifies the relationship between the HTML file and the linked file.
+Primeiro, você adiciona um elemento `<link>` de fechamento próprio dentro das tags de abertura e fechamento de `<head>` do arquivo HTML. O atributo `href` é o local do arquivo CSS, que pode ser um URL absoluto ou um URL relativo à localização do arquivo HTML (você usará essa última opção). No exemplo acima, você está assumindo que ambos os arquivos estão localizados no mesmo diretório. O atributo `rel` é necessário e especifica a relação entre o arquivo HTML e o arquivo vinculado.
 
-Then inside of the newly created `styles.css` file, you have the selector (the `div` and `p`), followed by a pair of opening and closing curly braces, which create a “declaration block”. Finally, you place any declarations inside of the declaration block. `color: white;` is one declaration, with `color` being the property and `white` being the value, and `background-color: black;` is another declaration.
+Então, dentro do arquivo de estilos recém-criado `styles.css`, você tem o seletor (`div` e `p`), seguido por um par de chaves de abertura e de fechamento, que criam um "bloco de declaração". Por fim, colocamos as declarações dentro do bloco da declaração. `color: white;` é uma declaração, com `color` sendo a propriedade e `white` o valor. `background-color: black;` é outra declaração.
 
-A note on file names: `styles.css` is just what you went with as the file name here. You can name the file whatever you want as long as the file type is `.css`, though “style” or “styles” is most commonly used.
+Uma observação sobre os nomes dos arquivos: `styles.css` é simplesmente um nome escolhido como nome do arquivo aqui. Você pode nomear o arquivo como quiser, desde que o tipo de arquivo seja `.css`. No entanto, "style" ou "styles" é o nome mais comumente usado.
 
-A couple of the pros to this method are:
+Algumas das vantagens desse método são:
 
-1. It keeps your HTML and CSS separated, which results in the HTML file being smaller and making things look cleaner.
-2. You only need to edit the CSS in one place, which is especially handy for websites with many pages that all share similar styles.
+1. Ele mantém o HTML e o CSS separados, fazendo com que o arquivo HTML seja menor e mais limpo.
+2. Você só precisa editar o CSS em um lugar, o que é especialmente útil para sites com muitas páginas e que compartilham estilos semelhantes.
 
 # --question--
 
 ## --text--
 
-Which of the following best describes the purpose of the `rel` attribute in the `<link>` element when linking an external CSS file to an HTML file?
+Qual das opções a seguir melhor descreve a finalidade do atributo `rel` no elemento `<link>` ao vincular um arquivo CSS externo a um arquivo HTML?
 
 ## --answers--
 
-It specifies the location of the CSS file relative to the location of the HTML file.
+Ele especifica o local do arquivo do CSS com relação ao local do arquivo do HTML.
 
 ---
 
-It specifies the relationship between the HTML file and the linked file.
+Ele mostra a relação entre o arquivo do HTML e o documento vinculado.
 
 ---
 
-It specifies the type of file being linked (e.g. "stylesheet").
+Ele especifica o tipo de arquivo que está sendo vinculado (por exemplo, "stylesheet" – ou folha de estilos).
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-g.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-g.md
index d31beea7a9..7ec9bfaf03 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-g.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-foundations/css-foundations-lesson-g.md
@@ -1,16 +1,16 @@
 ---
 id: 63ee35450d8d4841c3a70920
 videoId: LGQuIIv2RVA
-title: CSS Foundations Lesson G
+title: Lição G sobre Fundamentos de CSS
 challengeType: 15
 dashedName: css-foundations-lesson-g
 ---
 
 # --description--
 
-Internal CSS (or embedded CSS) involves adding the CSS within the HTML file itself instead of creating a completely separate file. With the internal method, you place all the rules inside of a pair of opening and closing `<style>` tags, which are then placed inside of the opening and closing `<head>` tags of your HTML file. Since the styles are being placed directly inside of the `<head>` tags, you no longer need a `<link>` element that the external method requires.
+CSS interno (ou CSS incorporado) envolve adicionar o CSS no próprio arquivo HTML em vez de criar um arquivo completamente separado. Com o método interno, você coloca todas as regras dentro de um par de tags `<style>`, de abertura e de fechamento, que são então colocadas dentro das tags de abertura e de fechamento de `<head>` do seu arquivo HTML. Como os estilos estão sendo colocados diretamente dentro das tags `<head>`, você não precisa mais de um elemento `<link>`, exigido pelo método externo.
 
-Besides these differences, the syntax is exactly the same as the external method (selector, curly braces, declarations):
+Apesar dessas diferenças, a sintaxe é exatamente a mesma que a do método externo (seletor, chaves, declarações):
 
 ```html
 <head>
@@ -28,25 +28,25 @@ Besides these differences, the syntax is exactly the same as the external method
 <body>...</body>
 ```
 
-This method can be useful for adding unique styles to a single page of a website, but it doesn’t keep things separate like the external method, and depending on how many rules and declarations there are it can cause the HTML file to get pretty big.
+Esse método pode ser útil para adicionar estilos exclusivos a uma página em um site, mas não mantém as responsabilidades separadas como o método externo. Dependendo de quantas regras e declarações existam, isso pode fazer com que o arquivo HTML fique muito grande.
 
 # --question--
 
 ## --text--
 
-Which of the following is a difference between internal and external CSS methods?
+Qual das seguintes opções é uma diferença entre os métodos interno e externo do CSS?
 
 ## --answers--
 
-The external method places CSS rules in a separate file, while the internal method places CSS rules within the HTML file itself.
+O método externo coloca as regras do CSS em um arquivo separado, enquanto o método interno coloca as regras do CSS dentro do próprio arquivo HTML.
 
 ---
 
-The internal method keeps CSS separate from HTML, while the external method embeds CSS directly in HTML.
+O método interno mantém o CSS separado do HTML, enquanto o método externo incorpora o CSS diretamente no HTML.
 
 ---
 
-The internal method uses `<link>` element to link CSS to HTML, while the external method embeds CSS directly in HTML.
+O método interno usa o elemento `<link>` para vincular o CSS ao HTML, enquanto o método externo incorpora o CSS diretamente no HTML.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-a.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-a.md
index 2e292c446f..78a7a5f018 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-a.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-a.md
@@ -1,38 +1,38 @@
 ---
 id: 6489bcd7b7600c818dc297ea
-title: The Cascade of CSS Lesson A
+title: Lição A sobre a cascata do CSS
 challengeType: 15
 dashedName: the-cascade-of-css-lesson-a
 ---
 
 # --description--
 
-Sometimes we may have rules that conflict with one another, and we end up with some unexpected results. “But I wanted these paragraphs to be blue, why are they red like these other paragraphs?!” As frustrating as this can be, it’s important to understand that CSS doesn’t just do things against your wishes. CSS only does what we tell it to do. One exception to this is the default styles that are provided by a browser. These default styles vary from browser to browser, and they are why some elements create a large “gap” between themselves and other elements, or why buttons look the way they do, despite us not writing any CSS rules to style them that way.
+Por vezes, podemos ter regras que entram em conflito umas com as outras e acabamos obtendo resultados inesperados. "Mas eu queria que esses parágrafos ficassem azuis. Por que eles estão vermelhos como os outros parágrafos?!" Por mais frustrante que isso possa ser, é importante entender que o CSS não faz as coisas apenas contra seus desejos. O CSS faz apenas o que dizemos para ele fazer. Uma exceção para isso são os estilos padrão fornecidos por um navegador. Esses estilos padrão variam de navegador para navegador. São o motivo pelo qual alguns elementos criam uma grande "lacuna" entre eles mesmos e outros elementos, ou pelo qual os botões têm a aparência que têm, apesar de não escrevermos quaisquer regras do CSS para estilizá-los desse modo.
 
-So if you end up with some unexpected behavior like this it’s either because of these default styles, not understanding how a property works, or not understanding this little thing called the cascade.
+Então, se você acabar com algum comportamento inesperado como esse, pode ser por causa desses estilos padrão, por não entender como funciona uma propriedade ou por não entender essa questão chamada de "cascata".
 
-The cascade is what determines which rules actually get applied to your HTML. There are different factors that the cascade uses to determine this. We will examine three of these factors, which will hopefully help you avoid those frustrating “I hate CSS” moments.
+A cascata é o que determina quais regras realmente são aplicadas ao seu HTML. Há diferentes fatores que a cascata usa para determinar isso. Examinaremos três desses fatores, o que acreditamos que ajudará você a evitar aqueles momentos frustrantes do tipo "Odeio o CSS".
 
 # --question--
 ## --text--
 
-Why might you encounter unexpected behavior in CSS?
+Por que você pode encontrar comportamentos inesperados no CSS?
 
 ## --answers--
 
-Due to conflicting rules and unexpected results
+Devido a regras conflitantes e resultados inesperados
 
 ---
 
-Due to the browser's default styles
+Devido aos estilos padrão do navegador
 
 ---
 
-Due to a lack of understanding of CSS properties
+Devido a uma falta de compreensão das propriedades do CSS
 
 ---
 
-All of the above
+Todas as anteriores
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-e.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-e.md
index b7608df509..1ab937b7da 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-e.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-e.md
@@ -1,6 +1,6 @@
 ---
 id: 6489cf6282cf2e4f86f03ae6
-title: The Cascade of CSS Lesson E
+title: Lição E sobre a cascata do CSS
 challengeType: 15
 dashedName: the-cascade-of-css-lesson-e
 ---
@@ -20,31 +20,31 @@ dashedName: the-cascade-of-css-lesson-e
 }
 ```
 
-In this final example, both rules are using ID and class selectors, so neither rule is using a more specific selector than the other. The cascade then checks the amounts of each selector type. Both rules only have one ID selector, but rule 2 has more class selectors, so rule 2 has a higher specificity!
+Neste exemplo final, as duas regras estão usando seletores de ID e de classe. Portanto, nenhuma regra está usando um seletor mais específico que a outra. A cascata, então, verifica as quantidades de cada tipo de seletor. As duas regras só têm um seletor de ID, mas a regra 2 tem mais seletores de classe, então a regra 2 tem uma especificidade superior!
 
-While the `color: red` declaration would take precedence, the `background-color: yellow` declaration would still be applied since there’s no conflicting declaration for it.
+Embora a declaração de `color: red` tenha precedência, a declaração de `background-color: yellow` ainda será aplicada, pois não há nenhuma declaração conflitante para ela.
 
 # --question--
 
 ## --text--
 
-Considering the updated CSS code, which of the following describes the rendering of the `<div class="list" id="subsection"></div>` element?
+Considerando o código em CSS atualizado, qual das afirmações abaixo descreve a renderização do elemento `<div class="list" id="subsection"></div>`?
 
 ## --answers--
 
-Text color: Red, Background color: Transparent
+Cor do texto: vermelho; cor de fundo: transparente
 
 ---
 
-Text color: Red, Background color: Yellow
+Cor do texto: vermelho; cor de fundo: amarelo
 
 ---
 
-Text color: Blue, Background color: Transparent
+Cor do texto: azul; cor de fundo: transparente
 
 ---
 
-Text color: Blue, Background color: Yellow
+Cor do texto: azul; cor de fundo: amarelo
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-f.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-f.md
index 97c78768eb..b1abc2e3e4 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-f.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-f.md
@@ -1,6 +1,6 @@
 ---
 id: 6489cf6782cf2e4f86f03ae7
-title: The Cascade of CSS Lesson F
+title: Lição F sobre a cascata do CSS
 challengeType: 15
 dashedName: the-cascade-of-css-lesson-f
 ---
@@ -19,7 +19,7 @@ dashedName: the-cascade-of-css-lesson-f
 }
 ```
 
-Here both rule 1 and rule 2 have the same specificity. Rule 1 uses a chaining selector (no space) and rule 2 uses a descendant combinator (the empty space). But both rules have two classes and the combinator symbol itself does not add to the specificity.
+Aqui, a regra 1 e a regra 2 têm a mesma especificidade. A regra 1 usa um seletor de encadeamento (sem espaço) e a regra 2 usa um combinador descendente (o espaço vazio). As duas regras, no entanto, têm duas classes e o símbolo do combinador em si não aumenta a especificidade.
 
 ```css
 /* rule 1 */
@@ -32,15 +32,15 @@ Here both rule 1 and rule 2 have the same specificity. Rule 1 uses a chaining se
 }
 ```
 
-This example shows the same thing. Even though rule 2 is using a child combinator (`>`), this does not change the specificity value. Both rules still have two classes so they have the same specificity values.
+Este exemplo mostra a mesma coisa. Mesmo que a regra 2 esteja usando um combinador de filhos (`>`), ele não altera o valor de especificidade. As duas regras ainda têm duas classes. Por isso, elas têm os mesmos valores de especificidade.
 
-*Note:* Not everything adds to specificity When comparing selectors, you may come across special symbols for the universal selector (`*`) as well as combinators (`+`, `~`, `>`, and an empty space). These symbols do not add any specificity in and of themselves.
+*Observação:* nem tudo adiciona especificidade. Ao comparar seletores, você pode encontrar símbolos especiais para o seletor universal (`*`), bem como os combinadores (`+`, `~`, `>` e o espaço vazio). Esses símbolos não adicionam nenhuma especificidade por eles mesmos.
 
 # --question--
 
 ## --text--
 
-Based on the given CSS code, which font size would be applied to elements with the class "class second-class"?
+Com base no código CSS dado, qual tamanho de fonte seria aplicado aos elementos com as classes "class second-class"?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-g.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-g.md
index ef09942a73..17b27771a0 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-g.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-css-specificity/the-cascade-of-css-lesson-g.md
@@ -1,15 +1,15 @@
 ---
 id: 6489cf7682cf2e4f86f03ae8
-title: The Cascade of CSS Lesson G
+title: Lição G sobre a cascata do CSS
 challengeType: 15
 dashedName: the-cascade-of-css-lesson-g
 ---
 
 # --description--
 
-Inheritance refers to certain CSS properties that, when applied to an element, are inherited by that element’s descendants, even if we don’t explicitly write a rule for those descendants. Typography based properties (`color`, `font-size`, `font-family`, etc.) are usually inherited, while most other properties aren’t.
+A herança se refere a certas propriedades do CSS que, quando aplicadas a um elemento, são herdados pelos descendentes desse elemento, mesmo se não escrevermos explicitamente uma regra para esses descendentes. Propriedades baseadas em tipografia (`color`, `font-size`, `font-family`, entre outras) são geralmente herdadas, enquanto a maioria das outras propriedades não é.
 
-The exception to this is when directly targeting an element, as this always beats inheritance:
+A exceção a isso é quando se tem um elemento como alvo diretamente, já que isso sempre vence a herança:
 
 ```html
 <!-- index.html -->
@@ -31,29 +31,29 @@ The exception to this is when directly targeting an element, as this always beat
 }
 ```
 
-Despite the `parent` element having a higher specificity with an ID, the `child` element would have the `color: blue` style applied since that declaration directly targets it, while `color: red` from the parent is only inherited.
+Apesar do elemento `parent` (pai) ter uma especificidade maior com um ID, o elemento `child` (filho) terá o estilo `color: blue` aplicado, pois essa declaração o tem como alvo diretamente, enquanto o estilo `color: red` do pai é apenas herdado.
 
 # --question--
 
 ## --text--
 
-Based on the given HTML and CSS code, what would be the color of the `<div class="child"></div>` element?
+Com base nos códigos HTML e CSS fornecidos, qual seria a cor do elemento `<div class="child"></div>`?
 
 ## --answers--
 
-Red
+Vermelho
 
 ---
 
-Blue
+Azul
 
 ---
 
-Inherited from the parent element
+Herdada do elemento pai
 
 ---
 
-Transparent
+Transparente
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-a.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-a.md
index 48136d7011..8501c6712f 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-a.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-a.md
@@ -1,17 +1,17 @@
 ---
 id: 65e9713d484dd50f720e6fe6
-title: Learn Data Types and Conditionals Lesson A
+title: Lição A de Aprenda tipos de dados e condicionais
 challengeType: 15
 dashedName: learn-data-types-and-conditionals-lesson-a
 ---
 
 # --description--
 
-Depending on what kind of work you're doing, you might end up working more with pieces of text rather than numbers. A **string** is a piece of text… and is a fundamental building block of the language.
+Dependendo do tipo de trabalho que você está fazendo, você pode acabar trabalhando mais com trechos de texto em vez de números. Uma **string** é um trecho de texto... e é um bloco de construção fundamental da linguagem.
 
-HTML provides structure and meaning to text, CSS allows us to precisely style it, and JavaScript offers many features for manipulating strings. These include creating custom welcome messages and prompts, showing the right text labels when needed, sorting terms into the desired order, and much more.
+O HTML fornece estrutura e significado ao texto, o CSS nos permite estilizá-lo com precisão e o JavaScript oferece muitos recursos para manipulação de strings. Isso inclui criar mensagens de boas-vindas personalizadas e prompts, mostrar os rótulos de texto corretos quando necessário, classificar termos na ordem desejada e muito mais.
 
-Strings are a fundamental data type in JavaScript. They are used to represent text and are wrapped in either single, double quotes or backticks:
+Strings são um tipo de dado fundamental em JavaScript. Elas são usadas para representar texto e são envoltas em aspas simples, duplas ou crases:
 
 ```javascript
 let greeting = "Hello World!";
@@ -21,29 +21,29 @@ let greeting2 = 'I am learning JavaScript!';
 let greeting3 = `with The Odin Project!`;
 ```
 
-Strings declared using single quotes and strings declared using double quotes are the same, and which you use is down to personal preference — although it is good practice to choose one style and use it consistently in your code.
+Strings declaradas usando aspas simples e strings declaradas usando aspas duplas produzem o mesmo resultado. O tipo de aspas que você usará dependerá de sua preferência pessoal — embora seja uma boa prática escolher um estilo e usá-lo consistentemente no seu código.
 
 # --assignment--
 
-There are many ways to manipulate strings in JavaScript. Go through points 8 through 12 of our <a href="https://www.freecodecamp.org/news/javascript-string-handbook/" target="_blank">JavaScript String Handbook</a>
+Há muitas maneiras de se manipular strings em JavaScript. Passe pelos pontos 8 a 12 do nosso <a href="https://www.freecodecamp.org/news/javascript-string-handbook/" target="_blank">JavaScript String Handbook</a>
 
 # --question--
 
 ## --text--
 
-Which statement accurately describes the versatility and use of strings in JavaScript in conjunction with HTML, CSS, and JavaScript itself?
+Qual instrução descreve com precisão a versatilidade e o uso de strings em JavaScript em conjunto com HTML, CSS e o próprio JavaScript?
 
 ## --answers--
 
-Strings in JavaScript can only be manipulated using CSS for web page design.
+Strings em JavaScript só podem ser manipuladas usando CSS para design de páginas da web.
 
 ---
 
-JavaScript strings are exclusively used for mathematical computations and cannot interact with HTML or CSS.
+Strings em JavaScript são usadas exclusivamente para cálculos matemáticos e não podem interagir com HTML ou CSS.
 
 ---
 
-Strings allow for text manipulation in JavaScript, including but not limited to creating custom messages, sorting terms, and dynamically updating HTML content with CSS styling.
+Strings permitem a manipulação de texto em JavaScript, incluindo, mas não se limitando a, criar mensagens personalizadas, classificar termos e atualizar dinamicamente o conteúdo HTML com estilo CSS.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-b.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-b.md
index f643bfb007..05f6e8fc56 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-b.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-b.md
@@ -1,15 +1,15 @@
 ---
 id: 65e97164484dd50f720e6fe7
-title: Learn Data Types and Conditionals Lesson B
+title: Lição B de Aprenda tipos de dados e condicionais
 challengeType: 15
 dashedName: learn-data-types-and-conditionals-lesson-b
 ---
 
 # --description--
 
-Now that you have gone through the points listed in the assignment of the previous challenge, you should have a good understanding of how strings can be manipulated in JavaScript.
+Agora que você passou pelos pontos listados na atribuição do desafio anterior, deve ter uma boa compreensão de como strings podem ser manipuladas em JavaScript.
 
-Currently, this given string has a trailing space at the end after the exclamation mark. To solve this, you need to remove the trailing space from the string using a predefined method.
+Atualmente, essa string fornecida tem um espaço à direita no final após o ponto de exclamação. Para resolver isso, você precisa remover o espaço à direita da string usando um método predefinido.
 
 ```javascript
 let greeting = "Hello World!  ";
@@ -17,17 +17,17 @@ let greeting = "Hello World!  ";
 console.log(greeting);
 ```
 
-<a href="https://www.freecodecamp.org/news/javascript-string-handbook" target="_blank"> Link to Guide </a>
+<a href="https://www.freecodecamp.org/news/javascript-string-handbook" target="_blank"> Link para o Guia </a>
 
 # --question--
 
 ## --text--
 
-Following the problem above, which method should be used to only remove the trailing space from the string?
+Seguindo o problema acima, qual método deve ser usado para remover apenas o espaço à direita da string?
 
 ## --answers--
 
-The `trim()` method should be used to only remove the trailing space from the string.
+O método `trim()` deve ser usado para remover apenas o espaço à direita da string.
 
 ---
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-e.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-e.md
index 8ca178a3a3..7be1802172 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-e.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-e.md
@@ -1,15 +1,15 @@
 ---
 id: 65e97260484dd50f720e6fea
-title: Learn Data Types and Conditionals Lesson E
+title: Lição E de Aprenda tipos de dados e condicionais
 challengeType: 15
 dashedName: learn-data-types-and-conditionals-lesson-e
 ---
 
 # --description--
 
-Strings defined using backticks are called template literals. They are a new way to define strings in JavaScript. They allow you to embed expressions within the string. This is done by wrapping the expression in `${}`.
+Strings definidas usando acentos graves (em inglês, backticks) são chamadas de template literals. É uma nova forma de definir strings em JavaScript. Elas permitem que você insira expressões dentro da string. Isso é feito envolvendo a expressão em `${}`.
 
-For example, the following code:
+Por exemplo, o código a seguir:
 
 ```javascript
 let name = "John";
@@ -17,13 +17,13 @@ let age = 25;
 let greeting = `Hello, my name is ${name} and I am ${age} years old.`;
 ```
 
-will result in the `greeting` variable containing the string "Hello, my name is John and I am 25 years old."
+resultará na variável `greeting` com a string "Hello, my name is John and I am 25 years old."
 
 # --question--
 
 ## --text--
 
-Which of the following is the correct way to define a template literal in JavaScript?
+Qual das seguintes é a maneira correta de definir um template literal em JavaScript?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-f.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-f.md
index aecb02987b..0a7768b3f7 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-f.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-f.md
@@ -7,20 +7,20 @@ dashedName: learn-data-types-and-conditionals-lesson-f
 
 # --description--
 
-You know that JavaScript has a variety of data types, including strings, numbers and booleans. You can use comparison operators to compare these data types and make decisions based on the results.
+Você sabe que o JavaScript possui uma variedade de tipos de dados, incluindo strings, números e booleanos. Você pode usar operadores de comparação para comparar esses tipos de dados e tomar decisões baseadas nos resultados.
 
-The following comparison operators are available in JavaScript:
+Os seguintes operadores de comparação estão disponíveis no JavaScript:
 
-| Operator | Description              | Example |
-| -------- | ------------------------ | ------- |
-| ==       | Equal (value comparison) | x == y  |
-| !=       | Not equal                | x != y  |
-| >        | Greater than             | x > y   |
-| <        | Less than                | x < y   |
-| >=       | Greater than or equal to | x >= y  |
-| <=       | Less than or equal to    | x <= y  |
+| Operador | Descrição                   | Exemplo |
+| -------- | --------------------------- | ------- |
+| ==       | Igual (comparação de valor) | x == y  |
+| !=       | Não igual                   | x != y  |
+| >        | Maior que                   | x > y   |
+| <        | Menor que                   | x < y   |
+| >=       | Maior ou igual a            | x >= y  |
+| <=       | Menor ou igual a            | x <= y  |
 
-To use a comparison in a variable assignment, you can use the `==` operator. For example:
+Para usar uma comparação em uma atribuição de variável, você pode usar o operador `==`. Por exemplo:
 
 ```javascript
 let x = 5;
@@ -36,7 +36,7 @@ console.log(result); // true
 
 ## --text--
 
-Which of the following is the correct way to check if the variable `x` is equal to the number `5` in JavaScript?
+Qual das seguintes é a maneira correta de verificar se a variável `x` é igual ao número `5` em JavaScript?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-g.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-g.md
index fb331d483e..acaaa47b49 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-g.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-g.md
@@ -1,13 +1,13 @@
 ---
 id: 65e9726d484dd50f720e6fec
-title: Learn Data Types and Conditionals Lesson G
+title: Lição G de Aprenda tipos de dados e condicionais
 challengeType: 15
 dashedName: learn-data-types-and-conditionals-lesson-g
 ---
 
 # --description--
 
-JavaScript also has the ability to compare types and values using the strict equality operator `===`. This operator checks if the two values are equal and of the same type. For example:
+O JavaScript também tem a capacidade de comparar tipos e valores usando o operador de igualdade estrita `===`. Esse operador verifica se os dois valores são iguais e do mesmo tipo. Por exemplo:
 
 ```javascript
 let x = 5;
@@ -18,35 +18,35 @@ let result = x === y;
 console.log(result); // false
 ```
 
-In this example, the `result` variable will contain `false` because `x` is a number and `y` is a string. But if you use the `==` operator, the result will be `true` because JavaScript will convert the string to a number and compare the values.
+Neste exemplo, a variável `result` conterá `false` porque `x` é um número e `y` é uma string. Se, contudo, você usar o operador `==`, o resultado será `true`, pois o JavaScript converterá a string para um número e comparará os valores.
 
-This operator is called the strict equality operator because it checks for both value and type equality. It is often recommended to use the `===` operator to avoid unexpected results when comparing values.
+Esse operador é chamado de operador de igualdade estrita porque verifica tanto a igualdade de valor quanto de tipo. É frequentemente recomendado usar o operador `===` para evitar resultados inesperados ao comparar valores.
 
-There is also a strict inequality operator `!==` that checks if the two values are not equal and of the same type.
+Há também um operador de desigualdade estrita `!==` que verifica se os dois valores não são iguais e do mesmo tipo.
 
-There are a lot of ways to use the strict equality operator, and it's important to understand how it works.
+Existem muitas maneiras de usar o operador de igualdade estrita, e é importante entender como ele funciona.
 
 # --assignment--
 
-Read <a href="https://javascript.info/comparison" target="_blank" rel="noopener noreferrer nofollow">this article on JavaScript.info</a> to learn more about the strict equality operator.
+Leia <a href="https://javascript.info/comparison" target="_blank" rel="noopener noreferrer nofollow">este artigo em JavaScript.info</a> para aprender mais sobre o operador de igualdade estrita.
 
 # --question--
 
 ## --text--
 
-What happens when you use the strict equality operator `===` to compare a number of the value `0` and a boolean of the value `false`?
+O que acontece quando você usa o operador de igualdade estrita `===` para comparar um número de valor `0` e um booleano de valor `false`?
 
 ## --answers--
 
-The output would be `true`.
+O resultado seria `true`.
 
 ---
 
-The output would be `false`.
+O resultado seria `false`.
 
 ---
 
-You cannot compare a number and a boolean using the strict equality operator.
+Você não pode comparar um número e um booleano usando o operador de igualdade estrita.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-h.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-h.md
index 47131dd400..66a8808331 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-h.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-h.md
@@ -1,17 +1,17 @@
 ---
 id: 65e9727a484dd50f720e6fed
-title: Learn Data Types and Conditionals Lesson H
+title: Lição H de Aprenda tipos de dados e condicionais
 challengeType: 15
 dashedName: learn-data-types-and-conditionals-lesson-h
 ---
 
 # --description--
 
-In any programming language, you need to compare values to make decisions. For example, if the weather is sunny, you will go out, otherwise you will stay at home. Another example would be to see if a user has enough points to level up in a game.
+Em qualquer linguagem de programação, você precisa comparar valores para tomar decisões. Por exemplo, se o tempo está ensolarado, você sairá; caso contrário, ficará em casa. Outro exemplo seria verificar se o usuário tem pontos suficientes para subir de nível em um jogo.
 
-The `if-else` conditional statement is used to make decisions in JavaScript. It is often used with comparison operators to compare values and make decisions based on the results.
+A instrução condicional `if-else` é usada para tomar decisões em JavaScript. Ela é frequentemente usada com operadores de comparação para comparar valores e tomar decisões com base nos resultados.
 
-An example of an if statement is:
+Um exemplo de uma instrução if é:
 
 ```javascript
 let x = 5;
@@ -23,13 +23,13 @@ if (x > 3) {
 }
 ```
 
-In this example, the `x` variable is compared to the number `3` using the `>` operator. If `x` is greater than `3`, the first block of code will be executed. Otherwise, the second block of code will be executed.
+Neste exemplo, a variável `x` é comparada ao número `3` usando o operador `>`. Se `x` for maior que `3`, o primeiro bloco de código será executado. Caso contrário, o segundo bloco de código será executado.
 
 # --question--
 
 ## --text--
 
-What will be the output of the following code?
+Como será a saída do seguinte código?
 
 ```javascript
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-k.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-k.md
index 59af5ee4ad..9ec9bc34fb 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-k.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-k.md
@@ -1,15 +1,15 @@
 ---
 id: 65e9728d484dd50f720e6ff0
-title: Learn Data Types and Conditionals Lesson K
+title: Lição K de Aprenda tipos de dados e condicionais
 challengeType: 15
 dashedName: learn-data-types-and-conditionals-lesson-k
 ---
 
 # --description--
 
-The `switch` statement is used to perform different actions based on different conditions. It is similar to the `if-else` statement, but is more readable and easier to understand when there are multiple conditions to check. The `switch` statement is used to select one of many code blocks to be executed.
+A instrução `switch` é usada para realizar ações diferentes com base em diferentes condições. É semelhante à instrução `if-else`, mas é mais legível e mais fácil de entender quando há várias condições a verificar. A instrução `switch` é usada para selecionar um de muitos blocos de código a serem executados.
 
-The `switch` statement evaluates an expression and compares it with the values of each case. If there is a match, the associated block of code is executed. If there is no match, the default block of code is executed.
+A instrução `switch` avalia uma expressão e a compara com os valores de cada caso. Se houver correspondência, o bloco de código associado é executado. Se não houver correspondência, o bloco de código padrão é executado.
 
 ```javascript
 let day = "Monday";
@@ -41,13 +41,13 @@ switch (day) {
 }
 ```
 
-In the above example, the value of the `day` variable is compared with the values of each case. If there is a match, the associated block of code is executed. If there is no match, the default block of code is executed.
+No exemplo acima, o valor da variável `day` é comparado com os valores de cada caso. Se houver correspondência, o bloco de código associado é executado. Se não houver correspondência, o bloco de código padrão é executado.
 
 # --question--
 
 ## --text--
 
-Given the JavaScript code snippet below, which modifies the `activity` variable based on the day of the week, what will be the value of the `activity` variable if the value of the `day` variable is `"Tuesday"`?
+Dado o trecho de código em JavaScript abaixo, que modifica a variável `activity` com base no dia da semana, qual será o valor da variável `activity` se o valor da variável `day` for `"Tuesday"`?
 
 ```javascript
 let day = "Tuesday";
@@ -83,19 +83,19 @@ switch (day) {
 
 ## --answers--
 
-The value of the `activity` variable will be `"Attend coding meetup"`.
+O valor da variável `activity` será `"Attend coding meetup"`.
 
 ---
 
-The value of the `activity` variable will be `"Watch a movie"`.
+O valor da variável `activity` será `"Watch a movie"`.
 
 ---
 
-The value of the `activity` variable will be `"Undefined day"`.
+O valor da variável `activity` será `"Undefined day"`.
 
 ---
 
-The value of the `activity` variable will be `"Go to the gym"`.
+O valor da variável `activity` será `"Go to the gym"`.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-l.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-l.md
index f17ab8ffd2..546b459a48 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-l.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-data-types-and-conditionals/learn-data-types-and-conditionals-lesson-l.md
@@ -1,27 +1,27 @@
 ---
 id: 65e97293484dd50f720e6ff1
-title: Learn Data Types and Conditionals Lesson L
+title: Lição L de Aprenda tipos de dados e condicionais
 challengeType: 15
 dashedName: learn-data-types-and-conditionals-lesson-l
 ---
 
 # --description--
 
-Another way to compare conditional statements would be the ternary operator. The ternary operator is a shorthand way of writing an `if-else` statement. It is used to evaluate a condition and return a value based on the result of the condition. The syntax of the ternary operator is as follows:
+Outra maneira de comparar instruções condicionais seria o operador ternário. O operador ternário é uma maneira abreviada de escrever uma instrução `if-else`. É usado para avaliar uma condição e retornar um valor com base no resultado da condição. A sintaxe do operador ternário é a seguinte:
 
 ```javascript
 let result = condition ? value1 : value2;
 ```
 
-In the above example, if the condition is true, the value of `result` will be `value1`. Otherwise, the value of `result` will be `value2`.
+No exemplo acima, se a condição for verdadeira, o valor de `result` será `value1`. Caso contrário, o valor de `result` será `value2`.
 
-Ternary operators are often used to assign a value to a variable based on a condition. They are also used to return a value based on a condition.
+Os operadores ternários são frequentemente usados para atribuir um valor a uma variável com base em uma condição. Eles também são usados para retornar um valor com base em uma condição.
 
 # --question--
 
 ## --text--
 
-What is the value of the `result` variable if the value of the `condition` variable is `true`?
+Qual é o valor da variável `result` se o valor da variável `condition` for `true`?
 
 ```javascript
 let condition = true;
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-c.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-c.md
index c64dc5b303..a410d227fd 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-c.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-c.md
@@ -1,13 +1,13 @@
 ---
 id: 6617aee05b87c334e7ae8014
-title: Learn Function Basics Lesson C
+title: Lição C de Aprenda funções básicas
 challengeType: 15
 dashedName: learn-function-basics-lesson-c
 ---
 
 # --description--
 
-A variable declared inside a function is only visible inside a function. This is called the scope of the variable, this particular scope is called the local scope. Variables declared outside of a function are called global variables and are visible throughout the program. For example, the following code will raise an error:
+Uma variável declarada dentro de uma função é visível apenas dentro de uma função. Isso é chamado de escopo da variável. Esse escopo em particular é chamado de escopo local. Variáveis declaradas fora de uma função são chamadas variáveis globais e são visíveis em todo o programa. Por exemplo, o código a seguir mostrará um erro:
 
 ```js
 function myFunction() {
@@ -17,9 +17,9 @@ function myFunction() {
 console.log(x);
 ```
 
-The variable `x` is declared inside the function `myFunction` and is not visible outside of the function. The code will raise a `ReferenceError` because `x` is not defined.
+A variável `x` é declarada dentro da função `myFunction` e não é visível fora da função. O código mostrará um `ReferenceError` porque `x` não está definido.
 
-If you declare a variable outside of a function, it is called a global variable and is visible throughout the program. For example, the following code will work:
+Se você declarar uma variável fora de uma função, ela é chamada de variável global e é visível em todo o programa. Por exemplo, o código a seguir funcionará:
 
 ```js
 let x = 10;
@@ -31,13 +31,13 @@ function myFunction() {
 myFunction();
 ```
 
-If a same-named variable is declared inside the function then it shadows the outer one.
+Se uma variável com o mesmo nome for declarada dentro da função, ela anulará a variável externa dentro da função.
 
 # --question--
 
 ## --text--
 
-What will be the output of the following code?
+Qual será a saída do seguinte código?
 
 ```js
 let x = 10;
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-d.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-d.md
index 39f0c73af6..f31844fab9 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-d.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-d.md
@@ -1,13 +1,13 @@
 ---
 id: 6617aee95b87c334e7ae8015
-title: Learn Function Basics Lesson D
+title: Lição D de Aprenda funções básicas
 challengeType: 15
 dashedName: learn-function-basics-lesson-d
 ---
 
 # --description--
 
-If a function is called, but an argument is not provided, then the parameter will be assigned the value of `undefined`. This can lead to unexpected results if the function is not designed to handle this case.
+Se uma função é chamada, mas um argumento não é fornecido, então o parâmetro receberá o valor `undefined`. Isso pode levar a resultados inesperados se a função não estiver projetada para lidar com esse caso.
 
 ```js
 function favoriteAnimal(animal) {
@@ -17,9 +17,9 @@ function favoriteAnimal(animal) {
 console.log(favoriteAnimal()); // Output: undefined is my favorite animal!
 ```
 
-In the example above, the function `favoriteAnimal` is called without an argument. The parameter `animal` is assigned the value of `undefined`, which is then concatenated with the string `" is my favorite animal!"`.
+No exemplo acima, a função `favoriteAnimal` é chamada sem um argumento. O parâmetro `animal` recebe o valor de `undefined`, que é então concatenado com a string `" is my favorite animal!"`.
 
-If a value is not provided you can make use of default parameters. Default parameters allow you to assign a default value to a parameter if no value is provided when the function is called.
+Se um valor não for fornecido, você pode fazer uso de parâmetros padrão. Parâmetros padrão permitem que você atribua um valor padrão a um parâmetro se nenhum valor for fornecido quando a função é chamada.
 
 ```js
 function favoriteAnimal(animal = 'Giant Panda') {
@@ -27,29 +27,29 @@ function favoriteAnimal(animal = 'Giant Panda') {
 }
 ```
 
-In the example above, the default value of the parameter `animal` is set to `'Giant Panda'`. If the function `favoriteAnimal` is called without an argument, the parameter `animal` will be assigned the value `'Giant Panda'`.
+No exemplo acima, o valor padrão do parâmetro `animal` é definido como `'Giant Panda'`. Se a função `favoriteAnimal` for chamada sem um argumento, o parâmetro `animal` receberá o valor `'Giant Panda'`.
 
 # --question--
 
 ## --text--
 
-How do default parameters in JavaScript functions enhance the behavior of functions like `favoriteAnimal` when called without any arguments?
+Como os parâmetros padrão em funções JavaScript melhoram o comportamento de funções como `favoriteAnimal` quando chamadas sem argumentos?
 
 ## --answers--
 
-They cause the function to throw an error if no argument is provided.
+Eles fazem com que a função lance um erro se nenhum argumento for fornecido.
 
 ---
 
-They prevent the function from being called without the required number of arguments.
+Eles impedem que a função seja chamada sem o número necessário de argumentos.
 
 ---
 
-They ensure the function returns `null` to indicate that no argument was passed.
+Eles garantem que a função retorne `null` para indicar que nenhum argumento foi passado.
 
 ---
 
-They allow the function to execute with a predefined value, avoiding `undefined` related issues.
+Eles permitem que a função seja executada com um valor predefinido, evitando problemas relacionados ao `undefined`.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-e.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-e.md
index 3f9b2b0ee2..a1997e5766 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-e.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-e.md
@@ -1,13 +1,13 @@
 ---
 id: 6617aef05b87c334e7ae8016
-title: Learn Function Basics Lesson E
+title: Lição E de Aprenda funções básicas
 challengeType: 15
 dashedName: learn-function-basics-lesson-e
 ---
 
 # --description--
 
-As you have seen before, functions can return a value using the `return` keyword. The `return` keyword is used to return a value from a function. When the `return` keyword is used, the function will stop executing and return the value specified after the `return` keyword.
+Como você viu antes, funções podem retornar um valor usando a palavra-chave `return`. A palavra-chave `return` é usada para retornar um valor de uma função. Quando a palavra-chave `return` é usada, a função vai parar de executar e retornar o valor especificado após a palavra-chave `return`.
 
 ```js
 function add(a, b) {
@@ -17,7 +17,7 @@ function add(a, b) {
 console.log(add(2, 3)); // Output: 5
 ```
 
-But what happens if the `return` keyword is used before the end of the function? To answer this question, consider the following example:
+O que acontece, porém, se a palavra-chave `return` for usada antes do fim da função? Para responder a essa pergunta, considere o exemplo a seguir:
 
 ```js
 function add(a, b) {
@@ -31,13 +31,13 @@ function add(a, b) {
 console.log(add(3, 7)); // Output: 7
 ```
 
-In the example above, the function `add` has a conditional statement that checks if the value of `a` is greater than `2`. If the condition is met, the function will return the value of `b` and stop executing. If the condition is not met, the function will return the sum of `a` and `b`.
+No exemplo acima, a função `add` tem uma instrução condicional que verifica se o valor de `a` é maior que `2`. Se a condição for atendida, a função retornará o valor de `b` e vai parar de executar. Se a condição não for atendida, a função retornará a soma de `a` e `b`.
 
 # --question--
 
 ## --text--
 
-What is the output of the following code snippet?
+Qual é o resultado do seguinte trecho de código?
 
 ```js
 function add(a, b = 12) {
@@ -55,19 +55,19 @@ console.log(add(3));
 
 ## --answers--
 
-The output is `24`.
+A saída é `24`.
 
 ---
 
-The output is `14`.
+A saída é `14`.
 
 ---
 
-The output is `15`.
+A saída é `15`.
 
 ---
 
-The output is `12`.
+A saída é `12`.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-f.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-f.md
index f78a891c6e..ecbaa3180d 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-f.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-function-basics/learn-function-basics-lesson-f.md
@@ -7,7 +7,7 @@ dashedName: learn-function-basics-lesson-f
 
 # --description--
 
-Arrow functions are a more modern way to write functions in JavaScript. They provide a more compact syntax compared to traditional function expressions. Arrow functions are defined using the `=>` syntax.
+As arrow functions são uma forma mais moderna de se escrever funções em JavaScript. Elas fornecem uma sintaxe mais compacta em comparação com expressões de função tradicionais. As arrow functions são definidas usando a sintaxe `=>`.
 
 ```js
 const add = (a, b) => {
@@ -15,37 +15,37 @@ const add = (a, b) => {
 }
 ```
 
-In the example above, the arrow function `add` takes two parameters `a` and `b` and returns their sum. The `return` keyword is used to return the result of the addition operation.
+No exemplo acima, a arrow function `add` recebe dois parâmetros `a` e `b` e retorna a sua soma. A palavra-chave `return` é usada para retornar o resultado da operação de adição.
 
-If the arrow function has only one expression, the curly braces `{}` and the `return` keyword can be omitted. The expression will be implicitly returned.
+Se a arrow function tem apenas uma expressão, as chaves `{}` e a palavra-chave `return` podem ser omitidas. A expressão será retornada implicitamente.
 
 ```js
 const add = (a, b) => a + b;
 ```
 
-In the example above, the arrow function `add` takes two parameters `a` and `b` and returns their sum. The `return` keyword and curly braces `{}` are omitted, and the result of the addition operation is implicitly returned.
+No exemplo acima, a função de seta `add` recebe dois parâmetros `a` e `b` e retorna a sua soma. A palavra-chave `return` e as chaves `{}` foram omitidos e o resultado da operação de adição é implicitamente retornado.
 
 # --question--
 
 ## --text--
 
-What makes arrow functions different from traditional function expressions in JavaScript?
+O que torna as arrow functions diferentes das expressões de função tradicionais em JavaScript?
 
 ## --answers--
 
-They cannot return values.
+Elas não podem retornar valores.
 
 ---
 
-They cannot take parameters.
+Elas não podem receber parâmetros.
 
 ---
 
-They have a more compact syntax compared to traditional function expressions.
+Elas têm uma sintaxe mais compacta em comparação com expressões de função tradicionais.
 
 ---
 
-They require the use of the `function` keyword.
+Elas requerem o uso da palavra-chave `function`.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-a.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-a.md
index 545705ca00..c3dc98d65d 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-a.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-a.md
@@ -1,44 +1,44 @@
 ---
 id: 637f4e0e72c65bc8e73dfe1e
 videoId: LGQuIIv2RVA
-title: HTML Foundations Lesson A
+title: Lição A sobre Fundamentos de HTML
 challengeType: 15
 dashedName: html-foundations-lesson-a
 ---
 
 # --description--
 
-Almost all elements on an HTML page are just pieces of content wrapped in opening and closing HTML tags.
+Quase todos os elementos de uma página HTML são apenas trechos de conteúdo envolvidos por tags de abertura e de fechamento do HTML.
 
-Opening tags tell the browser this is the start of an HTML element. They are comprised of a keyword enclosed in angle brackets `<>`. For example, an opening paragraph tag looks like this: `<p>`.
+As tags de abertura dizem ao navegador que este é o início de um elemento HTML. Elas são compostas por uma palavra-chave contida em sinais de menor e maior que, `<>`. Por exemplo, uma tag de abertura de um parágrafo terá esta aparência: `<p>`.
 
-Closing tags tell the browser where an element ends. They are almost the same as opening tags; the only difference is that they have a forward slash before the keyword. For example, a closing paragraph tag looks like this: `</p>`.
+As tags de fechamento dizem ao navegador onde um elemento termina. Quase sempre, elas são iguais às tags de abertura. A única diferença está no fato de terem uma barra antes da palavra-chave. Por exemplo, uma tag de fechamento de um parágrafo terá esta aparência: `</p>`.
 
-A full paragraph element looks like this:
+Um elemento de parágrafo completo terá esta aparência:
 
-<img src="https://cdn.freecodecamp.org/curriculum/odin-project/html-foundations/html-foundations-01.png" alt='An opening p tag, followed by the content string "some text content", followed by a closing p tag.' />
+<img src="https://cdn.freecodecamp.org/curriculum/odin-project/html-foundations/html-foundations-01.png" alt='Uma tag de abertura, seguida do conteúdo "some text content", seguida de uma tag p de fechamento.' />
 
 # --assignment--
 
-Watch Kevin Powell’s <a href="https://www.youtube.com/watch?v=LGQuIIv2RVA&list=PL4-IK0AVhVjM0xE0K2uZRvsM7LkIhsPT-" target="_blank">Introduction to HTML video</a>
+Assista ao <a href="https://www.youtube.com/watch?v=LGQuIIv2RVA&list=PL4-IK0AVhVjM0xE0K2uZRvsM7LkIhsPT-" target="_blank">vídeo de introdução ao HTML</a> de Kevin Powell
 
 # --question--
 
 ## --text--
 
-What are HTML tags?
+O que são as tags HTML?
 
 ## --answers--
 
-HTML tags tell the browser what content an element contains.
+As tags do HTML informam ao navegador o conteúdo que um elemento contém.
 
 ---
 
-HTML tags tell the browser when to load its content.
+As tags do HTML dizem ao navegador quando carregar seu conteúdo.
 
 ---
 
-HTML tags tell the browser what content the next element contains.
+As tags do HTML informam ao navegador o conteúdo que o próximo elemento contém.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-c.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-c.md
index 51c84c3d06..d20ef41139 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-c.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-c.md
@@ -1,52 +1,52 @@
 ---
 id: 637f4e1c72c65bc8e73dfe20
-title: HTML Foundations Lesson C
+title: Lição C sobre Fundamentos de HTML
 challengeType: 15
 dashedName: html-foundations-lesson-c
 ---
 
 # --description--
 
-To demonstrate an HTML boilerplate, you first need an HTML file to work with.
+Para demonstrar um boilerplate de HTML, você primeiro precisa de um arquivo HTML com o qual vamos trabalhar.
 
-Create a new folder on your computer and name it `html-boilerplate`. Within that folder create a new file and name it `index.html`.
+Crie uma pasta em seu computador e dê a ela o nome de `html-boilerplate`. Dentro dessa pasta, crie um arquivo e dê a ele o nome de `index.html`.
 
-You’re probably already familiar with a lot of different types of files, for example doc, pdf, and image files.
+Você, provavelmente, já está familiarizado com muitos tipos diferentes de arquivos, como, por exemplo, arquivos .doc, .pdf e arquivos de imagem.
 
-To let the computer know you want to create an HTML file, you need to append the filename with the `.html` extension as you have done when creating the `index.html` file.
+Para que o computador saiba que você deseja criar um arquivo HTML, é preciso anexar ao nome do arquivo a extensão `.html`, como você fez ao criar o arquivo `index.html`.
 
-It is worth noting that you named your HTML file index. You should always name the HTML file that will contain the homepage of your websites `index.html`. This is because web servers will by default look for an `index.html` page when users land on your websites - and not having one will cause big problems.
+Vale a pena observar que você nomeou o seu arquivo HTML como index. Você sempre deve dar ao arquivo HTML que conterá a página inicial do seu site o nome de `index.html`. Isso acontece porque os servidores da web procurarão, por padrão, por uma página `index.html` quando os usuários acessam os sites – não ter uma página com esse nome causará grandes problemas.
 
-## The DOCTYPE
+## O DOCTYPE
 
-Every HTML page starts with a doctype declaration. The doctype’s purpose is to tell the browser what version of HTML it should use to render the document. The latest version of HTML is HTML5, and the doctype for that version is simply `<!DOCTYPE html>`.
+Toda página HTML começa com uma declaração de doctype. O propósito do doctype é informar ao navegador qual versão de HTML ele deve usar para renderizar o documento. A versão mais recente do HTML é o HTML5. O tipo doctype para essa versão é simplesmente `<!DOCTYPE html>`.
 
-The doctypes for older versions of HTML were a bit more complicated. For example, this is the doctype declaration for HTML4:
+Os doctypes para versões mais antigas do HTML eram um pouco mais complicados. Por exemplo, esta era a declaração de doctype para o HTML4:
 
 ```html
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
 ```
 
-However, you probably won’t ever want to be using an older version of HTML, and so you’ll always use `<!DOCTYPE html>`.
+No entanto, você provavelmente não vai mais querer usar uma versão mais antiga do HTML. Então, use sempre `<!DOCTYPE html>`.
 
-Open the `index.html` file created earlier in your text editor and add `<!DOCTYPE html>` to the very first line.
+Abra o arquivo `index.html` criado anteriormente no seu editor de texto e adicione `<!DOCTYPE html>` à primeira linha.
 
 # --question--
 ## --text--
 
-What is the purpose of the `DOCTYPE` declaration?
+Qual é a finalidade da declaração de `DOCTYPE`?
 
 ## --answers--
 
-It tells the browser which version of HTML to use to render the document.
+Informar ao navegador qual versão de HTML usar para renderizar o documento.
 
 ---
 
-It tells the browser that this document uses JavaScript.
+Informar ao navegador que este documento usa JavaScript.
 
 ---
 
-It tells the browser the title of the document.
+Informar ao navegador o título do documento.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-e.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-e.md
index 6b23f758ad..4fe2328cf9 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-e.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-e.md
@@ -1,33 +1,33 @@
 ---
 id: 637f4e2f72c65bc8e73dfe22
-title: HTML Foundations Lesson E
+title: Lição E sobre Fundamentos de HTML
 challengeType: 15
 dashedName: html-foundations-lesson-e
 ---
 
 # --description--
 
-The `<head>` element is where you put important meta-information about your webpages, and stuff required for your webpages to render correctly in the browser. Inside the `<head>`, you should not use any element that displays content on the webpage.
+O elemento `<head>` é onde você coloca as metainformações importantes sobre suas páginas da web, além de coisas necessárias para que suas páginas da web sejam renderizadas corretamente no navegador. Dentro de `<head>`, você não deve usar elementos que exibam conteúdo na página.
 
-## The Charset Meta Element
-You should always have the `meta` tag for the `charset` encoding of the webpage in the `head` element: `<meta charset="utf-8">`.
+## O elemento meta charset
+Você deve sempre ter a tag `meta` para a codificação do conjunto de caracteres, ou `charset`, da página no elemento `head`: `<meta charset="utf-8">`.
 
-Setting the encoding is very important because it ensures that the webpage will display special symbols and characters from different languages correctly in the browser.
+Definir a codificação é muito importante, pois garante que a página da web exibirá símbolos especiais e caracteres de diferentes idiomas corretamente no navegador.
 
-## Title Element
-Another element you should always include in the head of an HTML document is the `title` element:
+## Elemento title
+Outro elemento que você sempre deve incluir na head de um documento HTML é o elemento `title`:
 
 ```html
 <title>My First Webpage</title>
 ```
 
-The `title` element is used to give webpages a human-readable title which is displayed in your webpage’s browser tab.
+O elemento `title` é usado para dar às páginas da web um título legível, o qual é exibido na guia do navegador da sua página.
 
-If you didn’t include a `title` element, the webpage’s title would default to its file name. In your case that would be `index.html`, which isn’t very meaningful for users; this would make it very difficult to find your webpage if the user has many browser tabs open.
+Se você não incluir um elemento `title`, o título da página da web será o padrão para o nome do arquivo. No seu caso, seria `index.html`, o que não é muito significativo para os usuários, o que tornaria muito difícil encontrar sua página da web se o usuário tivesse muitas abas do navegador abertas.
 
-There are many more elements that can go within the `head` of an HTML document. However, for now it’s only crucial to know about the two elements you have covered here. You will introduce more elements that go into the `head` throughout the rest of the curriculum.
+Há muito mais elementos que podem ser inseridos em `head` em um documento HTML. No entanto, por agora, é crucial saber apenas os dois elementos que vemos aqui. Você verá mais elementos que serão colocados em `head` durante a continuação do currículo.
 
-Back in `index.html` file, let’s add a `head` element with a `charset` `meta` element and a `title` within it. The head element goes within the HTML element and should always be the first element under the opening `<html>` tag:
+De volta ao arquivo `index.html`, vamos adicionar um elemento `head` e, dentro dele, um elemento `meta` `charset` e um elemento `title`. O elemento head vai dentro do elemento HTML e deve ser sempre o primeiro elemento após a tag de abertura de `<html>`:
 
 
 ```html
@@ -45,19 +45,19 @@ Back in `index.html` file, let’s add a `head` element with a `charset` `meta`
 
 ## --text--
 
-What is the purpose of the `head` element?
+Qual é a finalidade do elemento `head`?
 
 ## --answers--
 
-The `head` element is used to display all elements that are displayed on the webpage.
+O elemento `head` é usado para exibir todos os elementos que são exibidos na página da web.
 
 ---
 
-The `head` element is used to display important information about your webpage and is used to render web pages correctly with `meta` elements.
+O elemento `head` é usado para exibir informações importantes sobre sua página da web e é usado para renderizar as páginas da web corretamente com elementos `meta`.
 
 ---
 
-The `head` element is used to display the header content on top of the webpage.
+O elemento `head` é usado para exibir o conteúdo do cabeçalho na parte superior da página da web.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-f.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-f.md
index d63c23898c..dc13c987c8 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-f.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-f.md
@@ -1,46 +1,46 @@
 ---
 id: 637f4e3672c65bc8e73dfe23
 videoId: V8UAEoOvqFg
-title: HTML Foundations Lesson F
+title: Lição F sobre Fundamentos de HTML
 challengeType: 15
 dashedName: html-foundations-lesson-f
 ---
 
 # --description--
 
-The final element needed to complete the HTML boilerplate is the `<body>` element. This is where all the content that will be displayed to users will go - the text, images, lists, links, and so on.
+O elemento final necessário para completar o boilerplate do HTML é o elemento `<body>`. Aqui vai todo o conteúdo que será exibido aos usuários – texto, imagens, listas, links e assim por diante.
 
-To complete the boilerplate, add a `body` element to the `index.html` file. The `body` element also goes within the `html` element and is always below the `head` element, like so:
+Para completar o boilerplate, adicione um elemento `body` ao arquivo `index.html`. O elemento `body` também deve ir dentro do elemento `html` e estará sempre abaixo do elemento `head`, assim:
 
 # --assignment--
 
-Watch and follow along to Kevin Powell’s brilliant Building your first web page video above.
+Assista e acompanhe o vídeo de Kevin Powell, Build your first web page. O vídeo está acima.
 
 ---
 
-Build some muscle memory by deleting the contents of the `index.html` file and trying to write out all the boilerplate again from memory. Não se preocupe se precisar dar uma olhada no conteúdo da lição nas primeiras vezes caso não saiba o que fazer. Just keep going until you can do it a couple of times from memory.
+Desenvolva sua memória muscular excluindo o conteúdo do arquivo `index.html` e tente escrever todo o boilerplate novamente de memória. Não se preocupe se precisar dar uma olhada no conteúdo da lição nas primeiras vezes caso não saiba o que fazer. Apenas siga fazendo isso até que você possa fazer o processo algumas vezes de memória.
 
 ---
 
-Run your boilerplate through this [HTML validator](https://www.freeformatter.com/html-validator.html). Validators ensure your markup is correct and are an excellent learning tool, as they provide feedback on syntax errors you may be making often and aren’t aware of, such as missing closing tags and extra spaces in your HTML.
+Teste seu boilerplate através deste [validador de HTML](https://www.freeformatter.com/html-validator.html). Os validadores garantem que a marcação está correta e são uma excelente ferramenta de aprendizado, pois fornecem feedback sobre erros de sintaxe que você pode estar cometendo de vez em quando sem saber, como deixar de colocar tags de fechamento ou adicionar espaços a mais em seu HTML.
 
 # --question--
 
 ## --text--
 
-What is the purpose of the `body` element?
+Qual é a finalidade do elemento `body`?
 
 ## --answers--
 
-This is where all important information about the webpage is displayed such as the `title` and `meta` tags.
+É aqui que todas as informações importantes sobre a página da web são exibidas, como as tags `title` e `meta`.
 
 ---
 
-This is where you tell the browser how to render the webpage correctly.
+É aqui que você informa ao navegador como renderizar a página da web corretamente.
 
 ---
 
-This is where all content will be displayed on the page such images, text, and links.
+É aqui que vai todo o conteúdo que será exibido na página, como imagens, textos e links.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-g.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-g.md
index 5cfe098a52..b80f510d0d 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-g.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-html-foundations/html-foundations-lesson-g.md
@@ -1,31 +1,31 @@
 ---
 id: 6376327e2724a688c04636e3
-title: HTML Foundations Lesson G
+title: Lição G sobre Fundamentos de HTML
 challengeType: 15
 dashedName: html-foundations-lesson-g
 ---
 
 # --description--
 
-HTML and CSS are two languages that work together to create everything that you see when you look at something on the internet. HTML is the raw data that a webpage is built out of. All the text, links, cards, lists, and buttons are created in HTML. CSS is what adds style to those plain elements. HTML puts information on a webpage, and CSS positions that information, gives it color, changes the font, and makes it look great!
+O HTML e o CSS são duas linguagens que trabalham em conjunto para criar tudo o que você vê quando está na internet. O HTML são os dados brutos que constituem uma página da web. Todos os textos, links, cards, listas e botões são criados em HTML. O CSS é o que adiciona estilo a esses elementos simples. O HTML coloca informações em uma página da web e o CSS posiciona essas informações, dá cor a elas, muda as fontes, o que dá a elas uma aparência melhor!
 
 # --question--
 
 ## --text--
 
-What are the primary responsibilities of HTML and CSS in creating a webpage?
+Quais são as responsabilidades primárias do HTML e do CSS na criação de uma página para a web?
 
 ## --answers--
 
-HTML structures the content, while CSS styles the elements.
+O HTML estrutura o conteúdo, enquanto o CSS estiliza os elementos.
 
 ---
 
-HTML creates the visual design, while CSS organizes the content.
+O HTML cria o projeto visual, enquanto o CSS organiza o conteúdo.
 
 ---
 
-CSS manages the functionality, while HTML controls the layout.
+O CSS gerencia a funcionalidade, enquanto o HTML controla o layout.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
index d256c5c02b..7d6ef9c55a 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
@@ -7,45 +7,45 @@ dashedName: learn-to-solve-problems-and-understand-errors-lesson-a
 
 # --description--
 
-Before you start digging into some pretty nifty JavaScript, you need to begin talking about problem solving: the most important skill a developer needs.
+Antes de começar a mexer com scripts em JavaScript bem legais, você precisa começar a falar sobre resolução de problemas: a habilidade mais importante de que um desenvolvedor precisa.
 
-Problem solving is the core thing software developers do. The programming languages and tools they use are secondary to this fundamental skill.
+Resolver problemas é a essência do que fazem os desenvolvedores de software. As linguagens de programação e as ferramentas que eles usam são secundárias em relação a esta habilidade fundamental.
 
-From his book, "Think Like a Programmer", V. Anton Spraul defines problem solving in programming as:
+Em seu livro, "Pense Como um Programador", V. Anton Spraul define a resolução de problemas em programação como:
 
-> Problem solving is writing an original program that performs a particular set of tasks and meets all stated constraints.
+> Resolver problemas é escrever um programa original que realiza um conjunto específico de tarefas e atende a todas as restrições declaradas.
 
-The set of tasks can range from solving small coding exercises all the way up to building a social network site like Facebook or a search engine like Google. Each problem has its own set of constraints, for example, high performance and scalability may not matter too much in a coding exercise but it will be vital in apps like Google that need to service billions of search queries each day.
+O conjunto de tarefas pode variar desde resolver pequenos exercícios de programação até criar um site de rede social como o Facebook ou um mecanismo de busca como o Google. Cada problema tem seu próprio conjunto de restrições. Por exemplo, alto desempenho e escalabilidade podem não importar muito em um exercício de programação, mas serão essenciais em apps como o Google que precisam atender bilhões de consultas de busca diariamente.
 
-New programmers often find problem solving the hardest skill to build. It's not uncommon for budding programmers to breeze through learning syntax and programming concepts, yet when trying to code something on their own, they find themselves staring blankly at their text editor not knowing where to start.
+Novos programadores muitas vezes acham que resolver problemas é a habilidade mais difícil de desenvolver. Não é incomum para programadores iniciantes passarem facilmente pelo aprendizado de sintaxe e conceitos de programação, mas ao tentar programar algo por conta própria, se encontrarem encarando um editor de texto sem saber por onde começar.
 
-The best way to improve your problem solving ability is by building experience by making lots and lots of programs. The more practice you have the better you'll be prepared to solve real world problems.
+A melhor maneira de melhorar sua capacidade de resolver problemas é ganhando experiência fazendo muitos e muitos programas. Quanto mais prática você tiver, melhor estará preparado para resolver problemas do mundo real.
 
-# --question--
+# --assignment--
 
-## --assignment--
+Leia <a href="https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/" target="_blank">Como Pensar Como um Programador - Lições em Resolução de Problemas</a> de Richard Reis.
 
-Read <a href="https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/" target="_blank">How to Think Like a Programmer - Lessons in Problem Solving</a> by Richard Reis.
+# --question--
 
 ## --text--
 
-According to V. Anton Spraul in "Think Like a Programmer," what is problem solving in programming?
+De acordo com V. Anton Spraul em "Pense Como um Programador", o que é resolução de problemas em programação?
 
 ## --answers--
 
-Learning the syntax and concepts of different programming languages.
+Aprender a sintaxe e conceitos de diferentes linguagens de programação.
 
 ---
 
-Building applications with high performance and scalability as the key features.
+Criar aplicações com alto desempenho e escalabilidade como características principais.
 
 ---
 
-Writing an original program that performs a specific set of tasks and meets all stated constraints.
+Escrever um programa original que realiza um conjunto específico de tarefas e atende a todas as restrições declaradas.
 
 ---
 
-Solving coding exercises to improve programming skills.
+Resolver exercícios de programação para melhorar as habilidades de programação.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
index 409a083795..e43e633199 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
@@ -7,48 +7,48 @@ dashedName: learn-to-solve-problems-and-understand-errors-lesson-b
 
 # --description--
 
-## Understand the problem
-The first step to solving a problem is understanding exactly what the problem is. If you don’t understand the problem, you won’t know when you’ve successfully solved it and may waste a lot of time on a wrong solution.
+## Entender o problema
+A primeira etapa para resolver um problema é entender exatamente qual é o problema. Se você não entender o problema, não saberá quando o resolveu com sucesso e pode desperdiçar muito tempo em uma solução errada.
 
-To gain clarity and understanding of the problem, write it down on paper, reword it in plain English until it makes sense to you, and draw diagrams if that helps. When you can explain the problem to someone else in plain English, you understand it.
+Para obter clareza e compreensão do problema, escreva-o no papel, reescreva-o de maneira simples até que faça sentido para você. Desenhe diagramas se isso ajudar. Quando você consegue explicar o problema para outra pessoa com simplicidade, significa que você o entende.
 
-### Plan
-Now that you know what you’re aiming to solve, don’t jump into coding just yet. It’s time to plan out how you’re going to solve it first. Some of the questions you should answer at this stage of the process:
+### Planejamento
+Agora que você sabe o que está tentando resolver, não comece a programar ainda. É hora de planejar como você vai resolvê-lo primeiro. Algumas das perguntas que você deve responder nesta etapa do processo:
 
-- Does your program have a user interface? What will it look like? What functionality will the interface have? Sketch this out on paper.
+- Seu programa tem uma interface de usuário? Como será? Que funcionalidades a interface terá? Esboce isso no papel.
 
-- What inputs will your program have? Will the user enter data or will you get input from somewhere else?
+- Quais serão as entradas do seu programa? O usuário inserirá dados ou você obterá entrada de outro lugar?
 
-- What’s the desired output?
+- Qual é a saída desejada?
 
-- Given your inputs, what are the steps necessary to return the desired output?
+- Dadas suas entradas, quais são as etapas necessárias para retornar a saída desejada?
 
-The last question is where you will write out an algorithm to solve the problem. You can think of an algorithm as a recipe for solving a particular problem. It defines the steps that need to be taken by the computer to solve a problem in pseudocode.
+A última pergunta é onde você escreverá um algoritmo para resolver o problema. Você pode pensar em um algoritmo como uma receita para resolver um determinado problema. Ele define as etapas que o computador precisa seguir para resolver um problema em pseudocódigo.
 
-# --question--
+# --assignment--
+Assista <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">Como Começar a Pensar Como um Programador</a> pelo Coding Tech. Tem uma hora de duração, mas é repleto de informações e definitivamente vale a pena assistir.
 
-## --assignment--
-Watch <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">How to Begin Thinking Like a Programmer</a> by Coding Tech. It’s an hour long but packed full of information and definitely worth your time watching.
+# --question--
 
 ## --text--
 
-What should you do before starting to code according to the provided text?
+O que você deve fazer antes de começar a programar de acordo com o texto fornecido?
 
 ## --answers--
 
-Immediately start coding to see what problems arise.
+Comece a programar imediatamente para ver quais problemas surgem.
 
 ---
 
-Write out the problem in plain English and make sure you can explain it to someone else.
+Escreva o problema em linguagem simples e certifique-se de que você pode explicá-lo para outra pessoa.
 
 ---
 
-Sketch the user interface and start coding the most complex functions first.
+Desenhe a interface do usuário e comece a codificar as funções mais complexas primeiro.
 
 ---
 
-Collect all possible inputs from users and other sources.
+Colete todas as possíveis entradas dos usuários e outras fontes.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
index c837fd9658..2e51c6a844 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
@@ -1,17 +1,17 @@
 ---
 id: 66581a7bb1eb2281159492fc
-title: Learn to Solve Problems and Understand Errors Lesson C
+title: Lição C de Aprenda a resolver problemas e a entender erros
 challengeType: 15
 dashedName: learn-to-solve-problems-and-understand-errors-lesson-c
 ---
 
 # --description--
 
-## Psuedocode
+## Pseudocódigo
 
-Pseudocode is writing out the logic for your program in natural language instead of code. It helps you slow down and think through the steps your program will have to go through to solve the problem.
+Pseudocódigo é escrever a lógica do seu programa em linguagem natural em vez de código. Ele ajuda você a desacelerar e pensar sobre as etapas que seu programa terá que seguir para resolver o problema.
 
-Here’s an example of what the pseudocode for a program that prints all numbers up to an inputted number might look like:
+Aqui está um exemplo de como pode ser o pseudocódigo para um programa que imprime todos os números até um número inserido:
 
 ```bash
 When the user inputs a number
@@ -20,33 +20,33 @@ While counter is smaller than user inputted number increment the counter by one
 Print the value of the counter variable
 ```
 
-This is a basic program to demonstrate how pseudocode looks. There will be more examples of pseudocode included in the assignments.
+Este é um programa básico para demonstrar como o pseudocódigo se parece. Haverá mais exemplos de pseudocódigo incluídos nas tarefas.
 
+# --assignment--
 
-# --question--
+Leia o artigo <a href="https://builtin.com/data-science/pseudocode" target="_blank"> Pseudocódigo: O que é e como escrevê-lo</a>, da Built In.
 
-## --assignment--
-Read this <a href="https://builtin.com/data-science/pseudocode" target="_blank"> Pseudocode: What It Is and How to Write It</a> article from Built In.
+# --question--
 
 ## --text--
 
-What are the benefits of using pseudocode according to the linked article?
+Quais são os benefícios do uso de pseudocódigo de acordo com o artigo vinculado?
 
 ## --answers--
 
-Pseudocode is primarily beneficial for beginners as it helps them learn programming languages faster by skipping complex syntax.
+O pseudocódigo é principalmente benéfico para iniciantes, pois os ajuda a aprender linguagens de programação mais rapidamente, pulando a sintaxe complexa.
 
 ---
 
-Pseudocode simplifies communication with non-programmers, aids in code construction, provides a good basis for documentation, and helps in bug detection.
+O pseudocódigo simplifica a comunicação com pessoas que não são programadores, auxilia na construção de código, fornece uma boa base para documentação e ajuda na detecção de erros.
 
 ---
 
-Pseudocode entirely eliminates the need for programmers to understand or use programming languages, making it the primary tool for professional coders.
+O pseudocódigo elimina totalmente a necessidade de programadores entenderem ou usarem linguagens de programação, tornando-se a ferramenta principal para programadores profissionais.
 
 ---
 
-Pseudocode is used exclusively for creating detailed flowcharts that replace traditional coding in complex software development environments.
+O pseudocódigo é usado exclusivamente para criar fluxogramas detalhados que substituem a codificação tradicional em ambientes de desenvolvimento de software complexos.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-d.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-d.md
index 1a210400dd..3ac86c250c 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-d.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-d.md
@@ -1,37 +1,37 @@
 ---
 id: 66581a7bb1eb2281159492fd
-title: Learn to Solve Problems and Understand Errors Lesson D
+title: Lição D de Aprenda a resolver problemas e a entender erros
 challengeType: 15
 dashedName: learn-to-solve-problems-and-understand-errors-lesson-d
 ---
 
 # --description--
 
-Reading and understanding error messages is a requirement as a developer. At first glance, many beginners shrink away from error messages as they appear to be “scary” and difficult to understand because they include terms one may not be familiar with.
+Ler e entender mensagens de erro é um requisito como desenvolvedor. À primeira vista, muitos iniciantes recuam diante das mensagens de erro, pois elas parecem "assustadoras" e difíceis de entender, já que incluem termos com os quais você pode não estar familiarizado.
 
-However, error messages provide developers with a treasure trove of knowledge, and tell you everything you need to know about how to resolve them! Being able to parse error messages and warnings without fear will enable you to effectively debug your applications, receive meaningful help from others, and empower yourself to push forward when faced with an error.
+No entanto, as mensagens de erro fornecem aos desenvolvedores um tesouro de conhecimento e informam tudo que você precisa saber sobre como resolvê-las! Ser capaz de interpretar mensagens de erro e avisos sem medo permitirá que você depure efetivamente suas aplicações, receba ajuda significativa de outros e se fortaleça para seguir em frente quando enfrentar um erro.
 
 # --question--
 
 ## --text--
 
-According to the text, why should developers not shy away from error messages?
+De acordo com o texto, por que os desenvolvedores não devem fugir das mensagens de erro?
 
 ## --answers--
 
-Error messages are only for advanced programmers and can be ignored by beginners until they gain more experience.
+Mensagens de erro são apenas para programadores avançados e podem ser ignoradas por iniciantes até que ganhem mais experiência.
 
 ---
 
-Error messages need to be memorized completely to be effective in programming.
+Mensagens de erro precisam ser completamente memorizadas para serem eficazes na programação.
 
 ---
 
-Error messages provide crucial information that helps developers understand and fix problems in their code.
+Mensagens de erro fornecem informações cruciais que ajudam os desenvolvedores a entender e corrigir problemas em seu código.
 
 ---
 
-Error messages are meant to be handled by automated debugging tools and do not require human interpretation.
+Mensagens de erro devem ser tratadas por ferramentas automatizadas de depuração e não requerem interpretação humana.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-g.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-g.md
index 877c325422..ec3e4a96a0 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-g.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-to-solve-problems-and-understand-errors-lesson-g
 
 # --description--
 
-Say you have two strings that you would like to combine to create one message, such as below:
+Digamos que você tem duas strings que gostaria de combinar para criar uma mensagem, como abaixo:
 
 ```js
 const str1 = "Hello";
@@ -15,19 +15,19 @@ const str2 = "World!";
 const message = str1.push(str2);
 ```
 
-<img src="https://cdn.statically.io/gh/TheOdinProject/curriculum/4ed59981b4ce2c60b5b83bf7415d3127b61821f5/foundations/javascript_basics/understanding_errors/imgs/03.png" style="width:100%" alt="an example of a type error in the Chrome developer console" />
+<img src="https://cdn.statically.io/gh/TheOdinProject/curriculum/4ed59981b4ce2c60b5b83bf7415d3127b61821f5/foundations/javascript_basics/understanding_errors/imgs/03.png" style="width:100%" alt="um exemplo de um erro de tipo no console do desenvolvedor do Chrome" />
 
-Here, you'll get a `TypeError` with a message stating that `str1.push is not a function`. This is a common error message that confuses learners because you might know that `.push()` is certainly a function (for example, if you have used it to add items to arrays before).
+Aqui, você receberá um `TypeError` com uma mensagem afirmando `str1.push is not a function`. Essa é uma mensagem de erro comum que confunde os aprendizes porque você pode saber que `.push()` é certamente uma função (por exemplo, se você já a usou para adicionar itens a arrays antes).
 
-But that's the key - `.push()` is not a String method, it's an Array method. Hence, it is “not a function” that you can find as a String method. If you change`.push()` to `.concat()`, a proper String method, our code runs as intended!
+Essa é a chave – `.push()` não é um método de String; é um método de Array. Portanto, não é uma "função" que você pode encontrar como um método de String. Se você mudar `.push()` para `.concat()`, um método de String adequado, nosso código funciona como planejado!
 
-A good note to keep in mind when faced with a `TypeError` is to consider the data type you are trying to run a method or operation against. You'll likely find that it is not what you think, or the operation or method is not compatible with that type.
+Uma boa observação a se ter em mente quando confrontado com um `TypeError` é considerar o tipo de dados ao qual você está tentando aplicar um método ou operação. Você provavelmente descobrirá que não é o que você pensa ou que a operação ou método não é compatível com esse tipo.
 
 # --question--
 
 ## --text--
 
-Why does the following JavaScript code result in a `TypeError`?
+Por que o seguinte código em JavaScript resulta em um `TypeError`?
 
 ```js
 const str1 = "Hello";
@@ -37,19 +37,19 @@ const message = str1.push(str2);
 
 ## --answers--
 
-The `.push()` method can only be used on objects, not strings.
+O método `.push()` só pode ser usado em objetos, não em strings.
 
 ---
 
-The `.push()` method is not available for strings because it is an Array method.
+O método `.push()` não está disponível para strings porque é um método de arrays.
 
 ---
 
-The `.push()` method is incorrectly spelled and should be .pusch().
+O método `.push()` está escrito incorretamente e deveria ser .pusch().
 
 ---
 
-The `TypeError` is a result of a syntax error in the JavaScript code.
+O `TypeError` é resultado de um erro de sintaxe no código em JavaScript.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-h.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-h.md
index 5993f5c474..d3dc183541 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-h.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-h.md
@@ -1,41 +1,41 @@
 ---
 id: 66581a7fb1eb228115949301
-title: Learn to Solve Problems and Understand Errors Lesson H
+title: Lição H de Aprenda a resolver problemas e a entender erros
 challengeType: 15
 dashedName: learn-to-solve-problems-and-understand-errors-lesson-h
 ---
 
 # --description--
 
-At this point, you might be wondering how you can resolve these errors.
+Neste ponto, você pode estar se perguntando como pode resolver esses erros.
 
-1. You can start by understanding that the error message is your friend - not your enemy. Error messages tell you exactly what is wrong with your code, and which lines to examine to find the source of the error. Without error messages it would be a nightmare to debug our code - because it would still not work, you just wouldn’t know why!
+1. Você pode começar entendendo que a mensagem de erro é sua amiga – não sua inimiga. As mensagens de erro dizem exatamente o que há de errado com o código e quais linhas examinar para encontrar a origem do erro. Sem mensagens de erro seria um pesadelo depurar nosso código, porque ele ainda não funcionaria, você só não saberia por quê!
 
-1. You shoud search your error on the web, most of the time you will be able to find a fix or explanation on StackOverflow or in the documentation. If nothing else, you will receive more clarity as to why you are receiving this error.
+1. Você deve pesquisar seu erro na web. Na maioria das vezes, você encontrará uma correção ou explicação no StackOverflow ou na documentação. Ao menos, você perceberá com mais clareza o motivo de estar recebendo esse erro.
 
-1. Another way is to use `console.log()` — it is a popular choice for quick debugging. For more involved troubleshooting, using the debugger might be more appropriate, but using `console.log()` is great for getting immediate feedback without needing to step through your functions. There are also other useful methods such as `console.table()`, `console.trace()`, and more!
+1. Outra maneira é usar `console.log()` — é uma escolha popular para uma depuração rápida. Para uma solução de problemas mais detalhada, usar o depurador pode ser mais apropriado, mas usar `console.log()` é ótimo para obter feedback imediato sem precisar percorrer suas funções. Existem também outros métodos úteis como `console.table()`, `console.trace()` e mais!
 
 # --question--
 
 ## --text--
 
-When encountering an error in your code, which of the following is NOT a recommended step for identifying and resolving the issue?
+Ao encontrar um erro em seu código, qual das seguintes NÃO é uma etapa recomendada para identificar e resolver o problema?
 
 ## --answers--
 
-Utilizing `console.log()` or other console methods to debug and gain insights into the values and state of your code.
+Utilizar `console.log()` ou outros métodos de console para depurar e obter insights sobre os valores e o estado do seu código.
 
 ---
 
-Searching for the error message on resources like StackOverflow or reading documentation.
+Pesquisar a mensagem de erro em recursos como o StackOverflow ou ler a documentação.
 
 ---
 
-Ignoring the error messages and guessing what might be wrong.
+Ignorar as mensagens de erro e adivinhar o que pode estar errado.
 
 ---
 
-Using error messages as a guide to understand what part of the code is causing the problem.
+Usar as mensagens de erro como um guia para entender que parte do código está causando o problema.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-a.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-a.md
index 3cad23a270..8a20ecf736 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-a.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-a.md
@@ -6,7 +6,7 @@ dashedName: learn-variables-and-operators-lesson-a
 ---
 
 # --description--
-The simplest way to get started is to create an HTML file with the JavaScript code inside of it. Type the basic HTML skeleton into a file on your computer somewhere:
+A maneira mais simples de começar é criar um arquivo HTML com o código em JavaScript dentro dele. Digite o esqueleto básico do HTML em um arquivo no seu computador em algum lugar:
 
 ```html
 <!DOCTYPE html>
@@ -24,39 +24,39 @@ The simplest way to get started is to create an HTML file with the JavaScript co
 </html>
 ```
 
-Save and open this file up in a web browser (you can use <a href="https://marketplace.visualstudio.com/items?itemName=ritwickdey.LiveServer" target="_blank" >"Live Server" on Visual Studio Code</a> to do this!) and then open up the browser’s console by right-clicking on the blank webpage and selecting "Inspect" or "Inspect Element". In the ‘Developer Tools’ pane find and select the ‘Console’ tab, where you should see the output of our `console.log` statement.
+Salve e abra esse arquivo em um navegador da web (você pode usar o <a href="https://marketplace.visualstudio.com/items?itemName=ritwickdey.LiveServer" target="_blank" >"Live Server" no Visual Studio Code</a> para fazer isso!) e depois abra o console do navegador clicando com o botão direito na página da web em branco e selecionando "Inspecionar" ou "Inspecionar Elemento". No painel 'Ferramentas de Desenvolvedor', encontre e selecione a aba 'Console', onde você deve ver a saída da nossa instrução `console.log`.
 
-> `console.log()` is the command to print something to the developer console in your browser. You can use this to print the results from any of the following articles and exercises to the console. We encourage you to code along with all of the examples in this and future lessons.
+> `console.log()` é o comando para imprimir algo no console do desenvolvedor no seu navegador. Você pode usar isso para imprimir os resultados de qualquer um dos artigos e exercícios seguintes no console. Incentivamos você a programar junto com todos os exemplos nesta e em futuras lições.
 
-Another way to include JavaScript in a webpage is through an external script. This is very similar to linking external CSS docs to your website.
+Outra maneira de incluir JavaScript em uma página da web é por meio de um script externo. É muito semelhante a vincular documentos CSS externos ao seu site.
 
 ```html
   <script src="javascript.js"></script>
 ```
 
-JavaScript files have the extension `.js` similar to `.css` for stylesheets. External JavaScript files are used for more complex scripts.
+Arquivos em JavaScript têm a extensão `.js`, semelhante a `.css` para folhas de estilo. Arquivos em JavaScript externos são usados para scripts mais complexos.
 
 # --question--
 
 ## --text--
 
-Which statement accurately describes how to include JavaScript in an HTML document?
+Qual instrução descreve com precisão como incluir JavaScript em um documento HTML?
 
 ## --answers--
 
-JavaScript can only be included internally within a `<script>` tag in the HTML body.
+JavaScript só pode ser incluído internamente dentro de uma tag `<script>` no corpo do HTML.
 
 ---
 
-JavaScript code must be written in the `<head>` section of an HTML document for it to execute properly.
+O código em JavaScript deve ser escrito na seção `<head>` de um documento HTML para executar corretamente.
 
 ---
 
-JavaScript can be included directly in an HTML file using a `<script>` tag or linked externally via a `<script src="javascript.js">` tag.
+JavaScript pode ser incluído diretamente em um arquivo HTML usando uma tag `<script>` ou vinculado externamente via uma tag `<script src="javascript.js">`.
 
 ---
 
-External JavaScript files require a special attribute in the `<script>` tag to be recognized by web browsers.
+Arquivos em JavaScript externos requerem um atributo especial na tag `<script>` para serem reconhecidos pelos navegadores da web.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-d.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-d.md
index 7ae96cfc89..9614269724 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-d.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-d.md
@@ -19,9 +19,9 @@ let userName;
 let test123;
 ```
 
-Uma coisa interessante: o símbolo de cifrão, `'$'`, e o sublinhado, `'_'`, também podem ser usados em nomes. They are regular symbols, just like letters, without any special meaning.
+Uma coisa interessante: o símbolo de cifrão, `'$'`, e o sublinhado, `'_'`, também podem ser usados em nomes. Eles são símbolos regulares, assim como as letras, sem nenhum significado especial.
 
-These names are valid:
+Esses nomes são válidos:
 
 ```js
 let $ = 1; // declared a variable with the name "$"
@@ -30,7 +30,7 @@ let _ = 2; // and now a variable with the name "_"
 console.log($ + _); // 3
 ```
 
-Examples of incorrect variable names:
+Exemplos de nomes de variáveis incorretos:
 
 ```js
 let 1a; // cannot start with a digit
@@ -42,7 +42,7 @@ let my-name; // hyphens '-' aren't allowed in the name
 
 ## --text--
 
-Which of the following is a valid JavaScript variable name?
+Qual das opções a seguir é um nome de variável válido no JavaScript?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-e.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-e.md
index 10c4179324..1c8cffbabd 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-e.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-e.md
@@ -1,49 +1,49 @@
 ---
 id: 65e19bc3500d930ce8ed90a8
-title: Learn Variables and Operators Lesson E
+title: Lição E de Aprenda variáveis e operadores
 challengeType: 15
 dashedName: learn-variables-and-operators-lesson-e
 ---
 
 # --description--
 
-Numbers are the building blocks of programming logic! In fact, it’s hard to think of any useful programming task that doesn’t involve at least a little basic math… so knowing how numbers work is obviously quite important. Luckily, it’s also fairly straightforward.
+Números são os blocos de construção da lógica de programação! Na verdade, é difícil pensar em qualquer tarefa de programação útil que não envolva pelo menos um pouco de matemática básica... assim, saber como os números funcionam é obviamente bastante importante. Felizmente, também é bastante simples.
 
-| Operator | Description    | Example      |
-| -------- | -------------- | ------------ |
-| +        | Addition       | 5 + 3 = 8    |
-| -        | Subtraction    | 5 - 3 = 2    |
-| *        | Multiplication | 5 * 3 = 15   |
-| **       | Exponentiation | 5 ** 3 = 125 |
-| /        | Division       | 6 / 3 = 2    |
-| %        | Modulus        | 5 % 3 = 2    |
+| Operador | Descrição     | Exemplo      |
+| -------- | ------------- | ------------ |
+| +        | Adição        | 5 + 3 = 8    |
+| -        | Subtração     | 5 - 3 = 2    |
+| *        | Multiplicação | 5 * 3 = 15   |
+| **       | Exponenciação | 5 ** 3 = 125 |
+| /        | Divisão       | 6 / 3 = 2    |
+| %        | Módulo        | 5 % 3 = 2    |
 
 
 # --assignment--
 
-Given the table of operators above, write a simple program snippet that demonstrates the use of each operator with the variable `x` initialized to `10`.
+Dada a tabela de operadores acima, escreva um trecho de programa simples que demonstre o uso de cada operador com a variável `x` inicializada como `10`.
 
 # --question--
 
 ## --text--
 
-What is the result of applying the modulus operator to `x` where `x = 10`?
+Qual é o resultado de aplicar o operador módulo a `x` onde `x = 10`?
 
 ## --answers--
 
-`x % 3` results in `1`
+`x % 3` resulta em `1`
 
 ---
 
-`x % 3` results in `3`
+`x % 3` resulta em `3`
 
 ---
 
-`x % 3` results in `0`
+`x % 3` resulta em `0`
 
 ---
 
-`x % 3` results in `2`
+`x % 3` resulta em `2`
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-f.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-f.md
index 232a3a5e5c..d74cefd95f 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-f.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-f.md
@@ -7,45 +7,45 @@ dashedName: learn-variables-and-operators-lesson-f
 
 # --description--
 
-Let’s meet the features of JavaScript operators that are beyond school arithmetics.
+Vamos conhecer os recursos dos operadores de JavaScript que vão além da aritmética escolar.
 
-Usually, the plus operator `+` sums numbers.
+Normalmente, o operador de soma, `+`, soma números.
 
-But, if the binary `+` is applied to strings, it merges (concatenates) them:
+Porém, se o binário `+` for aplicado a strings, ele as mescla (concatena):
 
 ```js
 let s = "my" + "string";
 console.log(s); // mystring
 ```
 
-Note that if any of the operands is a string, then the other one is converted to a string too.
+Observe que se qualquer dos operandos for uma string, o outro também é convertido para string.
 
-For example:
+Por exemplo:
 
 ```js
 console.log(1 + '2'); // '12'
 console.log('1' + 2); // '12'
 ```
 
-See, it doesn’t matter whether the first operand is a string or the second one.
+Não importa se o primeiro operando é uma string ou o segundo.
 
-Here’s a more complex example:
+Aqui está um exemplo mais complexo:
 
 ```js
 console.log(2 + 2 + '1') // "41" and not "221"
 ```
 
-Here, operators work one after another. The first `+` sums two numbers, so it returns `4`, then the next `+`   adds the string `1` to it, so it’s like `4 + '1' = '41'`.
+Aqui, os operadores funcionam um após o outro. O primeiro `+` soma dois números, então ele retorna `4`, em seguida o próximo `+` adiciona a string `1` a ele, resultando em `4 + '1' = '41'`.
 
 ```js
 console.log('1' + 2 + 2) // "122" and not "14"
 ```
 
-Here, the first `+` concatenates the string and the number, so it returns `'12'`, then the next `+` adds `2` to it, so it’s like `'12' + 2 = '122'`.
+Aqui, o primeiro `+` concatena a string e o número, então ele retorna `'12'`, em seguida o próximo `+` adiciona `2` a ele, então é como `'12' + 2 = '122'`.
 
-The binary `+` is the only operator that supports strings in such a way. Other arithmetic operators work only with numbers and always convert their operands to numbers.
+O binário `+` é o único operador que suporta strings dessa forma. Outros operadores aritméticos funcionam apenas com números e sempre convertem seus operandos em números.
 
-Here’s the demo for subtraction and division:
+Aqui está a demonstração para subtração e divisão:
 
 ```js
 console.log( 6 - '2' ); // 4, converts '2' to a number
@@ -55,7 +55,7 @@ console.log( '6' / '2' ); // 3, converts both operands to numbers
 # --question--
 
 ## --text--
-Considering the behavior of the `+` operator with mixed data types in JavaScript, what will be the output of the following code snippet?
+Considerando o comportamento do operador `+` com tipos de dados mistos em JavaScript, qual será a saída do seguinte trecho de código?
 
 ```js
 console.log('3' + 2 - 1);
@@ -63,19 +63,19 @@ console.log('3' + 2 - 1);
 
 ## --answers--
 
-`31`, because the `+` operator concatenates the string and number before subtraction.
+`31`, porque o operador `+` concatena a string e o número antes da subtração.
 
 ---
 
-`32`, because `+` concatenates the string and number before subtraction.
+`32`, porque `+` concatena a string e o número antes da subtração.
 
 ---
 
-`4`, because all operands are converted to numbers first.
+`4`, porque todos os operandos são convertidos para números primeiro.
 
 ---
 
-`321`, because the `-` operator is not supported with strings.
+`321`, porque o operador `-` não é suportado com strings.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-g.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-g.md
index da3ca683fb..8d7070a45f 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-g.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-g.md
@@ -1,17 +1,17 @@
 ---
 id: 65e1aaf8500d930ce8ed90aa
-title: Learn Variables and Operators Lesson G
+title: Lição G de Aprenda variáveis e operadores
 challengeType: 15
 dashedName: learn-variables-and-operators-lesson-g
 ---
 
 # --description--
 
-The plus `+` exists in two forms: the binary form that you used in the last challenge and the unary form.
+O sinal de mais `+` existe em duas formas: a forma binária que você usou no último desafio e a forma unária.
 
-The unary plus or, in other words, the plus operator `+` applied to a single value, doesn’t do anything to numbers. But if the operand is not a number, the unary plus converts it into a number.
+O sinal de mais unário ou, em outras palavras, o operador de mais `+` aplicado a um único valor, não faz nada com números. Se o operando, no entanto, não for um número, o mais unário o converte em um número.
 
-For example:
+Por exemplo:
 
 ```js
 // No effect on numbers
@@ -26,9 +26,9 @@ console.log( +true ); // 1
 console.log( +"" );   //
 ```
 
-The need to convert strings to numbers arises very often. For example, if you are getting values from HTML form fields, they are usually strings. What if you want to sum them?
+A necessidade de converter strings em números surge com muita frequência. Por exemplo, se você está obtendo valores de campos de formulário HTML, eles geralmente são strings. O que você faria se quisesse somá-los?
 
-The binary plus would add them as strings:
+O sinal de mais binário os adicionaria como strings:
 
 ```js
 let apples = "2";
@@ -37,7 +37,7 @@ let oranges = "3";
 alert( apples + oranges ); // "23", the binary plus concatenates strings
 ```
 
-If you want to treat them as numbers, you need to convert and then sum them:
+Se você quiser tratá-los como números, você precisa convertê-los e depois somá-los:
 
 ```js
 let apples = "2";
@@ -50,14 +50,14 @@ alert( +apples + +oranges ); // 5
 // alert( Number(apples) + Number(oranges) ); // 5
 ```
 
-From a mathematician’s standpoint, the abundance of pluses may seem strange. But from a programmer’s standpoint, there’s nothing special: unary pluses are applied first, they convert strings to numbers, and then the binary plus sums them up.
+Do ponto de vista de um matemático, a abundância de sinais de mais pode parecer estranha. Do ponto de vista de um programador, no entanto, não há nada de especial: os mais unários são aplicados primeiro, convertem strings em números e o mais binário os soma.
 
-Why are unary pluses applied to values before the binary ones? As you’re going to see, that’s because of their _higher_ precedence.
+Por que os mais unários são aplicados aos valores antes dos binários? Como você verá, isso é por causa de sua _maior_ precedência.
 
 # --question--
 
 ## --text--
-Given the explanation of unary and binary `+` operators in JavaScript, how can you correctly sum the string values `'2'` and `'3'` as numbers using unary `+`?
+Dada a explicação dos operadores `+` unário e binário em JavaScript, como você pode somar corretamente os valores de string `'2'` e `'3'` como números usando o `+` unário?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-i.md b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-i.md
index 3e8bf1ce09..cc6e333a4d 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-i.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-learn-variables-and-operators/learn-variables-and-operators-lesson-i.md
@@ -1,17 +1,17 @@
 ---
 id: 65e1b46e500d930ce8ed90ad
-title: Learn Variables and Operators Lesson I
+title: Lição I de Aprenda variáveis e operadores
 challengeType: 15
 dashedName: learn-variables-and-operators-lesson-i
 ---
 
 # --description--
 
-Increasing or decreasing a number by one is among the most common numerical operations.
+Aumentar ou diminuir um número em um é uma das operações numéricas mais comuns.
 
-So, there are special operators for it:
+Então, existem operadores especiais para isso:
 
-- Increment `++` increases a variable by 1:
+- Incremento `++` aumenta uma variável em 1:
 
 ```js
 let counter = 2;
@@ -22,7 +22,7 @@ counter++;
 console.log(counter); // 3
 ```
 
-- Decrement `--` decreases a variable by 1:
+- Decremento `--` diminui uma variável em 1:
 
 ```js
 let counter = 2;
@@ -33,19 +33,19 @@ counter--;
 console.log(counter); // 1
 ```
 
-The operators `++` and `--` can be placed either before or after a variable.
+Os operadores `++` e `--` podem ser colocados antes ou depois de uma variável.
 
-- When the operator goes after the variable, it is in "postfix form": `counter++`.
+- Quando o operador vai depois da variável, está na "forma de pós-fixo": `counter++`.
 
-- The "prefix form" is when the operator goes before the variable: `++counter`.
+- A "forma de prefixo" é quando o operador vai antes da variável: `++counter`.
 
-Both of these statements do the same thing: increase `counter` by `1`.
+Ambas as instruções fazem a mesma coisa: aumentam `counter` em `1`.
 
-Is there any difference? Yes, but you can only see it if you use the returned value of `++/--`  .
+Há alguma diferença? Sim, mas você só pode vê-la se usar o valor retornado de `++/--`.
 
-Let’s clarify. As you know, all operators return a value. Increment/decrement is no exception. The prefix form returns the new value while the postfix form returns the old value (prior to increment/decrement).
+Vamos esclarecer. Como você sabe, todos os operadores retornam um valor. Incremento/decremento não é exceção. A forma prefixada retorna o novo valor enquanto a forma pós-fixada retorna o valor antigo (antes do incremento/decremento).
 
-To see the difference, here’s an example:
+Para ver a diferença, aqui está um exemplo:
 
 ```js
 let counter = 1;
@@ -54,9 +54,9 @@ let a = ++counter; // (*)
 console.log(a); // 2
 ```
 
-To summarize:
+Para resumir:
 
-- If the result of increment/decrement is not used, there is no difference in which form to use:
+- Se o resultado do incremento/decremento não for usado, não há diferença em qual forma usar:
 
 ```js
 let counter = 0;
@@ -66,14 +66,14 @@ counter++;
 console.log( counter ); // 2, the lines above did the same
 ```
 
-- If you’d like to increase a value and immediately use the result of the operator, you need the prefix form:
+- Se você quiser aumentar um valor e usar imediatamente o resultado do operador, você precisa da forma prefixada:
 
 ```js
 let counter = 0;
 console.log( ++counter ); // 1
 ```
 
-- If you’d like to increment a value but use its previous value, you need the postfix form:
+- Se você quiser incrementar um valor mas usar seu valor anterior, você precisa da forma pós-fixada:
 
 ```js 
 let counter = 0;
@@ -84,7 +84,7 @@ console.log( counter++ ); // 0
 
 ## --text--
 
-What is the difference in the result of the two console log statements in the JavaScript code below?
+Qual é a diferença no resultado das duas instruções de registro no console no código JavaScript abaixo?
 
 ```js
 let counter = 1;
@@ -96,19 +96,19 @@ console.log(2 * counter++); // Statement B
 
 ## --answers--
 
-There is no difference; both alert statements will show the same result.
+Não há diferença. As duas instruções de alerta mostrarão o mesmo resultado.
 
 ---
 
-Statement A will log `4` because `++counter` increments the value before the multiplication. Statement B will log `2` because `counter++` increments the value after the multiplication.
+A instrução A registrará `4` porque `++counter` incrementa o valor antes da multiplicação. A instrução B registrará `2` porque `counter++` incrementa o valor após a multiplicação.
 
 ---
 
-Statement A will log `2` because `++counter` is a syntax error. Statement B will log `4` because `counter++` is the correct way to increment a counter.
+A instrução A registrará `2` porque `++counter` é um erro de sintaxe. A instrução B registrará `4` porque `counter++` é a maneira correta de incrementar um contador.
 
 ---
 
-Both statements will log `3` because the counter is incremented in both cases before the `console.log`.
+As duas instruções registrarão `3`, pois o contador é incrementado em ambos os casos antes de `console.log`.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-a.md b/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-a.md
index ca0dd6762c..e007ff3205 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-a.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-a.md
@@ -1,55 +1,55 @@
 ---
 id: 637f704072c65bc8e73dfe36
 videoId: tsEQgGjSmkM
-title: Links and Images Lesson A
+title: Lição A de Links e imagens
 challengeType: 15
 dashedName: links-and-images-lesson-a
 ---
 
 # --description--
 
-To get some practice using links and images throughout this lesson you need an HTML project to work with.
+Para fazer alguns exercícios práticos usando links e imagens nesta lição, você precisará de um projeto de HTML no qual poderá trabalhar.
 
-- Create a new directory named `odin-links-and-images`.
+- Crie um diretório chamado `odin-links-and-images`.
 
-- Within that directory, create a new file named `index.html`.
+- Dentro desse diretório, crie um arquivo e dê a ele o nome de `index.html`.
 
-- Fill in the usual HTML boilerplate.
+- Preencha o boilerplate do HTML de sempre.
 
-- Finally, add the following `h1` to the `body`: `<h1>Homepage</h1>`
+- Por fim, adicione o seguinte `h1` ao `body`: `<h1>Homepage</h1>`
 
-## Anchor Elements
-To create a link in HTML, you use the anchor element. An anchor element is defined by wrapping the text or another HTML element you want to be a link with an `<a>` tag.
+## Elementos de âncora
+Para criar um link em HTML, use o elemento de âncora. Um elemento de âncora é definido agregando o texto ou outro elemento do HTML que você quer que seja um link à tag `<a>`.
 
-Add the following to the `body` of the `index.html` page you created and open it in the browser:
+Adicione o seguinte ao `body` da página `index.html` que você criou e abra a página no navegador:
 
 ```html
 <a>click me</a>
 ```
 
-You may have noticed that clicking this link doesn’t do anything. This is because an anchor tag on its own won’t know where you want to link to. You have to tell it a destination to go to. You do this by using an HTML attribute.
+Você pode ter notado que, ao clicar nesse link, nada acontece. Isso ocorre porque uma tag de âncora sozinha não saberá para onde você quer ir. Você tem que informar a ela um destino. Você faz isso utilizando um atributo do HTML.
 
-An HTML attribute gives additional information to an HTML element and always goes in the element’s opening tag. An attribute is usually made up of two parts: a name, and a value; however, not all attributes require a value. In your case, you need to add an `href` (hyperlink reference) attribute to the opening anchor tag. The value of the `href` attribute is the destination you want your link to go to.
+Um atributo do HTML fornece informações adicionais para um elemento do HTML e sempre vai na tag de abertura do elemento. Um atributo é geralmente composto por duas partes: um nome e um valor. No entanto, nem todos os atributos requerem um valor. No seu caso, você precisa adicionar um atributo `href` (referência de hiperlink) à tag de abertura do elemento de âncora. O valor do atributo `href` é o destino para o qual você quer o seu link vá.
 
-Add the following `href` attribute to the anchor element you created previously and try clicking it again, don’t forget to refresh the browser so the new changes can be applied.
+Adicione o atributo `href` abaixo ao elemento de âncora que você criou anteriormente e tente clicar novamente. Não se esqueça de atualizar o navegador para que as novas alterações possam ser aplicadas.
 
 ```html
 <a href="https://www.theodinproject.com/about">click me</a>
 ```
 
-By default, any text wrapped with an anchor tag without an `href` attribute will look like plain text. If the `href` attribute is present, the browser will give the text a blue color and underline it to signify it is a link.
+Por padrão, qualquer texto encapsulado com uma tag de âncora sem um atributo `href` parecerá texto simples. Se o atributo `href` estiver presente, o navegador dará ao texto uma cor azul e vai sublinhá-lo para representar um link.
 
-It’s worth noting you can use anchor tags to link to any kind of resource on the internet, not just other HTML documents. You can link to videos, pdf files, images, and so on, but for the most part, you will be linking to other HTML documents.
+Vale a pena notar que você pode usar tags de âncora para vincular qualquer tipo de recurso na internet, não apenas outros documentos HTML. Você pode vincular vídeos, arquivos em PDF, imagens e assim por diante. Na maioria das vezes, no entanto, você vinculará a tag a outros documentos HTML.
 
 # --assignment--
 
-Watch Kevin Powell’s HTML Links video above.
+Assista ao vídeo de Kevin Powell sobre links do HTML acima.
 
 # --question--
 
 ## --text--
 
-What HTML tag is used to create a link?
+Qual é a tag do HTML usada para criar um link?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-e.md b/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-e.md
index c4c3e5fbc1..f6fe64c47a 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-e.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-e.md
@@ -8,25 +8,25 @@ dashedName: links-and-images-lesson-e
 
 # --description--
 
-Websites would be fairly boring if they could only display text. Luckily HTML provides a wide variety of elements for displaying all sorts of different media. The most widely used of these is the image element.
+Os sites da web seriam muito chatos se apenas pudessem exibir texto. Felizmente, o HTML fornece uma grande variedade de elementos para exibir todos os tipos diferentes de mídias. O mais utilizado é o elemento de imagem.
 
-To display an image in HTML you use the `<img>` element. Unlike the other elements you have encountered, the `<img>` element is self-closing. Empty, self-closing HTML elements do not need a closing tag.
+Para exibir uma imagem em HTML, você usa o elemento `<img>`. Diferente dos outros elementos que você encontrou, o elemento `<img>` tem fechamento próprio. Os elementos vazios ou de fechamento próprio do HTML não precisam de uma tag de fechamento.
 
-Instead of wrapping content with an opening and closing tag, it embeds an image into the page using a `src` attribute which tells the browser where the image file is located. The `src` attribute works much like the `href` attribute for anchor tags. It can embed an image using both absolute and relative paths.
+Em vez de envolver o conteúdo com uma tag de abertura e fechamento, esse elemento incorpora uma imagem na página usando um atributo `src`, que informa ao navegador onde o arquivo da imagem está localizado. O atributo `src` funciona muito como o atributo `href` para tags de âncora. Ele pode incorporar uma imagem usando caminhos relativos e absolutos.
 
-For example, using an absolute path you can display an image located on The Odin Project site:
+Por exemplo, ao usar um caminho absoluto, você pode exibir uma imagem localizada no site do The Odin Project:
 
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/gORbExZ?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=gORbExZ&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_gORbExZ"></iframe>
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/gORbExZ?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=gORbExZ&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_gORbExZ"></iframe>
 
-To use images that you have on your own websites, you can use a relative path.
+Para usar imagens que você tem em seus próprios sites, você pode usar um caminho relativo.
 
-- Create a new directory named `images` within the `odin-links-and-images` project.
+- Crie um diretório chamado `images` dentro do projeto `odin-links-and-images`.
 
-- Next, download <a href="https://unsplash.com/photos/Mv9hjnEUHR4/download?force=true&w=640" target="_blank">this image</a> and move it into the `images` directory you just created.
+- Em seguida, baixe <a href="https://unsplash.com/photos/Mv9hjnEUHR4/download?force=true&w=640" target="_blank">esta imagem</a> e mova-a para o diretório `imagens` que você acabou de criar.
 
-- Rename the image to `dog.jpg`.
+- Renomeie a imagem para `dog.jpg`.
 
-Finally add the image to the `index.html` file:
+Por fim, adicione a imagem ao arquivo `index.html`:
 
 ```html
 <body>
@@ -39,47 +39,47 @@ Finally add the image to the `index.html` file:
 </body>
 ```
 
-Save the `index.html` file and open it in a browser to view Charles in all his glory.
+Salve o arquivo `index.html` e abra-o em um navegador para conhecer o Charles e ver como ele é lindo.
 
 
-## Parent Directories
+## Diretórios pai
 
-What if you want to use the dog image in the `about` page? You would first have to go up one level out of the pages directory into its parent directory so you could then access the images directory.
+Como usar a imagem do cachorro na página `about`? Primeiro, você precisa subir um nível no diretório de páginas para o diretório pai para depois poder acessar o diretório de imagens.
 
-To go to the parent directory you need to use two dots in the relative filepath like this: `../.` Let’s see this in action, within the `body` of the `about.html` file, add the following image below the heading you added earlier:
+Para subir para o diretório pai, você precisa usar dois pontos no caminho relativo, assim: `../.` Vamos ver isso em ação, dentro do `body` do arquivo `about.html`, adicione a seguinte imagem abaixo do título que você adicionou anteriormente:
 
 ```html
 <img src="../images/dog.jpg">
 ```
 
-To break this down:
+Em detalhes:
 
-- First, you are going to the parent directory of the pages directory which is `odin-links-and-images`.
+- Primeiro, você vai ao diretório pai do diretório das páginas, que é o `odin-links-and-images`.
 
-- Then, from the parent directory, you can go into the `images` directory.
+- Em seguida, a partir do diretório pai, você pode ir para o diretório `images`.
 
-- Finally, you can access the `dog.jpg` file.
+- Por fim, você pode acessar o arquivo `dog.jpg`.
 
-Using the metaphor we used earlier, using `../` in a filepath is kind of like stepping out from the room you are currently in to the main hallway so you can go to another room.
+Usando a metáfora que usamos anteriormente, usar `../` em um caminho de arquivo é como sair do quarto em que você está no momento, indo para o corredor principal para que você possa chegar à sala.
 
-## `Alt` attribute
+## Atributo `Alt`
 
-Besides the `src` attribute, every image element should also have an `alt` (alternative text) attribute.
+Além do atributo `src`, cada elemento de imagem deve ter também um atributo `alt` (texto alternativo).
 
-The `alt` attribute is used to describe an image. It will be used in place of the image if it cannot be loaded. It is also used with screen readers to describe what the image is to visually impaired users.
+O atributo `alt` é usado para descrever uma imagem. Ele será usado no lugar da imagem, caso ela não possa ser carregada. Ele também é usado com leitores de tela para descrever a imagem para usuários com deficiência visual.
 
-This is how the The Odin Project logo example you used earlier looks with an `alt` attribute included:
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_2" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/ExXjoEp?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=ExXjoEp&amp;user=TheOdinProjectExamples&amp;name=cp_embed_2" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_ExXjoEp"></iframe>
+É assim que o logotipo do The Odin Project que você usou anteriormente fica com um atributo `alt` incluído:
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_2" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/ExXjoEp?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=ExXjoEp&amp;user=TheOdinProjectExamples&amp;name=cp_embed_2" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_ExXjoEp"></iframe>
 
 # --assignment--
 
-Watch Kevin Powell’s HTML Images Video above.
+Assista ao vídeo de Kevin Powell sobre imagens do HTML acima.
 
 # --question--
 
 ## --text--
 
-Which tag is used to display an image?
+Qual é a tag usada para exibir uma imagem?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-f.md b/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-f.md
index 5ea069897a..91ccd84fc4 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-f.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-f.md
@@ -1,31 +1,31 @@
 ---
 id: 637f701c72c65bc8e73dfe31
-title: Links and Images Lesson F
+title: Lição F de Links e imagens
 challengeType: 15
 dashedName: links-and-images-lesson-f
 ---
 
 # --description--
 
-Websites would be fairly boring if they could only display text. Luckily HTML provides a wide variety of elements for displaying all sorts of different media. The most widely used of these is the image element.
+Os sites da web seriam muito chatos se apenas pudessem exibir texto. Felizmente, o HTML fornece uma grande variedade de elementos para exibir todos os tipos diferentes de mídias. O mais utilizado é o elemento de imagem.
 
-To display an image in HTML you use the `<img>` element. Unlike the other elements you have encountered, the `<img>` element is self-closing. Empty, self-closing HTML elements do not need a closing tag.
+Para exibir uma imagem em HTML, você usa o elemento `<img>`. Diferente dos outros elementos que você encontrou, o elemento `<img>` tem fechamento próprio. Os elementos vazios ou de fechamento próprio do HTML não precisam de uma tag de fechamento.
 
-Instead of wrapping content with an opening and closing tag, it embeds an image into the page using a `src` attribute which tells the browser where the image file is located. The `src` attribute works much like the `href` attribute for anchor tags. It can embed an image using both absolute and relative paths.
+Em vez de envolver o conteúdo com uma tag de abertura e fechamento, esse elemento incorpora uma imagem na página usando um atributo `src`, que informa ao navegador onde o arquivo da imagem está localizado. O atributo `src` funciona muito como o atributo `href` para tags de âncora. Ele pode incorporar uma imagem usando caminhos relativos e absolutos.
 
-For example, using an absolute path you can display an image located on The Odin Project site:
+Por exemplo, ao usar um caminho absoluto, você pode exibir uma imagem localizada no site do The Odin Project:
 
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/gORbExZ?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=gORbExZ&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_gORbExZ"></iframe>
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/gORbExZ?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=gORbExZ&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_gORbExZ"></iframe>
 
-To use images that you have on your own websites, you can use a relative path.
+Para usar imagens que você tem em seus próprios sites, você pode usar um caminho relativo.
 
-- Create a new directory named `images` within the `odin-links-and-images` project.
+- Crie um diretório chamado `images` dentro do projeto `odin-links-and-images`.
 
-- Next, download <a href="https://unsplash.com/photos/Mv9hjnEUHR4/download?force=true&w=640" target="_blank">this image</a> and move it into the images directory you just created.
+- Em seguida, baixe <a href="https://unsplash.com/photos/Mv9hjnEUHR4/download?force=true&w=640" target="_blank">esta imagem</a> e mova-a para o diretório de imagens que você acabou de criar.
 
-- Rename the image to `dog.jpg`.
+- Renomeie a imagem para `dog.jpg`.
 
-Finally add the image to the `index.html` file:
+Por fim, adicione a imagem ao arquivo `index.html`:
 
 ```html
 <body>
@@ -38,55 +38,55 @@ Finally add the image to the `index.html` file:
 </body>
 ```
 
-Save the `index.html` file and open it in a browser to view Charles in all his glory.
+Salve o arquivo `index.html` e abra-o em um navegador para conhecer o Charles e ver como ele é lindo.
 
 
-## Parent Directories
+## Diretórios pai
 
-What if you want to use the dog image in the `about` page? You would first have to go up one level out of the pages directory into its parent directory so you could then access the images directory.
+Como usar a imagem do cachorro na página `about`? Primeiro, você precisa subir um nível no diretório de páginas para o diretório pai para depois poder acessar o diretório de imagens.
 
-To go to the parent directory you need to use two dots in the relative filepath like this: `../.` Let’s see this in action, within the `body` of the `about.html` file, add the following image below the heading you added earlier:
+Para subir para o diretório pai, você precisa usar dois pontos no caminho relativo, assim: `../.` Vamos ver isso em ação, dentro do `body` do arquivo `about.html`, adicione a seguinte imagem abaixo do título que você adicionou anteriormente:
 
 ```html
 <img src="../images/dog.jpg">
 ```
 
-To break this down:
+Em detalhes:
 
-- First, you are going to the parent directory of the pages directory which is `odin-links-and-images`.
+- Primeiro, você vai ao diretório pai do diretório das páginas, que é o `odin-links-and-images`.
 
-- Then, from the parent directory, you can go into the `images` directory.
+- Em seguida, a partir do diretório pai, você pode ir para o diretório `images`.
 
-- Finally, you can access the `dog.jpg` file.
+- Por fim, você pode acessar o arquivo `dog.jpg`.
 
-Using the metaphor we used earlier, using `../` in a filepath is kind of like stepping out from the room you are currently in to the main hallway so you can go to another room.
+Usando a metáfora que usamos anteriormente, usar `../` em um caminho de arquivo é como sair do quarto em que você está no momento, indo para o corredor principal para que você possa chegar à sala.
 
-## Alt attribute
+## Atributo alt
 
-Besides the `src` attribute, every image element should also have an `alt` (alternative text) attribute.
+Além do atributo `src`, cada elemento de imagem deve ter também um atributo `alt` (texto alternativo).
 
-The `alt` attribute is used to describe an image. It will be used in place of the image if it cannot be loaded. It is also used with screen readers to describe what the image is to visually impaired users.
+O atributo `alt` é usado para descrever uma imagem. Ele será usado no lugar da imagem, caso ela não possa ser carregada. Ele também é usado com leitores de tela para descrever a imagem para usuários com deficiência visual.
 
-This is how the The Odin Project logo example you used earlier looks with an alt attribute included:
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_2" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/ExXjoEp?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=ExXjoEp&amp;user=TheOdinProjectExamples&amp;name=cp_embed_2" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_ExXjoEp"></iframe>
+É assim que o logotipo do The Odin Project que você usou anteriormente fica com um atributo alt incluído:
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_2" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/ExXjoEp?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=ExXjoEp&amp;user=TheOdinProjectExamples&amp;name=cp_embed_2" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_ExXjoEp"></iframe>
 
 # --question--
 
 ## --text--
 
-What two attributes do images always need to have?
+Quais são os dois atributos que as imagens sempre precisam ter?
 
 ## --answers--
 
-`href` and `alt`
+`href` e `alt`
 
 ---
 
-`name` and `href`
+`name` e `href`
 
 ---
 
-`alt` and `src`
+`alt` e `src`
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-g.md b/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-g.md
index 71bdf4add9..1de7cc3990 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-g.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-links-and-images/links-and-images-lesson-g.md
@@ -1,31 +1,31 @@
 ---
 id: 637f701572c65bc8e73dfe30
-title: Links and Images Lesson G
+title: Lição G de Links e imagens
 challengeType: 15
 dashedName: links-and-images-lesson-g
 ---
 
 # --description--
 
-Websites would be fairly boring if they could only display text. Luckily HTML provides a wide variety of elements for displaying all sorts of different media. The most widely used of these is the image element.
+Os sites da web seriam muito chatos se apenas pudessem exibir texto. Felizmente, o HTML fornece uma grande variedade de elementos para exibir todos os tipos diferentes de mídias. O mais utilizado é o elemento de imagem.
 
-To display an image in HTML you use the `<img>` element. Unlike the other elements you have encountered, the `<img>` element is self-closing. Empty, self-closing HTML elements do not need a closing tag.
+Para exibir uma imagem em HTML, você usa o elemento `<img>`. Diferente dos outros elementos que você encontrou, o elemento `<img>` tem fechamento próprio. Os elementos vazios ou de fechamento próprio do HTML não precisam de uma tag de fechamento.
 
-Instead of wrapping content with an opening and closing tag, it embeds an image into the page using a `src` attribute which tells the browser where the image file is located. The `src` attribute works much like the `href` attribute for anchor tags. It can embed an image using both absolute and relative paths.
+Em vez de envolver o conteúdo com uma tag de abertura e uma de fechamento, esse elemento incorpora uma imagem na página usando um atributo `src`, que informa ao navegador onde o arquivo da imagem está localizado. O atributo `src` funciona muito como o atributo `href` para tags de âncora. Ele pode incorporar uma imagem usando caminhos relativos e absolutos.
 
-For example, using an absolute path you can display an image located on The Odin Project site:
+Por exemplo, ao usar um caminho absoluto, você pode exibir uma imagem localizada no site do The Odin Project:
 
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/gORbExZ?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=gORbExZ&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_gORbExZ"></iframe>
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/gORbExZ?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=gORbExZ&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_gORbExZ"></iframe>
 
-To use images that you have on your own websites, you can use a relative path.
+Para usar imagens que você tem em seus próprios sites, você pode usar um caminho relativo.
 
-- Create a new directory named `images` within the `odin-links-and-images` project.
+- Crie um diretório chamado `images` dentro do projeto `odin-links-and-images`.
 
-- Next, download <a href="https://unsplash.com/photos/Mv9hjnEUHR4/download?force=true&w=640" target="_blank">this image</a> and move it into the images directory you just created.
+- Em seguida, baixe <a href="https://unsplash.com/photos/Mv9hjnEUHR4/download?force=true&w=640" target="_blank">esta imagem</a> e mova-a para o diretório de imagens que você acabou de criar.
 
-- Rename the image to `dog.jpg`.
+- Renomeie a imagem para `dog.jpg`.
 
-Finally add the image to the `index.html` file:
+Por fim, adicione a imagem ao arquivo `index.html`:
 
 ```html
 <body>
@@ -38,43 +38,43 @@ Finally add the image to the `index.html` file:
 </body>
 ```
 
-Save the `index.html` file and open it in a browser to view Charles in all his glory.
+Salve o arquivo `index.html` e abra-o em um navegador para conhecer o Charles e ver como ele é lindo.
 
 
-## Parent Directories
+## Diretórios pai
 
-What if you want to use the dog image in the `about` page? You would first have to go up one level out of the pages directory into its parent directory so you could then access the images directory.
+Como usar a imagem do cachorro na página `about`? Primeiro, você precisa subir um nível no diretório de páginas para o diretório pai para depois poder acessar o diretório de imagens.
 
-To go to the parent directory you need to use two dots in the relative filepath like this: `../.` Let’s see this in action, within the `body` of the `about.html` file, add the following image below the heading you added earlier:
+Para subir para o diretório pai, você precisa usar dois pontos no caminho relativo, assim: `../.` Vamos ver isso em ação! Dentro do `body` do arquivo `about.html`, adicione a seguinte imagem abaixo do título que você adicionou anteriormente:
 
 ```html
 <img src="../images/dog.jpg">
 ```
 
-To break this down:
+Em detalhes:
 
-- First, you are going to the parent directory of the pages directory which is `odin-links-and-images`.
+- Primeiro, você vai ao diretório pai do diretório das páginas, que é o `odin-links-and-images`.
 
-- Then, from the parent directory, you can go into the `images` directory.
+- Em seguida, a partir do diretório pai, você pode ir para o diretório `images`.
 
-- Finally, you can access the `dog.jpg` file.
+- Por fim, você pode acessar o arquivo `dog.jpg`.
 
-Using the metaphor we used earlier, using `../` in a filepath is kind of like stepping out from the room you are currently in to the main hallway so you can go to another room.
+Usando a metáfora que usamos anteriormente, usar `../` em um caminho de arquivo é como sair do quarto em que você está no momento, indo para o corredor principal para que você possa chegar à sala.
 
-## Alt attribute
+## Atributo alt
 
-Besides the `src` attribute, every image element should also have an `alt` (alternative text) attribute.
+Além do atributo `src`, cada elemento de imagem deve ter também um atributo `alt` (texto alternativo).
 
-The `alt` attribute is used to describe an image. It will be used in place of the image if it cannot be loaded. It is also used with screen readers to describe what the image is to visually impaired users.
+O atributo `alt` é usado para descrever uma imagem. Ele será usado no lugar da imagem, caso ela não possa ser carregada. Ele também é usado com leitores de tela para descrever a imagem para usuários com deficiência visual.
 
-This is how the The Odin Project logo example you used earlier looks with an alt attribute included:
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_2" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/ExXjoEp?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=ExXjoEp&amp;user=TheOdinProjectExamples&amp;name=cp_embed_2" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_ExXjoEp"></iframe>
+É assim que o logotipo do The Odin Project que você usou anteriormente fica com um atributo alt incluído:
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_2" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/ExXjoEp?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=ExXjoEp&amp;user=TheOdinProjectExamples&amp;name=cp_embed_2" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_ExXjoEp"></iframe>
 
 # --question--
 
 ## --text--
 
-How do you access a parent directory in a filepath?
+Como você acessa um diretório pai em um caminho de arquivo?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-c.md b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-c.md
index 0af6ab5fc2..cfde4ec0cc 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-c.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-c.md
@@ -1,44 +1,44 @@
 ---
 id: 64a5551d02815a7d323aab8a
-title: The Box Model Lesson C
+title: Lição C sobre o modelo de caixas
 challengeType: 15
 dashedName: the-box-model-lesson-c
 --- 
 # --description--
 
-In the Elements pane, you can see the entire HTML structure of your page. You can click on any of the elements in this pane to select that specific element. Alternatively, you can click the blue-highlighted icon shown below on the left, and hover over any element on the page.
+No painel Elementos, é possível ver toda a estrutura do HTML da página. Você pode clicar em qualquer um dos elementos nesse painel para selecionar o elemento específico. Como alternativa, você pode clicar no ícone realçado em azul mostrado abaixo e à esquerda, passando o mouse sobre qualquer elemento da página.
 
 <img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/inspector-icon.png" alt="Um ambiente de desenvolvimento para a web com ferramentas de desenvolvedor abertas, destacando um ícone azul de inspetor no canto superior esquerdo para selecionar elementos da página da web para visualizar a estrutura HTML e estilos." />
 
-When an element is selected, the Styles tab will show all the currently applied styles, as well as any styles that are being overwritten (indicated by a strikethrough of the text). For example, if you use the inspector to click on the “Your Career in Web Development Starts Here” header on <a href="https://www.theodinproject.com/" target="_blank">the The Odin Project homepage</a>, on the right-hand side you’ll see all the styles that are currently affecting the element, as seen below:
+Quando um elemento é selecionado, a guia Estilos mostrará todos os estilos atualmente aplicados, assim como quaisquer estilos que estão sendo substituídos (indicado por um texto com um risco no meio). Por exemplo, se você usar o inspetor para clicar no cabeçalho "Your Career in Web Development Starts Here" na <a href="https://www.theodinproject.com/" target="_blank">página do The Odin Project</a>, no lado direito, você verá todos os estilos que atualmente estão afetando o elemento, como vistos abaixo:
 
-<img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/overwritten-style.png" alt="CSS code snippet in the developer console showing .hero_main-heading with applied margin-bottom: 100px, padding-bottom: 1.875rem, .accent color #ce973e. h1 style rules include font-size, weight, letter-spacing, with its margin-bottom: 2rem overridden." />
+<img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/overwritten-style.png" alt="Trecho de código do CSS no console de desenvolvedor mostrando .hero_main-heading com margin-bottom: 100px, padding-bottom: 1.875rem e .accent color #ce973e aplicados. As regras de estilo de h1 incluem tamanho da fonte, peso, espaçamento das letras, e margem inferior de 2rem sobrescrita." />
 
 # --assignment--
 
-Play around with Chrome Dev Tools and see if you can answer the following question.
+Divirta-se um pouco com as ferramentas de desenvolvimento do Chrome e veja se consegue responder à seguinte pergunta.
 
 # --question--
 
 ## --text--
 
-Which feature in the Elements pane allows you to select any element on a webpage by hovering over it?
+Qual recurso no painel Elementos permite selecionar qualquer elemento em uma página da web, passando o mouse sobre ele?
 
 ## --answers--
 
-Blue-highlighted icon
+O ícone realçado em azul
 
 ---
 
-Styles tab
+A guia Estilos
 
 ---
 
-Inspector tab
+A guia Inspetor
 
 ---
 
-HTML structure view
+A visualização de estrutura do HTML
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-d.md b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-d.md
index ddf45d16db..0e885816cd 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-d.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-d.md
@@ -1,44 +1,44 @@
 ---
 id: 64a55a6102815a7d323aab8b
-title: The Box Model Lesson D
+title: Lição D sobre o modelo de caixas
 challengeType: 15
 dashedName: the-box-model-lesson-d
 --- 
 # --description--
 
-In the Elements pane, you can see the entire HTML structure of your page. You can click on any of the elements in this pane to select that specific element. Alternatively, you can click the blue-highlighted icon shown below on the left, and hover over any element on the page.
+No painel Elementos, é possível ver toda a estrutura do HTML da página. Você pode clicar em qualquer um dos elementos nesse painel para selecionar o elemento específico. Como alternativa, você pode clicar no ícone realçado em azul mostrado abaixo e à esquerda, passando o mouse sobre qualquer elemento da página.
 
 <img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/inspector-icon.png" alt="Um ambiente de desenvolvimento para a web com ferramentas de desenvolvedor abertas, destacando um ícone azul de inspetor no canto superior esquerdo para selecionar elementos da página da web para visualizar a estrutura HTML e estilos." />
 
-When an element is selected, the Styles tab will show all the currently applied styles, as well as any styles that are being overwritten (indicated by a strikethrough of the text). For example, if you use the inspector to click on the “Your Career in Web Development Starts Here” header on <a href="https://www.theodinproject.com/" target="_blank">the The Odin Project homepage</a>, on the right-hand side you’ll see all the styles that are currently affecting the element, as seen below:
+Quando um elemento é selecionado, a guia Estilos mostrará todos os estilos atualmente aplicados, assim como quaisquer estilos que estão sendo substituídos (indicado por um texto com um risco no meio). Por exemplo, se você usar o inspetor para clicar no cabeçalho "Your Career in Web Development Starts Here" na <a href="https://www.theodinproject.com/" target="_blank">página do The Odin Project</a>, no lado direito, você verá todos os estilos que atualmente estão afetando o elemento, como vistos abaixo:
 
-<img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/overwritten-style.png" alt="CSS code snippet in the developer console showing .hero_main-heading with applied margin-bottom: 100px, padding-bottom: 1.875rem, .accent color #ce973e. h1 style rules include font-size, weight, letter-spacing, with its margin-bottom: 2rem overridden." />
+<img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/overwritten-style.png" alt="Trecho de código do CSS no console de desenvolvedor mostrando .hero_main-heading com margin-bottom: 100px, padding-bottom: 1.875rem e .accent color #ce973e aplicados. As regras de estilo de h1 incluem tamanho da fonte, peso, espaçamento das letras e margem inferior de 2rem sobrescrita." />
 
 # --assignment--
 
-Play around with Chrome Dev Tools and see if you can answer the following question.
+Divirta-se um pouco com as ferramentas de desenvolvimento do Chrome e veja se consegue responder à seguinte pergunta.
 
 # --question--
 
 ## --text--
 
-In the Styles pane, what information can you view about an element when it is selected?
+No painel Estilos, que informação você pode ver sobre um elemento quando ele é selecionado?
 
 ## --answers--
 
-HTML structure and CSS rules
+A estrutura do HTML e as regras do CSS
 
 ---
 
-Styles tab
+A guia Estilos
 
 ---
 
-Inspector tab
+A guia Inspetor
 
 ---
 
-Applied styles and overwritten styles.
+Os estilos aplicados e os estilos sobrescritos.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-e.md b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-e.md
index e2b9e44feb..8ecb98f691 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-e.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-e.md
@@ -1,36 +1,36 @@
 ---
 id: 64a669f77a7d00f97013ed0c
-title: The Box Model Lesson E
+title: Lição E sobre o modelo de caixas
 challengeType: 15
 dashedName: the-box-model-lesson-e
 --- 
 # --description--
 
-Now that you understand the basic syntax of HTML and CSS, we’re going to get serious. The most important skills you need to master with CSS are positioning and layout. Changing fonts and colors is a crucial skill, but being able to put things exactly where you want them on a webpage is even more crucial. After all, how many webpages can you find where absolutely every element is just stacked one on top of another?
+Agora que você entende a sintaxe básica do HTML e do CSS, vamos nos aprofundar um pouco mais. As habilidades mais importantes que você precisa dominar em CSS são o posicionamento e o layout. Alterar fontes e cores é uma habilidade crucial, mas ser capaz de colocar as coisas exatamente onde você as quer numa página da web é mais importante ainda. Afinal, quantas páginas podem ser encontradas onde os elementos estão simplesmente empilhados uns em cima dos outros?
 
-Learning to position elements on a webpage is not that difficult once you understand just a few key concepts. Unfortunately, many learners race through learning HTML and CSS to get to JavaScript and end up missing these fundamental concepts. This leads to frustration, pain, (and funny gifs) because all the JavaScript skills in the world are meaningless if you can’t stick your elements on the page where you need them to be. So with that in mind, let’s get started.
+Aprender a posicionar elementos em uma página da web não é tão difícil quando você entende apenas alguns conceitos-chave. Infelizmente, muitos alunos passam rapidamente pelo aprendizado de HTML e CSS para chegar ao JavaScript e acabam perdendo esses conceitos fundamentais. Isso leva à frustração, dor e a alguns gifs engraçados, pois todas as habilidades em JavaScript no mundo perdem o sentido se você não puder encaixar seus elementos na página onde você precisa que eles estejam. Tendo isso em mente, vamos começar.
 
 # --question--
 
 ## --text--
 
-Why is it important to have a solid understanding of CSS in web development?
+Por que é importante ter uma compreensão satisfatória do CSS no desenvolvimento para a web?
 
 ## --answers--
 
-It allows you to create complex animations and interactive effects.
+Ele permite que você crie animações complexas e efeitos interativos.
 
 ---
 
-It allows you to create complex animations and interactive effects.
+Ele permite que você crie animações complexas e efeitos interativos.
 
 ---
 
-It helps in optimizing database queries for improved performance.
+Ele ajuda a otimizar as consultas ao banco de dados para um melhor desempenho.
 
 ---
 
-It enables you to style and design webpages with precision and control.
+Ele permite a você estilizar e projetar páginas da web com precisão e controle.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-h.md b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-h.md
index 9e5c2dda6e..55945b634d 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-h.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-h.md
@@ -1,35 +1,35 @@
 ---
 id: 64a674937a7d00f97013ed0f
 videoId: rIO5326FgPE
-title: The Box Model Lesson H
+title: Lição H sobre o modelo de caixas
 challengeType: 15
 dashedName: the-box-model-lesson-h
 --- 
 # --description--
 
-Because the box model concept is so incredibly fundamental, let’s dig a bit deeper with <a href="https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/The_box_model#what_is_the_css_box_model" target="_blank">this lesson from MDN</a>. Ela trata do mesmo material que o vídeo acima e apresentará as caixas em linha, das quais trataremos na próxima lição. Pay close attention to the examples and take the time to experiment with their in-browser editor!
+Como o conceito do modelo de caixas é incrivelmente fundamental, vamos aprofundar um pouco com <a href="https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/The_box_model#what_is_the_css_box_model" target="_blank">esta lição do MDN</a>. Ela trata do mesmo material que o vídeo acima e apresentará as caixas em linha, das quais trataremos na próxima lição. Preste muita atenção nos exemplos e reserve um tempo para experimentar com o editor no navegador!
 
 # --question--
 
 ## --text--
 
-What does the box-sizing CSS property do?
+O que faz a propriedade box-sizing do CSS?
 
 ## --answers--
 
-It determines the order of the box-model properties.
+Determina a ordem das propriedades do modelo de caixas.
 
 ---
 
-It specifies the position of an element on the webpage.
+Especifica a posição de um elemento na página da web.
 
 ---
 
-It controls how the total width and height of an element are calculated.
+Controla como a largura e a altura total de um elemento são calculadas.
 
 ---
 
-It sets the background color of an element.
+Define a cor de fundo de um elemento.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-i.md b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-i.md
index 07d6b57d56..e4fa240f6f 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-i.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-i.md
@@ -1,35 +1,35 @@
 ---
 id: 64a6749a7a7d00f97013ed10
 videoId: rIO5326FgPE
-title: The Box Model Lesson I
+title: Lição I sobre o modelo de caixas
 challengeType: 15
 dashedName: the-box-model-lesson-i
 --- 
 # --description--
 
-Because the box model concept is so incredibly fundamental, let’s dig a bit deeper with <a href="https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/The_box_model#what_is_the_css_box_model" target="_blank">this lesson from MDN</a>. Ela trata do mesmo material que o vídeo acima e apresentará as caixas em linha, das quais trataremos na próxima lição. Pay close attention to the examples and take the time to experiment with their in-browser editor!
+Como o conceito do modelo de caixas é incrivelmente fundamental, vamos aprofundar um pouco com <a href="https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/The_box_model#what_is_the_css_box_model" target="_blank">esta lição do MDN</a>. Ela trata do mesmo material que o vídeo acima e apresentará as caixas em linha, das quais trataremos na próxima lição. Preste muita atenção nos exemplos e reserve um tempo para experimentar com o editor no navegador!
 
 # --question--
 
 ## --text--
 
-What is the difference between the standard and alternative box model?
+Qual é a diferença entre o modelo de caixas padrão e o modelo alternativo?
 
 ## --answers--
 
-The standard box model calculates the width and height of an element based on the content alone, while the alternative box model calculates based on the content plus padding and border.
+O modelo de caixas padrão calcula a largura e a altura de um elemento com base exclusivamente no conteúdo, enquanto o modelo alternativo de caixas calcula ambos com base no conteúdo mais preenchimento e borda.
 
 ---
 
-The standard box model includes content, padding, and border, while the alternative box model includes only the content.
+O modelo de caixas padrão inclui conteúdo, preenchimento e borda, enquanto o modelo de caixas alternativo inclui apenas o conteúdo.
 
 ---
 
-The standard box model and the alternative box model are the same and have no differences.
+O modelo de caixas padrão e o modelo de caixas alternativo são a mesma coisa, não tendo diferenças.
 
 ---
 
-The standard box model includes only the content, while the alternative box model includes content, padding, and border.
+O modelo de caixas padrão inclui apenas o conteúdo, enquanto o modelo alternativo inclui conteúdo, preenchimento e borda.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-j.md b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-j.md
index d7e70da8ed..675b280b9b 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-j.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-j.md
@@ -1,19 +1,19 @@
 ---
 id: 64a674a47a7d00f97013ed11
 videoId: rIO5326FgPE
-title: The Box Model Lesson J
+title: Lição J sobre o modelo de caixas
 challengeType: 15
 dashedName: the-box-model-lesson-j
 --- 
 # --description--
 
-Because the box model concept is so incredibly fundamental, let’s dig a bit deeper with <a href="https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/The_box_model#what_is_the_css_box_model" target="_blank">this lesson from MDN</a>. Ela trata do mesmo material que o vídeo acima e apresentará as caixas em linha, das quais trataremos na próxima lição. Pay close attention to the examples and take the time to experiment with their in-browser editor!
+Como o conceito do modelo de caixas é incrivelmente fundamental, vamos aprofundar um pouco com <a href="https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/The_box_model#what_is_the_css_box_model" target="_blank">esta lição do MDN</a>. Ela trata do mesmo material que o vídeo acima e apresentará as caixas em linha, das quais trataremos na próxima lição. Preste muita atenção nos exemplos e reserve um tempo para experimentar com o editor no navegador!
 
 # --question--
 
 ## --text--
 
-Would you use margin or padding to create more space between 2 elements?
+Você usaria margin ou padding para criar mais espaço entre dois elementos?
 
 ## --answers--
 
@@ -21,11 +21,11 @@ Padding
 
 ---
 
-Both margin and padding can be used interchangeably
+Margin e padding podem ser usados sem distinção
 
 ---
 
-Neither margin nor padding can be used to create more space between elements
+Margin e padding não podem ser usados para criar mais espaço entre elementos
 
 ---
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-k.md b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-k.md
index 084f448008..0ed5a60f82 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-k.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-the-box-model/the-box-model-lesson-k.md
@@ -7,13 +7,13 @@ dashedName: the-box-model-lesson-k
 --- 
 # --description--
 
-Because the box model concept is so incredibly fundamental, let’s dig a bit deeper with <a href="https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/The_box_model#what_is_the_css_box_model" target="_blank">this lesson from MDN</a>. Ela trata do mesmo material que o vídeo acima e apresentará as caixas em linha, das quais trataremos na próxima lição. Pay close attention to the examples and take the time to experiment with their in-browser editor!
+Como o conceito do modelo de caixas é incrivelmente fundamental, vamos aprofundar um pouco com <a href="https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/The_box_model#what_is_the_css_box_model" target="_blank">esta lição do MDN</a>. Ela trata do mesmo material que o vídeo acima e apresentará as caixas em linha, das quais trataremos na próxima lição. Preste muita atenção nos exemplos e reserve um tempo para experimentar com o editor no navegador!
 
 # --question--
 
 ## --text--
 
-Which CSS property would you use to create more space between the contents of an element and its border?
+Qual propriedade do CSS você usaria para criar mais espaço entre o conteúdo de um elemento e sua borda?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-a.md b/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-a.md
index e44f4fa753..96e4efba37 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-a.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-a.md
@@ -1,14 +1,14 @@
 ---
 id: 637f4e5872c65bc8e73dfe27
 videoId: yqcd-XkxZNM
-title: Working With Text Lesson A
+title: Lição A de Trabalhando com textos
 challengeType: 15
 dashedName: working-with-text-lesson-a
 ---
 
 # --description--
 
-What would you expect the following text to output on an HTML page?
+O que você esperaria que o seguinte texto exibisse em uma página HTML?
 
 ```html
 <body>
@@ -20,27 +20,27 @@ What would you expect the following text to output on an HTML page?
 </body>
 ```
 
-It looks like two paragraphs of text, and so you might expect it to display in that way. However that is not the case, as you can see in the output below:
+Parece que há dois parágrafos do texto. Ou seja, pode-se esperar que sejam exibidos desse modo. No entanto, esse não é o caso, como você pode ver pelo resultado abaixo:
 
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/xxrKqeV?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=xxrKqeV&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_xxrKqeV"></iframe>
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_1" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/xxrKqeV?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=xxrKqeV&amp;user=TheOdinProjectExamples&amp;name=cp_embed_1" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_xxrKqeV"></iframe>
 
-When the browser encounters new lines like this in your HTML, it will compress them down into one single space. The result of this compression is that all of the text is clumped together into one long line.
+Quando o navegador encontrar novas linhas como essa em seu HTML, ele as comprimirá em um único espaço. O resultado desta compressão é que todo o texto é colocado em uma única linha.
 
-If you want to create paragraphs in HTML, you need to use the paragraph element, which will add a newline after each of your paragraphs. A paragraph element is defined by wrapping text content with a `<p>` tag.
+Se quiser criar parágrafos em HTML, é preciso utilizar o elemento de parágrafo, que acrescentará uma nova linha após cada um dos parágrafos. Um elemento de parágrafo é definido envolvendo o conteúdo do texto com uma tag `<p>`.
 
-Changing our example from before to use paragraph elements fixes the issue:
+Ao mudar nosso exemplo de antes para usar elementos dos parágrafos, corrigimos o problema:
 
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_2" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/mdwbmdp?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=mdwbmdp&amp;user=TheOdinProjectExamples&amp;name=cp_embed_2" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_mdwbmdp"></iframe>
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_2" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/mdwbmdp?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=mdwbmdp&amp;user=TheOdinProjectExamples&amp;name=cp_embed_2" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_mdwbmdp"></iframe>
 
 # --assignment--
 
-Watch and follow along to Kevin Powell’s HTML Paragraph and Headings Video above.
+Assista o vídeo de Kevin Powell sobre Parágrafos e títulos do HTML acima.
 
 # --question--
 
 ## --text--
 
-How do you create a paragraph in HTML?
+Como se cria um parágrafo em HTML?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-b.md b/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-b.md
index 390147c962..c8f597851c 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-b.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-b.md
@@ -1,38 +1,38 @@
 ---
 id: 637f4e5f72c65bc8e73dfe28
-title: Working With Text Lesson B
+title: Lição B de Trabalhando com textos
 challengeType: 15
 dashedName: working-with-text-lesson-b
 ---
 
 # --description--
 
-Headings are different from other HTML text elements: they are displayed larger and bolder than other text to signify that they are headings.
+Títulos são diferentes de outros elementos de texto do HTML: eles são exibidos maiores e com a fonte mais forte do que outros textos para representar que são títulos.
 
-There are 6 different levels of headings starting from `<h1>` to `<h6>`. The number within a heading tag represents that heading’s level. The largest and most important heading is `h1`, while `h6` is the tiniest heading at the lowest level.
+Existem 6 níveis diferentes de títulos, de `<h1>` até `<h6>`. O número dentro de uma tag de título representa o nível desse título. O título maior e mais importante é `h1`, enquanto `h6` é o menor título, de nível mais baixo.
 
-Headings are defined much like paragraphs. For example, to create an `h1` heading, we wrap our heading text in a `<h1>` tag.
+Os títulos são definidos do mesmo modo que os parágrafos. Por exemplo, para criar um título `h1`, envolvemos o texto do título com uma tag `<h1>`.
 
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_3" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/LYLPLbg?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=LYLPLbg&amp;user=TheOdinProjectExamples&amp;name=cp_embed_3" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_LYLPLbg"></iframe>
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_3" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/LYLPLbg?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=LYLPLbg&amp;user=TheOdinProjectExamples&amp;name=cp_embed_3" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_LYLPLbg"></iframe>
 
-Using the correct level of heading is important as levels provide a hierarchy to the content. An `h1` heading should always be used for the heading of the overall page, and the lower level headings should be used as the headings for content in smaller sections of the page.
+Usar o nível correto de título é importante porque os níveis fornecem uma hierarquia para o conteúdo. Um título `h1` deve ser sempre usado para o título geral da página. Os títulos de nível inferior devem ser usados como títulos para o conteúdo em seções menores da página.
 
 # --question--
 ## --text--
 
-How many different levels of headings are there and what is the difference between them?
+Quantos níveis diferentes de títulos existem e qual é a diferença entre eles?
 
 ## --answers--
 
-There are 5 different levels of headings. `h5` is the smallest and least important heading, and `h1` is the largest and most important heading.
+Existem 5 níveis diferentes de títulos. `h5` é o título menor e de menor importância, enquanto `h1` é a maior e mais importante.
 
 ---
 
-There are 6 different levels of headings. `h6` is the largest and most important heading, and `h1` is the smallest and least important heading.
+Existem 6 níveis diferentes de títulos. `h6` é o título maior e de maior importância, enquanto `h1` é o menor e menos importante.
 
 ---
 
-There are 6 different levels of headings. `h1` is the largest and most important heading, and `h6` is the smallest and least important heading.
+Existem 6 níveis diferentes de títulos. `h1` é o título maior e de maior importância, enquanto `h6` é o menor e menos importante.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-d.md b/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-d.md
index 0e03f07318..a2eea2f028 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-d.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-d.md
@@ -1,25 +1,25 @@
 ---
 id: 637f4e6e72c65bc8e73dfe2a
-title: Working With Text Lesson D
+title: Lição D de Trabalhando com textos
 challengeType: 15
 dashedName: working-with-text-lesson-d
 ---
 
 # --description--
 
-The `em` element makes text italic. It also semantically places emphasis on the text, which again may affect things like screen readers. To define an emphasized element you wrap text content in an `<em>` tag.
+O elemento `em` torna o texto itálico. Ele também coloca ênfase semântica no texto, o que pode afetar coisas como leitores de tela. Para definir um elemento enfatizado, você encapsula o conteúdo do texto em uma tag `<em>`.
 
-To use `em` on its own:
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_6" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/wvewqpp?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=wvewqpp&amp;user=TheOdinProjectExamples&amp;name=cp_embed_6" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_wvewqpp"></iframe>
+Para usar `em` sozinho:
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_6" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/wvewqpp?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=wvewqpp&amp;user=TheOdinProjectExamples&amp;name=cp_embed_6" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_wvewqpp"></iframe>
 
-Again, like the `strong` element, you will find yourself mostly using the `em` element with other text elements:
+Novamente, assim como ocorre com o elemento `strong`, você usará principalmente o elemento `em` com outros elementos de texto:
 
-<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_7" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/VwWZzyj?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=VwWZzyj&amp;user=TheOdinProjectExamples&amp;name=cp_embed_7" style="width: 100%; overflow:hidden; display:block;" title="CodePen Embed" loading="lazy" id="cp_embed_VwWZzyj"></iframe>
+<iframe allowfullscreen="true" allowpaymentrequest="true" allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="300" width="100%" name="cp_embed_7" scrolling="no" src="https://codepen.io/TheOdinProjectExamples/embed/VwWZzyj?height=300&amp;theme-id=dark&amp;default-tab=html%2Cresult&amp;slug-hash=VwWZzyj&amp;user=TheOdinProjectExamples&amp;name=cp_embed_7" style="width: 100%; overflow:hidden; display:block;" title="CodePen incorporado" loading="lazy" id="cp_embed_VwWZzyj"></iframe>
 
 # --question--
 ## --text--
 
-What element should you use to make text italicized to add emphasis?
+Qual é o elemento que você deve usar para deixar o texto em itálico para adicionar ênfase?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-f.md b/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-f.md
index 14c3d7faf0..02750f2cd6 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-f.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-f.md
@@ -1,17 +1,17 @@
 ---
 id: 637f4e8072c65bc8e73dfe2c
-title: Working With Text Lesson F
+title: Lição F de Trabalhando com textos
 challengeType: 15
 dashedName: working-with-text-lesson-f
 ---
 
 # --description--
 
-You may have noticed that in all the examples in this lesson you indent any elements that are within other elements. This is known as nesting elements.
+Você deve ter notado que em todos os exemplos desta lição, você faz a indentação de elementos que estejam dentro de outros elementos. Isso é conhecido como aninhamento de elementos.
 
-When you nest elements within other elements, you create a parent and child relationship between them. The nested elements are the children and the element they are nested within is the parent.
+Quando você aninha elementos dentro de outros elementos, cria um relacionamento de pai e filho entre eles. Os elementos aninhados são os filhos e o elemento dentro dos quais eles estão aninhados é o pai.
 
-In the following example, the body element is the parent and the paragraph is the child:
+No exemplo seguinte, body é o pai e o parágrafo é o filho:
 
 ```html
 <html>
@@ -23,9 +23,9 @@ In the following example, the body element is the parent and the paragraph is th
  </html>
 ```
 
-Just as in human relationships, HTML parent elements can have many children. Elements at the same level of nesting are considered to be siblings.
+Assim como nas relações humanas, os elementos-pai do HTML podem ter muitos filhos. Elementos no mesmo nível de aninhamento são considerados irmãos.
 
-For example, the two paragraphs in the following code are siblings, since they are both children of the body tag and are at the same level of nesting as each other:
+Por exemplo, os dois parágrafos do código a seguir são irmãos, já que ambos são filhos de body e estão no mesmo nível de aninhamento um do outro:
 
 ```html
 <html>
@@ -38,27 +38,27 @@ For example, the two paragraphs in the following code are siblings, since they a
  </html>
 ```
 
-You use indentation to make the level of nesting clear and readable for yourselves and other developers who will work with your HTML in the future. It is recommended to indent any child elements by two spaces.
+Você usa a indentação para tornar o nível de aninhamento claro e legível para você e para outros desenvolvedores que trabalharão com o seu HTML no futuro. Recomenda-se a indentação de qualquer elemento filho com dois espaços.
 
-The parent, child, and sibling relationships between elements will become much more important later when you start styling your HTML with CSS and adding behavior with JavaScript. For now, however, it is just important to know the distinction between how elements are related and the terminology used to describe their relationships.
+As relações de pai, filho e irmãos entre os elementos se tornarão muito mais importantes depois, ao começar a estilizar seu HTML com CSS e ao adicionar um comportamento com JavaScript. Agora, porém, é apenas importante conhecer a distinção entre o modo como os elementos estão relacionados e a terminologia utilizada para descrever as suas relações.
 
 # --question--
 
 ## --text--
 
-What relationship does an element have with any nested element within it?
+Qual é a relação que um elemento tem com outro elemento aninhado dentro dele?
 
 ## --answers--
 
-The element within the other element is called the parent element.
+O elemento dentro do outro elemento é chamado de elemento pai.
 
 ---
 
-The element within the other element is called the child element.
+O elemento dentro do outro elemento é chamado de elemento filho.
 
 ---
 
-The element within the other element is called the sibling element.
+O elemento dentro do outro elemento é chamado de elemento irmão.
 
 
 ## --video-solution--
diff --git a/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-g.md b/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-g.md
index 1452e57ff4..59caf452af 100644
--- a/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-g.md
+++ b/curriculum/challenges/portuguese/16-the-odin-project/top-working-with-text/working-with-text-lesson-g.md
@@ -1,15 +1,15 @@
 ---
 id: 637f4e8772c65bc8e73dfe2d
-title: Working With Text Lesson G
+title: Lição G de Trabalhando com textos
 challengeType: 15
 dashedName: working-with-text-lesson-g
 ---
 
 # --description--
 
-HTML comments are not visible to the browser; they allow us to comment on your code so that other developers or your future selves can read them and get some context about something that might not be clear in the code.
+Os comentários em HTML não são visíveis para o navegador. Eles nos permitem comentar o código para que outros desenvolvedores ou você mesmo no futuro possam lê-los e ter algum contexto sobre algo que pode não estar claro no código.
 
-Writing an HTML comment is simple: You just enclose the comment with `<!--` and `-->`tags. For example:
+Escrever um comentário em HTML é simples: basta envolver o comentário com as tags `<!--` e `-->`. Por exemplo:
 
 ```html
 <h1> View the html to see the hidden comments </h1>
@@ -23,13 +23,13 @@ Writing an HTML comment is simple: You just enclose the comment with `<!--` and
 
 # --assignment--
 
-To get some practice working with text in HTML, create a plain blog article page which uses different headings, uses paragraphs, and has some text in the paragraphs bolded and italicized. You can use [Lorem Ipsum](https://loremipsum.io) to generate dummy text, in place of real text as you build your sites.
+Para praticar um pouco o trabalho com textos em HTML, crie uma página simples de artigos de blog que use títulos diferentes e parágrafos. Coloque algum texto nos parágrafos em negritos e em itálico. Você pode usar o [Lorem Ipsum](https://loremipsum.io) para gerar texto fictício, no lugar do texto real, enquanto cria seus sites.
 
 # --question--
 
 ## --text--
 
-How do you create HTML comments?
+Como você cria comentários em HTML?
 
 ## --answers--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
index 7e32448252..73cc3fe057 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-Até agora, você aprendeu como criar perguntas com o verbo `to be`. Em frases com o verbo `to be` (am, is, are), você só precisa mudar a ordem do substantivo e do verbo para criar uma pergunta. Assim:
+So far you have learned how to create questions with the verb `to be`. Em frases com o verbo `to be` (am, is, are), você só precisa mudar a ordem do substantivo e do verbo para criar uma pergunta. Assim:
 
 `You are a developer` -> `Are you a developer?`
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
index 783efa7d03..5f53df460a 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
@@ -21,7 +21,7 @@ Qual frase é correta para descrever um lugar perto de você?
 
 ### --feedback--
 
-`There are` é usado para substantivos plurais; `bank` é singular. Você aprenderá sobre `there are` nas próximas lições.
+`There are` é usado para substantivos plurais; `bank` é singular. You’ll learn about `there are` in the next few lessons.
 
 ---
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
index e85b6131e8..7e0dddbb22 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
@@ -7,7 +7,7 @@ dashedName: task-112
 
 # --description--
 
-Para elaborar uma pergunta usando `there is` basta mudar a ordem do verbo `to be`, assim:
+To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so:
 
 `There is an ATM nearby` -> `Is there an ATM nearby?`
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/6543abeff5f028dba112f278.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/6543abeff5f028dba112f278.md
index 6460b8f0f4..3bbb3b8c40 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/6543abeff5f028dba112f278.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/6543abeff5f028dba112f278.md
@@ -12,13 +12,13 @@ Tom: Hi, that's right! I'm Tom McKenzie.
 
 # --description--
 
-In English, the verb `to be` is used to talk about identities, characteristics, and more. The contraction `I'm` is a combination of `I` and `am`. Aqui, o Tom a usa para se apresentar.
+Em inglês, o verbo `to be` é usado para falar sobre identidades, características e muito mais. A contração `I'm` é uma combinação de `I` e `am`. Aqui, o Tom a usa para se apresentar.
 
 # --question--
 
 ## --text--
 
-Which operation correctly expands the contraction `I'm`?
+Qual operação expande corretamente a contração `I'm`?
 
 ## --answers--
 
@@ -26,7 +26,7 @@ Which operation correctly expands the contraction `I'm`?
 
 ### --feedback--
 
-Think about which verb form would correctly fit with `I` to talk about oneself in the present.
+Pense em qual forma verbal caberia corretamente com `I` para falar sobre você mesmo no presente.
 
 ---
 
@@ -38,7 +38,7 @@ Think about which verb form would correctly fit with `I` to talk about oneself i
 
 ### --feedback--
 
-Think about which verb form would correctly fit with `I` to talk about oneself in the present.
+Pense em qual forma verbal caberia corretamente com `I` para falar sobre você mesmo no presente.
 
 ---
 
@@ -46,7 +46,7 @@ Think about which verb form would correctly fit with `I` to talk about oneself i
 
 ### --feedback--
 
-Think about which verb form would correctly fit with `I` to talk about oneself in the present.
+Pense em qual forma verbal caberia corretamente com `I` para falar sobre você mesmo no presente.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656a509eeac7e030e2a16bab.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656a509eeac7e030e2a16bab.md
index 5c837736b7..aece677293 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656a509eeac7e030e2a16bab.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656a509eeac7e030e2a16bab.md
@@ -12,7 +12,7 @@ Tom: Hey, is this one of those standing desks?
 
 # --description--
 
-Demonstrative pronouns like `this` and `those` help to point to specific items, distinguishing them from others. Tom uses one to inquire about a particular type of desk he observes.
+Pronomes demonstrativos como `this` e `those` ajudam a apontar itens específicos, distinguindo-os dos outros. Tom usa um deles para perguntar sobre um tipo específico de mesa que ele observa.
 
 # --fillInTheBlank--
 
@@ -26,7 +26,7 @@ Demonstrative pronouns like `this` and `those` help to point to specific items,
 
 ### --feedback--
 
-Listen again.
+Ouça novamente.
 
 ---
 
@@ -34,7 +34,7 @@ Listen again.
 
 ### --feedback--
 
-Listen again.
+Ouça novamente.
 
 # --cena--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656a52da3392f631b9f3e022.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656a52da3392f631b9f3e022.md
index a99b64ae15..44edf2e651 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656a52da3392f631b9f3e022.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656a52da3392f631b9f3e022.md
@@ -12,7 +12,7 @@ Tom: These are great! It is good to stand up a little instead of just sitting al
 
 # --description--
 
-In workplaces, especially in offices, there's a focus on ergonomics and health. One popular discussion is about the benefits of standing instead of sitting continuously. `Stand up` refers to the action of rising from a sitting position, while `sitting` means being in a position where one's weight is supported by one's buttocks rather than one's feet.
+Nos locais de trabalho, especialmente em escritórios, há um foco em ergonomia e saúde. Uma discussão popular é sobre os benefícios de ficar em pé em vez de sentar continuamente. `Stand up` refere-se à ação de levantar-se de uma posição sentada, enquanto `sitting` significa estar em uma posição onde o peso é sustentado pelas nádegas em vez de pelos pés.
 
 # --fillInTheBlank--
 
@@ -26,7 +26,7 @@ In workplaces, especially in offices, there's a focus on ergonomics and health.
 
 ### --feedback--
 
-Think of the two actions that are commonly contrasted in discussions about office ergonomics.
+Pense nas duas ações que são comumente contrastadas em discussões sobre ergonomia de escritório.
 
 ---
 
@@ -34,7 +34,7 @@ Think of the two actions that are commonly contrasted in discussions about offic
 
 ### --feedback--
 
-Think of the two actions that are commonly contrasted in discussions about office ergonomics.
+Pense nas duas ações que são comumente contrastadas em discussões sobre ergonomia de escritório.
 
 ---
 
@@ -42,7 +42,7 @@ Think of the two actions that are commonly contrasted in discussions about offic
 
 ### --feedback--
 
-Think of the two actions that are commonly contrasted in discussions about office ergonomics.
+Pense nas duas ações que são comumente contrastadas em discussões sobre ergonomia de escritório.
 
 # --cena--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cc523e668741073c4e916.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cc523e668741073c4e916.md
index 94b299e3fd..f44bd607ab 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cc523e668741073c4e916.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cc523e668741073c4e916.md
@@ -12,13 +12,13 @@ Tom: Wow, I'm so hungry. Is it lunch time?
 
 # --description--
 
-To ask a question using `it is`, you change the order. Instead of `it is`, you say `is it`. This is how you turn a statement into a question in English.
+Para fazer uma pergunta usando `it is`, você altera a ordem. Em vez de `it is`, você diz `is it`. É assim que se transforma uma instrução em uma pergunta em inglês.
 
 # --question--
 
 ## --text--
 
-Which of the following is a correct form of a question?
+Qual das seguintes opções é a forma correta de uma pergunta?
 
 ## --answers--
 
@@ -26,7 +26,7 @@ Which of the following is a correct form of a question?
 
 ### --feedback--
 
-This sentence can be understood, but this is not the common way to form a question.
+Essa frase pode ser entendida, mas não é a maneira comum de formar uma pergunta.
 
 ---
 
@@ -34,7 +34,7 @@ This sentence can be understood, but this is not the common way to form a questi
 
 ### --feedback--
 
-This order is not commonly used for questions.
+Essa ordem não é comumente usada para perguntas.
 
 ---
 
@@ -42,7 +42,7 @@ This order is not commonly used for questions.
 
 ### --feedback--
 
-This order is incorrect for asking questions.
+Essa ordem é incorreta para fazer perguntas.
 
 ---
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cc6981cbf2711196a284f.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cc6981cbf2711196a284f.md
index 713c9f157c..b20c6f3d36 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cc6981cbf2711196a284f.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cc6981cbf2711196a284f.md
@@ -12,7 +12,7 @@ Tom: Are you eating here or are you going out?
 
 # --description--
 
-To ask about someone's actions or plans in the present with the verb `to be`, you can use the structure `are you` at the beginning of the question. This combination of verb (`are`) and subject (`you`) helps form questions in the present simple tense.
+Para perguntar sobre as ações ou planos de alguém no presente com o verbo `to be`, você pode usar a estrutura `are you` no início da pergunta. Essa combinação do verbo (`are`) e do sujeito (`you`) ajuda a formar perguntas no presente simples.
 
 # --fillInTheBlank--
 
@@ -26,7 +26,7 @@ To ask about someone's actions or plans in the present with the verb `to be`, yo
 
 ### --feedback--
 
-Tom is asking Sophie about her plans. When forming questions in the present simple tense about someone's actions or choices, you start with `are` followed by `you`.
+Tom está perguntando a Sophie sobre os planos dela. Ao formar perguntas no presente simples sobre as ações ou escolhas de alguém, você começa com `are` seguido por `you`.
 
 ---
 
@@ -34,7 +34,7 @@ Tom is asking Sophie about her plans. When forming questions in the present simp
 
 ### --feedback--
 
-Tom is asking Sophie about her plans. When forming questions in the present simple tense about someone's actions or choices, you start with `are` followed by `you`.
+Tom está perguntando a Sophie sobre os planos dela. Ao formar perguntas no presente simples sobre as ações ou escolhas de alguém, você começa com `are` seguido por `you`.
 
 # --cena--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cd63a45146d1c2c51e682.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cd63a45146d1c2c51e682.md
index 5ed8f80eea..3da190c86c 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cd63a45146d1c2c51e682.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/656cd63a45146d1c2c51e682.md
@@ -7,41 +7,41 @@ dashedName: task-129
 
 # --description--
 
-The question `How is everything?` is a way to ask someone how they are and how things are going in their life.
+A pergunta `How is everything?` é uma maneira de perguntar a alguém como está e como as coisas estão indo na vida dessa pessoa.
 
 # --question--
 
 ## --text--
 
-What does `How is everything?` mean?
+O que `How is everything?` significa?
 
 ## --answers--
 
-How is your health?
+Como está sua saúde?
 
 ### --feedback--
 
-It's not just about health.
+Não é apenas sobre saúde.
 
 ---
 
-How is your work?
+Como está seu trabalho?
 
 ### --feedback--
 
-It's not just about work.
+Não é apenas sobre trabalho.
 
 ---
 
-How is your life?
+Como está sua vida?
 
 ---
 
-How is your family?
+Como está sua família?
 
 ### --feedback--
 
-It's not just about family.
+Não é apenas sobre família.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b1240ef768447b80817ad.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b1240ef768447b80817ad.md
index 7c2074fc39..bd59a774c4 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b1240ef768447b80817ad.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b1240ef768447b80817ad.md
@@ -9,13 +9,13 @@ dashedName: task-9
 
 # --description--
 
-The simple past tense, as reviewed earlier, is used for actions completed in the past. In this context, `we were involved in` combines the simple past tense (`were`) with the expression `involved in`, which means being a part of something, especially in an active or important role. For example, `They were involved in organizing the event` means they played an important role in organizing it.
+O passado simples, conforme revisado anteriormente, é usado para ações concluídas no passado. Nesse contexto, `we were involved in` combina o tempo passado simples (`were`) com a expressão `involved in`, que significa fazer parte de algo, especialmente em um papel ativo ou importante. Por exemplo, `They were involved in organizing the event` significa que eles desempenharam um papel importante na organização.
 
 # --question--
 
 ## --text--
 
-How does the candidate describe their role in the project?
+Como o candidato descreve seu papel no projeto?
 
 ## --answers--
 
@@ -23,7 +23,7 @@ How does the candidate describe their role in the project?
 
 ### --feedback--
 
-Although this phrase communicates involvement, the more common expression in English is `were involved in`.
+Embora essa frase comunique envolvimento, a expressão mais comum em inglês é `were involved in`.
 
 ---
 
@@ -31,7 +31,7 @@ Although this phrase communicates involvement, the more common expression in Eng
 
 ### --feedback--
 
-`engaged in` is similar but not the exact phrase used by the candidate. `Involved in` specifically indicates an active participation.
+`engaged in` é semelhante, mas não é a frase exata usada pelo candidato. `Involved in` indica especificamente uma participação ativa.
 
 ---
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b163c9da40e62b904be1f.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b163c9da40e62b904be1f.md
index 7ccde058aa..2a6f7008c2 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b163c9da40e62b904be1f.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b163c9da40e62b904be1f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-Esta tarefa é uma revisão do passado simples na forma interrogativa. In questions, the simple past tense often begins with a past tense verb, followed by the subject and the rest of the sentence. This structure is used to ask about past events or states.
+Esta tarefa é uma revisão do passado simples na forma interrogativa. Em perguntas, o passado simples, muitas vezes, começa com um verbo no passado, seguido do sujeito e o restante da frase. Essa estrutura é usada para perguntar sobre eventos ou estados passados.
 
 # --fillInTheBlank--
 
@@ -23,7 +23,7 @@ Esta tarefa é uma revisão do passado simples na forma interrogativa. In questi
 
 ### --feedback--
 
-This is the past form of `are` used to ask about a past state or condition.
+Essa é a forma passada de `are` usada para perguntar sobre um estado ou condição passada.
 
 ---
 
@@ -31,7 +31,7 @@ This is the past form of `are` used to ask about a past state or condition.
 
 ### --feedback--
 
-Think of a word that means `participated in` or `engaged with`.
+Pense em uma palavra que signifique `participated in` ou `engaged with`.
 
 ---
 
@@ -39,7 +39,7 @@ Think of a word that means `participated in` or `engaged with`.
 
 ### --feedback--
 
-A preposition that often follows `involved` to indicate participation or inclusion.
+Uma preposição que frequentemente segue `involved` para indicar participação ou inclusão.
 
 # --scene--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b1e2fad2ffe84ab420a56.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b1e2fad2ffe84ab420a56.md
index 49615e3e0b..124918bcf8 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b1e2fad2ffe84ab420a56.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b1e2fad2ffe84ab420a56.md
@@ -8,47 +8,47 @@ dashedName: task-37
 <!-- (Audio) Sophie: I didn't study computer science at university, but I majored in electrical engineering. -->
 
 # --description--
-For most verbs, if you want to make a negative sentence in the past tense, simply put `didn't` in front of the main verb. `Didn't` is short for `did not`.
+Para a maioria dos verbos, se você quer fazer uma frase negativa no passado, simplesmente coloque `didn't` na frente do verbo principal. `Didn't` é a forma abreviada de `did not`.
 
-Remember that the main verb stays in its simple form. Only the auxiliary verb `did` is conjugated. Por exemplo:
+Lembre-se de que o verbo principal permanece em sua forma simples. Apenas o verbo auxiliar `did` é conjugado. Por exemplo:
 
-**Affirmative sentence in the past**: `I worked yesterday` - The Verb `work` is conjugated to the past.
+**Frase afirmativa no passado**: `I worked yesterday` - O verbo `work` é conjugado no passado.
 
-**Negative sentence in the past**: `I didn't work yesterday` - Only the auxiliary verb is conjugated to the past.
+**Frase negativa no passado**: `I didn't work yesterday` - Apenas o verbo auxiliar é conjugado no passado.
 
 # --question--
 
 ## --text--
 
-If someone says that `Sophie didn't study computer science`, what could you understand from this sentence?
+Se alguém diz que `Sophie didn't study computer science`, o que você poderia entender dessa frase?
 
 ## --answers--
 
-Sophie enjoyed the computer science degree
+Sophie gostou do curso de ciência da computação
 
 ### --feedback--
 
-Using `didn't` suggests she did not study it, contradicting the idea of enjoying it.
+Usar `didn't` sugere que ela não estudou, contradizendo a ideia de ter gostado.
 
 ---
 
-Computer science is not something Sophie studied in college
+Ciência da computação não é algo que Sophie estudou na faculdade
 
 ---
 
-Sophie always studies computer science
+Sophie sempre estuda ciência da computação
 
 ### --feedback--
 
-This expression refers to a regular habit, not a specific event in the past.
+Essa expressão refere-se a um hábito regular, não a um evento específico no passado.
 
 ---
 
-Sophie is looking forward to studying computer science
+Sophie está ansiosa para estudar ciência da computação
 
 ### --feedback--
 
-This option is about future anticipation.
+Essa opção é sobre antecipação futura.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b2310b8cd52a4f15c1818.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b2310b8cd52a4f15c1818.md
index 06c6eea34f..b8cbcfd0c4 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b2310b8cd52a4f15c1818.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-ask-and-share-about-educational-and-professional-background/657b2310b8cd52a4f15c1818.md
@@ -10,41 +10,41 @@ Alice: My background is a bit unconventional. -->
 
 # --description--
 
-The word `unconventional` is used to describe something that's not based on or conforming to what is generally done or believed. It often implies a method or approach that is different from the norm.
+A palavra `unconventional` é usada para descrever algo que não é baseado ou não se conforma com o que geralmente é feito ou acreditado. Frequentemente implica um método ou abordagem que é diferente do normal.
 
 # --question--
 
 ## --text--
 
-What does `unconventional` imply about Alice's background in tech?
+O que `unconventional` implica sobre o histórico de Alice em tecnologia?
 
 ## --answers--
 
-Her background is different from the usual way people get into tech
+O histórico dela é diferente do modo usual como as pessoas entram em tecnologia
 
 ---
 
-Her background is exactly the same as most people in tech
+O histórico dela é exatamente o mesmo que a maioria das pessoas em tecnologia
 
 ### --feedback--
 
-`Unconventional` means not following the usual conventions, which contradicts being the same as most people.
+`Unconventional` significa não seguir as convenções usuais, o que contradiz ser o mesmo que a maioria das pessoas.
 
 ---
 
-She doesn't have any background in tech
+Ela não tem nenhum histórico em tecnologia
 
 ### --feedback--
 
-`Unconventional` suggests a different approach, not the absence of a background.
+`Unconventional` sugere uma abordagem diferente, não a ausência de um histórico.
 
 ---
 
-She followed a very traditional path into tech
+Ela seguiu um caminho muito tradicional em tecnologia
 
 ### --feedback--
 
-`Unconventional` indicates a non-traditional path, not a very traditional one.
+`Unconventional` indica um caminho não tradicional, não um muito tradicional.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-tech-trends-and-updates/666339cedcfb436e2c9fd550.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-tech-trends-and-updates/666339cedcfb436e2c9fd550.md
index e5c9ba9021..5e7c5cb433 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-tech-trends-and-updates/666339cedcfb436e2c9fd550.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-tech-trends-and-updates/666339cedcfb436e2c9fd550.md
@@ -9,9 +9,9 @@ dashedName: task-6
 
 # --description--
 
-`To make something with less` is an expression that means the amount of effort to be put on a task will be reduced. In this context, Sarah explains that `Low-code development` helps in the creation of software and developers don't need to code as much as in regular solutions.
+`To make something with less` é uma expressão que significa que a quantidade de esforço a ser colocada em uma tarefa será reduzida. Nesse contexto, Sarah explica que `Low-code development` auxilia na criação de software e os desenvolvedores não precisam programar tanto quanto nas soluções comuns.
 
-Listen to the audio and fill in the blanks.
+Ouça o áudio e preencha os espaços em branco.
 
 # --fillInTheBlank--
 
@@ -25,7 +25,7 @@ Listen to the audio and fill in the blanks.
 
 ### --feedback--
 
-The verb used to talk about producing something. Use the `-ing` form.
+O verbo usado para falar sobre produzir algo. Use a forma `-ing`.
 
 ---
 
@@ -33,7 +33,7 @@ The verb used to talk about producing something. Use the `-ing` form.
 
 ### --feedback--
 
-The opposite of `more`. A smaller amount of something.
+O oposto de `more`. Uma quantidade menor de algo.
 
 # --scene--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-tech-trends-and-updates/666339dd9d6dc46efa85c8cb.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-tech-trends-and-updates/666339dd9d6dc46efa85c8cb.md
index cfa676a3bf..05feb5f6ed 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-tech-trends-and-updates/666339dd9d6dc46efa85c8cb.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-tech-trends-and-updates/666339dd9d6dc46efa85c8cb.md
@@ -27,23 +27,23 @@ The development still happens; it just needs less code.
 
 ---
 
-It eliminates the need of coding altogether
+Elimina completamente a necessidade de criação de código
 
 ### --feedback--
 
-`Low-code` does not mean no code. Some coding is still necessary.
+`Low-code` não significa sem código. Um pouco de programação ainda é necessário.
 
 ---
 
-It helps them write more low-level code
+Ajuda-os a escrever mais código de baixo nível
 
 ### --feedback--
 
-The idea of `low-code development` is to write less code, not more.
+A ideia de `low-code development` é escrever menos código, não mais.
 
 ---
 
-By having them write less code
+Faz com que escrevam menos código
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-your-morning-or-evening-routine/655a54506b259313b2d59577.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-your-morning-or-evening-routine/655a54506b259313b2d59577.md
index 486e3ed3aa..0bf958e5d6 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-your-morning-or-evening-routine/655a54506b259313b2d59577.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-discuss-your-morning-or-evening-routine/655a54506b259313b2d59577.md
@@ -9,43 +9,43 @@ dashedName: task-58
 
 # --description--
 
-Conditional sentences often use `if` to describe a situation (cause) that will lead to a particular result (consequence). They typically consist of two parts: the `if` clause (condition) and the main clause (result). Por exemplo:
+Sentenças condicionais frequentemente usam `if` para descrever uma situação (causa) que levará a um determinado resultado (consequência). Elas tipicamente consistem em duas partes: a cláusula `if` (condição) e a cláusula principal (resultado). Por exemplo:
 
-`If you sleep well, you will feel refreshed.` (condition: sleeping well; result: feeling refreshed)
+`If you sleep well, you will feel refreshed.` (condição: dormir bem; resultado: sentir-se revigorado)
 
 # --question--
 
 ## --text--
 
-What is the cause and consequence of the expert’s advice?
+Qual é a causa e a consequência do conselho do especialista?
 
 ## --answers--
 
-Feeling relaxed at the end of the day causes a more productive day
+Sentir-se relaxado no final do dia causa um dia mais produtivo
 
 ### --feedback--
 
-The condition is about starting the day feeling relaxed, not ending it.
+A condição é sobre começar o dia sentindo-se relaxado, não terminá-lo.
 
 ---
 
-Starting the day relaxed can lead to a more productive day
+Começar o dia relaxado pode levar a um dia mais produtivo
 
 ---
 
-Being productive in the morning causes relaxation during the day
+Ser produtivo pela manhã causa relaxamento durante o dia
 
 ### --feedback--
 
-The advice suggests that relaxation leads to productivity, not the other way around.
+O conselho sugere que o relaxamento leva à produtividade, e não o contrário.
 
 ---
 
-Rushing in the morning leads to relaxation later
+Apressar-se pela manhã leva a relaxamento mais tarde
 
 ### --feedback--
 
-The focus is on the benefit of starting the day relaxed.
+O foco é no benefício de começar o dia relaxado.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-talk-about-a-typical-workday-and-tasks/657e4fc397780aa2bc046ed7.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-talk-about-a-typical-workday-and-tasks/657e4fc397780aa2bc046ed7.md
index 39595b3474..123fcdab42 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-talk-about-a-typical-workday-and-tasks/657e4fc397780aa2bc046ed7.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-talk-about-a-typical-workday-and-tasks/657e4fc397780aa2bc046ed7.md
@@ -7,43 +7,43 @@ dashedName: task-80
 
 # --description--
 
-To `promote ethics` means to encourage and support moral principles and standards.
+A expressão `promote ethics` significa incentivar e apoiar princípios e padrões morais.
 
-For example: `The manager promotes ethics by enforcing transparent reporting.`
+Por exemplo: `The manager promotes ethics by enforcing transparent reporting.`
 
 # --question--
 
 ## --text--
 
-What does it mean to `promote ethics` in a company?
+O que significa `promote ethics` em uma empresa?
 
 ## --answers--
 
-To encourage social interactions.
+Encorajar interações sociais.
 
 ### --feedback--
 
-Promoting ethics is more about moral conduct than socializing.
+Promover ética é mais sobre conduta moral do que socialização.
 
 ---
 
-To advance personal gains.
+Avançar ganhos pessoais.
 
 ### --feedback--
 
-Ethics promotion is about collective standards, not personal gains.
+Promoção de ética envolve padrões coletivos, não ganhos pessoais.
 
 ---
 
-To encourage and support moral principles.
+Encorajar e apoiar princípios morais.
 
 ---
 
-To focus on individual achievements.
+Focar em conquistas individuais.
 
 ### --feedback--
 
-Ethics are about collective moral standards, not just individual achievements.
+A ética diz respeito a padrões morais coletivos, não apenas a conquistas individuais.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-talk-about-a-typical-workday-and-tasks/657e77b682b49f70a3adcc0a.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-talk-about-a-typical-workday-and-tasks/657e77b682b49f70a3adcc0a.md
index d432b4b064..633eeb9cd1 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-talk-about-a-typical-workday-and-tasks/657e77b682b49f70a3adcc0a.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-how-to-talk-about-a-typical-workday-and-tasks/657e77b682b49f70a3adcc0a.md
@@ -7,9 +7,9 @@ dashedName: task-129
 
 # --description--
 
-This challenge helps to summarize and reinforce the understanding of Sarah's workday as a QA tester. It includes vocabulary and concepts discussed throughout the dialogue.
+Este desafio ajuda a resumir e reforçar o entendimento do dia de trabalho de Sarah como testadora de QA. Ele inclui vocabulário e conceitos discutidos ao longo do diálogo.
 
-Fill in the blanks with the correct words to complete the summary of the dialogue between Brian and Sarah.
+Preencha as lacunas com as palavras corretas para completar o resumo do diálogo entre Brian e Sarah.
 
 # --fillInTheBlank--
 
@@ -31,7 +31,7 @@ A ação de se levantar da cama.
 
 ### --feedback--
 
-Moving towards a location.
+Mover-se em direção a um local.
 
 ---
 
@@ -39,7 +39,7 @@ Moving towards a location.
 
 ### --feedback--
 
-Examining or evaluating something.
+Examinar ou avaliar algo.
 
 ---
 
@@ -47,7 +47,7 @@ Examining or evaluating something.
 
 ### --feedback--
 
-A process to access an account.
+Um processo para acessar uma conta.
 
 ---
 
@@ -55,7 +55,7 @@ A process to access an account.
 
 ### --feedback--
 
-Consuming a meal.
+Consumir uma refeição.
 
 ---
 
@@ -63,7 +63,7 @@ Consuming a meal.
 
 ### --feedback--
 
-Evaluating different parts.
+Avaliar diferentes partes.
 
 ---
 
@@ -71,7 +71,7 @@ Evaluating different parts.
 
 ### --feedback--
 
-A group discussion with colleagues.
+Uma discussão em grupo com colegas.
 
 ---
 
@@ -79,7 +79,7 @@ A group discussion with colleagues.
 
 ### --feedback--
 
-Errors or problems in software.
+Erros ou problemas em software.
 
 # --scene--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/651dd5a46ffb500e3f2ce47b.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/651dd5a46ffb500e3f2ce47b.md
index d3701d4c07..b773703e04 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/651dd5a46ffb500e3f2ce47b.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/651dd5a46ffb500e3f2ce47b.md
@@ -1,6 +1,6 @@
 ---
 id: 651dd5a46ffb500e3f2ce47b
-title: "Dialogue 1: A Mobile Developer Joins the Team"
+title: "Diálogo 1: Um desenvolvedor mobile se junta à equipe"
 challengeType: 21
 dashedName: dialogue-a-mobile-developer-joins-the-team
 ---
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657ca06716e21b803ffb55d5.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657ca06716e21b803ffb55d5.md
index eace74d901..ed15a658bb 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657ca06716e21b803ffb55d5.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657ca06716e21b803ffb55d5.md
@@ -12,21 +12,21 @@ Bob: Alright, team. This is Alice's first day with us, so please let me introduc
 
 # --description--
 
-Listen to the audio and answer the question.
+Ouça o áudio e responda à pergunta.
 
 # --question--
 
 ## --text--
 
-In Bob's sentence, who does the pronoun `her` refer to?
+Na frase de Bob, a quem o pronome `her` se refere?
 
 ## --answers--
 
-The team
+À equipe
 
 ### --feedback--
 
-`Her` is not used for a group like the team.
+`Her` não é usado para um grupo como a equipe.
 
 ---
 
@@ -38,15 +38,15 @@ Bob
 
 ### --feedback--
 
-In this context, `Her` is not for Bob.
+Nesse contexto, `Her` não é para Bob.
 
 ---
 
-You
+Você
 
 ### --feedback--
 
-`Her` does not refer to the listener.
+`Her` não se refere ao ouvinte.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657ca59e6e559782e4c10056.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657ca59e6e559782e4c10056.md
index 632bd65b0b..8e7a60ab04 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657ca59e6e559782e4c10056.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657ca59e6e559782e4c10056.md
@@ -12,15 +12,15 @@ This is Sarah, the senior software developer.
 
 # --description--
 
-In companies, job titles often include words that indicate the level of seniority. `Senior` means having a higher level or more experience in a role. For instance, a `senior software developer` usually has more experience than a `software developer`.
+Nas empresas, os cargos muitas vezes incluem palavras que indicam o nível de senioridade. `Senior` significa ter um nível mais alto ou mais experiência em um cargo. Por exemplo, um `senior software developer` geralmente tem mais experiência do que um `software developer`.
 
-Other common terms include `junior`, for less experienced roles, and `lead` or `head`, for top-level positions. Aqui estão alguns exemplos:
+Outros termos comuns incluem `junior`, para cargos com menos experiência, e `lead` ou `head`, para cargos de nível superior. Aqui estão alguns exemplos:
 
-`Junior Accountant`: An entry-level position in accounting.
+`Junior Accountant`: um cargo inicial na contabilidade.
 
-`Lead Engineer`: A top-level engineering role with leadership responsibilities.
+`Lead Engineer`: um cargo de engenharia de nível superior com responsabilidades de liderança.
 
-`Senior Manager`: A managerial role with significant experience.
+`Senior Manager`: um cargo gerencial com experiência significativa.
 
 # --fillInTheBlank--
 
@@ -34,7 +34,7 @@ Other common terms include `junior`, for less experienced roles, and `lead` or `
 
 ### --feedback--
 
-Used here to indicate that Sarah has more experience and expertise in her role as a software developer.
+Usado aqui para indicar que Sarah tem mais experiência e expertise em seu cargo como desenvolvedora de software.
 # --cena--
 
 ```json
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657cd6c342d0e8093dd5c540.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657cd6c342d0e8093dd5c540.md
index 905719b857..96ada18ca8 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657cd6c342d0e8093dd5c540.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657cd6c342d0e8093dd5c540.md
@@ -12,9 +12,9 @@ Bob: Good morning, everyone! I hope you're all well.
 
 # --description--
 
-The word `hope` is used to express a wish for something to be true or to happen. For example, saying `I hope you're doing well` means you wish that the person is fine or happy.
+A palavra `hope` é usada para expressar um desejo de que algo seja verdade ou aconteça. Por exemplo, dizer `I hope you're doing well` significa que você deseja que a pessoa esteja bem ou feliz.
 
-`Well` is often used to mean in good health or in a good condition. For example, `Are you feeling well today?` is asking if someone is in good health.
+`Well` é frequentemente usado para significar em boa saúde ou em boas condições. Por exemplo, `Are you feeling well today?` está perguntando se alguém está bem de saúde.
 
 # --fillInTheBlank--
 
@@ -28,7 +28,7 @@ The word `hope` is used to express a wish for something to be true or to happen.
 
 ### --feedback--
 
-This word indicates the time of day and is used as a greeting.
+Essa palavra indica a hora do dia e é usada como uma saudação.
 
 ---
 
@@ -36,7 +36,7 @@ This word indicates the time of day and is used as a greeting.
 
 ### --feedback--
 
-Used to express a wish or desire for something.
+Usada para expressar um desejo por algo.
 
 ---
 
@@ -44,7 +44,7 @@ Used to express a wish or desire for something.
 
 ### --feedback--
 
-In this context refers to being in good health or condition.
+Neste contexto, refere-se a estar em boa saúde ou condição.
 
 # --cena--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657daa5ab8505427a5b99cd2.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657daa5ab8505427a5b99cd2.md
index 3d5b6ab281..8f7f34fff6 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657daa5ab8505427a5b99cd2.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657daa5ab8505427a5b99cd2.md
@@ -12,41 +12,41 @@ Bob: And I’m Bob, the team’s project manager.
 
 # --description--
 
-In the audio, Bob introduces himself and states his role in the company.
+No áudio, Bob se apresenta e declara seu papel na empresa.
 
 # --question--
 
 ## --text--
 
-What is Bob's role in the company?
+Qual é o papel de Bob na empresa?
 
 ## --answers--
 
-He is the team's project manager.
+Ele é o gerente de projetos da equipe.
 
 ---
 
-He is the team's graphic designer.
+Ele é o designer gráfico da equipe.
 
 ### --feedback--
 
-Remember to listen carefully to the specific role mentioned in the introduction.
+Lembre-se de ouvir atentamente para a função específica mencionada na introdução.
 
 ---
 
-He is the new intern.
+Ele é o novo estagiário.
 
 ### --feedback--
 
-Bob introduces himself with a specific management role, not as an intern.
+Bob se apresenta em uma função de gestão específica, não como estagiário.
 
 ---
 
-He is the company's CEO.
+Ele é o CEO da empresa.
 
 ### --feedback--
 
-Bob's introduction clearly states a different role, not the CEO.
+A introdução de Bob declara claramente uma função diferente, não a de CEO.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657daad61699f1281c5dca55.md b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657daad61699f1281c5dca55.md
index 00d4967e02..82a37c8f02 100644
--- a/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657daad61699f1281c5dca55.md
+++ b/curriculum/challenges/portuguese/21-a2-english-for-developers/learn-introductions-in-an-online-team-meeting/657daad61699f1281c5dca55.md
@@ -7,43 +7,43 @@ dashedName: task-65
 
 # --description--
 
-A `project manager` is a key role in many companies. This person is responsible for planning, organizing, and directing the completion of specific projects while ensuring these projects are on time, on budget, and within scope.
+A função de `project manager` é fundamental em muitas empresas. Essa pessoa é responsável por planejar, organizar e dirigir a conclusão de projetos específicos, ao mesmo tempo em garante que os projetos estejam no prazo, dentro do orçamento e dentro do escopo.
 
-A `project manager` often coordinates with different team members, sets deadlines, assigns responsibilities, and monitors the progress of the project.
+Quem se encontra na função de `project manager` frequentemente coordena com diferentes membros da equipe, define prazos, atribui responsabilidades e monitora o progresso do projeto.
 
 # --question--
 
 ## --text--
 
-Which activities best describe what a project manager does?
+Quais atividades melhor descrevem o que um gerente de projetos faz?
 
 ## --answers--
 
-Designs the products and creates marketing strategies.
+Desenha os produtos e cria estratégias de marketing.
 
 ### --feedback--
 
-These tasks are typically handled by other specialized roles, not the project manager.
+Essas tarefas são tipicamente tratadas por outras funções especializadas, não pelo gerente de projetos.
 
 ---
 
-Plans and organizes projects, sets deadlines, and monitors progress.
+Planeja e organiza projetos, define prazos e monitora o progresso.
 
 ---
 
-Teaches new employees and manages company finances.
+Ensina novos funcionários e gerencia as finanças da empresa.
 
 ### --feedback--
 
-While important, these activities are not typically the primary responsibilities of a project manager.
+Embora importantes, essas atividades não são tipicamente as principais responsabilidades de um gerente de projetos.
 
 ---
 
-Prepares food and serves customers in a restaurant.
+Prepara comida e serve clientes em um restaurante.
 
 ### --feedback--
 
-This description fits roles in the food service industry, not a project manager.
+Essa descrição se encaixa em funções no setor de serviços alimentícios, não na de um gerente de projetos.
 
 ## --video-solution--
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md b/curriculum/challenges/portuguese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
new file mode 100644
index 0000000000..7d664a8876
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
@@ -0,0 +1,25 @@
+---
+id: 5f1a4ef5d5d6b5ab580fc6ae
+title: Build a Celestial Bodies Database
+challengeType: 13
+url: freeCodeCamp/learn-celestial-bodies-database
+dashedName: lab-celestial-bodies-database
+---
+
+# --description--
+
+For this project, you will build a database of celestial bodies using PostgreSQL.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `universe.sql` file so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `universe.sql`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/portuguese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md b/curriculum/challenges/portuguese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
new file mode 100644
index 0000000000..d9aa29190a
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
@@ -0,0 +1,611 @@
+---
+id: 5a8b073d06fa14fcfde687aa
+title: Crie um monitor de exercícios
+challengeType: 4
+dashedName: build-an-exercise-tracker
+---
+
+# --description--
+
+Crie uma aplicação full-stack em JavaScript que seja funcionalmente semelhante a esta: <a href="https://exercise-tracker.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://exercise-tracker.freecodecamp.rocks</a>. Trabalhar nesse projeto vai fazer com que você escreva o código usando um dos seguintes métodos:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">este repositório do GitHub</a> e complete o projeto localmente.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">nosso projeto inicial no Gitpod</a> para completar seu projeto.
+-   Use um criador de sites de sua escolha para completar o projeto. Certifique-se de incorporar todos os arquivos do nosso repositório no GitHub.
+
+# --instructions--
+
+As respostas devem ter as seguintes estruturas.
+
+Exercício:
+
+```js
+{
+  username: "fcc_test",
+  description: "test",
+  duration: 60,
+  date: "Mon Jan 01 1990",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Usuário:
+
+```js
+{
+  username: "fcc_test",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Log:
+
+```js
+{
+  username: "fcc_test",
+  count: 1,
+  _id: "5fb5853f734231456ccb3b05",
+  log: [{
+    description: "test",
+    duration: 60,
+    date: "Mon Jan 01 1990",
+  }]
+}
+```
+
+**Dica:** para a propriedade `date`, o método `toDateString` da API `Date` pode ser usado para conseguir o resultado esperado.
+
+# --hints--
+
+Você deve fornecer seu próprio projeto, não o exemplo de URL.
+
+```js
+(getUserInput) => {
+  const url = getUserInput('url');
+  assert(
+    !/.*\/exercise-tracker\.freecodecamp\.rocks/.test(getUserInput('url'))
+  );
+};
+```
+
+Você pode fazer a solicitação de `POST` para `/api/users` com dados do formulário `username` para criar um usuário.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+A resposta retornada de `POST /api/users` com dados do formulário `username` será um objeto com as propriedades `username` e `_id`.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    assert.exists(_id);
+    assert.exists(username);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+Você pode fazer uma solicitação de `GET` a `/api/users` para obter uma lista com todos os usuários.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+A solicitação de `GET` a `/api/users` retorna um array.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    assert.isArray(users);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Cada elemento do array retornado de `GET /api/users` é um objeto literal que contém o `username` e a `_id` do usuário.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    const user = users[0];
+    assert.exists(user);
+    assert.exists(user.username);
+    assert.exists(user._id);
+    assert.isString(user.username);
+    assert.isString(user._id);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Você pode fazer a solicitação de `POST` para `/api/users/:_id/exercises` com dados do formulário `description`, `duration` e, como opção, a `date`. Se nenhuma data for fornecida, a data atual será utilizada.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+  assert.isTrue(addRes.ok);
+  if(!addRes.ok) {
+    throw new Error(`${addRes.status} ${addRes.statusText}`)
+  };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A resposta retornada de `POST /api/users/:_id/exercises` será o objeto do usuário com os campos de exercício adicionados.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    if (addRes.ok) {
+      const actual = await addRes.json();
+      assert.deepEqual(actual, expected);
+      assert.isString(actual.description);
+      assert.isNumber(actual.duration);
+      assert.isString(actual.date);
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+Você pode fazer uma solicitação de `GET` a `/api/users/:_id/logs` para obter um registro completo dos exercícios de qualquer usuário.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+    assert.isTrue(logRes.ok);
+    if(!logRes.ok) {
+      throw new Error(`${logRes.status} ${logRes.statusText}`)
+    };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+Uma solicitação para o registro (log) de um usuário `GET /api/users/:_id/logs` retornará um objeto com uma propriedade `count`, que representa o número de exercícios que pertencem àquele usuário.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if (logRes.ok) {
+        const { count } = await logRes.json();
+        assert(count);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+Uma solicitação de `GET` a `/api/users/:_id/logs` retornará o objeto do usuário com um array `log` de todos os exercícios adicionados.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  })
+  if(res.ok){
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok){
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+Cada item no array `log` que é retornado de `GET /api/users/:_id/logs` é um objeto que deve ter as propriedades `description`, `duration`, e `date`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + `/api/users`, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+     const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.exists(exercise);
+        assert.exists(exercise.description);
+        assert.exists(exercise.duration);
+        assert.exists(exercise.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+A propriedade `description` de qualquer objeto no array `log` retornada de `GET /api/users/:_id/logs` deve ser uma string.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.description);
+        assert.equal(exercise.description, expected.description);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+A propriedade `duration` de qualquer objeto no array `log` que é retornada de `GET /api/users/:_id/logs` deve ser um número.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isNumber(exercise.duration);
+        assert.equal(exercise.duration, expected.duration);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+A propriedade `date` de qualquer objeto no array `log` retornada de `GET /api/users/:_id/logs` deve ser uma string. Use o formato `dateString` da API `Date`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toLocaleDateString("en-US", {
+        timeZone: "UTC", weekday: "short", month: "short",
+        day: "2-digit", year: "numeric"
+      }).replaceAll(',', '')
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.date);
+        assert.equal(exercise.date, expected.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Você pode adicionar os parâmetros `from`, `to` e `limit` a uma solicitação para `GET /api/users/:_id/logs` para recuperar parte do registro de qualquer usuário. `from` e `to` são datas no formato `yyyy-mm-dd`. `limit` é um número inteiro de quantos registros devem ser enviados de volta.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addExerciseRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    const addExerciseTwoRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-03`
+    });
+    if (addExerciseRes.ok && addExerciseTwoRes.ok) {
+      const logRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1989-12-31&to=1990-01-04`
+      );
+      if (logRes.ok) {
+        const { log } = await logRes.json();
+        assert.isArray(log);
+        assert.equal(2, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+      const limitRes = await fetch(
+        url + `/api/users/${_id}/logs?limit=1`
+      );
+      if (limitRes.ok) {
+        const { log } = await limitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${limitRes.status} ${limitRes.statusText}`);
+      }
+      const filterDateBeforeLimitRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1990-01-02&to=1990-01-04&limit=1`
+      );
+      if (filterDateBeforeLimitRes.ok) {
+        const { log } = await filterDateBeforeLimitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${filterDateBeforeLimitRes.status} ${filterDateBeforeLimitRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${res.status} ${res.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
diff --git a/curriculum/challenges/portuguese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md b/curriculum/challenges/portuguese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
new file mode 100644
index 0000000000..ef87dc6720
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
@@ -0,0 +1,25 @@
+---
+id: 602da04c22201c65d2a019f4
+title: Build a Number Guessing Game
+challengeType: 13
+url: freeCodeCamp/learn-number-guessing-game
+dashedName: lab-number-guessing-game
+---
+
+# --description--
+
+For this lab, you will use Bash scripting, PostgreSQL, and Git to create a number guessing game that runs in the terminal and saves user information.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `number_guess.sql` file, as well as your `number_guess.sh` file, so you can complete step 2. There will be instructions on how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `number_guess.sql`, `number_guess.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/portuguese/25-front-end-development/lab-real-time-counter/66bb3e20d3dc5b6d0a21f5dd.md b/curriculum/challenges/portuguese/25-front-end-development/lab-real-time-counter/66bb3e20d3dc5b6d0a21f5dd.md
index 3f08b91ea0..aaa270bddb 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/lab-real-time-counter/66bb3e20d3dc5b6d0a21f5dd.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/lab-real-time-counter/66bb3e20d3dc5b6d0a21f5dd.md
@@ -1,6 +1,6 @@
 ---
 id: 66bb3e20d3dc5b6d0a21f5dd
-title: Build a Real Time Counter
+title: Compilação de um contador em tempo real
 challengeType: 14
 dashedName: build-a-real-time-counter
 demoType: onClick
@@ -8,45 +8,45 @@ demoType: onClick
 
 # --description--
 
-In this lab, you will build a real-time character counter by using JavaScript. The character counter will display the number of characters entered in a `textarea` element. The counter will update in real-time as the user types in the `textarea`.
+Neste laboratório, você vai criar um contador de caracteres em tempo real usando JavaScript. O contador de caracteres exibirá o número de caracteres inseridos em um elemento `textarea`. O contador será atualizado em tempo real à medida que o usuário digita na `textarea`.
 
-**Objective:** Fulfill the user stories below and get all the tests to pass to complete the lab. **Do not copy this demo project**.
+**Objetivo:** atender às histórias de usuário abaixo e fazer todos os testes passarem para completar o laboratório. **Não copie este projeto de demonstração**.
 
-**User Stories:**
+**Histórias de usuário:**
 
-1. You should have a `textarea` element with the `id` of `text-input`.
-2. There should be a `p` element with the `id` of `char-count`. It should initially contain the text `Character Count: 0/50`. This placeholder text should be replaced with the current count of characters in the `textarea` element.
-3. When the `#text-input` element contains the text `hello coder` the `#char-count` element should contain the text `"Character Count: 11/50"`
-4. When the `#text-input` element contains the text `i am a programmer` the `#char-count` element should contain the text `"Character Count: 17/50"`
-5. When the `#text-input` element contains the text `hello world` the `#char-count` element should contain the text `"Character Count: 11/50"`
-6. When the `#text-input` element contains the text `I am learning a new language and it is called c++.` the `#char-count` element should contain the text `"Character Count: 50/50"`.
-7. The user should not be able to enter more than `50` characters in the `textarea` element. When the character count reaches `50`, the text `Character Count: 50/50` should be displayed in `red`.
+1. Você deve ter um elemento `textarea` com o `id` de `text-input`.
+2. Deve haver um elemento `p` com o `id` de `char-count`. Deve conter inicialmente o texto `Character Count: 0/50`. Este texto de substituição deve ser substituído pela contagem atual de caracteres no elemento `textarea`.
+3. Quando o elemento `#text-input` contiver o texto `hello coder`, o elemento `#char-count` deverá conter o texto `"Character Count: 11/50"`
+4. Quando o elemento `#text-input` contiver o texto `i am a programmer`, o elemento `#char-count` deverá conter o texto `"Character Count: 17/50"`
+5. Quando o elemento `#text-input` contiver o texto `hello world`, o elemento `#char-count` deverá conter o texto `"Character Count: 11/50"`
+6. Quando o elemento `#text-input` contiver o texto `I am learning a new language and it is called c++.`, o elemento `#char-count` deverá conter o texto `"Character Count: 50/50"`.
+7. O usuário não deve conseguir inserir mais de `50` caracteres no elemento `textarea`. Quando a contagem de caracteres alcançar `50`, o texto `Character Count: 50/50` deve ser exibido usando a cor `red`.
 
-**Note:** Be sure to link your stylesheet and the JavaScript file in your HTML.
+**Observação:** certifique-se de vincular sua folha de estilo e o arquivo JavaScript no seu HTML.
 
 # --hints--
 
-You should have a `textarea` element with the `id` of `text-input`.
+Você deve ter um elemento `textarea` com o `id` de `text-input`.
 
 ```js
 const textInput = document.querySelector('textarea');
 assert.equal(textInput.id, 'text-input');
 ```
 
-You should have a `p` element with the `id` of `char-count`.
+Você deve ter um elemento `p` com o `id` de `char-count`.
 
 ```js
 const charCount = document.querySelector('p');
 assert.equal(charCount.id, 'char-count');
 ```
 
-The `#char-count` `p` element should initially contain the text `Character Count: 0/50`.
+O elemento `#char-count` `p` deve inicialmente conter o texto `Character Count: 0/50`.
 
 ```js
 assert(document.querySelector('p')?.innerText, 'Character Count: 0/50');
 ```
 
-When the `#text-input` element contains the text `hello coder` the `#char-count` element should contain the text `"Character Count: 11/50"`
+Quando o elemento `#text-input` contiver o texto `hello coder`, o elemento `#char-count` deverá conter o texto `"Character Count: 11/50"`
 
 ```js
 const textInput = document.getElementById('text-input');
@@ -57,7 +57,7 @@ textInput.dispatchEvent(new Event('change'));
 assert.strictEqual(charCount.innerText.trim(), 'Character Count: 11/50');
 ```
 
-When the character count is `50`, the text should be displayed in `red`.
+Quando a contagem de caracteres for `50`, o texto deve ser exibido na cor `red`.
 
 ```js
 const textInput = document.getElementById('text-input');
@@ -68,7 +68,7 @@ textInput.dispatchEvent(new Event('change'));
 assert.strictEqual(charCount.style.color, 'red');
 ```
 
-If character count is greater than or equal to `50`, the user shouldn't be able to enter more characters.
+Se a contagem de caracteres for maior ou igual a `50`, o usuário não deve conseguir inserir mais caracteres.
 
 ```js
 const textInput = document.getElementById('text-input');
diff --git a/curriculum/challenges/portuguese/25-front-end-development/lab-recipe-page/668f08ea07b99b1f4a91acab.md b/curriculum/challenges/portuguese/25-front-end-development/lab-recipe-page/668f08ea07b99b1f4a91acab.md
index 8f60e5dd4e..02c159f0cb 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/lab-recipe-page/668f08ea07b99b1f4a91acab.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/lab-recipe-page/668f08ea07b99b1f4a91acab.md
@@ -21,7 +21,7 @@ demoType: onClick
 1. Você deve ter um elemento `h2` com o texto `Ingredients` para a seção de ingredientes.
 1. Você deve ter uma lista não ordenada (elemento `ul`) com pelo menos quatro itens de lista (elementos `li`) que listam os ingredientes abaixo do primeiro elemento `h2`.
 1. Você deve ter um segundo elemento `h2` com o texto `Instructions` para a seção de instruções.
-1. Você deve ter uma lista ordenada (elemento `ol`) com pelo menos quatro itens de lista que listam as etapas da receita em ordem, abaixo do segundo elemento `h2`.
+1. Você deve ter uma lista ordenada (elemento `ol`) com pelo menos quatro itens de lista que listam os passos da receita em ordem, abaixo do segundo elemento `h2`.
 1. Você deve ter um elemento `img` com um atributo `src` definido para uma imagem válida, você pode usar `https://cdn.freecodecamp.org/curriculum/labs/recipe.jpg` se preferir, além de um atributo `alt` descrevendo a imagem.
 
 # --hints--
diff --git a/curriculum/challenges/portuguese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md b/curriculum/challenges/portuguese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
new file mode 100644
index 0000000000..5040e27424
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
@@ -0,0 +1,65 @@
+---
+id: bd7158d8c443edefaeb5bdff
+title: Build a Request Header Parser Microservice
+challengeType: 4
+dashedName: lab-request-header-parser-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://request-header-parser-microservice.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://request-header-parser-microservice.freecodecamp.rocks/</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/request-header-parser-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+A request to `/api/whoami` should return a JSON object with your IP address in the `ipaddress` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.ipaddress && data.ipaddress.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your preferred language in the `language` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.language && data.language.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your software in the `software` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.software && data.software.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/lab-stylized-to-do-list/66c051d13a6a20255a963695.md b/curriculum/challenges/portuguese/25-front-end-development/lab-stylized-to-do-list/66c051d13a6a20255a963695.md
index 29a914364d..1d14a51673 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/lab-stylized-to-do-list/66c051d13a6a20255a963695.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/lab-stylized-to-do-list/66c051d13a6a20255a963695.md
@@ -1,6 +1,6 @@
 ---
 id: 66c051d13a6a20255a963695
-title: Build a Stylized To-Do list
+title: Compilar uma lista de tarefas estilizada
 challengeType: 14
 dashedName: build-a-stylized-to-do-list
 demoType: onClick
@@ -8,60 +8,60 @@ demoType: onClick
 
 # --description--
 
-In this lab, you will practice the different styles that can be applied to links when they are hovered over, focused, clicked, and visited.
+Neste laboratório, você praticará os diferentes estilos que podem ser aplicados aos links quando passado o mouse por cima, quando ele for focado, clicado e visitado.
 
-**Objective:** Fulfill the user stories below and get all the tests to pass to complete the lab.
+**Objetivo:** atender às histórias de usuário abaixo e fazer todos os testes passarem para completar o laboratório.
 
-**User Stories:**
+**Histórias de usuário:**
 
-1. You should have an unordered list with the class `todo-list`.
-2. Inside the unordered list, you should have four list items.
-3. Inside each list item, there should be:
+1. Você deve ter uma lista não ordenada com a classe `todo-list`.
+2. Dentro da lista não ordenada, você deve ter quatro itens de lista.
+3. Dentro de cada item de lista, deve haver:
 
-   - An `input` element with the type `checkbox` and `id` set to a unique value.
-   - A `label` element with the `for` attribute set to the corresponding `input` element's `id`.
-   - An unordered list with the class `sub-item`.
-   - A list item with an anchor element in it. The anchor should have the class `sub-item-link`, a valid `href` value, and a `target` value that makes the link open in a new tab.
+   - Um elemento `input` com o tipo `checkbox` e `id` definido para um valor único.
+   - Um elemento `label` com o atributo `for` definido para o `id` do elemento `input` correspondente.
+   - Uma lista não ordenada com a classe `sub-item`.
+   - Um item de lista com um elemento de âncora nele. A âncora deve ter a classe `sub-item-link`, um valor `href` válido e um valor `target`, que faça o link abrir em uma nova aba.
 
-4. You should remove the default list style from your `.todo-list`.
-5. Your anchor elements shouldn't have any default text decoration.
-6. You should set the text color of the links to a color of your choice.
-7. When your links are visited, the color should change to another color of your choice.
-8. When your links are hovered over, the color should change to another color of your choice.
-9.  When your links are focused, there should be a colored outline around the link.
-10. When your links are clicked, the color should change to another color of your choice.
+4. Você deve remover o estilo de lista padrão do seu `.todo-list`.
+5. Os elementos de âncora não devem ter nenhuma decoração de texto padrão.
+6. Você deve definir a cor do texto dos links para uma cor de sua escolha.
+7. Quando os links são visitados, a cor deve mudar para outra cor de sua escolha.
+8. Quando os links são passados o mouse por cima, a cor deve mudar para outra cor de sua escolha.
+9.  Quando os links são focados, deve haver um contorno colorido em torno do link.
+10. Quando os links são clicados, a cor deve mudar para outra cor de sua escolha.
 
-**Note:** Be sure to link your stylesheet in your HTML and apply your CSS.
+**Observação:** certifique-se de vincular sua folha de estilo ao HTML e de aplicar o CSS.
 
 # --hints--
 
-You should have an unordered list with the class `todo-list`.
+Você deve ter uma lista não ordenada com a classe `todo-list`.
 
 ```js
 assert.exists(document.querySelector('.todo-list'));
 ```
 
-You should remove the default list style from your `.todo-list`.
+Você deve remover o estilo de lista padrão do elemento `.todo-list`.
 
 ```js
 assert(new __helpers.CSSHelp(document).getStyle('.todo-list')?.listStyleType === 'none' || new __helpers.CSSHelp(document).getStyle('.todo-list')?.listStyle === 'none');
 ```
 
-You should have four list items inside the unordered list.
+Você deve ter quatro itens de lista dentro da lista não ordenada.
 
 ```js
 const li = document.querySelectorAll('.todo-list li');
 assert.strictEqual(li.length, 8);
 ```
 
-Each list item should contain an `input` element with the type `checkbox`.
+Cada item de lista deve conter um elemento `input` com o tipo `checkbox`.
 
 ```js
 const checkboxes = document.querySelectorAll('.todo-list li input[type="checkbox"]');
 assert.strictEqual(checkboxes.length, 4);
 ```
 
-All of the `input` elements should have an `id`.
+Todos os elementos `input` devem ter um `id`.
 
 ```js
 const inputs = document.querySelectorAll('input');
@@ -71,21 +71,21 @@ for (let input of inputs) {
 }
 ```
 
-After the `label` elements, there should be an unordered list with the class `sub-item`.
+Após os elementos `label`, deve haver uma lista não ordenada com a classe `sub-item`.
 
 ```js
 const labelSbItems = document.querySelectorAll('label+ul.sub-item');
 assert.equal(labelSbItems.length, 4);
 ```
 
-The `li` inside the `ul` with the class `sub-item` should have an anchor element with the class `sub-item-link`.
+O `li` dentro do `ul` com a classe `sub-item` deve ter um elemento de âncora com a classe `sub-item-link`.
 
 ```js
 const allItems = document.querySelectorAll('label + ul.sub-item li a.sub-item-link');
 assert.equal(allItems.length, 4);
 ```
 
-All of the anchor elements should have a valid `href`.
+Todos os elementos de âncora devem ter um `href` válido.
 
 ```js
 const links = document.querySelectorAll('a');
@@ -95,7 +95,7 @@ for (let link of links) {
 }
 ```
 
-All of the `anchor` elements should have a text.
+Todos os elementos `anchor` devem ter um texto.
 
 ```js
 const links = document.querySelectorAll('a');
@@ -105,7 +105,7 @@ for (let link of links) {
 }
 ```
 
-All of the `label` elements should have a `for` attribute.
+Todos os elementos `label` devem ter um atributo `for`.
 
 ```js
 const labels = document.querySelectorAll('label');
@@ -115,7 +115,7 @@ for (let label of labels) {
 }
 ```
 
-All of the `label` elements should have some text.
+Todos os elementos `label` devem ter algum texto.
 
 ```js
 const labels = document.querySelectorAll('label');
@@ -125,7 +125,7 @@ for (let label of labels) {
 }
 ```
 
-Each `a` element should have a `target` attribute with the value of `_blank`.
+Cada elemento `a` deve ter um atributo `target` com o valor de `_blank`.
 
 ```js
 const anchors = document.querySelectorAll('a');
@@ -135,33 +135,33 @@ for (let anchor of anchors) {
 }
 ```
 
-The links on the page should have no underline by default.
+Os links na página não devem ser sublinhados por padrão.
 
 ```js
 assert(new __helpers.CSSHelp(document).getStyle('a.sub-item-link')?.textDecoration === 'none' || new __helpers.CSSHelp(document).getStyle('a')?.textDecoration === 'none' ||  new __helpers.CSSHelp(document).getStyle('.sub-item-link')?.textDecoration === 'none' );
 
 ```
 
-The links should change color when hovered over.
+Os links devem mudar de cor quando passado o mouse por cima.
 
 ```js
 assert(new __helpers.CSSHelp(document).getStyle('.sub-item-link:hover')?.color || new __helpers.CSSHelp(document).getStyle('a:hover')?.color || new __helpers.CSSHelp(document).getStyle('a.sub-item-link:hover')?.color);
 ```
 
-The links should change color when they are being clicked.
+Os links devem mudar de cor quando estão sendo clicados.
 
 ```js
 assert(new __helpers.CSSHelp(document).getStyle('.sub-item-link:active')?.color || new __helpers.CSSHelp(document).getStyle('a:active')?.color || new __helpers.CSSHelp(document).getStyle('a.sub-item-link:active')?.color);
 ```
 
-The links should have an outline when focused.
+Os links devem ter um contorno quando focados.
 
 ```js
 assert(new __helpers.CSSHelp(document).getStyle('.sub-item-link:focus')?.outline || new __helpers.CSSHelp(document).getStyle('a:focus')?.outline || new __helpers.CSSHelp(document).getStyle('a.sub-item-link:focus')?.outline);
 
 ```
 
-The links should change color once visited.
+Os links devem mudar de cor ao serem visitados.
 
 ```js
 assert(new __helpers.CSSHelp(document).getStyle('.sub-item-link:visited')?.color || new __helpers.CSSHelp(document).getStyle('a:visited')?.color || new __helpers.CSSHelp(document).getStyle('a.sub-item-link:visited')?.color);
diff --git a/curriculum/challenges/portuguese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md b/curriculum/challenges/portuguese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
new file mode 100644
index 0000000000..0fbf80a0bf
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
@@ -0,0 +1,107 @@
+---
+id: bd7158d8c443edefaeb5bd0e
+title: URL Shortener Microservice
+challengeType: 4
+dashedName: url-shortener-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://url-shortener-microservice.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://url-shortener-microservice.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+**HINT:** Do not forget to use a body parsing middleware to handle the POST requests. Also, you can use the function `dns.lookup(host, cb)` from the `dns` core module to verify a submitted URL.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/url-shortener-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+You can POST a URL to `/api/shorturl` and get a JSON response with `original_url` and `short_url` properties. Here's an example: `{ original_url : 'https://freeCodeCamp.org', short_url : 1}`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (res.ok) {
+    const { short_url, original_url } = await res.json();
+    assert.isNotNull(short_url);
+    assert.strictEqual(original_url, `${url}/?v=${urlVariable}`);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+When you visit `/api/shorturl/<short_url>`, you will be redirected to the original URL.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  let shortenedUrlVariable;
+  const postResponse = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (postResponse.ok) {
+    const { short_url } = await postResponse.json();
+    shortenedUrlVariable = short_url;
+  } else {
+    throw new Error(`${postResponse.status} ${postResponse.statusText}`);
+  }
+  const getResponse = await fetch(
+    url + '/api/shorturl/' + shortenedUrlVariable
+  );
+  if (getResponse) {
+    const { redirected, url } = getResponse;
+    assert.isTrue(redirected);
+    assert.strictEqual(url,fullUrl);
+  } else {
+    throw new Error(`${getResponse.status} ${getResponse.statusText}`);
+  }
+};
+```
+
+If you pass an invalid URL that doesn't follow the valid `http://www.example.com` format, the JSON response will contain `{ error: 'invalid url' }`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=ftp:/john-doe.invalidTLD`
+  });
+  if (res.ok) {
+    const { error } = await res.json();
+    assert.isNotNull(error);
+    assert.strictEqual(error.toLowerCase(), 'invalid url');
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md b/curriculum/challenges/portuguese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
new file mode 100644
index 0000000000..d77442a1ba
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
@@ -0,0 +1,25 @@
+---
+id: 5f9771307d4d22b9d2b75a94
+title: Build a World Cup Database
+challengeType: 13
+url: freeCodeCamp/learn-world-cup-database
+dashedName: lab-world-cup-database
+---
+
+# --description--
+
+For this project, you will create a Bash script that enters information from World Cup games into PostgreSQL, then query the database for useful statistics.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `worldcup.sql` file, as well as your `insert_data.sh` and `queries.sh` files, so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `worldcup.sql`, `insert_data.sh`, `queries.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-blog-page/66a33e9bd3aa213cd23d9c57.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-blog-page/66a33e9bd3aa213cd23d9c57.md
index dac16f172d..2ba0774b5c 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-blog-page/66a33e9bd3aa213cd23d9c57.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-blog-page/66a33e9bd3aa213cd23d9c57.md
@@ -7,7 +7,7 @@ dashedName: step-21
 
 # --description--
 
-Para a etapa final, você precisará adicionar o número de telefone e o endereço de e-mail do autor do blog.
+Para o passo final, você precisará adicionar o número de telefone e o endereço de e-mail do autor do blog.
 
 Dentro do elemento `address`, adicione um elemento de parágrafo com o texto `Phone: 555-555-5555`.
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-calculator/66cc0de2920bec775f610424.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-calculator/66cc0de2920bec775f610424.md
index bac639f8c0..c2c5aac2ff 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-calculator/66cc0de2920bec775f610424.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-calculator/66cc0de2920bec775f610424.md
@@ -15,7 +15,7 @@ Seria melhor criar uma única função reutilizável que possa adicionar dois n
 
 Remova todo o código que você escreveu até agora.
 
-Na próxima etapa, você revisará como trabalhar com parâmetros e argumentos em funções.
+No próximo passo, você revisará como trabalhar com parâmetros e argumentos em funções.
 
 # --hints--
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-calculator/66cc281d687975858049fd8d.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-calculator/66cc281d687975858049fd8d.md
index 2137636350..1859935c91 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-calculator/66cc281d687975858049fd8d.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-calculator/66cc281d687975858049fd8d.md
@@ -7,7 +7,7 @@ dashedName: step-19
 
 # --description--
 
-Na etapa final do workshop, você precisará testar a função `calculateSquareRoot`.
+No passo final do workshop, você precisará testar a função `calculateSquareRoot`.
 
 Adicione um segundo `console.log` que chama a função `calculateSquareRoot` com o argumento de `25`.
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-final-exams-table/66a9ca099e3ecb1be10a2696.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-final-exams-table/66a9ca099e3ecb1be10a2696.md
index 6a9f1759e4..29a5def035 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-final-exams-table/66a9ca099e3ecb1be10a2696.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-final-exams-table/66a9ca099e3ecb1be10a2696.md
@@ -9,7 +9,7 @@ dashedName: step-10
 
 Agora é hora de adicionar mais dois estudantes à tabela.
 
-Seguindo o mesmo padrão das etapas anteriores, adicione uma quarta `table row` de estudante. Use os seguintes dados para os elementos de `table data`:
+Seguindo o mesmo padrão dos passos anteriores, adicione uma quarta `table row` de estudante. Use os seguintes dados para os elementos de `table data`:
 
 - Sobrenome: `Thompson`
 - Nome: `Jane`
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-greeting-bot/66add47d27763c4862492c8c.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-greeting-bot/66add47d27763c4862492c8c.md
index 3db439ad70..e1ac777b10 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-greeting-bot/66add47d27763c4862492c8c.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-greeting-bot/66add47d27763c4862492c8c.md
@@ -7,7 +7,7 @@ dashedName: step-15
 
 # --description--
 
-Para a etapa final, você registrará a mensagem do bot de `"Well, it was nice to talk to you. Have a nice day!"` no console.
+Para o passo final, você registrará a mensagem do bot de `"Well, it was nice to talk to you. Have a nice day!"` no console.
 
 Com isso, o bot de saudações está completo!
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
index 25b4ca6e2f..4e9bdc047d 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
@@ -7,9 +7,9 @@ dashedName: step-22
 
 # --description--
 
-Adicione outro `label` com o texto `Personal Recommendation`. O atributo `for` deve estar definido como `"recommendation"`.
+Add another `label` with the text of `Personal Recommendation`. O atributo `for` deve estar definido como `"recommendation"`.
 
-Abaixo do elemento `label`, adicione outro `input` de caixa de seleção com os atributos `id`, `name` e `value` definidos como `"recommendation"`.
+Below the `label` element, add another checkbox `input` with the `id`, `name` and `value` attributes set to `"recommendation"`.
 
 # --hints--
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
index d39b9294a5..2c29cfc58b 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
@@ -11,7 +11,7 @@ Em seguida, adicione outro elemento `label` com o texto `Location` e o atributo
 
 Para o `input` de caixa de seleção, os atributos `id`, `name` e `value` devem ser definidos como `"location"`.
 
-Abaixo desse elemento `input`, adicione outro elemento `label` com o texto `Reputation` e o atributo `for` definido como `"reputation"`.
+Below that `input` element, add another `label` element with the text of `Reputation` and the `for` attribute set to `"reputation"`.
 
 Para o `input` de caixa de seleção, os atributos `id`, `name` e `value` devem ser definidos como `"reputation"`.
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
index 2e77fb4dc6..239ad7da0f 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
@@ -7,7 +7,7 @@ dashedName: step-28
 
 # --description--
 
-Dentro do elemento `select`, adicione os cinco elementos `option` a seguir, com os valores correspondentes para o texto da opção e o atributo `value`:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Atributos de value:**
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
index a65464d38d..d03388ad59 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
@@ -7,7 +7,7 @@ dashedName: step-31
 
 # --description--
 
-Dentro do elemento `select`, adicione os seguintes cinco elementos `option` com esses valores correspondentes para o texto dos atributos `value` e `option`:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Atributo value:**
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a9843525e9fa8046d709b7.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a9843525e9fa8046d709b7.md
index dc9fceb1c5..80b61f8c1b 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a9843525e9fa8046d709b7.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-hotel-feedback-form/66a9843525e9fa8046d709b7.md
@@ -7,7 +7,7 @@ dashedName: step-35
 
 # --description--
 
-Para a última etapa do workshop de formulário de feedback de hotéis, você precisará adicionar um botão de envio ao formulário.
+Para o último passo do workshop de formulário de feedback de hotéis, você precisará adicionar um botão de envio ao formulário.
 
 Lembre-se de que você aprendeu a trabalhar com botões de envio nos vídeos da aula anterior.
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
new file mode 100644
index 0000000000..af553ceaec
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
@@ -0,0 +1,71 @@
+---
+id: 66c8ba41a77db20a93f9d7a1
+title: Passo 1
+challengeType: 1
+dashedName: step-1
+---
+
+# --description--
+
+Neste workshop, você revisará condicionais JavaScript criando uma aplicação verificadora de qualificação para empréstimo.
+
+A aplicação verificará se o usuário é elegível para um empréstimo de duplex, carro e condomínio com base na renda anual e pontuação de crédito. Uma pontuação de crédito é um número que representa o nível de gerenciamento de dinheiro emprestado.
+
+Para começar, crie as seguintes variáveis e valores.
+
+| Nome da variável          | Valor   |
+| ------------------------- | ------- |
+| `minIncomeForDuplex`      | `60000` |
+| `minCreditScoreForDuplex` | `700`   |
+| `minIncomeForCondo`       | `45000` |
+| `minCreditScoreForCondo`  | `680`   |
+| `minIncomeForCar`         | `30000` |
+| `minCreditScoreForCar`    | `650`   |
+
+# --hints--
+
+Você deve criar uma variável `minIncomeForDuplex` definida como `60000`.
+
+```js
+assert.equal(minIncomeForDuplex, 60000);
+```
+
+Você deve criar uma `minCreditScoreForDuplex` definida como `700`.
+
+```js
+assert.equal(minCreditScoreForDuplex, 700);
+```
+
+Você deve criar uma variável `minIncomeForCar` definida como `30000`.
+
+```js
+assert.equal(minIncomeForCar, 30000);
+```
+
+Você deve criar uma variável `minCreditScoreForCar` definida como `650`.
+
+```js
+assert.equal(minCreditScoreForCar, 650);
+```
+
+Você deve criar uma variável `minIncomeForCondo` definida como `45000`.
+
+```js
+assert.equal(minIncomeForCondo, 45000);
+```
+
+Você deve criar uma variável `minCreditScoreForCondo` definida como `680`.
+
+```js
+assert.equal(minCreditScoreForCondo, 680);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
new file mode 100644
index 0000000000..629fee13a9
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
@@ -0,0 +1,53 @@
+---
+id: 66c8ba975ee7230e29f6c4ac
+title: Passo 2
+challengeType: 1
+dashedName: step-2
+---
+
+# --description--
+
+Quando o usuário for elegível para um empréstimo, você vai querer exibir uma mensagem para ele no console.
+
+Para isso, você vai criar uma função dentro da qual terá algumas verificações que retornarão para qual empréstimo o candidato é elegível.
+
+Crie uma função vazia `getLoanMessage` com parâmetros `annualIncome` e `creditScore`.
+
+# --hints--
+
+Você deve criar uma função `getLoanMessage`
+
+```js
+assert.isFunction(getLoanMessage)
+```
+
+A função `getLoanMessage` deve ter `annualIncome` e `creditScore` como parâmetros.
+
+```js
+assert.match(getLoanMessage?.toString(), /\(\s*annualIncome,\s*creditScore\s*\)|\(\s*creditScore,\s*annualIncome\s*\)/);
+```
+
+`getLoanMessage` deve ser uma função vazia.
+
+```js
+assert.match(getLoanMessage?.toString(), /\{\s*\}/);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
new file mode 100644
index 0000000000..ffc0c81f12
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
@@ -0,0 +1,55 @@
+---
+id: 66c8ba975ee7230e29f6c4ad
+title: Passo 3
+challengeType: 1
+dashedName: step-3
+---
+
+# --description--
+
+Para verificar para qual empréstimo um usuário está qualificado com base na `annualIncome` e na `creditScore`, você deve usar a instrução `if/else if` ou um ternário dentro da função `getLoanMessage`. Você então retornará a string adequada no bloco de cada condição.
+
+Começando com o empréstimo duplex, verifique se `annualIncome` é maior ou igual a `minIncomeForDuplex` E se `creditScore` é maior que `minCreditScoreForDuplex`.
+
+Se essa condição for verdadeira, então o candidato é elegível para um empréstimo duplex e os outros empréstimos. Então, dentro da verificação, retorne a string `"You qualify for a car, duplex and Condo loan."`
+
+# --hints--
+
+A função `getLoanMessage` deve retornar uma string.
+
+```js
+assert.isString(getLoanMessage(65000, 750));
+```
+
+A função `getLoanMessage` deve retornar a string `"You qualify for a duplex, condo, and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(65000, 750), "You qualify for a duplex, condo, and car loan.");
+```
+
+A função `getLoanMessage` deve retornar `undefined` se a renda anual do candidato e a pontuação de crédito não atenderem aos requisitos para um empréstimo duplex.
+
+```js
+assert.strictEqual(getLoanMessage(59000, 700), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+function getLoanMessage(annualIncome, creditScore) {
+
+}
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
new file mode 100644
index 0000000000..1ab05b6efd
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4af
+title: Passo 4
+challengeType: 1
+dashedName: step-4
+---
+
+# --description--
+
+Se a renda anual do candidato for maior ou igual a `minIncomeForCondo`, E se a pontuação de crédito for maior ou igual a `minCreditScoreForCondo`, então ele se qualifica para um empréstimo de condomínio e carro.
+
+Verifique se isso é verdade na função `getLoanMessage`. Se for, retorne a string `"You qualify for a condo and car loan."`
+
+# --hints--
+
+A função `getLoanMessage` deve retornar uma string se o candidato se qualificar para um empréstimo de condomínio e carro.
+
+```js
+assert.isString(getLoanMessage(45000, 680));
+```
+
+A função `getLoanMessage` deve retornar a string `"You qualify for a condo and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 680), "You qualify for a condo and car loan.");
+```
+
+A função `getLoanMessage` deve retornar `undefined` se a renda anual e a pontuação de crédito do candidato não atenderem aos requisitos para um empréstimo de condomínio.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 650), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
new file mode 100644
index 0000000000..e81b54a30e
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4b0
+title: Passo 5
+challengeType: 1
+dashedName: step-5
+---
+
+# --description--
+
+Agora, você deve verificar se o solicitante está qualificado apenas para um empréstimo de carro. Se estiver, retorne a string `"You qualify for a car loan."`.
+
+# --hints--
+
+A função `getLoanMessage` deve retornar uma string se o solicitante estiver qualificado para um empréstimo de carro.
+
+```js
+assert.isString(getLoanMessage(30000, 650));
+```
+
+A função `getLoanMessage` deve retornar a string `"You qualify for a car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 650), "You qualify for a car loan.");
+```
+
+A função `getLoanMessage` deve retornar `undefined` se a renda anual e a pontuação de crédito do solicitante não atenderem aos requisitos para um empréstimo de carro.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 600), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+--fcc-editable-region--
+  } 
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
new file mode 100644
index 0000000000..c49a7a6557
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
@@ -0,0 +1,54 @@
+---
+id: 66c8ba975ee7230e29f6c4b1
+title: Passo 6
+challengeType: 1
+dashedName: step-6
+---
+
+# --description--
+
+Se a renda anual do solicitante e a pontuação de crédito estiverem abaixo de `minIncomeForCar` e `minCreditScoreForCar`, ele não se qualifica para nenhum empréstimo. Então, retorne a string `"You don't qualify for any loans."`
+
+# --hints--
+
+A função `getLoanMessage` deve retornar uma string se o solicitante não se qualificar para nenhum empréstimo.
+
+```js
+assert.isString(getLoanMessage(25000, 550));
+```
+
+A função `getLoanMessage` deve retornar a string `"You don't qualify for any loans."` se o solicitante não atender aos requisitos para nenhum empréstimo.
+
+```js
+assert.strictEqual(getLoanMessage(15000, 600), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(25000, 550), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(20000, 500), "You don't qualify for any loans.");
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
new file mode 100644
index 0000000000..37d1ef1f85
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
@@ -0,0 +1,165 @@
+---
+id: 66c8ba975ee7230e29f6c4b2
+title: Passo 7
+challengeType: 1
+dashedName: step-7
+---
+
+# --description--
+
+Agora é hora de testar a função `getLoanMessage`.
+
+Use a tabela abaixo para criar `4` variáveis e seus valores:
+
+| Nome da variável | Valor                        |
+| ---------------- | ---------------------------- |
+| `duplexLoanMsg`  | `getLoanMessage(85000, 850)` |
+| `condoLoanMsg`   | `getLoanMessage(65000, 690)` |
+| `carLoanMsg`     | `getLoanMessage(45000, 660)` |
+| `noLoanMsg`      | `getLoanMessage(25000, 550)` |
+
+Após isso, registre cada variável no console para ver as mensagens.
+
+Com isso, o projeto de verificação de qualificação de empréstimo está completo!
+
+# --hints--
+
+Você deve ter uma variável chamada `duplexLoanMsg`.
+
+```js
+assert.isNotNull(duplexLoanMsg);
+```
+
+A variável `duplexLoanMsg` deve ser definida como o resultado de `getLoanMessage(85000, 850)`.
+
+```js
+assert.equal(duplexLoanMsg, getLoanMessage(85000, 850));
+```
+
+Você deve registrar a variável `duplexLoanMsg` no console.
+
+```js
+assert.match(code, /console\.log\(duplexLoanMsg\)/)
+```
+
+Você deve ter uma variável chamada `condoLoanMsg`.
+
+```js
+assert.isNotNull(condoLoanMsg);
+```
+
+A variável `condoLoanMsg` deve ser definida como o resultado de `getLoanMessage(65000, 690)`.
+
+```js
+assert.equal(condoLoanMsg, getLoanMessage(65000, 690));
+```
+
+Você deve registrar a variável `condoLoanMsg` no console.
+
+```js
+assert.match(code, /console\.log\(condoLoanMsg\)/)
+```
+
+Você deve ter uma variável chamada `carLoanMsg`.
+
+```js
+assert.isNotNull(carLoanMsg);
+```
+
+A variável `carLoanMsg` deve ser definida como o resultado de `getLoanMessage(45000, 660)`.
+
+```js
+assert.equal(carLoanMsg, getLoanMessage(45000, 660));
+```
+
+Você deve registrar a variável `carLoanMsg` no console.
+
+```js
+assert.match(code, /console\.log\(carLoanMsg\)/)
+```
+
+Você deve ter uma variável chamada `noLoanMsg`.
+
+```js
+assert.isNotNull(noLoanMsg);
+```
+
+A variável `noLoanMsg` deve ser definida como o resultado de `getLoanMessage(25000, 550)`.
+
+```js
+assert.equal(noLoanMsg, getLoanMessage(25000, 550));
+```
+
+Você deve registrar a variável `noLoanMsg` no console.
+
+```js
+assert.match(code, /console\.log\(noLoanMsg\)/)
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
+
+# --solutions--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+const duplexLoanMsg = getLoanMessage(85000, 850)
+console.log(duplexLoanMsg)
+
+const condoLoanMsg = getLoanMessage(65000, 690)
+console.log(condoLoanMsg)
+
+const carLoanMsg = getLoanMessage(45000, 660)
+console.log(carLoanMsg)
+
+const noLoanMsg = getLoanMessage(25000, 550)
+console.log(noLoanMsg)
+```
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
new file mode 100644
index 0000000000..4e11751ca0
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
@@ -0,0 +1,19 @@
+---
+id: 5f2c289f164c29556da632fd
+title: Build a Mario Database
+challengeType: 12
+url: freeCodeCamp/learn-relational-databases-by-building-a-mario-database
+dashedName: build-a-mario-database
+---
+
+# --description--
+
+In this 165-lesson workshop, you will learn the basics of a relational database by creating a PostgreSQL database filled with video game characters.
+
+# --instructions--
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
new file mode 100644
index 0000000000..8d4c90410d
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
@@ -0,0 +1,53 @@
+---
+id: 587d7fb3367417b2b2512bfb
+title: How to Use package.json, the Core of Any Node.js Project or npm Package
+challengeType: 2
+forumTopicId: 301528
+dashedName: how-to-use-package-json-the-core-of-any-node-js-project-or-npm-package
+---
+
+# --description--
+
+Working on these challenges will involve you writing your code using one of the following methods:
+
+- Clone <a href="https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete these challenges locally.
+- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+The `package.json` file is the center of any Node.js project or npm package. It stores information about your project. It consists of a single JSON object where information is stored in key-value pairs. There are only two required fields; `name` and `version`, but it’s good practice to provide additional information.
+
+You can create the `package.json` file from the terminal using the `npm init` command. This will run a guided setup. Using `npm init` with the `-y` flag will generate the file without having it ask any questions, `npm init -y`.
+
+If you look at the file tree of your project, you will find the `package.json` file on the top level of the tree. This is the file that you will be improving in the next couple of challenges.
+
+One of the most common pieces of information in this file is the `author` field. It specifies who created the project, and can consist of a string or an object with contact or other details. An object is recommended for bigger projects, but a simple string like the following example will do for this project.
+
+```json
+"author": "Jane Doe",
+```
+
+# --instructions--
+
+Add your name as the `author` of the project in the `package.json` file.
+
+**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (") and be separated with a comma (,).
+
+If you are using Gitpod, make sure the app is running and the preview window is open. Copy the preview window's URL and paste it into the Solution Link input below.
+
+# --hints--
+
+`package.json` should have a valid "author" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.author, '"author" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
new file mode 100644
index 0000000000..37d15d5261
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb3367417b2b2512bfc
+title: Add a Description to Your package.json
+challengeType: 2
+forumTopicId: 301522
+dashedName: add-a-description-to-your-package-json
+---
+
+# --description--
+
+The next part of a good package.json file is the `description` field; where a short, but informative description about your project belongs.
+
+If some day you plan to publish a package to npm, this is the string that should sell your idea to the user when they decide whether to install your package or not. However, that’s not the only use case for the description, it’s a great way to summarize what a project does. It’s just as important in any Node.js project to help other developers, future maintainers or even your future self understand the project quickly.
+
+Regardless of what you plan for your project, a description is definitely recommended. Here's an example:
+
+```json
+"description": "A project that does something awesome",
+```
+
+# --instructions--
+
+Add a `description` to the package.json file of your project.
+
+**Note:** Remember to use double-quotes for field-names (") and commas (,) to separate fields.
+
+# --hints--
+
+package.json should have a valid "description" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.description, '"description" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
new file mode 100644
index 0000000000..a001cdd477
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
@@ -0,0 +1,75 @@
+---
+id: 587d7fb4367417b2b2512bfd
+title: Add Keywords to Your package.json
+challengeType: 2
+forumTopicId: 301526
+dashedName: add-keywords-to-your-package-json
+---
+
+# --description--
+
+The `keywords` field is where you can describe your project using related keywords. Here's an example:
+
+```json
+"keywords": [ "descriptive", "related", "words" ],
+```
+
+As you can see, this field is structured as an array of double-quoted strings.
+
+# --instructions--
+
+Add an array of suitable strings to the `keywords` field in the package.json file of your project.
+
+One of the keywords should be "freecodecamp".
+
+# --hints--
+
+package.json should have a valid "keywords" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.keywords, '"keywords" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" field should be an Array
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.isArray(packJson.keywords, '"keywords" is not an array');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" should include "freecodecamp"
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.include(
+        packJson.keywords,
+        'freecodecamp',
+        '"keywords" does not include "freecodecamp"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
new file mode 100644
index 0000000000..7b09acd042
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
@@ -0,0 +1,39 @@
+---
+id: 587d7fb4367417b2b2512bfe
+title: Add a License to Your package.json
+challengeType: 2
+forumTopicId: 301523
+dashedName: add-a-license-to-your-package-json
+---
+
+# --description--
+
+The `license` field is where you inform users of what they are allowed to do with your project.
+
+Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do. Here's an example of the license field:
+
+```json
+"license": "MIT",
+```
+
+# --instructions--
+
+Fill the `license` field in the package.json file of your project as you find suitable.
+
+# --hints--
+
+package.json should have a valid "license" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.license, '"license" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
new file mode 100644
index 0000000000..f2e571faed
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
@@ -0,0 +1,37 @@
+---
+id: 587d7fb4367417b2b2512bff
+title: Add a Version to Your package.json
+challengeType: 2
+forumTopicId: 301525
+dashedName: add-a-version-to-your-package-json
+---
+
+# --description--
+
+A `version` is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example:
+
+```json
+"version": "1.2.0",
+```
+
+# --instructions--
+
+Add a `version` to the package.json file of your project.
+
+# --hints--
+
+package.json should have a valid "version" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.version, '"version" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
new file mode 100644
index 0000000000..161c60fe69
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
@@ -0,0 +1,68 @@
+---
+id: 587d7fb4367417b2b2512c00
+title: Expand Your Project with External Packages from npm
+challengeType: 2
+forumTopicId: 301527
+dashedName: expand-your-project-with-external-packages-from-npm
+---
+
+# --description--
+
+One of the biggest reasons to use a package manager, is their powerful dependency management. Instead of manually having to make sure that you get all dependencies whenever you set up a project on a new computer, npm automatically installs everything for you. But how can npm know exactly what your project needs? Meet the `dependencies` section of your package.json file.
+
+In this section, packages your project requires are stored using the following format:
+
+```json
+"dependencies": {
+  "package-name": "version",
+  "express": "4.14.0"
+}
+
+```
+
+# --instructions--
+
+Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file.
+
+**Note:** `@freecodecamp/example` is a faux package used as a learning tool.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.1.0"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^[\^\~]?1\.1\.0/,
+        'Wrong version of "@freecodecamp/example" installed. It should be 1.1.0'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
new file mode 100644
index 0000000000..deda9b82de
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
@@ -0,0 +1,64 @@
+---
+id: 587d7fb5367417b2b2512c01
+title: Manage npm Dependencies By Understanding Semantic Versioning
+challengeType: 2
+forumTopicId: 301529
+dashedName: manage-npm-dependencies-by-understanding-semantic-versioning
+---
+
+# --description--
+
+`Versions` of the npm packages in the dependencies section of your package.json file follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes projects can expect if they update.
+
+Knowing SemVer can be useful when you develop software that uses external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things that worked yesterday suddenly don’t work today. This is how Semantic Versioning works according to the official website:
+
+```json
+"package": "MAJOR.MINOR.PATCH"
+```
+
+The MAJOR version should increment when you make incompatible API changes. The MINOR version should increment when you add functionality in a backwards-compatible manner. The PATCH version should increment when you make backwards-compatible bug fixes. This means that PATCHes are bug fixes and MINORs add new features but neither of them break what worked before. Finally, MAJORs add changes that won’t work with earlier versions.
+
+# --instructions--
+
+In the dependencies section of your `package.json` file, change the version of `@freecodecamp/example` to match MAJOR version 1, MINOR version 2 and PATCH version 13
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.equal(
+        packJson.dependencies["@freecodecamp/example"],
+        '1.2.13',
+        'Wrong version of "@freecodecamp/example". It should be 1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
new file mode 100644
index 0000000000..8eae5f51ee
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c02
+title: Use the Tilde-Character to Always Use the Latest Patch Version of a Dependency
+challengeType: 2
+forumTopicId: 301532
+dashedName: use-the-tilde-character-to-always-use-the-latest-patch-version-of-a-dependency
+---
+
+# --description--
+
+In the last challenge, you told npm to only include a specific version of a package. That’s a useful way to freeze your dependencies if you need to make sure that different parts of your project stay compatible with each other. But in most use cases, you don’t want to miss bug fixes since they often include important security patches and (hopefully) don’t break things in doing so.
+
+To allow an npm dependency to update to the latest PATCH version, you can prefix the dependency’s version with the tilde (`~`) character. Here's an example of how to allow updates to any `1.3.x` version.
+
+```json
+"package": "~1.3.8"
+```
+
+# --instructions--
+
+In the package.json file, your current rule for how npm may upgrade `@freecodecamp/example` is to use a specific version (`1.2.13`). But now, you want to allow the latest `1.2.x` version.
+
+Use the tilde (`~`) character to prefix the version of `@freecodecamp/example` in your dependencies, and allow npm to update it to any new _patch_ release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"~1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\~1\.2\.13/,
+        'Wrong version of "@freecodecamp/example". It should be ~1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
new file mode 100644
index 0000000000..adc3014ea4
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c03
+title: Use the Caret-Character to Use the Latest Minor Version of a Dependency
+challengeType: 2
+forumTopicId: 301531
+dashedName: use-the-caret-character-to-use-the-latest-minor-version-of-a-dependency
+---
+
+# --description--
+
+Similar to how the tilde we learned about in the last challenge allows npm to install the latest PATCH for a dependency, the caret (`^`) allows npm to install future updates as well. The difference is that the caret will allow both MINOR updates and PATCHes.
+
+Your current version of `@freecodecamp/example` should be `~1.2.13` which allows npm to install to the latest `1.2.x` version. If you were to use the caret (^) as a version prefix instead, npm would be allowed to update to any `1.x.x` version.
+
+```json
+"package": "^1.3.8"
+```
+
+This would allow updates to any `1.x.x` version of the package.
+
+# --instructions--
+
+Use the caret (`^`) to prefix the version of `@freecodecamp/example` in your dependencies and allow npm to update it to any new MINOR release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"^1.x.x"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\^1\./,
+        'Wrong version of "@freecodecamp/example". It should be ^1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
new file mode 100644
index 0000000000..5f695eed88
--- /dev/null
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb5367417b2b2512c04
+title: Remove a Package from Your Dependencies
+challengeType: 2
+forumTopicId: 301530
+dashedName: remove-a-package-from-your-dependencies
+---
+
+# --description--
+
+You have now tested a few ways you can manage dependencies of your project by using the package.json's dependencies section. You have also included external packages by adding them to the file and even told npm what types of versions you want, by using special characters such as the tilde or the caret.
+
+But what if you want to remove an external package that you no longer need? You might already have guessed it, just remove the corresponding key-value pair for that package from your dependencies.
+
+This same method applies to removing other fields in your package.json as well.
+
+# --instructions--
+
+Remove the `@freecodecamp/example` package from your dependencies.
+
+**Note:** Make sure you have the right amount of commas after removing it.
+
+# --hints--
+
+`"dependencies"` should not include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.notProperty(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" still includes "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf13fe7619e9a1d57c7b5e.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf13fe7619e9a1d57c7b5e.md
index ec8a6e2d1e..43b0b04330 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf13fe7619e9a1d57c7b5e.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf13fe7619e9a1d57c7b5e.md
@@ -1,33 +1,33 @@
 ---
 id: 66cf13fe7619e9a1d57c7b5e
-title: Step 3
+title: Passo 3
 challengeType: 0
 dashedName: step-3
 ---
 
 # --description--
 
-The next step is to build out the functionality that will generate a random choice for the computer.
+O próximo passo é compilar a funcionalidade que gerará uma escolha aleatória para o computador.
 
-Create a function called `getRandomComputerResult` that returns a random choice from the `options` array.
+Crie uma função chamada `getRandomComputerResult` que retorna uma escolha aleatória do array `options`.
 
-*Hint*: Don't forget that in the earlier JavaScript fundamentals section, you learned about using `Math.random()` and `Math.floor()`.
+*Dica*: não se esqueça de que, na seção anterior de fundamentos de JavaScript, você aprendeu sobre o uso de `Math.random()` e `Math.floor()`.
 
 # --hints--
 
-Your `getRandomComputerResult` function should return a string.
+A função `getRandomComputerResult` deve retornar uma string.
 
 ```js
 assert.isString(getRandomComputerResult());
 ```
 
-Your `getRandomComputerResult` function should return one of the options in the `options` array.
+A função `getRandomComputerResult` deve retornar uma das opções no array `options`.
 
 ```js
 assert.include(["Rock", "Paper", "Scissors"], getRandomComputerResult());
 ```
 
-Your `getRandomComputerResult` function should return a random option each time.
+A função `getRandomComputerResult` deve retornar uma opção aleatória cada vez.
 
 ```js
 const results = new Set();
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf315cff4d36b27da828ba.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf315cff4d36b27da828ba.md
index 861a361bc9..75ebe0952f 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf315cff4d36b27da828ba.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf315cff4d36b27da828ba.md
@@ -1,63 +1,63 @@
 ---
 id: 66cf315cff4d36b27da828ba
-title: Step 4
+title: Passo 4
 challengeType: 0
 dashedName: step-4
 ---
 
 # --description--
 
-In this step, you will focus on determining if the player has won the round.
+Neste passo, você focará em determinar se o jogador ganhou a rodada.
 
-Create a `hasPlayerWonTheRound` function with two parameters called `player` and `computer`.
+Crie uma função `hasPlayerWonTheRound` com dois parâmetros chamados `player` e `computer`.
 
-The function should return `true` if the player has won the round, and `false` if the player has lost or tied the round.
+A função deve retornar `true` se o jogador ganhou a rodada, e `false` se o jogador perdeu ou empatou a rodada.
 
-Here are the criteria for the player to win a round:
+Aqui estão os critérios para o jogador vencer uma rodada:
 
-- If the player chooses `"Rock"` and the computer chooses `"Scissors"`
-- If the player chooses `"Scissors"` and the computer chooses `"Paper"`
-- If the player chooses `"Paper"` and the computer chooses `"Rock"`
+- Se o jogador escolher `"Rock"` e o computador escolher `"Scissors"`
+- Se o jogador escolher `"Scissors"` e o computador escolher `"Paper"`
+- Se o jogador escolher `"Paper"` e o computador escolher `"Rock"`
 
 # --hints--
 
-You should have a function called `hasPlayerWonTheRound`.
+Você deve ter uma função chamada `hasPlayerWonTheRound`.
 
 ```js
 assert.isFunction(hasPlayerWonTheRound);
 ```
 
-Your function should have two parameters called `player` and `computer`.
+A função deve ter dois parâmetros chamados `player` e `computer`.
 
 ```js
 assert.match(code, /hasPlayerWonTheRound\s*(?:=\s*)?\(\s*player\s*,\s*computer\s*\)\s*/);
 ```
 
-Your `hasPlayerWonTheRound` function should return a boolean.
+A função `hasPlayerWonTheRound` deve retornar um booleano.
 
 ```js
 assert.isBoolean(hasPlayerWonTheRound("Rock", "Scissors"));
 ```
 
-Your `hasPlayerWonTheRound` function should return `true` if the player chose `"Rock"` and the computer chose `"Scissors"`.
+A função `hasPlayerWonTheRound` deve retornar `true` se o jogador escolheu `"Rock"` e o computador escolheu `"Scissors"`.
 
 ```js
 assert.isTrue(hasPlayerWonTheRound("Rock", "Scissors"));
 ```
 
-Your `hasPlayerWonTheRound` function should return `true` if the player chose `"Scissors"` and the computer chose `"Paper"`.
+A função `hasPlayerWonTheRound` deve retornar `true` se o jogador escolheu `"Scissors"` e o computador escolheu `"Paper"`.
 
 ```js
 assert.isTrue(hasPlayerWonTheRound("Scissors", "Paper"));
 ```
 
-Your `hasPlayerWonTheRound` function should return `true` if the player chose `"Paper"` and the computer chose `"Rock"`.
+A função `hasPlayerWonTheRound` deve retornar `true` se o jogador escolheu `"Paper"` e o computador escolheu `"Rock"`.
 
 ```js
 assert.isTrue(hasPlayerWonTheRound("Paper", "Rock"));
 ```
 
-Your `hasPlayerWonTheRound` function should return `false` if the player and computer chose the same option.
+A função `hasPlayerWonTheRound` deve retornar `false` se o jogador e o computador escolheram a mesma opção.
 
 ```js
 assert.isFalse(hasPlayerWonTheRound("Rock", "Rock"));
@@ -65,7 +65,7 @@ assert.isFalse(hasPlayerWonTheRound("Scissors", "Scissors"));
 assert.isFalse(hasPlayerWonTheRound("Paper", "Paper"));
 ```
 
-Your `hasPlayerWonTheRound` function should return `false` if the computer won the round.
+A função `hasPlayerWonTheRound` deve retornar `false` se o computador ganhou a rodada.
 
 ```js
 assert.isFalse(hasPlayerWonTheRound("Scissors", "Rock"));
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf33305293e1b35c1aef7f.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf33305293e1b35c1aef7f.md
index ce6a79b338..8c9b1f058d 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf33305293e1b35c1aef7f.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf33305293e1b35c1aef7f.md
@@ -1,31 +1,31 @@
 ---
 id: 66cf33305293e1b35c1aef7f
-title: Step 6
+title: Passo 6
 challengeType: 0
 dashedName: step-6
 ---
 
 # --description--
 
-Now it’s time to get the results of the round. Complete the `getRoundResults` function.
+Agora é hora de obter os resultados da rodada. Complete a função `getRoundResults`.
 
-If the player wins the round, update the `playerScore` by `1` and return the message `"Player wins! [player's choice] beats [computer's choice]"`.
+Se o jogador ganhar a rodada, atualize o `playerScore` em `1` e retorne a mensagem `"Player wins! [player's choice] beats [computer's choice]"`.
 
-If the computer and player choose the same option, return the message `"It's a tie! Both chose [player's choice]"`.
+Se o computador e o jogador escolherem a mesma opção, retorne a mensagem `"It's a tie! Both chose [player's choice]"`.
 
-If the computer wins the round, update the `computerScore` by `1` and return the message `"Computer wins! [computer's choice] beats [player's choice]"`.
+Se o computador ganhar a rodada, atualize o `computerScore` em `1` e retorne a mensagem `"Computer wins! [computer's choice] beats [player's choice]"`.
 
-`[computer's choice]` should be replaced with `computerResult` while `[player's choice]` should be replaced with the `userOption`.
+`[computer's choice]` deve ser substituído por `computerResult` enquanto `[player's choice]` deve ser substituído pela `userOption`.
 
 # --hints--
 
-Your `getRoundResults` should return a string.
+`getRoundResults` deve retornar uma string.
 
 ```js
 assert.isString(getRoundResults("Rock"));
 ```
 
-Your `getRoundResults` function should return the correct message based on who wins the round. If no one wins, the message should say it's a tie.
+A função `getRoundResults` deve retornar a mensagem correta com base em quem vence a rodada. Se ninguém ganhar, a mensagem deve dizer que é um empate.
 
 ```js
 const result = getRoundResults("Paper")
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf34fcb005e7b447141afd.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf34fcb005e7b447141afd.md
index 18ae7b780f..5e624ea9f7 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf34fcb005e7b447141afd.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf34fcb005e7b447141afd.md
@@ -1,37 +1,37 @@
 ---
 id: 66cf34fcb005e7b447141afd
-title: Step 8
+title: Passo 8
 challengeType: 0
 dashedName: step-8
 ---
 
 # --description--
 
-Now it is time to update the scores and the round results message.
+Agora é hora de atualizar as pontuações e a mensagem de resultados da rodada.
 
-Create a `showResults` function with a parameter called `userOption`.
+Crie uma função `showResults` com um parâmetro chamado `userOption`.
 
-Inside your `showResults` function, the `roundResultsMsg` should be updated with the result of the round.
+Dentro da função `showResults`, o `roundResultsMsg` deve ser atualizado com o resultado da rodada.
 
-Then, the `playerScoreSpanElement` and `computerScoreSpanElement` should also be updated to show the updated scores of the player and computer.
+Em seguida, o `playerScoreSpanElement` e o `computerScoreSpanElement` também devem ser atualizados para mostrar as pontuações atualizadas do jogador e do computador.
 
-Remember, that the order matters here. You will need to first update the `roundResultsMsg`, then the `playerScoreSpanElement`, and finally the `computerScoreSpanElement` because the `roundResultsMsg` will be used to determine the scores.
+Lembre-se de que a ordem importa aqui. Você precisará primeiro atualizar `roundResultsMsg`, seguido de `playerScoreSpanElement` e, finalmente, `computerScoreSpanElement`, porque `roundResultsMsg` será usado para determinar as pontuações.
 
 # --hints--
 
-You should have a function called `showResults`.
+Você deve ter uma função chamada `showResults`.
 
 ```js
 assert.isFunction(showResults);
 ```
 
-Your `showResults` function should have a parameter called `userOption`.
+A função `showResults` deve ter um parâmetro chamado `userOption`.
 
 ```js
 assert.match(code, /showResults\s*(?:=\s*)?(?:\(\s*)?userOption(?:\s*\))?\s*/);
 ```
 
-Your `showResults` function should update the `roundResultsMsg` with the result of the round.
+A função `showResults` deve atualizar o `roundResultsMsg` com o resultado da rodada.
 
 ```js
 const possibleResults = [
@@ -49,7 +49,7 @@ showResults("Rock");
 assert.include(possibleResults, roundResultsMsg.innerText.replace(/\//g, "'"));
 ```
 
-Your `showResults` function should update the `computerScoreSpanElement` to show the updated score of the computer.
+A função `showResults` deve atualizar o `computerScoreSpanElement` para mostrar a pontuação atualizada do computador.
 
 ```js
 computerScore = 0;
@@ -62,7 +62,7 @@ assert.equal(computerScoreSpanElement.innerText, "1");
 getRandomComputerResult = oldRandomResult;
 ```
 
-Your `showResults` function should update the `playerScoreSpanElement` to show the updated score of the player.
+A função `showResults` deve atualizar o `playerScoreSpanElement` para mostrar a pontuação atualizada do jogador.
 
 ```js
 playerScore = 0;
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf35a75f891ab4f4e5497b.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf35a75f891ab4f4e5497b.md
index c3db0bcbf8..56e58a48d9 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf35a75f891ab4f4e5497b.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf35a75f891ab4f4e5497b.md
@@ -1,23 +1,23 @@
 ---
 id: 66cf35a75f891ab4f4e5497b
-title: Step 12
+title: Passo 12
 challengeType: 0
 dashedName: step-12
 ---
 
 # --description--
 
-If you try to play the game, you will see that you can play for an infinite amount of rounds. But the rules state that the first one to three points wins. You want to check if there's a winner, and display a message.
+Se você tentar jogar o jogo, verá que pode jogar por uma quantidade infinita de rodadas. As regras, porém, afirmam que o primeiro que fizer três pontos vence. Você quer verificar se há um vencedor e exibir uma mensagem.
 
-In your `showResults` function, if the player has reached three points, update the `winnerMsgElement` to `"Player has won the game!"`. If the computer has reached three points, update the `winnerMsgElement` to `"Computer has won the game!"`.
+Na função `showResults`, se o jogador alcançar três pontos, atualize o `winnerMsgElement` para `"Player has won the game!"`. Se o computador alcançar três pontos, atualize o `winnerMsgElement` para `"Computer has won the game!"`.
 
-If there is a winner, show the `resetGameBtn` button by settings it's `display` to `block` and hide the `optionsContainer` by setting it's `display` to `none`.
+Se houver um vencedor, mostre o botão `resetGameBtn` definindo o `display` como `block` e esconda o `optionsContainer` definindo o `display` como `none`.
 
-Now, try to play the game and see if the winner message is displayed when a player reaches three points.
+Agora, tente jogar o jogo e veja se a mensagem de vencedor é exibida quando um jogador alcançar três pontos.
 
 # --hints--
 
-You should update the `winnerMsgElement` if there is a winner.
+Você deve atualizar `winnerMsgElement` se houver um vencedor.
 
 ```js
 while (playerScore < 3 && computerScore < 3) {
@@ -32,7 +32,7 @@ if (playerScore === 3) {
 
 ```
 
-You should hide the `optionsContainer` if the player or computer has reached three points.
+Você deve esconder o `optionsContainer` se o jogador ou computador alcançar três pontos.
 
 ```js
 playerScore = 3;
@@ -40,7 +40,7 @@ showResults("Scissors");
 assert.equal(optionsContainer.style.display, "none");
 ```
 
-You should show the `resetGameBtn` button if the player or computer has reached three points.
+Você deve mostrar o botão `resetGameBtn` se o jogador ou computador alcançar três pontos.
 
 ```js
 computerScore = 3;
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf3639aca119b5c00b02d3.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf3639aca119b5c00b02d3.md
index 1e38823bb3..b2c86bfa28 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf3639aca119b5c00b02d3.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66cf3639aca119b5c00b02d3.md
@@ -1,29 +1,29 @@
 ---
 id: 66cf3639aca119b5c00b02d3
-title: Step 14
+title: Passo 14
 challengeType: 0
 dashedName: step-14
 ---
 
 # --description--
 
-For the final step of the workshop, you will need to build out the reset game functionality.
+Para o passo final do workshop, você precisará criar a funcionalidade de reiniciar o jogo.
 
-Create a `resetGame` function that accomplishes the following:
+Crie uma função `resetGame` que realize o seguinte:
 
-- Resets the player and computer scores to `0`.
-- Updates the `playerScoreSpanElement` and `computerScoreSpanElement` to display the new scores.
-- Hides the `resetGameBtn` button.
-- Shows the `optionsContainer` so the player can play again.
-- Clears the content for the `winnerMsgElement` and `roundResultsMsg` elements.
+- Redefine as pontuações do jogador e do computador para `0`.
+- Atualiza o `playerScoreSpanElement` e o `computerScoreSpanElement` para exibir as novas pontuações.
+- Esconde o botão `resetGameBtn`.
+- Mostra o `optionsContainer` para que o jogador possa jogar novamente.
+- Limpa o conteúdo dos elementos `winnerMsgElement` e `roundResultsMsg`.
 
-Try testing out the game by playing a few rounds until one of the players reaches `3` points. Then, click the `"Play again?"` button to see if the game resets correctly.
+Tente testar o jogo jogando algumas rodadas até que um dos jogadores alcance `3` pontos. Em seguida, clique no botão `"Play again?"` para ver se o jogo reinicia corretamente.
 
-And with this final step, you have completed the Rock, Paper, Scissors game!
+Com esse passo final, você concluiu o jogo de Pedra, Papel, Tesoura!
 
 # --hints--
 
-Your `resetGame` function should set the `playerScore` to `0`.
+A função `resetGame` deve definir `playerScore` como `0`.
 
 ```js
 playerScore = 1;
@@ -31,7 +31,7 @@ resetGame();
 assert.equal(playerScore, 0);
 ```
 
-Your `resetGame` function should set the `computerScore` to `0`.
+A função `resetGame` deve definir `computerScore` como `0`.
 
 ```js
 computerScore = 1;
@@ -39,7 +39,7 @@ resetGame();
 assert.equal(computerScore, 0);
 ```
 
-Your `resetGame` function should set the `playerScoreSpanElement` to `0`.
+A função `resetGame` deve definir `playerScoreSpanElement` como `0`.
 
 ```js
 playerScoreSpanElement.innerText = "1";
@@ -47,7 +47,7 @@ resetGame();
 assert.equal(playerScoreSpanElement.innerText, "0");
 ```
 
-Your `resetGame` function should set the `computerScoreSpanElement` to `0`.
+A função `resetGame` deve definir `computerScoreSpanElement` como `0`.
 
 ```js
 computerScoreSpanElement.innerText = "1";
@@ -55,7 +55,7 @@ resetGame();
 assert.equal(computerScoreSpanElement.innerText, "0");
 ```
 
-Your `resetGame` function should set the `roundResultsMsg` to an empty string.
+A função `resetGame` deve definir `roundResultsMsg` como uma string vazia.
 
 ```js
 rockBtn.click();
@@ -64,7 +64,7 @@ resetGame();
 assert.equal(roundResultsMsg.innerText, "");
 ```
 
-Your `resetGame` function should set the `winnerMsgElement` to an empty string.
+A função `resetGame` deve definir `winnerMsgElement` como uma string vazia.
 
 ```js
 winnerMsgElement.innerText = "Player has won the game!";
@@ -72,7 +72,7 @@ resetGame();
 assert.equal(winnerMsgElement.innerText, "");
 ```
 
-Your `resetGame` function should hide the `resetGameBtn`.
+A função `resetGame` deve esconder o `resetGameBtn`.
 
 ```js
 playerScore = 3;
@@ -83,7 +83,7 @@ resetGame();
 assert.equal(window.getComputedStyle(resetGameBtn).display, "none");
 ```
 
-Your `resetGame` function should show the `optionsContainer`.
+A função `resetGame` deve mostrar o `optionsContainer`.
 
 ```js
 playerScore = 3;
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d05da61ff145d7a46fe41b.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d05da61ff145d7a46fe41b.md
index 341ee0af43..13b527701f 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d05da61ff145d7a46fe41b.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d05da61ff145d7a46fe41b.md
@@ -1,43 +1,43 @@
 ---
 id: 66d05da61ff145d7a46fe41b
-title: Step 2
+title: Passo 2
 challengeType: 0
 dashedName: step-2
 ---
 
 # --description--
 
-In the first part of the workshop, you will focus on building the functionality that generates a random choice for the computer.
+Na primeira parte do workshop, você se concentrará em construir a funcionalidade que gera uma escolha aleatória para o computador.
 
-Start by creating a variable called `options` and assign it an array with the following strings: `"Rock"`, `"Paper"`, and `"Scissors"`.
+Comece criando uma variável chamada `options` e atribua a ela um array com as seguintes strings: `"Rock"`, `"Paper"` e `"Scissors"`.
 
 # --hints--
 
-You should have a variable called `options`.
+Você deve ter uma variável chamada `options`.
 
 ```js
 assert.isNotNull(options);
 ```
 
-Your `options` variable should be an array.
+A variável `options` deve ser um array.
 
 ```js
 assert.isArray(options);
 ```
 
-Your `options` array should contain the string `"Rock"`.
+A variável `options` deve conter a string `"Rock"`.
 
 ```js
 assert.include(options, "Rock");
 ```
 
-Your `options` array should contain the string `"Paper"`.
+A variável `options` deve conter a string `"Paper"`.
 
 ```js
 assert.include(options, "Paper");
 ```
 
-Your `options` array should contain the string `"Scissors"`.
+A variável `options` deve conter a string `"Scissors"`.
 
 ```js
 assert.include(options, "Scissors");
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d064c7d79408da050f8b2f.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d064c7d79408da050f8b2f.md
index 88e9ce02b6..5ce3e77778 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d064c7d79408da050f8b2f.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d064c7d79408da050f8b2f.md
@@ -1,53 +1,53 @@
 ---
 id: 66d064c7d79408da050f8b2f
-title: Step 5
+title: Passo 5
 challengeType: 0
 dashedName: step-5
 ---
 
 # --description--
 
-The next step is to create the variables responsible for keeping track of the player and computer scores.
+O próximo passo é criar as variáveis responsáveis por acompanhar as pontuações do jogador e do computador.
 
-Create a variable called `playerScore` and initialize it with the value `0`.
+Crie uma variável chamada `playerScore` e inicialize-a com o valor `0`.
 
-Then, create a variable called `computerScore` and initialize it with the value `0`.
+Em seguida, crie uma variável chamada `computerScore` e inicialize-a com o valor `0`.
 
-You will need to use `let` to declare these variables because their values will change throughout the game.
+Você precisará usar `let` para declarar essas variáveis porque os valores delas mudarão ao longo do jogo.
 
 # --hints--
 
-You should have a variable called `playerScore`.
+Você deve ter uma variável chamada `playerScore`.
 
 ```js
 assert.isNotNull(playerScore);
 ```
 
-You should use `let` to declare the `playerScore` variable.
+Você deve usar `let` para declarar a variável `playerScore`.
 
 ```js
 assert.match(code, /let\s+playerScore/);
 ```
 
-Your `playerScore` should be initialized with the value `0`.
+`playerScore` deve ser inicializada com o valor `0`.
 
 ```js
 assert.strictEqual(playerScore, 0);
 ```
 
-You should have a variable called `computerScore`.
+Você deve ter uma variável chamada `computerScore`.
 
 ```js
 assert.isNotNull(computerScore);
 ```
 
-You should use `let` to declare the `computerScore` variable.
+Você deve usar `let` para declarar a variável `computerScore`.
 
 ```js
 assert.match(code, /let\s+computerScore/);
 ```
 
-Your `computerScore` should be initialized with the value `0`.
+`computerScore` deve ser inicializada com o valor `0`.
 
 ```js
 assert.strictEqual(computerScore, 0);
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d068348ca093db469b4d59.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d068348ca093db469b4d59.md
index b3ef0d42b6..34b567b2aa 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d068348ca093db469b4d59.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d068348ca093db469b4d59.md
@@ -1,53 +1,53 @@
 ---
 id: 66d068348ca093db469b4d59
-title: Step 7
+title: Passo 7
 challengeType: 0
 dashedName: step-7
 ---
 
 # --description--
 
-The next portion of the workshop is to create the functionality that will show the results.
+A próxima parte do workshop é criar a funcionalidade que mostrará os resultados.
 
-Start by creating a variable called `playerScoreSpanElement` and assign it the value of the element with the id `player-score`.
+Comece criando uma variável chamada `playerScoreSpanElement` e atribua a ela o valor do elemento com o id `player-score`.
 
-Then create a variable called `computerScoreSpanElement` and assign it the value of the element with the id `computer-score`.
+Em seguida, crie uma variável chamada `computerScoreSpanElement` e atribua a ela o valor do elemento com o id `computer-score`.
 
-Finally, create a variable called `roundResultsMsg` and assign it the value of the element with the id `results-msg`.
+Finalmente, crie uma variável chamada `roundResultsMsg` e atribua a ela o valor do elemento com o id `results-msg`.
 
 # --hints--
 
-You should have a variable called `playerScoreSpanElement`.
+Você deve ter uma variável chamada `playerScoreSpanElement`.
 
 ```js
 assert.isNotNull(playerScoreSpanElement);
 ```
 
-You should assign the value of the element with the id `player-score` to the `playerScoreSpanElement`.
+Você deve atribuir o valor do elemento com o id `player-score` ao `playerScoreSpanElement`.
 
 ```js
 assert.equal(playerScoreSpanElement, document.getElementById("player-score"));
 ```
 
-You should have a variable called `computerScoreSpanElement`.
+Você deve ter uma variável chamada `computerScoreSpanElement`.
 
 ```js
 assert.isNotNull(computerScoreSpanElement);
 ```
 
-You should assign the value of the element with the id `computer-score` to the `computerScoreSpanElement`.
+Você deve atribuir o valor do elemento com o id `computer-score` ao `computerScoreSpanElement`.
 
 ```js
 assert.equal(computerScoreSpanElement, document.getElementById("computer-score"));
 ```
 
-You should have a variable called `roundResultsMsg`.
+Você deve ter uma variável chamada `roundResultsMsg`.
 
 ```js
 assert.isNotNull(roundResultsMsg);
 ```
 
-You should assign the value of the element with the id `results-msg` to the `roundResultsMsg`.
+Você deve atribuir o valor do elemento com o id `results-msg` ao `roundResultsMsg`.
 
 ```js
 assert.equal(roundResultsMsg, document.getElementById("results-msg"));
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d0746099f6f3de3678fd26.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d0746099f6f3de3678fd26.md
index 4e9e64b758..c0d3d1c136 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d0746099f6f3de3678fd26.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d0746099f6f3de3678fd26.md
@@ -1,53 +1,53 @@
 ---
 id: 66d0746099f6f3de3678fd26
-title: Step 9
+title: Passo 9
 challengeType: 0
 dashedName: step-9
 ---
 
 # --description--
 
-Now it is time to test out your `showResults` function.
+Agora é hora de testar a função `showResults`.
 
-Start by creating a variable called `rockBtn` and assign it the value of the button with the id of `rock-btn`.
+Comece criando uma variável chamada `rockBtn` e atribua a ela o valor do botão com o id de `rock-btn`.
 
-Then, create a variable called `paperBtn` and assign it the value of the button with the id of `paper-btn`.
+Em seguida, crie uma variável chamada `paperBtn` e atribua a ela o valor do botão com o id de `paper-btn`.
 
-Finally, create a variable called `scissorsBtn` and assign it the value of the button with the id of `scissors-btn`.
+Finalmente, crie uma variável chamada `scissorsBtn` e atribua a ela o valor do botão com o id de `scissors-btn`.
 
 # --hints--
 
-You should have a variable called `rockBtn`.
+Você deve ter uma variável chamada `rockBtn`.
 
 ```js
 assert.isNotNull(rockBtn);
 ```
 
-Your `rockBtn` variable should be assigned to the button with the id of `rock-btn`.
+A variável `rockBtn` deve ser atribuída ao botão com o id de `rock-btn`.
 
 ```js
 assert.equal(rockBtn, document.getElementById("rock-btn"));
 ```
 
-You should have a variable called `paperBtn`.
+Você deve ter uma variável chamada `paperBtn`.
 
 ```js
 assert.isNotNull(paperBtn);
 ```
 
-Your `paperBtn` variable should be assigned to the button with the id of `paper-btn`.
+A variável `paperBtn` deve ser atribuída ao botão com o id de `paper-btn`.
 
 ```js
 assert.equal(paperBtn, document.getElementById("paper-btn"));
 ```
 
-You should have a variable called `scissorsBtn`.
+Você deve ter uma variável chamada `scissorsBtn`.
 
 ```js
 assert.isNotNull(scissorsBtn);
 ```
 
-Your `scissorsBtn` variable should be assigned to the button with the id of `scissors-btn`.
+A variável `scissorsBtn` deve ser atribuída ao botão com o id de `scissors-btn`.
 
 ```js
 assert.equal(scissorsBtn, document.getElementById("scissors-btn"));
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d076040c7d1cdf36525af9.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d076040c7d1cdf36525af9.md
index 2d1d80954d..5f52d0d4ae 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d076040c7d1cdf36525af9.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d076040c7d1cdf36525af9.md
@@ -1,25 +1,25 @@
 ---
 id: 66d076040c7d1cdf36525af9
-title: Step 10
+title: Passo 10
 challengeType: 0
 dashedName: step-10
 ---
 
 # --description--
 
-The next step is to attach event listeners to each of the buttons you created in the previous step.
+O próximo passo é anexar ouvintes de evento a cada um dos botões que você criou na etapa anterior.
 
-Start by creating an event listener for the `rockBtn` button. When the `rockBtn` button is clicked, you should call the `showResults` function with the argument `"Rock"`.
+Comece criando um ouvinte de evento para o botão `rockBtn`. Quando o botão `rockBtn` é clicado, você deve chamar a função `showResults` com o argumento `"Rock"`.
 
-Then, create an event listener for the `paperBtn` button. When the `paperBtn` button is clicked, you should call the `showResults` function with the argument `"Paper"`.
+Em seguida, crie um ouvinte de evento para o botão `paperBtn`. Quando o botão `paperBtn` é clicado, você deve chamar a função `showResults` com o argumento `"Paper"`.
 
-Finally, create an event listener for the `scissorsBtn` button. When the `scissorsBtn` button is clicked, you should call the `showResults` function with the argument `"Scissors"`.
+Finalmente, crie um ouvinte de evento para o botão `scissorsBtn`. Quando o botão `scissorsBtn` é clicado, você deve chamar a função `showResults` com o argumento `"Scissors"`.
 
-Now, you should be able to click on any of the buttons and see the results for each round.
+Agora, você deve ser capaz de clicar em qualquer um dos botões e ver os resultados de cada rodada.
 
 # --hints--
 
-You should attach an `addEventListener` to the `rockBtn` button. Your event listener should take a `"click"` event and callback function that calls the `showResults` function with the argument `"Rock"`.
+Você deve anexar um `addEventListener` ao botão `rockBtn`. O ouvinte de evento deve receber um evento `"click"` e uma função de callback que chama a função `showResults` com o argumento `"Rock"`.
 
 ```js
 resetRoundMsg();
@@ -32,7 +32,7 @@ const availableOptions = [
 assert.include(availableOptions, roundResultsMsg.innerText);
 ```
 
-You should attach an `addEventListener` to the `paperBtn` button. Your event listener should take a `"click"` event and callback function that calls the `showResults` function with the argument `"Paper"`.
+Você deve anexar um `addEventListener` ao botão `paperBtn`. O ouvinte de evento deve receber um evento `"click"` e uma função de callback que chama a função `showResults` com o argumento `"Paper"`.
 
 ```js
 resetRoundMsg();
@@ -45,7 +45,7 @@ const availableOptions = [
 assert.include(availableOptions, roundResultsMsg.innerText);
 ```
 
-You should attach an `addEventListener` to the `scissorsBtn` button. Your event listener should take a `"click"` event and callback function that calls the `showResults` function with the argument `"Scissors"`.
+Você deve anexar um `addEventListener` ao botão `scissorsBtn`. O ouvinte de evento deve receber um evento `"click"` e uma função de callback que chama a função `showResults` com o argumento `"Scissors"`.
 
 ```js
 resetRoundMsg();
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d081d79b1d57e1b42caabf.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d081d79b1d57e1b42caabf.md
index e17ce8cb72..c9fcdbfcc2 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d081d79b1d57e1b42caabf.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d081d79b1d57e1b42caabf.md
@@ -1,53 +1,53 @@
 ---
 id: 66d081d79b1d57e1b42caabf
-title: Step 11
+title: Passo 11
 challengeType: 0
 dashedName: step-11
 ---
 
 # --description--
 
-For the last portion of the workshop, you will focus on building out the winner message and reset button functionality.
+Para a última parte do workshop, você focará na compilação da mensagem do vencedor e na funcionalidade do botão de reinicialização.
 
-Start by creating a variable called `winnerMsgElement` that will store the element with the id of `winner-msg`.
+Comece criando uma variável chamada `winnerMsgElement` que armazenará o elemento com o id de `winner-msg`.
 
-Then, create a variable called `optionsContainer` that will store the element with the class of `options-container`.
+Em seguida, crie uma variável chamada `optionsContainer` que armazenará o elemento com a classe de `options-container`.
 
-Finally, create a variable called `resetGameBtn` that will store the element with the id of `reset-game-btn`.
+Por fim, crie uma variável chamada `resetGameBtn` que armazenará o elemento com o id de `reset-game-btn`.
 
 # --hints--
 
-You should have a `winnerMsgElement` variable.
+Você deve ter uma variável `winnerMsgElement`.
 
 ```js
 assert.isNotNull(winnerMsgElement);
 ```
 
-Your `winnerMsgElement` variable should store the element with the id of `winner-msg`.
+A variável `winnerMsgElement` deve armazenar o elemento com o id de `winner-msg`.
 
 ```js
 assert.equal(winnerMsgElement, document.getElementById("winner-msg"));
 ```
 
-You should have an `optionsContainer` variable.
+Você deve ter uma variável `optionsContainer`.
 
 ```js
 assert.isNotNull(optionsContainer);
 ```
 
-Your `optionsContainer` variable should store the element with the class of `options-container`.
+A variável `optionsContainer` deve armazenar o elemento com a classe de `options-container`.
 
 ```js
 assert.equal(optionsContainer, document.querySelector(".options-container"));
 ```
 
-You should have a `resetGameBtn` variable.
+Você deve ter uma variável `resetGameBtn`.
 
 ```js
 assert.isNotNull(resetGameBtn);
 ```
 
-Your `resetGameBtn` variable should store the element with the id of `reset-game-btn`.
+A variável `resetGameBtn` deve armazenar o elemento com o id de `reset-game-btn`.
 
 ```js
 assert.equal(resetGameBtn, document.getElementById("reset-game-btn"));
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d085d37aeffce2ef786de3.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d085d37aeffce2ef786de3.md
index e0e36cbd50..a12aa500db 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d085d37aeffce2ef786de3.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d085d37aeffce2ef786de3.md
@@ -1,19 +1,19 @@
 ---
 id: 66d085d37aeffce2ef786de3
-title: Step 13
+title: Passo 13
 challengeType: 0
 dashedName: step-13
 ---
 
 # --description--
 
-If the player or computer has won the game, there should be an option to reset the game and play again.
+Se o jogador ou o computador venceu o jogo, deve haver uma opção para redefinir o jogo e jogar novamente.
 
-Add an event listener to the `resetGameBtn` button. Your event listener should take in a `"click"` event and a reference to the `resetGame` function.
+Adicione um "ouvinte" de evento ao botão `resetGameBtn`. O "ouvinte" de evento deve aceitar um evento de `"click"` e uma referência à função `resetGame`.
 
 # --hints--
 
-You should add an event listener to the `resetGameBtn` button. The event listener should take in a `"click"` event and a reference to the `resetGame` function.
+Você deve adicionar um "ouvinte" de evento ao botão `resetGameBtn`. O "ouvinte" de evento deve aceitar um evento de `"click"` e uma referência à função `resetGame`.
 
 ```js
 resetGameBtn.click();
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d8fade439d513e5f77c906.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d8fade439d513e5f77c906.md
index b3c90b1624..cab67338c4 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d8fade439d513e5f77c906.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-rps-game/66d8fade439d513e5f77c906.md
@@ -1,6 +1,6 @@
 ---
 id: 66d8fade439d513e5f77c906
-title: Step 1
+title: Passo 1
 challengeType: 0
 dashedName: step-1
 demoType: onLoad
@@ -8,21 +8,21 @@ demoType: onLoad
 
 # --description--
 
-In this workshop, you will continue to practice working with the DOM and event handling by building a Rock, Paper, Scissors game.
+Neste workshop, você continuará a praticar o trabalho com o DOM a manipulação de eventos criando um jogo de Pedra, Papel e Tesoura.
 
-The HTML and CSS boilerplate for the game has been provided for you.
+O boilerplate HTML e CSS para o jogo foram fornecidos para você.
 
-On the screen, you will see the rules to the game, the player and computer scores and the buttons for the user to select Rock, Paper, or Scissors.
+Na tela, você verá as regras do jogo, as pontuações do jogador e do computador e os botões para o usuário selecionar Pedra, Papel ou Tesoura.
 
-Your task over the next few steps is to build the JavaScript functionality that generates a computer choice, compares it to the player's choice, and updates the scores accordingly.
+A tarefa nos próximos passos é construir a funcionalidade em JavaScript que gera uma escolha do computador, compara com a escolha do jogador e atualiza as pontuações conforme necessário.
 
-Take some time to look through the HTML provided and familiarize yourself with the structure of the game.
+Reserve algum tempo para examinar o HTML fornecido e familiarize-se com a estrutura do jogo.
 
-When you're ready, click on the `"Check your code"` button to proceed to the next step and start the workshop.
+Quando estiver pronto, clique no botão `"Check your code"` para prosseguir para o próximo passo e iniciar o workshop.
 
 # --hints--
 
-Submit to continue.
+Envie para continuar.
 
 ```js
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-shopping-list/66c72b0ffbc5522525768558.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-shopping-list/66c72b0ffbc5522525768558.md
index 93f8b9c244..0f30aa432b 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-shopping-list/66c72b0ffbc5522525768558.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-shopping-list/66c72b0ffbc5522525768558.md
@@ -7,7 +7,7 @@ dashedName: step-11
 
 # --description--
 
-Nas etapas anteriores, você revisou como adicionar um item ao final do array usando o método `push`.
+Nos passos anteriores, você revisou como adicionar um item ao final do array usando o método `push`.
 
 O método `push`, no entanto, aceita múltiplos argumentos. Então, você pode adicionar múltiplos itens ao final do array assim:
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-shopping-list/66c748ffdfbe4f2ede268be2.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-shopping-list/66c748ffdfbe4f2ede268be2.md
index 324f651caf..b6f1bfced2 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-shopping-list/66c748ffdfbe4f2ede268be2.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-shopping-list/66c748ffdfbe4f2ede268be2.md
@@ -7,7 +7,7 @@ dashedName: step-20
 
 # --description--
 
-Na etapa final do workshop, registre a lista de compras final no console.
+No passo final do workshop, registre a lista de compras final no console.
 
 Com este último passo, a lista de compras está completa!
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b59be6ab830800c4df9146.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b59be6ab830800c4df9146.md
index fbc3193210..00872475b9 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b59be6ab830800c4df9146.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b59be6ab830800c4df9146.md
@@ -7,7 +7,7 @@ dashedName: step-5
 
 # --description--
 
-Agora, é hora de usar as variáveis que você criou na etapa anterior.
+Agora, é hora de usar as variáveis que você criou no passo anterior.
 
 Nos vídeos da aula, você aprendeu a trabalhar com template literals assim:
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b6e62423e8a031d6c1f03d.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b6e62423e8a031d6c1f03d.md
index 303e5424e5..1796d03c8b 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b6e62423e8a031d6c1f03d.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b6e62423e8a031d6c1f03d.md
@@ -18,7 +18,7 @@ console.log(`Hello, my name is ${developer}.`);
 
 Comece exibindo a mensagem `Here is an example of using the length property on the word [topic].` para o console.
 
-Lembre-se de substituir `[topic]` pela variável `topic` e de usar a sintaxe apropriada de template literals, como você fez nas etapas anteriores.
+Lembre-se de substituir `[topic]` pela variável `topic` e de usar a sintaxe apropriada de template literals, como você fez nos passos anteriores.
 
 Em seguida, adicione uma segunda instrução de `console.log` que exiba o comprimento da string `topic` no console.
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b6e80d6c3f0b329c360283.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b6e80d6c3f0b329c360283.md
index 9b98316c3d..479046b736 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b6e80d6c3f0b329c360283.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b6e80d6c3f0b329c360283.md
@@ -11,7 +11,7 @@ A próxima parte deste workshop é revisar o acesso a caracteres de uma string.
 
 Comece exibindo a mensagem `Here is an example of accessing the first letter in the word [subject].` no console.
 
-Lembre-se de substituir `[subject]` pela variável `subject` e usar a sintaxe correta de template literals como você fez nas etapas anteriores.
+Lembre-se de substituir `[subject]` pela variável `subject` e usar a sintaxe correta de template literals como você fez nos passos anteriores.
 
 # --hints--
 
diff --git a/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b7049b7709ea3a9547c79d.md b/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b7049b7709ea3a9547c79d.md
index 6c0339d9de..8683174ce8 100644
--- a/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b7049b7709ea3a9547c79d.md
+++ b/curriculum/challenges/portuguese/25-front-end-development/workshop-teacher-chatbot/66b7049b7709ea3a9547c79d.md
@@ -7,7 +7,7 @@ dashedName: step-15
 
 # --description--
 
-A próxima etapa é adicionar outra instrução de `console` que produz a string `"Here are examples of finding the positions of substrings in the sentence."`.
+O próximo passo é adicionar outra instrução de `console` que produz a string `"Here are examples of finding the positions of substrings in the sentence."`.
 
 # --hints--
 
diff --git a/curriculum/challenges/swahili/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md b/curriculum/challenges/swahili/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
index db5b0c61e0..5608918f2f 100644
--- a/curriculum/challenges/swahili/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
+++ b/curriculum/challenges/swahili/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
@@ -8,7 +8,7 @@ dashedName: build-a-periodic-table-database
 
 # --description--
 
-This is one of the required projects to earn your certification. For this project, you will create Bash a script to get information about chemical elements from a periodic table database.
+This is one of the required projects to earn your certification. For this project, you will create a Bash script to get information about chemical elements from a periodic table database.
 
 # --instructions--
 
diff --git a/curriculum/challenges/swahili/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md b/curriculum/challenges/swahili/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
index 9b8a64f995..cb03f33bf1 100644
--- a/curriculum/challenges/swahili/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
+++ b/curriculum/challenges/swahili/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
@@ -9,6 +9,8 @@ dashedName: step-64
 
 Ndani ya `footer`, ongeza kipengele cha `p`. Kisha, weka kipengee (`a`) katika `p` ambacho kinaunganishwa na `https://www.freecodecamp.org` na kina maandishi `Visit our website`.
 
+Make sure that the link opens in a new tab by adding a `target` attribute with the value `_blank`.
+
 # --hints--
 
 Hupaswi kubadilisha kipengele cha `footer` kilichopo.
@@ -43,6 +45,12 @@ Kipengele chako kipya cha `a` kinapaswa kuunganishwa na `https://www.freecodecam
 assert(document.querySelector("footer > p > a")?.href === "https://www.freecodecamp.org/");
 ```
 
+Your new `a` element should have the `target` attribute set to `_blank`.
+
+```js
+assert.equal(document.querySelector("footer > p > a")?.target, "_blank");
+```
+
 # --seed--
 
 ## --seed-contents--
diff --git a/curriculum/challenges/swahili/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md b/curriculum/challenges/swahili/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
index d2ad72a1ea..1b6ca05444 100644
--- a/curriculum/challenges/swahili/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
+++ b/curriculum/challenges/swahili/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
@@ -21,12 +21,12 @@ Remove `flex: 1` from `.item` and add `justify-content: space-between` to `.cont
 
 `justify-content` aligns items across the **main axis**. There are a few values that you can use here. You'll learn the rest of them in the reading assignments, but for now try changing it to center, which should center the boxes along the main axis.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see what is possible with the `justify-content` property. Read this [interactive article on MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) and play around with the different values of `justify-content` on the example.
 
+# --question--
+
 ## --text--
 
 How does applying `justify-content: space-between` to a flex container affect the positioning of its items?
diff --git a/curriculum/challenges/swahili/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md b/curriculum/challenges/swahili/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
index d3137b0af5..59acb55a29 100644
--- a/curriculum/challenges/swahili/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
+++ b/curriculum/challenges/swahili/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
@@ -17,12 +17,12 @@ To change the placement of items along the cross axis use `align-items`. Try get
 
 Because `justify-content` and `align-items` are based on the main and cross axis of your container, their behavior changes when you change the flex-direction of a flex-container. For example, when you change `flex-direction` to `column`, `justify-content` aligns vertically and `align-items` aligns horizontally. The most common behavior, however, is the default, i.e. `justify-content` aligns items horizontally (because the main axis defaults to horizontal), and `align-items` aligns them vertically. One of the biggest sticking points that beginners have with flexbox is confusion when this behavior changes.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Before moving on to the next lesson, see if you can figure out how `align-items` behaves when you change the `flex-direction` property to `column`.
 
+# --question--
+
 ## --text--
 
 When changing the `flex-direction` property to `column` in a flex container, how does `align-items` behave in relation to the flex items?
diff --git a/curriculum/challenges/swahili/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md b/curriculum/challenges/swahili/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
index 1adf9ce84f..49edeac0e4 100644
--- a/curriculum/challenges/swahili/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
+++ b/curriculum/challenges/swahili/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
@@ -9,12 +9,12 @@ dashedName: learn-block-and-inline-lesson-b
 
 Inline elements, however, do not start on a new line. They appear in line with whatever elements they are placed beside. A clear example of an inline element is a link, or `<a>` tag. If you stick one of these in the middle of a paragraph of text, it will behave like a part of the paragraph. <a  href="https://www.freecodecamp.org/" target="_blank">(Like this)</a> The link’s text will sit alongside other words in that paragraph. Additionally, padding and margin behave differently on inline elements. In general, you do not want to try to put extra padding or margin on inline elements.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Search the web for a list of `block` elements and a list of `inline` elements.
 
+# --question--
+
 ## --text--
 
 What is the difference between a `block` element and an `inline` element?
diff --git a/curriculum/challenges/swahili/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md b/curriculum/challenges/swahili/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
index cdd4d5aa87..e75492e9c1 100644
--- a/curriculum/challenges/swahili/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
+++ b/curriculum/challenges/swahili/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-block-and-inline-lesson-g
 
 # --description--
 
-Now that you have some basic understanding of `block` and inline `elements`, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
+Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
 
 # --question--
 
diff --git a/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md b/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
index 995073b8a2..a7a2ee9a51 100644
--- a/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
+++ b/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
@@ -21,12 +21,12 @@ New programmers often find problem solving the hardest skill to build. It's not
 
 The best way to improve your problem solving ability is by building experience by making lots and lots of programs. The more practice you have the better you'll be prepared to solve real world problems.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Read <a href="https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/" target="_blank">How to Think Like a Programmer - Lessons in Problem Solving</a> by Richard Reis.
 
+# --question--
+
 ## --text--
 
 According to V. Anton Spraul in "Think Like a Programmer," what is problem solving in programming?
diff --git a/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md b/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
index ae905ecf89..c57a7d43e8 100644
--- a/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
+++ b/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
@@ -25,11 +25,11 @@ Now that you know what you’re aiming to solve, don’t jump into coding just y
 
 The last question is where you will write out an algorithm to solve the problem. You can think of an algorithm as a recipe for solving a particular problem. It defines the steps that need to be taken by the computer to solve a problem in pseudocode.
 
-# --question--
-
-## --assignment--
+# --assignment--
 Watch <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">How to Begin Thinking Like a Programmer</a> by Coding Tech. It’s an hour long but packed full of information and definitely worth your time watching.
 
+# --question--
+
 ## --text--
 
 What should you do before starting to code according to the provided text?
diff --git a/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md b/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
index c837fd9658..082f2d51ae 100644
--- a/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
+++ b/curriculum/challenges/swahili/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
@@ -22,12 +22,12 @@ Print the value of the counter variable
 
 This is a basic program to demonstrate how pseudocode looks. There will be more examples of pseudocode included in the assignments.
 
+# --assignment--
 
-# --question--
-
-## --assignment--
 Read this <a href="https://builtin.com/data-science/pseudocode" target="_blank"> Pseudocode: What It Is and How to Write It</a> article from Built In.
 
+# --question--
+
 ## --text--
 
 What are the benefits of using pseudocode according to the linked article?
diff --git a/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md b/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
index 8a14cf666c..be3d4a264f 100644
--- a/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
+++ b/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-So far you have learned how to create questions with the verb to be. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
+So far you have learned how to create questions with the verb `to be`. In sentences with the verb `to be` (am, is, are) you just have to change the order of the noun and the verb to create a question. Like this:
 
 `You are a developer` -> `Are you a developer?`
 
diff --git a/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md b/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
index 544d8f1988..8cd311a518 100644
--- a/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
+++ b/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
@@ -21,7 +21,7 @@ Which sentence is correct for describing one place near you?
 
 ### --feedback--
 
-`There are` is used for plural nouns, and `bank` is singular. You’ll learn about there are in the next few lessons.
+`There are` is used for plural nouns, and `bank` is singular. You’ll learn about `there are` in the next few lessons.
 
 ---
 
diff --git a/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md b/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
index 6526b1e95b..10c0845779 100644
--- a/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
+++ b/curriculum/challenges/swahili/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
@@ -7,7 +7,7 @@ dashedName: task-112
 
 # --description--
 
-To elaborate a question using `there is` you just need to change the order of the verb to be, like so:
+To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so:
 
 `There is an ATM nearby` -> `Is there an ATM nearby?`
 
diff --git a/curriculum/challenges/swahili/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md b/curriculum/challenges/swahili/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
new file mode 100644
index 0000000000..7d664a8876
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
@@ -0,0 +1,25 @@
+---
+id: 5f1a4ef5d5d6b5ab580fc6ae
+title: Build a Celestial Bodies Database
+challengeType: 13
+url: freeCodeCamp/learn-celestial-bodies-database
+dashedName: lab-celestial-bodies-database
+---
+
+# --description--
+
+For this project, you will build a database of celestial bodies using PostgreSQL.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `universe.sql` file so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `universe.sql`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/swahili/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md b/curriculum/challenges/swahili/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
new file mode 100644
index 0000000000..9492b82cb4
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
@@ -0,0 +1,611 @@
+---
+id: 5a8b073d06fa14fcfde687aa
+title: Build an Exercise Tracker
+challengeType: 4
+dashedName: build-an-exercise-tracker
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://exercise-tracker.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://exercise-tracker.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+Your responses should have the following structures.
+
+Exercise:
+
+```js
+{
+  username: "fcc_test",
+  description: "test",
+  duration: 60,
+  date: "Mon Jan 01 1990",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+User:
+
+```js
+{
+  username: "fcc_test",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Log:
+
+```js
+{
+  username: "fcc_test",
+  count: 1,
+  _id: "5fb5853f734231456ccb3b05",
+  log: [{
+    description: "test",
+    duration: 60,
+    date: "Mon Jan 01 1990",
+  }]
+}
+```
+
+**Hint:** For the `date` property, the `toDateString` method of the `Date` API can be used to achieve the expected output.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  const url = getUserInput('url');
+  assert(
+    !/.*\/exercise-tracker\.freecodecamp\.rocks/.test(getUserInput('url'))
+  );
+};
+```
+
+You can `POST` to `/api/users` with form data `username` to create a new user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The returned response from `POST /api/users` with form data `username` will be an object with `username` and `_id` properties.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    assert.exists(_id);
+    assert.exists(username);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users` to get a list of all users.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `GET` request to `/api/users` returns an array.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    assert.isArray(users);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Each element in the array returned from `GET /api/users` is an object literal containing a user's `username` and `_id`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    const user = users[0];
+    assert.exists(user);
+    assert.exists(user.username);
+    assert.exists(user._id);
+    assert.isString(user.username);
+    assert.isString(user._id);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can `POST` to `/api/users/:_id/exercises` with form data `description`, `duration`, and optionally `date`. If no date is supplied, the current date will be used.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+  assert.isTrue(addRes.ok);
+  if(!addRes.ok) {
+    throw new Error(`${addRes.status} ${addRes.statusText}`)
+  };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+The response returned from `POST /api/users/:_id/exercises` will be the user object with the exercise fields added.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    if (addRes.ok) {
+      const actual = await addRes.json();
+      assert.deepEqual(actual, expected);
+      assert.isString(actual.description);
+      assert.isNumber(actual.duration);
+      assert.isString(actual.date);
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users/:_id/logs` to retrieve a full exercise log of any user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+    assert.isTrue(logRes.ok);
+    if(!logRes.ok) {
+      throw new Error(`${logRes.status} ${logRes.statusText}`)
+    };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A request to a user's log `GET /api/users/:_id/logs` returns a user object with a `count` property representing the number of exercises that belong to that user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if (logRes.ok) {
+        const { count } = await logRes.json();
+        assert(count);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A `GET` request to `/api/users/:_id/logs` will return the user object with a `log` array of all the exercises added.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  })
+  if(res.ok){
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok){
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+Each item in the `log` array that is returned from `GET /api/users/:_id/logs` is an object that should have a `description`, `duration`, and `date` properties.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + `/api/users`, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+     const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.exists(exercise);
+        assert.exists(exercise.description);
+        assert.exists(exercise.duration);
+        assert.exists(exercise.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `description` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.description);
+        assert.equal(exercise.description, expected.description);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `duration` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a number.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isNumber(exercise.duration);
+        assert.equal(exercise.duration, expected.duration);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `date` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string. Use the `dateString` format of the `Date` API.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toLocaleDateString("en-US", {
+        timeZone: "UTC", weekday: "short", month: "short",
+        day: "2-digit", year: "numeric"
+      }).replaceAll(',', '')
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.date);
+        assert.equal(exercise.date, expected.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can add `from`, `to` and `limit` parameters to a `GET /api/users/:_id/logs` request to retrieve part of the log of any user. `from` and `to` are dates in `yyyy-mm-dd` format. `limit` is an integer of how many logs to send back.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addExerciseRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    const addExerciseTwoRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-03`
+    });
+    if (addExerciseRes.ok && addExerciseTwoRes.ok) {
+      const logRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1989-12-31&to=1990-01-04`
+      );
+      if (logRes.ok) {
+        const { log } = await logRes.json();
+        assert.isArray(log);
+        assert.equal(2, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+      const limitRes = await fetch(
+        url + `/api/users/${_id}/logs?limit=1`
+      );
+      if (limitRes.ok) {
+        const { log } = await limitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${limitRes.status} ${limitRes.statusText}`);
+      }
+      const filterDateBeforeLimitRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1990-01-02&to=1990-01-04&limit=1`
+      );
+      if (filterDateBeforeLimitRes.ok) {
+        const { log } = await filterDateBeforeLimitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${filterDateBeforeLimitRes.status} ${filterDateBeforeLimitRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${res.status} ${res.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
diff --git a/curriculum/challenges/swahili/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md b/curriculum/challenges/swahili/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
new file mode 100644
index 0000000000..ef87dc6720
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
@@ -0,0 +1,25 @@
+---
+id: 602da04c22201c65d2a019f4
+title: Build a Number Guessing Game
+challengeType: 13
+url: freeCodeCamp/learn-number-guessing-game
+dashedName: lab-number-guessing-game
+---
+
+# --description--
+
+For this lab, you will use Bash scripting, PostgreSQL, and Git to create a number guessing game that runs in the terminal and saves user information.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `number_guess.sql` file, as well as your `number_guess.sh` file, so you can complete step 2. There will be instructions on how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `number_guess.sql`, `number_guess.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/swahili/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md b/curriculum/challenges/swahili/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
new file mode 100644
index 0000000000..5040e27424
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
@@ -0,0 +1,65 @@
+---
+id: bd7158d8c443edefaeb5bdff
+title: Build a Request Header Parser Microservice
+challengeType: 4
+dashedName: lab-request-header-parser-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://request-header-parser-microservice.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://request-header-parser-microservice.freecodecamp.rocks/</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/request-header-parser-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+A request to `/api/whoami` should return a JSON object with your IP address in the `ipaddress` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.ipaddress && data.ipaddress.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your preferred language in the `language` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.language && data.language.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your software in the `software` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.software && data.software.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/swahili/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md b/curriculum/challenges/swahili/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
new file mode 100644
index 0000000000..0fbf80a0bf
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
@@ -0,0 +1,107 @@
+---
+id: bd7158d8c443edefaeb5bd0e
+title: URL Shortener Microservice
+challengeType: 4
+dashedName: url-shortener-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://url-shortener-microservice.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://url-shortener-microservice.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+**HINT:** Do not forget to use a body parsing middleware to handle the POST requests. Also, you can use the function `dns.lookup(host, cb)` from the `dns` core module to verify a submitted URL.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/url-shortener-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+You can POST a URL to `/api/shorturl` and get a JSON response with `original_url` and `short_url` properties. Here's an example: `{ original_url : 'https://freeCodeCamp.org', short_url : 1}`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (res.ok) {
+    const { short_url, original_url } = await res.json();
+    assert.isNotNull(short_url);
+    assert.strictEqual(original_url, `${url}/?v=${urlVariable}`);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+When you visit `/api/shorturl/<short_url>`, you will be redirected to the original URL.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  let shortenedUrlVariable;
+  const postResponse = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (postResponse.ok) {
+    const { short_url } = await postResponse.json();
+    shortenedUrlVariable = short_url;
+  } else {
+    throw new Error(`${postResponse.status} ${postResponse.statusText}`);
+  }
+  const getResponse = await fetch(
+    url + '/api/shorturl/' + shortenedUrlVariable
+  );
+  if (getResponse) {
+    const { redirected, url } = getResponse;
+    assert.isTrue(redirected);
+    assert.strictEqual(url,fullUrl);
+  } else {
+    throw new Error(`${getResponse.status} ${getResponse.statusText}`);
+  }
+};
+```
+
+If you pass an invalid URL that doesn't follow the valid `http://www.example.com` format, the JSON response will contain `{ error: 'invalid url' }`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=ftp:/john-doe.invalidTLD`
+  });
+  if (res.ok) {
+    const { error } = await res.json();
+    assert.isNotNull(error);
+    assert.strictEqual(error.toLowerCase(), 'invalid url');
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
diff --git a/curriculum/challenges/swahili/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md b/curriculum/challenges/swahili/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
new file mode 100644
index 0000000000..d77442a1ba
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
@@ -0,0 +1,25 @@
+---
+id: 5f9771307d4d22b9d2b75a94
+title: Build a World Cup Database
+challengeType: 13
+url: freeCodeCamp/learn-world-cup-database
+dashedName: lab-world-cup-database
+---
+
+# --description--
+
+For this project, you will create a Bash script that enters information from World Cup games into PostgreSQL, then query the database for useful statistics.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `worldcup.sql` file, as well as your `insert_data.sh` and `queries.sh` files, so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `worldcup.sql`, `insert_data.sh`, `queries.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md b/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
index 51ea9e3069..753ee1a6bb 100644
--- a/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
@@ -7,9 +7,9 @@ dashedName: step-22
 
 # --description--
 
-Add another label with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
+Add another `label` with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
 
-Below the label element, add another checkbox input with the `id`, `name` and `value` attributes set to `"recommendation"`.
+Below the `label` element, add another checkbox `input` with the `id`, `name` and `value` attributes set to `"recommendation"`.
 
 # --hints--
 
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md b/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
index 42c425209d..80a23ca86d 100644
--- a/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
@@ -11,7 +11,7 @@ Next, add another `label` element with the text of `Location` and the `for` attr
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"location"`.
 
-Below that `input` element, add another `label` element with the text of `Reputation` and the for attribute set to `"reputation"`.
+Below that `input` element, add another `label` element with the text of `Reputation` and the `for` attribute set to `"reputation"`.
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"reputation"`.
 
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md b/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
index 69efa4832c..09e3e6e59b 100644
--- a/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
@@ -7,7 +7,7 @@ dashedName: step-28
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attributes:**
 
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md b/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
index 6549345d45..22b9a707be 100644
--- a/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
@@ -7,7 +7,7 @@ dashedName: step-31
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attribute:**
 
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
new file mode 100644
index 0000000000..237515fd88
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
@@ -0,0 +1,71 @@
+---
+id: 66c8ba41a77db20a93f9d7a1
+title: Step 1
+challengeType: 1
+dashedName: step-1
+---
+
+# --description--
+
+In this workshop, you'll review JavaScript conditionals by building a loan qualification checker app.
+
+The app will check whether the user is eligible for a duplex, car, and condo loan based on their annual income and credit score. A credit score is a number that represents how good you are at managing borrowed money.
+
+To get started, create the following variables and values.
+
+| Variable Name             | Value   |
+| ------------------------- | ------- |
+| `minIncomeForDuplex`      | `60000` |
+| `minCreditScoreForDuplex` | `700`   |
+| `minIncomeForCondo`       | `45000` |
+| `minCreditScoreForCondo`  | `680`   |
+| `minIncomeForCar`         | `30000` |
+| `minCreditScoreForCar`    | `650`   |
+
+# --hints--
+
+You should create a `minIncomeForDuplex` variable set to `60000`.
+
+```js
+assert.equal(minIncomeForDuplex, 60000);
+```
+
+You should create a `minCreditScoreForDuplex` set to `700`.
+
+```js
+assert.equal(minCreditScoreForDuplex, 700);
+```
+
+You should create a `minIncomeForCar` variable set to `30000`.
+
+```js
+assert.equal(minIncomeForCar, 30000);
+```
+
+You should create a `minCreditScoreForCar` variable set to `650`.
+
+```js
+assert.equal(minCreditScoreForCar, 650);
+```
+
+You should create a `minIncomeForCondo` variable set to `45000`.
+
+```js
+assert.equal(minIncomeForCondo, 45000);
+```
+
+You should create a `minCreditScoreForCondo` variable set to `680`.
+
+```js
+assert.equal(minCreditScoreForCondo, 680);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
new file mode 100644
index 0000000000..7755f823c4
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
@@ -0,0 +1,53 @@
+---
+id: 66c8ba975ee7230e29f6c4ac
+title: Step 2
+challengeType: 1
+dashedName: step-2
+---
+
+# --description--
+
+When the user is eligible for a loan, you'll want to display a message to them in the console.
+
+For that, you'll build out a function inside which you'll have some checks that'll return what loan the applicant is eligible for.
+
+Create an empty `getLoanMessage` function with an `annualIncome` and `creditScore` parameters.
+
+# --hints--
+
+You should create a `getLoanMessage` function
+
+```js
+assert.isFunction(getLoanMessage)
+```
+
+Your `getLoanMessage` function should have an `annualIncome` and `creditScore` as parameters.
+
+```js
+assert.match(getLoanMessage?.toString(), /\(\s*annualIncome,\s*creditScore\s*\)|\(\s*creditScore,\s*annualIncome\s*\)/);
+```
+
+`getLoanMessage` should be an empty function.
+
+```js
+assert.match(getLoanMessage?.toString(), /\{\s*\}/);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
new file mode 100644
index 0000000000..82a29d7cd9
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
@@ -0,0 +1,55 @@
+---
+id: 66c8ba975ee7230e29f6c4ad
+title: Step 3
+challengeType: 1
+dashedName: step-3
+---
+
+# --description--
+
+To check which loan a user is qualified for based on the `annualIncome` and `creditScore`, you have to use `if/else if` statement or a ternary right inside the `getLoanMessage` function. You'll then return the appropraite message in the block of each condition.
+
+Starting with the duplex loan, check if `annualIncome` is greater than or equal to `minIncomeForDuplex` AND if `creditScore` is greater than `minCreditScoreForDuplex`.
+
+If that condition is true, then the applicant is eligible for a duplex loan and the other loans. So, inside the check, return the string `"You qualify for a car, duplex and Condo loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string.
+
+```js
+assert.isString(getLoanMessage(65000, 750));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a duplex, condo, and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(65000, 750), "You qualify for a duplex, condo, and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a duplex loan.
+
+```js
+assert.strictEqual(getLoanMessage(59000, 700), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+function getLoanMessage(annualIncome, creditScore) {
+
+}
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
new file mode 100644
index 0000000000..638e6291a4
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4af
+title: Step 4
+challengeType: 1
+dashedName: step-4
+---
+
+# --description--
+
+If the applicant's annual income is greater than or equal to `minIncomeForCondo`, AND if their credit score is greater than or equal to `minCreditScoreForCondo`, then they qualify for a condo and car loan.
+
+Check if that's true in the `getLoanMessage` function. If it is, return the string `"You qualify for a condo and car loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a condo and car loan.
+
+```js
+assert.isString(getLoanMessage(45000, 680));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a condo and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 680), "You qualify for a condo and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a condo loan.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 650), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
new file mode 100644
index 0000000000..374ba7b8fe
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4b0
+title: Step 5
+challengeType: 1
+dashedName: step-5
+---
+
+# --description--
+
+Now, you should check if the applicant is qualified for a car loan only. If they're, return the string `"You qualify for a car loan."`.
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a car loan.
+
+```js
+assert.isString(getLoanMessage(30000, 650));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 650), "You qualify for a car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a car loan.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 600), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+--fcc-editable-region--
+  } 
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
new file mode 100644
index 0000000000..16e8c7baca
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
@@ -0,0 +1,54 @@
+---
+id: 66c8ba975ee7230e29f6c4b1
+title: Step 6
+challengeType: 1
+dashedName: step-6
+---
+
+# --description--
+
+If the applicant's annual income and credit score fall below `minIncomeForCar` and `minCreditScoreForCar`, then they don't qualify for any loan. So, return the string `"You don't qualify for any loans."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant doesn't qualify for any loan.
+
+```js
+assert.isString(getLoanMessage(25000, 550));
+```
+
+Your `getLoanMessage` function should return the string `"You don't qualify for any loans."` if the applicant does not meet the requirements for any loan.
+
+```js
+assert.strictEqual(getLoanMessage(15000, 600), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(25000, 550), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(20000, 500), "You don't qualify for any loans.");
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
new file mode 100644
index 0000000000..9d19f9ea4c
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
@@ -0,0 +1,165 @@
+---
+id: 66c8ba975ee7230e29f6c4b2
+title: Step 7
+challengeType: 1
+dashedName: step-7
+---
+
+# --description--
+
+Now, it is time to test out your `getLoanMessage` function.
+
+Use the table below to create `4` variables and their values:
+
+| Variable Name   | Value                        |
+| --------------- | ---------------------------- |
+| `duplexLoanMsg` | `getLoanMessage(85000, 850)` |
+| `condoLoanMsg`  | `getLoanMessage(65000, 690)` |
+| `carLoanMsg`    | `getLoanMessage(45000, 660)` |
+| `noLoanMsg`     | `getLoanMessage(25000, 550)` |
+
+After that, log each variable to the console to see the messages.
+
+With that, your loan qualification checker project is complete!
+
+# --hints--
+
+You should have a variable called `duplexLoanMsg`.
+
+```js
+assert.isNotNull(duplexLoanMsg);
+```
+
+Your `duplexLoanMsg` variable should be set to the result of `getLoanMessage(85000, 850)`.
+
+```js
+assert.equal(duplexLoanMsg, getLoanMessage(85000, 850));
+```
+
+You should log the `duplexLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(duplexLoanMsg\)/)
+```
+
+You should have a variable called `condoLoanMsg`.
+
+```js
+assert.isNotNull(condoLoanMsg);
+```
+
+Your `condoLoanMsg` variable should be set to the result of `getLoanMessage(65000, 690)`.
+
+```js
+assert.equal(condoLoanMsg, getLoanMessage(65000, 690));
+```
+
+You should log the `condoLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(condoLoanMsg\)/)
+```
+
+You should have a variable called `carLoanMsg`.
+
+```js
+assert.isNotNull(carLoanMsg);
+```
+
+Your `carLoanMsg` variable should be set to the result of `getLoanMessage(45000, 660)`.
+
+```js
+assert.equal(carLoanMsg, getLoanMessage(45000, 660));
+```
+
+You should log the `carLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(carLoanMsg\)/)
+```
+
+You should have a variable called `noLoanMsg`.
+
+```js
+assert.isNotNull(noLoanMsg);
+```
+
+Your `noLoanMsg` variable should be set to the result of `getLoanMessage(25000, 550)`.
+
+```js
+assert.equal(noLoanMsg, getLoanMessage(25000, 550));
+```
+
+You should log the `noLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(noLoanMsg\)/)
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
+
+# --solutions--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+const duplexLoanMsg = getLoanMessage(85000, 850)
+console.log(duplexLoanMsg)
+
+const condoLoanMsg = getLoanMessage(65000, 690)
+console.log(condoLoanMsg)
+
+const carLoanMsg = getLoanMessage(45000, 660)
+console.log(carLoanMsg)
+
+const noLoanMsg = getLoanMessage(25000, 550)
+console.log(noLoanMsg)
+```
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md b/curriculum/challenges/swahili/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
new file mode 100644
index 0000000000..4e11751ca0
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
@@ -0,0 +1,19 @@
+---
+id: 5f2c289f164c29556da632fd
+title: Build a Mario Database
+challengeType: 12
+url: freeCodeCamp/learn-relational-databases-by-building-a-mario-database
+dashedName: build-a-mario-database
+---
+
+# --description--
+
+In this 165-lesson workshop, you will learn the basics of a relational database by creating a PostgreSQL database filled with video game characters.
+
+# --instructions--
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
new file mode 100644
index 0000000000..8d4c90410d
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
@@ -0,0 +1,53 @@
+---
+id: 587d7fb3367417b2b2512bfb
+title: How to Use package.json, the Core of Any Node.js Project or npm Package
+challengeType: 2
+forumTopicId: 301528
+dashedName: how-to-use-package-json-the-core-of-any-node-js-project-or-npm-package
+---
+
+# --description--
+
+Working on these challenges will involve you writing your code using one of the following methods:
+
+- Clone <a href="https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete these challenges locally.
+- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+The `package.json` file is the center of any Node.js project or npm package. It stores information about your project. It consists of a single JSON object where information is stored in key-value pairs. There are only two required fields; `name` and `version`, but it’s good practice to provide additional information.
+
+You can create the `package.json` file from the terminal using the `npm init` command. This will run a guided setup. Using `npm init` with the `-y` flag will generate the file without having it ask any questions, `npm init -y`.
+
+If you look at the file tree of your project, you will find the `package.json` file on the top level of the tree. This is the file that you will be improving in the next couple of challenges.
+
+One of the most common pieces of information in this file is the `author` field. It specifies who created the project, and can consist of a string or an object with contact or other details. An object is recommended for bigger projects, but a simple string like the following example will do for this project.
+
+```json
+"author": "Jane Doe",
+```
+
+# --instructions--
+
+Add your name as the `author` of the project in the `package.json` file.
+
+**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (") and be separated with a comma (,).
+
+If you are using Gitpod, make sure the app is running and the preview window is open. Copy the preview window's URL and paste it into the Solution Link input below.
+
+# --hints--
+
+`package.json` should have a valid "author" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.author, '"author" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
new file mode 100644
index 0000000000..37d15d5261
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb3367417b2b2512bfc
+title: Add a Description to Your package.json
+challengeType: 2
+forumTopicId: 301522
+dashedName: add-a-description-to-your-package-json
+---
+
+# --description--
+
+The next part of a good package.json file is the `description` field; where a short, but informative description about your project belongs.
+
+If some day you plan to publish a package to npm, this is the string that should sell your idea to the user when they decide whether to install your package or not. However, that’s not the only use case for the description, it’s a great way to summarize what a project does. It’s just as important in any Node.js project to help other developers, future maintainers or even your future self understand the project quickly.
+
+Regardless of what you plan for your project, a description is definitely recommended. Here's an example:
+
+```json
+"description": "A project that does something awesome",
+```
+
+# --instructions--
+
+Add a `description` to the package.json file of your project.
+
+**Note:** Remember to use double-quotes for field-names (") and commas (,) to separate fields.
+
+# --hints--
+
+package.json should have a valid "description" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.description, '"description" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
new file mode 100644
index 0000000000..a001cdd477
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
@@ -0,0 +1,75 @@
+---
+id: 587d7fb4367417b2b2512bfd
+title: Add Keywords to Your package.json
+challengeType: 2
+forumTopicId: 301526
+dashedName: add-keywords-to-your-package-json
+---
+
+# --description--
+
+The `keywords` field is where you can describe your project using related keywords. Here's an example:
+
+```json
+"keywords": [ "descriptive", "related", "words" ],
+```
+
+As you can see, this field is structured as an array of double-quoted strings.
+
+# --instructions--
+
+Add an array of suitable strings to the `keywords` field in the package.json file of your project.
+
+One of the keywords should be "freecodecamp".
+
+# --hints--
+
+package.json should have a valid "keywords" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.keywords, '"keywords" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" field should be an Array
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.isArray(packJson.keywords, '"keywords" is not an array');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" should include "freecodecamp"
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.include(
+        packJson.keywords,
+        'freecodecamp',
+        '"keywords" does not include "freecodecamp"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
new file mode 100644
index 0000000000..7b09acd042
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
@@ -0,0 +1,39 @@
+---
+id: 587d7fb4367417b2b2512bfe
+title: Add a License to Your package.json
+challengeType: 2
+forumTopicId: 301523
+dashedName: add-a-license-to-your-package-json
+---
+
+# --description--
+
+The `license` field is where you inform users of what they are allowed to do with your project.
+
+Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do. Here's an example of the license field:
+
+```json
+"license": "MIT",
+```
+
+# --instructions--
+
+Fill the `license` field in the package.json file of your project as you find suitable.
+
+# --hints--
+
+package.json should have a valid "license" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.license, '"license" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
new file mode 100644
index 0000000000..f2e571faed
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
@@ -0,0 +1,37 @@
+---
+id: 587d7fb4367417b2b2512bff
+title: Add a Version to Your package.json
+challengeType: 2
+forumTopicId: 301525
+dashedName: add-a-version-to-your-package-json
+---
+
+# --description--
+
+A `version` is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example:
+
+```json
+"version": "1.2.0",
+```
+
+# --instructions--
+
+Add a `version` to the package.json file of your project.
+
+# --hints--
+
+package.json should have a valid "version" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.version, '"version" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
new file mode 100644
index 0000000000..161c60fe69
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
@@ -0,0 +1,68 @@
+---
+id: 587d7fb4367417b2b2512c00
+title: Expand Your Project with External Packages from npm
+challengeType: 2
+forumTopicId: 301527
+dashedName: expand-your-project-with-external-packages-from-npm
+---
+
+# --description--
+
+One of the biggest reasons to use a package manager, is their powerful dependency management. Instead of manually having to make sure that you get all dependencies whenever you set up a project on a new computer, npm automatically installs everything for you. But how can npm know exactly what your project needs? Meet the `dependencies` section of your package.json file.
+
+In this section, packages your project requires are stored using the following format:
+
+```json
+"dependencies": {
+  "package-name": "version",
+  "express": "4.14.0"
+}
+
+```
+
+# --instructions--
+
+Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file.
+
+**Note:** `@freecodecamp/example` is a faux package used as a learning tool.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.1.0"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^[\^\~]?1\.1\.0/,
+        'Wrong version of "@freecodecamp/example" installed. It should be 1.1.0'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
new file mode 100644
index 0000000000..deda9b82de
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
@@ -0,0 +1,64 @@
+---
+id: 587d7fb5367417b2b2512c01
+title: Manage npm Dependencies By Understanding Semantic Versioning
+challengeType: 2
+forumTopicId: 301529
+dashedName: manage-npm-dependencies-by-understanding-semantic-versioning
+---
+
+# --description--
+
+`Versions` of the npm packages in the dependencies section of your package.json file follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes projects can expect if they update.
+
+Knowing SemVer can be useful when you develop software that uses external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things that worked yesterday suddenly don’t work today. This is how Semantic Versioning works according to the official website:
+
+```json
+"package": "MAJOR.MINOR.PATCH"
+```
+
+The MAJOR version should increment when you make incompatible API changes. The MINOR version should increment when you add functionality in a backwards-compatible manner. The PATCH version should increment when you make backwards-compatible bug fixes. This means that PATCHes are bug fixes and MINORs add new features but neither of them break what worked before. Finally, MAJORs add changes that won’t work with earlier versions.
+
+# --instructions--
+
+In the dependencies section of your `package.json` file, change the version of `@freecodecamp/example` to match MAJOR version 1, MINOR version 2 and PATCH version 13
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.equal(
+        packJson.dependencies["@freecodecamp/example"],
+        '1.2.13',
+        'Wrong version of "@freecodecamp/example". It should be 1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
new file mode 100644
index 0000000000..8eae5f51ee
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c02
+title: Use the Tilde-Character to Always Use the Latest Patch Version of a Dependency
+challengeType: 2
+forumTopicId: 301532
+dashedName: use-the-tilde-character-to-always-use-the-latest-patch-version-of-a-dependency
+---
+
+# --description--
+
+In the last challenge, you told npm to only include a specific version of a package. That’s a useful way to freeze your dependencies if you need to make sure that different parts of your project stay compatible with each other. But in most use cases, you don’t want to miss bug fixes since they often include important security patches and (hopefully) don’t break things in doing so.
+
+To allow an npm dependency to update to the latest PATCH version, you can prefix the dependency’s version with the tilde (`~`) character. Here's an example of how to allow updates to any `1.3.x` version.
+
+```json
+"package": "~1.3.8"
+```
+
+# --instructions--
+
+In the package.json file, your current rule for how npm may upgrade `@freecodecamp/example` is to use a specific version (`1.2.13`). But now, you want to allow the latest `1.2.x` version.
+
+Use the tilde (`~`) character to prefix the version of `@freecodecamp/example` in your dependencies, and allow npm to update it to any new _patch_ release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"~1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\~1\.2\.13/,
+        'Wrong version of "@freecodecamp/example". It should be ~1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
new file mode 100644
index 0000000000..adc3014ea4
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c03
+title: Use the Caret-Character to Use the Latest Minor Version of a Dependency
+challengeType: 2
+forumTopicId: 301531
+dashedName: use-the-caret-character-to-use-the-latest-minor-version-of-a-dependency
+---
+
+# --description--
+
+Similar to how the tilde we learned about in the last challenge allows npm to install the latest PATCH for a dependency, the caret (`^`) allows npm to install future updates as well. The difference is that the caret will allow both MINOR updates and PATCHes.
+
+Your current version of `@freecodecamp/example` should be `~1.2.13` which allows npm to install to the latest `1.2.x` version. If you were to use the caret (^) as a version prefix instead, npm would be allowed to update to any `1.x.x` version.
+
+```json
+"package": "^1.3.8"
+```
+
+This would allow updates to any `1.x.x` version of the package.
+
+# --instructions--
+
+Use the caret (`^`) to prefix the version of `@freecodecamp/example` in your dependencies and allow npm to update it to any new MINOR release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"^1.x.x"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\^1\./,
+        'Wrong version of "@freecodecamp/example". It should be ^1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
new file mode 100644
index 0000000000..5f695eed88
--- /dev/null
+++ b/curriculum/challenges/swahili/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb5367417b2b2512c04
+title: Remove a Package from Your Dependencies
+challengeType: 2
+forumTopicId: 301530
+dashedName: remove-a-package-from-your-dependencies
+---
+
+# --description--
+
+You have now tested a few ways you can manage dependencies of your project by using the package.json's dependencies section. You have also included external packages by adding them to the file and even told npm what types of versions you want, by using special characters such as the tilde or the caret.
+
+But what if you want to remove an external package that you no longer need? You might already have guessed it, just remove the corresponding key-value pair for that package from your dependencies.
+
+This same method applies to removing other fields in your package.json as well.
+
+# --instructions--
+
+Remove the `@freecodecamp/example` package from your dependencies.
+
+**Note:** Make sure you have the right amount of commas after removing it.
+
+# --hints--
+
+`"dependencies"` should not include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.notProperty(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" still includes "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/ukrainian/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md b/curriculum/challenges/ukrainian/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
index 66a80ce222..bc476347cc 100644
--- a/curriculum/challenges/ukrainian/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
+++ b/curriculum/challenges/ukrainian/13-relational-databases/build-a-periodic-table-database-project/build-a-periodic-table-database.md
@@ -8,7 +8,7 @@ dashedName: build-a-periodic-table-database
 
 # --description--
 
-Це один з обов’язкових проєктів для отримання сертифікації. У цьому проєкті ви створите скрипт Bash для отримання інформації про хімічні елементи з бази даних періодичної таблиці.
+Це один з обов’язкових проєктів для отримання сертифікації. У цьому проєкті ви створите Bash-скрипт, щоб отримати інформацію про хімічні елементи з бази даних періодичної таблиці.
 
 # --instructions--
 
diff --git a/curriculum/challenges/ukrainian/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md b/curriculum/challenges/ukrainian/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
index d5b2e5218c..def95eaa56 100644
--- a/curriculum/challenges/ukrainian/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
+++ b/curriculum/challenges/ukrainian/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f3ef6e0a81099d9a697b550.md
@@ -9,6 +9,8 @@ dashedName: step-64
 
 Всередині `footer` додайте елемент `p`. Потім вкладіть елемент прив'язки (`a`) в `p`, що посилає на `https://www.freecodecamp.org` та має текст `Visit our website`.
 
+Make sure that the link opens in a new tab by adding a `target` attribute with the value `_blank`.
+
 # --hints--
 
 Ви не повинні змінювати наявний елемент `footer`.
@@ -43,6 +45,12 @@ assert(document.querySelector("footer > p > a")?.innerText === "Visit our websit
 assert(document.querySelector("footer > p > a")?.href === "https://www.freecodecamp.org/");
 ```
 
+Your new `a` element should have the `target` attribute set to `_blank`.
+
+```js
+assert.equal(document.querySelector("footer > p > a")?.target, "_blank");
+```
+
 # --seed--
 
 ## --seed-contents--
diff --git a/curriculum/challenges/ukrainian/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md b/curriculum/challenges/ukrainian/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md
index 47779ee0ec..c298237e68 100644
--- a/curriculum/challenges/ukrainian/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md
+++ b/curriculum/challenges/ukrainian/14-responsive-web-design-22/learn-intermediate-css-by-building-a-cat-painting/646de7b64467e96b7d35b5cd.md
@@ -7,7 +7,7 @@ dashedName: step-47
 
 # --description--
 
-Move the right eye into position with a `position` property of `absolute`, a `top` of `54px`, and a `left` of `134px`.
+Перемістіть праве око на місце за допомогою властивостей `position` зі значенням `absolute`, `top` зі значенням `54px` та `left` зі значенням `134px`.
 
 # --hints--
 
diff --git a/curriculum/challenges/ukrainian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md b/curriculum/challenges/ukrainian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
index 203968fb7f..09951fa0f7 100644
--- a/curriculum/challenges/ukrainian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
+++ b/curriculum/challenges/ukrainian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-j.md
@@ -21,12 +21,12 @@ dashedName: introduction-flexbox-lesson-j
 
 `justify-content` вирівнює предмети по **головній осі**. До цієї властивості можна використати декілька значень. Про решту ви дізнаєтесь в завданнях з читання. А зараз спробуйте використати значення `center`, що відцентрує блоки вздовж головної осі.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Перш ніж перейти до наступного уроку, подивіться, що можливо за допомогою властивості `justify-content`. Прочитайте [цю статтю](https://webdoky.org/uk/docs/Web/CSS/justify-content/#syntaksys) (англійською мовою) та ознайомтесь з різними значеннями властивості `justify-content` на прикладі.
 
+# --question--
+
 ## --text--
 
 Як застосування властивості `justify-content: space-between` до гнучкого контейнера впливає на розташування його предметів?
diff --git a/curriculum/challenges/ukrainian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md b/curriculum/challenges/ukrainian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
index 690525e092..268849cc07 100644
--- a/curriculum/challenges/ukrainian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
+++ b/curriculum/challenges/ukrainian/16-the-odin-project/top-introduction-to-flexbox/introduction-flexbox-lesson-k.md
@@ -17,12 +17,12 @@ allowtransparency="true" class="cp_embed_iframe " frameborder="0" height="400" w
 
 Оскільки `justify-content` та `align-items` базуються на головній та перехресній осях контейнера, то їхня поведінка змінюється, якщо ви змінюєте `flex-direction` гнучкого контейнера. Наприклад, якщо змінити `flex-direction` на `column`, то `justify-content` вирівнюватиме вертикально, а `align-items` — горизонтально. Однак найпоширенішою поведінкою є поведінка за замовчуванням: `justify-content` вирівнює предмети горизонтально (оскільки головна вісь за замовчуванням горизонтальна), а `align-items` вирівнює їх вертикально. Одна з найбільших труднощів, з якими початківці стикаються при роботі з flexbox, — це плутанина при зміні поведінки.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Перш ніж перейти до наступного уроку, переконайтесь, що розумієте, як поводиться `align-items` при зміні властивості `flex-direction` на `column`.
 
+# --question--
+
 ## --text--
 
 Як поводиться `align-items` стосовно гнучких предметів, якщо в гнучкому контейнері змінити властивість `flex-direction` на `column`?
diff --git a/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md b/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
index a17f68fb7b..1d2377e19d 100644
--- a/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
+++ b/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-b.md
@@ -9,12 +9,12 @@ dashedName: learn-block-and-inline-lesson-b
 
 А ось рядкові елементи не починаються з нового рядка. Вони з’являються в рядку з будь-якими елементами, біля яких їх розташували. Хорошим прикладом рядкового елемента є посилання (тег `<a>`). Якщо розмістити один з таких елементів всередині абзацу тексту, то він поводитиметься як частина абзацу. <a  href="https://www.freecodecamp.org/ukrainian/" target="_blank">(Ось так)</a> Текст посилання знаходитиметься між іншими словами абзацу. До того ж відступ та поле рядкових елементів поводяться по-іншому. Загалом, не намагайтесь надати додатковий відступ або поле до рядкових елементів.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Знайдіть в інтернеті список блокових та рядкових елементів.
 
+# --question--
+
 ## --text--
 
 Яка різниця між блоковими та рядковими елементами?
diff --git a/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md b/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
index 112efe5871..fa54e1e4b3 100644
--- a/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
+++ b/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-block-and-inline/learn-block-and-inline-lesson-g.md
@@ -7,7 +7,7 @@ dashedName: learn-block-and-inline-lesson-g
 
 # --description--
 
-Тепер у вас є базове розуміння блокових та рядкових елементів. Поверніться до списку блокових та рядкових елементів з попереднього завдання та перевірте, чи зможете ідентифікувати блокові та рядкові елементи.
+Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements.
 
 # --question--
 
diff --git a/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md b/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
index 5e6f3b5494..ec454b41b3 100644
--- a/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
+++ b/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-a.md
@@ -21,12 +21,12 @@ dashedName: learn-to-solve-problems-and-understand-errors-lesson-a
 
 Найкращий спосіб покращити цю навичку — набувати досвід, створюючи багато програм. Чим більше практики, тим краще ви будете розв’язувати реальні проблеми.
 
-# --question--
-
-## --assignment--
+# --assignment--
 
 Прочитайте статтю <a href="https://www.freecodecamp.org/ukrainian/news/dumay-yak-prohramist-uroky-rozv-yazannya-problem/" target="_blank">«Думай як програміст: уроки розв’язання проблем»</a> Річарда Рейса.
 
+# --question--
+
 ## --text--
 
 Що таке «розв’язання проблем» у програмуванні відповідно до книги «Думай як програміст» В. Антона Спраула?
diff --git a/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md b/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
index 5f4b64dce3..a6ff4d2190 100644
--- a/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
+++ b/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-b.md
@@ -25,11 +25,11 @@ dashedName: learn-to-solve-problems-and-understand-errors-lesson-b
 
 Для останнього запитання ви писатимете алгоритм розв’язання проблеми. Алгоритм можна вважати «рецептом» розв’язання проблеми. Він визначає кроки в псевдокоді, які має зробити комп’ютер, щоб розв’язати проблему.
 
-# --question--
-
-## --assignment--
+# --assignment--
 Перегляньте відео <a href="https://www.youtube.com/watch?v=azcrPFhaY9k" target="_blank">«Як розпочати мислити, як програміст»</a> від Coding Tech (англійською мовою). Воно триває годину, але містить важливу інформацію та вартує перегляду.
 
+# --question--
+
 ## --text--
 
 Що потрібно зробити перед тим, як розпочати програмувати, відповідно до даного тексту?
diff --git a/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md b/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
index 35a4e47082..b3e332f0da 100644
--- a/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
+++ b/curriculum/challenges/ukrainian/16-the-odin-project/top-learn-to-solve-problems-and-understand-errors/learn-to-solve-problems-and-understand-errors-lesson-c.md
@@ -22,12 +22,12 @@ Print the value of the counter variable
 
 Це базова програма, щоб продемонструвати псевдокод. У завданнях буде ще більше прикладів псевдокоду.
 
+# --assignment--
 
-# --question--
-
-## --assignment--
 Прочитайте статтю <a href="https://builtin.com/data-science/pseudocode" target="_blank"> «Псевдокод: що це і як його написати»</a> від Built In (англійською мовою).
 
+# --question--
+
 ## --text--
 
 Які переваги використання псевдокоду відповідно до наданої статті?
diff --git a/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-b.md b/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-b.md
index 09a5adb5e2..8a9e8c0d2d 100644
--- a/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-b.md
+++ b/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-b.md
@@ -9,7 +9,7 @@ dashedName: the-box-model-lesson-b
 
 На панелі «Елементи» можна побачити повну структуру HTML. Ви можете натиснути на будь-який елемент панелі, щоб обрати певний елемент. Або ж ви можете натиснути на голубий значок зліва (показано нижче) та навести на будь-який елемент сторінки.
 
-<img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/inspector-icon.png" alt="A web development environment with developer tools open, highlighting a blue inspector icon in the top-left for selecting webpage elements to view HTML structure and styles." />
+<img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/inspector-icon.png" alt="Середовище веброзробки з відкритими інструментами розробника, де у верхньому лівому куті виділено синій значок інспектора для вибору елементів вебсторінки, щоб переглянути структуру та стилі HTML." />
 
 Коли елемент обрано, вкладка «Стилі» покаже всі застосовані стилі, а також усі змінені стилі (у вигляді закресленого тексту). Наприклад, якщо використати інспектора та натиснути на заголовок «Your Career in Web Development Starts Here» <a href="https://www.theodinproject.com/" target="_blank">домашньої сторінки проєкту Odin</a>, справа ви побачите всі стилі, які наразі застосовані до елемента:
 
diff --git a/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-c.md b/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-c.md
index 55e221c980..558502cda4 100644
--- a/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-c.md
+++ b/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-c.md
@@ -8,7 +8,7 @@ dashedName: the-box-model-lesson-c
 
 На панелі «Елементи» можна побачити повну структуру HTML. Ви можете натиснути на будь-який елемент панелі, щоб обрати певний елемент. Або ж ви можете натиснути на голубий значок зліва (показано нижче) та навести на будь-який елемент сторінки.
 
-<img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/inspector-icon.png" alt="A web development environment with developer tools open, highlighting a blue inspector icon in the top-left for selecting webpage elements to view HTML structure and styles." />
+<img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/inspector-icon.png" alt="Середовище веброзробки з відкритими інструментами розробника, де у верхньому лівому куті виділено синій значок інспектора для вибору елементів вебсторінки, щоб переглянути структуру та стилі HTML." />
 
 Коли елемент обрано, вкладка «Стилі» покаже всі застосовані стилі, а також усі змінені стилі (у вигляді закресленого тексту). Наприклад, якщо використати інспектора та натиснути на заголовок «Your Career in Web Development Starts Here» <a href="https://www.theodinproject.com/" target="_blank">домашньої сторінки проєкту Odin</a>, справа ви побачите всі стилі, які наразі застосовані до елемента:
 
diff --git a/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-d.md b/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-d.md
index 5f8b3e5627..ef449854aa 100644
--- a/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-d.md
+++ b/curriculum/challenges/ukrainian/16-the-odin-project/top-the-box-model/the-box-model-lesson-d.md
@@ -8,7 +8,7 @@ dashedName: the-box-model-lesson-d
 
 На панелі «Елементи» можна побачити повну структуру HTML. Ви можете натиснути на будь-який елемент панелі, щоб обрати певний елемент. Або ж ви можете натиснути на голубий значок зліва (показано нижче) та навести на будь-який елемент сторінки.
 
-<img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/inspector-icon.png" alt="A web development environment with developer tools open, highlighting a blue inspector icon in the top-left for selecting webpage elements to view HTML structure and styles." />
+<img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/inspector-icon.png" alt="Середовище веброзробки з відкритими інструментами розробника, де у верхньому лівому куті виділено синій значок інспектора для вибору елементів вебсторінки, щоб переглянути структуру та стилі HTML." />
 
 Коли елемент обрано, вкладка «Стилі» покаже всі застосовані стилі, а також усі змінені стилі (у вигляді закресленого тексту). Наприклад, якщо використати інспектора та натиснути на заголовок «Your Career in Web Development Starts Here» <a href="https://www.theodinproject.com/" target="_blank">домашньої сторінки проєкту Odin</a>, справа ви побачите всі стилі, які наразі застосовані до елемента:
 
diff --git a/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md b/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
index 33bd67fe1d..302860af33 100644
--- a/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
+++ b/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657b69e10d6606a0185d4d4f.md
@@ -9,7 +9,7 @@ dashedName: task-23
 
 # --description--
 
-Ви вже вмієте утворювати запитання з дієсловом `to be`. Щоб утворити запитання з дієсловом `to be` (am, is, are), вам просто потрібно поміняти місцями іменник з дієсловом. Наприклад:
+So far you have learned how to create questions with the verb `to be`. Щоб утворити запитання з дієсловом `to be` (am, is, are), вам просто потрібно поміняти місцями іменник з дієсловом. Наприклад:
 
 `You are a developer` -> `Are you a developer?`
 
diff --git a/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md b/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
index f5496de3dc..450d02034f 100644
--- a/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
+++ b/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dce8ff35869721311a5e3.md
@@ -21,7 +21,7 @@ Which sentence is correct for describing one place near you?
 
 ### --feedback--
 
-`There are` is used for plural nouns, and `bank` is singular. You’ll learn about there are in the next few lessons.
+`There are` is used for plural nouns, and `bank` is singular. You’ll learn about `there are` in the next few lessons.
 
 ---
 
diff --git a/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md b/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
index 8784d91772..4e2e7d8bc2 100644
--- a/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
+++ b/curriculum/challenges/ukrainian/21-a2-english-for-developers/learn-conversation-starters-in-the-break-room/657dcee413423174ca3747f5.md
@@ -7,7 +7,7 @@ dashedName: task-112
 
 # --description--
 
-To elaborate a question using `there is` you just need to change the order of the verb to be, like so:
+To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so:
 
 `There is an ATM nearby` -> `Is there an ATM nearby?`
 
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md b/curriculum/challenges/ukrainian/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
new file mode 100644
index 0000000000..7d664a8876
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/lab-celestial-bodies-database/5f1a4ef5d5d6b5ab580fc6ae.md
@@ -0,0 +1,25 @@
+---
+id: 5f1a4ef5d5d6b5ab580fc6ae
+title: Build a Celestial Bodies Database
+challengeType: 13
+url: freeCodeCamp/learn-celestial-bodies-database
+dashedName: lab-celestial-bodies-database
+---
+
+# --description--
+
+For this project, you will build a database of celestial bodies using PostgreSQL.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `universe.sql` file so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `universe.sql`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md b/curriculum/challenges/ukrainian/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
new file mode 100644
index 0000000000..9492b82cb4
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/lab-exercise-tracker/5a8b073d06fa14fcfde687aa.md
@@ -0,0 +1,611 @@
+---
+id: 5a8b073d06fa14fcfde687aa
+title: Build an Exercise Tracker
+challengeType: 4
+dashedName: build-an-exercise-tracker
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://exercise-tracker.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://exercise-tracker.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+Your responses should have the following structures.
+
+Exercise:
+
+```js
+{
+  username: "fcc_test",
+  description: "test",
+  duration: 60,
+  date: "Mon Jan 01 1990",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+User:
+
+```js
+{
+  username: "fcc_test",
+  _id: "5fb5853f734231456ccb3b05"
+}
+```
+
+Log:
+
+```js
+{
+  username: "fcc_test",
+  count: 1,
+  _id: "5fb5853f734231456ccb3b05",
+  log: [{
+    description: "test",
+    duration: 60,
+    date: "Mon Jan 01 1990",
+  }]
+}
+```
+
+**Hint:** For the `date` property, the `toDateString` method of the `Date` API can be used to achieve the expected output.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  const url = getUserInput('url');
+  assert(
+    !/.*\/exercise-tracker\.freecodecamp\.rocks/.test(getUserInput('url'))
+  );
+};
+```
+
+You can `POST` to `/api/users` with form data `username` to create a new user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The returned response from `POST /api/users` with form data `username` will be an object with `username` and `_id` properties.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    assert.exists(_id);
+    assert.exists(username);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users` to get a list of all users.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  assert.isTrue(res.ok);
+  if(!res.ok) {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `GET` request to `/api/users` returns an array.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    assert.isArray(users);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+Each element in the array returned from `GET /api/users` is an object literal containing a user's `username` and `_id`.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users');
+  if(res.ok){
+    const users = await res.json();
+    const user = users[0];
+    assert.exists(user);
+    assert.exists(user.username);
+    assert.exists(user._id);
+    assert.isString(user.username);
+    assert.isString(user._id);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can `POST` to `/api/users/:_id/exercises` with form data `description`, `duration`, and optionally `date`. If no date is supplied, the current date will be used.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+  assert.isTrue(addRes.ok);
+  if(!addRes.ok) {
+    throw new Error(`${addRes.status} ${addRes.statusText}`)
+  };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+The response returned from `POST /api/users/:_id/exercises` will be the user object with the exercise fields added.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: 'Mon Jan 01 1990'
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    if (addRes.ok) {
+      const actual = await addRes.json();
+      assert.deepEqual(actual, expected);
+      assert.isString(actual.description);
+      assert.isNumber(actual.duration);
+      assert.isString(actual.date);
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+You can make a `GET` request to `/api/users/:_id/logs` to retrieve a full exercise log of any user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+    assert.isTrue(logRes.ok);
+    if(!logRes.ok) {
+      throw new Error(`${logRes.status} ${logRes.statusText}`)
+    };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A request to a user's log `GET /api/users/:_id/logs` returns a user object with a `count` property representing the number of exercises that belong to that user.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if (addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if (logRes.ok) {
+        const { count } = await logRes.json();
+        assert(count);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+A `GET` request to `/api/users/:_id/logs` will return the user object with a `log` array of all the exercises added.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  })
+  if(res.ok){
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok){
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+Each item in the `log` array that is returned from `GET /api/users/:_id/logs` is an object that should have a `description`, `duration`, and `date` properties.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + `/api/users`, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded'
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+     const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok) {
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.exists(exercise);
+        assert.exists(exercise.description);
+        assert.exists(exercise.duration);
+        assert.exists(exercise.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      };
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`)
+  };
+};
+```
+
+The `description` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.description);
+        assert.equal(exercise.description, expected.description);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `duration` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a number.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isNumber(exercise.duration);
+        assert.equal(exercise.duration, expected.duration);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+The `date` property of any object in the `log` array that is returned from `GET /api/users/:_id/logs` should be a string. Use the `dateString` format of the `Date` API.
+
+```js
+async(getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/x-www-form-urlencoded',
+    },
+    body: `username=fcc_test_${Date.now()}`.substring(0,29)
+  });
+  if(res.ok) {
+    const {_id, username} = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toLocaleDateString("en-US", {
+        timeZone: "UTC", weekday: "short", month: "short",
+        day: "2-digit", year: "numeric"
+      }).replaceAll(',', '')
+    };
+    const addRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/x-www-form-urlencoded',
+      },
+      body: `description=${expected.description}&duration=${expected.duration}`
+    });
+    if(addRes.ok) {
+      const logRes = await fetch(url + `/api/users/${_id}/logs`);
+      if(logRes.ok){
+        const {log} = await logRes.json();
+        const exercise = log[0];
+        assert.isString(exercise.date);
+        assert.equal(exercise.date, expected.date);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${addRes.status} ${addRes.statusText}`);
+    };
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  };
+};
+```
+
+You can add `from`, `to` and `limit` parameters to a `GET /api/users/:_id/logs` request to retrieve part of the log of any user. `from` and `to` are dates in `yyyy-mm-dd` format. `limit` is an integer of how many logs to send back.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/users', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `username=fcc_test_${Date.now()}`.substring(0, 29)
+  });
+  if (res.ok) {
+    const { _id, username } = await res.json();
+    const expected = {
+      username,
+      description: 'test',
+      duration: 60,
+      _id,
+      date: new Date().toDateString()
+    };
+    const addExerciseRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-01`
+    });
+    const addExerciseTwoRes = await fetch(url + `/api/users/${_id}/exercises`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+      body: `description=${expected.description}&duration=${expected.duration}&date=1990-01-03`
+    });
+    if (addExerciseRes.ok && addExerciseTwoRes.ok) {
+      const logRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1989-12-31&to=1990-01-04`
+      );
+      if (logRes.ok) {
+        const { log } = await logRes.json();
+        assert.isArray(log);
+        assert.equal(2, log.length);
+      } else {
+        throw new Error(`${logRes.status} ${logRes.statusText}`);
+      }
+      const limitRes = await fetch(
+        url + `/api/users/${_id}/logs?limit=1`
+      );
+      if (limitRes.ok) {
+        const { log } = await limitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${limitRes.status} ${limitRes.statusText}`);
+      }
+      const filterDateBeforeLimitRes = await fetch(
+        url + `/api/users/${_id}/logs?from=1990-01-02&to=1990-01-04&limit=1`
+      );
+      if (filterDateBeforeLimitRes.ok) {
+        const { log } = await filterDateBeforeLimitRes.json();
+        assert.isArray(log);
+        assert.equal(1, log.length);
+      } else {
+        throw new Error(`${filterDateBeforeLimitRes.status} ${filterDateBeforeLimitRes.statusText}`);
+      }
+    } else {
+      throw new Error(`${res.status} ${res.statusText}`);
+    }
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md b/curriculum/challenges/ukrainian/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
new file mode 100644
index 0000000000..ef87dc6720
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/lab-number-guessing-game/602da04c22201c65d2a019f4.md
@@ -0,0 +1,25 @@
+---
+id: 602da04c22201c65d2a019f4
+title: Build a Number Guessing Game
+challengeType: 13
+url: freeCodeCamp/learn-number-guessing-game
+dashedName: lab-number-guessing-game
+---
+
+# --description--
+
+For this lab, you will use Bash scripting, PostgreSQL, and Git to create a number guessing game that runs in the terminal and saves user information.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `number_guess.sql` file, as well as your `number_guess.sh` file, so you can complete step 2. There will be instructions on how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `number_guess.sql`, `number_guess.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md b/curriculum/challenges/ukrainian/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
new file mode 100644
index 0000000000..5040e27424
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/lab-request-header-parser-microservice/bd7158d8c443edefaeb5bdff.md
@@ -0,0 +1,65 @@
+---
+id: bd7158d8c443edefaeb5bdff
+title: Build a Request Header Parser Microservice
+challengeType: 4
+dashedName: lab-request-header-parser-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://request-header-parser-microservice.freecodecamp.rocks/" target="_blank" rel="noopener noreferrer nofollow">https://request-header-parser-microservice.freecodecamp.rocks/</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-headerparser/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/request-header-parser-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+A request to `/api/whoami` should return a JSON object with your IP address in the `ipaddress` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.ipaddress && data.ipaddress.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your preferred language in the `language` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.language && data.language.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+A request to `/api/whoami` should return a JSON object with your software in the `software` key.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/api/whoami').then(
+    (data) => assert(data.software && data.software.length > 0),
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md b/curriculum/challenges/ukrainian/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
new file mode 100644
index 0000000000..0fbf80a0bf
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/lab-url-shortener-microservice/bd7158d8c443edefaeb5bd0e.md
@@ -0,0 +1,107 @@
+---
+id: bd7158d8c443edefaeb5bd0e
+title: URL Shortener Microservice
+challengeType: 4
+dashedName: url-shortener-microservice
+---
+
+# --description--
+
+Build a full stack JavaScript app that is functionally similar to this: <a href="https://url-shortener-microservice.freecodecamp.rocks" target="_blank" rel="noopener noreferrer nofollow">https://url-shortener-microservice.freecodecamp.rocks</a>. Working on this project will involve you writing your code using one of the following methods:
+
+-   Clone <a href="https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete your project locally.
+-   Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-project-urlshortener/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete your project.
+-   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+# --instructions--
+
+**HINT:** Do not forget to use a body parsing middleware to handle the POST requests. Also, you can use the function `dns.lookup(host, cb)` from the `dns` core module to verify a submitted URL.
+
+# --hints--
+
+You should provide your own project, not the example URL.
+
+```js
+(getUserInput) => {
+  assert(
+    !/.*\/url-shortener-microservice\.freecodecamp\.rocks/.test(
+      getUserInput('url')
+    )
+  );
+};
+```
+
+You can POST a URL to `/api/shorturl` and get a JSON response with `original_url` and `short_url` properties. Here's an example: `{ original_url : 'https://freeCodeCamp.org', short_url : 1}`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (res.ok) {
+    const { short_url, original_url } = await res.json();
+    assert.isNotNull(short_url);
+    assert.strictEqual(original_url, `${url}/?v=${urlVariable}`);
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
+When you visit `/api/shorturl/<short_url>`, you will be redirected to the original URL.
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const urlVariable = Date.now();
+  const fullUrl = `${url}/?v=${urlVariable}`
+  let shortenedUrlVariable;
+  const postResponse = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=${fullUrl}`
+  });
+  if (postResponse.ok) {
+    const { short_url } = await postResponse.json();
+    shortenedUrlVariable = short_url;
+  } else {
+    throw new Error(`${postResponse.status} ${postResponse.statusText}`);
+  }
+  const getResponse = await fetch(
+    url + '/api/shorturl/' + shortenedUrlVariable
+  );
+  if (getResponse) {
+    const { redirected, url } = getResponse;
+    assert.isTrue(redirected);
+    assert.strictEqual(url,fullUrl);
+  } else {
+    throw new Error(`${getResponse.status} ${getResponse.statusText}`);
+  }
+};
+```
+
+If you pass an invalid URL that doesn't follow the valid `http://www.example.com` format, the JSON response will contain `{ error: 'invalid url' }`
+
+```js
+async (getUserInput) => {
+  const url = getUserInput('url');
+  const res = await fetch(url + '/api/shorturl', {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
+    body: `url=ftp:/john-doe.invalidTLD`
+  });
+  if (res.ok) {
+    const { error } = await res.json();
+    assert.isNotNull(error);
+    assert.strictEqual(error.toLowerCase(), 'invalid url');
+  } else {
+    throw new Error(`${res.status} ${res.statusText}`);
+  }
+};
+```
+
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md b/curriculum/challenges/ukrainian/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
new file mode 100644
index 0000000000..d77442a1ba
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/lab-world-cup-database/5f9771307d4d22b9d2b75a94.md
@@ -0,0 +1,25 @@
+---
+id: 5f9771307d4d22b9d2b75a94
+title: Build a World Cup Database
+challengeType: 13
+url: freeCodeCamp/learn-world-cup-database
+dashedName: lab-world-cup-database
+---
+
+# --description--
+
+For this project, you will create a Bash script that enters information from World Cup games into PostgreSQL, then query the database for useful statistics.
+
+# --instructions--
+
+**Important:** After you pass all the project tests, save a dump of your database into a `worldcup.sql` file, as well as your `insert_data.sh` and `queries.sh` files, so you can complete step 2. There will be instructions how to do that within the virtual machine.
+
+# --notes--
+
+Required files: `worldcup.sql`, `insert_data.sh`, `queries.sh`
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
index 51ea9e3069..753ee1a6bb 100644
--- a/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a96127422411756204bc1b.md
@@ -7,9 +7,9 @@ dashedName: step-22
 
 # --description--
 
-Add another label with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
+Add another `label` with the text of `Personal Recommendation`. The `for` attribute should be set to `"recommendation"`.
 
-Below the label element, add another checkbox input with the `id`, `name` and `value` attributes set to `"recommendation"`.
+Below the `label` element, add another checkbox `input` with the `id`, `name` and `value` attributes set to `"recommendation"`.
 
 # --hints--
 
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
index 42c425209d..80a23ca86d 100644
--- a/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a962954f4e0d76223b37ed.md
@@ -11,7 +11,7 @@ Next, add another `label` element with the text of `Location` and the `for` attr
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"location"`.
 
-Below that `input` element, add another `label` element with the text of `Reputation` and the for attribute set to `"reputation"`.
+Below that `input` element, add another `label` element with the text of `Reputation` and the `for` attribute set to `"reputation"`.
 
 For the checkbox `input`, both the `id`, `name` and `value` attributes should be set to `"reputation"`.
 
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
index 69efa4832c..09e3e6e59b 100644
--- a/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a972137acd1179fa3fe8a0.md
@@ -7,7 +7,7 @@ dashedName: step-28
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attributes:**
 
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
index 6549345d45..22b9a707be 100644
--- a/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-hotel-feedback-form/66a97ca8c4cbae7d0bb6e0ad.md
@@ -7,7 +7,7 @@ dashedName: step-31
 
 # --description--
 
-Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute:
+Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute:
 
 **Value Attribute:**
 
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
new file mode 100644
index 0000000000..237515fd88
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba41a77db20a93f9d7a1.md
@@ -0,0 +1,71 @@
+---
+id: 66c8ba41a77db20a93f9d7a1
+title: Step 1
+challengeType: 1
+dashedName: step-1
+---
+
+# --description--
+
+In this workshop, you'll review JavaScript conditionals by building a loan qualification checker app.
+
+The app will check whether the user is eligible for a duplex, car, and condo loan based on their annual income and credit score. A credit score is a number that represents how good you are at managing borrowed money.
+
+To get started, create the following variables and values.
+
+| Variable Name             | Value   |
+| ------------------------- | ------- |
+| `minIncomeForDuplex`      | `60000` |
+| `minCreditScoreForDuplex` | `700`   |
+| `minIncomeForCondo`       | `45000` |
+| `minCreditScoreForCondo`  | `680`   |
+| `minIncomeForCar`         | `30000` |
+| `minCreditScoreForCar`    | `650`   |
+
+# --hints--
+
+You should create a `minIncomeForDuplex` variable set to `60000`.
+
+```js
+assert.equal(minIncomeForDuplex, 60000);
+```
+
+You should create a `minCreditScoreForDuplex` set to `700`.
+
+```js
+assert.equal(minCreditScoreForDuplex, 700);
+```
+
+You should create a `minIncomeForCar` variable set to `30000`.
+
+```js
+assert.equal(minIncomeForCar, 30000);
+```
+
+You should create a `minCreditScoreForCar` variable set to `650`.
+
+```js
+assert.equal(minCreditScoreForCar, 650);
+```
+
+You should create a `minIncomeForCondo` variable set to `45000`.
+
+```js
+assert.equal(minIncomeForCondo, 45000);
+```
+
+You should create a `minCreditScoreForCondo` variable set to `680`.
+
+```js
+assert.equal(minCreditScoreForCondo, 680);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
new file mode 100644
index 0000000000..7755f823c4
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ac.md
@@ -0,0 +1,53 @@
+---
+id: 66c8ba975ee7230e29f6c4ac
+title: Step 2
+challengeType: 1
+dashedName: step-2
+---
+
+# --description--
+
+When the user is eligible for a loan, you'll want to display a message to them in the console.
+
+For that, you'll build out a function inside which you'll have some checks that'll return what loan the applicant is eligible for.
+
+Create an empty `getLoanMessage` function with an `annualIncome` and `creditScore` parameters.
+
+# --hints--
+
+You should create a `getLoanMessage` function
+
+```js
+assert.isFunction(getLoanMessage)
+```
+
+Your `getLoanMessage` function should have an `annualIncome` and `creditScore` as parameters.
+
+```js
+assert.match(getLoanMessage?.toString(), /\(\s*annualIncome,\s*creditScore\s*\)|\(\s*creditScore,\s*annualIncome\s*\)/);
+```
+
+`getLoanMessage` should be an empty function.
+
+```js
+assert.match(getLoanMessage?.toString(), /\{\s*\}/);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
new file mode 100644
index 0000000000..82a29d7cd9
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4ad.md
@@ -0,0 +1,55 @@
+---
+id: 66c8ba975ee7230e29f6c4ad
+title: Step 3
+challengeType: 1
+dashedName: step-3
+---
+
+# --description--
+
+To check which loan a user is qualified for based on the `annualIncome` and `creditScore`, you have to use `if/else if` statement or a ternary right inside the `getLoanMessage` function. You'll then return the appropraite message in the block of each condition.
+
+Starting with the duplex loan, check if `annualIncome` is greater than or equal to `minIncomeForDuplex` AND if `creditScore` is greater than `minCreditScoreForDuplex`.
+
+If that condition is true, then the applicant is eligible for a duplex loan and the other loans. So, inside the check, return the string `"You qualify for a car, duplex and Condo loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string.
+
+```js
+assert.isString(getLoanMessage(65000, 750));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a duplex, condo, and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(65000, 750), "You qualify for a duplex, condo, and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a duplex loan.
+
+```js
+assert.strictEqual(getLoanMessage(59000, 700), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+--fcc-editable-region--
+function getLoanMessage(annualIncome, creditScore) {
+
+}
+--fcc-editable-region--
+```
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
new file mode 100644
index 0000000000..638e6291a4
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4af.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4af
+title: Step 4
+challengeType: 1
+dashedName: step-4
+---
+
+# --description--
+
+If the applicant's annual income is greater than or equal to `minIncomeForCondo`, AND if their credit score is greater than or equal to `minCreditScoreForCondo`, then they qualify for a condo and car loan.
+
+Check if that's true in the `getLoanMessage` function. If it is, return the string `"You qualify for a condo and car loan."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a condo and car loan.
+
+```js
+assert.isString(getLoanMessage(45000, 680));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a condo and car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 680), "You qualify for a condo and car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a condo loan.
+
+```js
+assert.strictEqual(getLoanMessage(45000, 650), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
new file mode 100644
index 0000000000..374ba7b8fe
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b0.md
@@ -0,0 +1,56 @@
+---
+id: 66c8ba975ee7230e29f6c4b0
+title: Step 5
+challengeType: 1
+dashedName: step-5
+---
+
+# --description--
+
+Now, you should check if the applicant is qualified for a car loan only. If they're, return the string `"You qualify for a car loan."`.
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant qualifies for a car loan.
+
+```js
+assert.isString(getLoanMessage(30000, 650));
+```
+
+Your `getLoanMessage` function should return the string `"You qualify for a car loan."`.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 650), "You qualify for a car loan.");
+```
+
+Your `getLoanMessage` function should return `undefined` if the applicant's annual income and credit score do not meet the requirements for a car loan.
+
+```js
+assert.strictEqual(getLoanMessage(30000, 600), undefined);
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+--fcc-editable-region--
+  } 
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
new file mode 100644
index 0000000000..16e8c7baca
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b1.md
@@ -0,0 +1,54 @@
+---
+id: 66c8ba975ee7230e29f6c4b1
+title: Step 6
+challengeType: 1
+dashedName: step-6
+---
+
+# --description--
+
+If the applicant's annual income and credit score fall below `minIncomeForCar` and `minCreditScoreForCar`, then they don't qualify for any loan. So, return the string `"You don't qualify for any loans."`
+
+# --hints--
+
+Your `getLoanMessage` function should return a string if the applicant doesn't qualify for any loan.
+
+```js
+assert.isString(getLoanMessage(25000, 550));
+```
+
+Your `getLoanMessage` function should return the string `"You don't qualify for any loans."` if the applicant does not meet the requirements for any loan.
+
+```js
+assert.strictEqual(getLoanMessage(15000, 600), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(25000, 550), "You don't qualify for any loans.");
+assert.strictEqual(getLoanMessage(20000, 500), "You don't qualify for any loans.");
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+--fcc-editable-region--
+  }
+
+--fcc-editable-region--
+}
+```
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
new file mode 100644
index 0000000000..9d19f9ea4c
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-loan-qualification-checker/66c8ba975ee7230e29f6c4b2.md
@@ -0,0 +1,165 @@
+---
+id: 66c8ba975ee7230e29f6c4b2
+title: Step 7
+challengeType: 1
+dashedName: step-7
+---
+
+# --description--
+
+Now, it is time to test out your `getLoanMessage` function.
+
+Use the table below to create `4` variables and their values:
+
+| Variable Name   | Value                        |
+| --------------- | ---------------------------- |
+| `duplexLoanMsg` | `getLoanMessage(85000, 850)` |
+| `condoLoanMsg`  | `getLoanMessage(65000, 690)` |
+| `carLoanMsg`    | `getLoanMessage(45000, 660)` |
+| `noLoanMsg`     | `getLoanMessage(25000, 550)` |
+
+After that, log each variable to the console to see the messages.
+
+With that, your loan qualification checker project is complete!
+
+# --hints--
+
+You should have a variable called `duplexLoanMsg`.
+
+```js
+assert.isNotNull(duplexLoanMsg);
+```
+
+Your `duplexLoanMsg` variable should be set to the result of `getLoanMessage(85000, 850)`.
+
+```js
+assert.equal(duplexLoanMsg, getLoanMessage(85000, 850));
+```
+
+You should log the `duplexLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(duplexLoanMsg\)/)
+```
+
+You should have a variable called `condoLoanMsg`.
+
+```js
+assert.isNotNull(condoLoanMsg);
+```
+
+Your `condoLoanMsg` variable should be set to the result of `getLoanMessage(65000, 690)`.
+
+```js
+assert.equal(condoLoanMsg, getLoanMessage(65000, 690));
+```
+
+You should log the `condoLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(condoLoanMsg\)/)
+```
+
+You should have a variable called `carLoanMsg`.
+
+```js
+assert.isNotNull(carLoanMsg);
+```
+
+Your `carLoanMsg` variable should be set to the result of `getLoanMessage(45000, 660)`.
+
+```js
+assert.equal(carLoanMsg, getLoanMessage(45000, 660));
+```
+
+You should log the `carLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(carLoanMsg\)/)
+```
+
+You should have a variable called `noLoanMsg`.
+
+```js
+assert.isNotNull(noLoanMsg);
+```
+
+Your `noLoanMsg` variable should be set to the result of `getLoanMessage(25000, 550)`.
+
+```js
+assert.equal(noLoanMsg, getLoanMessage(25000, 550));
+```
+
+You should log the `noLoanMsg` variable to the console.
+
+```js
+assert.match(code, /console\.log\(noLoanMsg\)/)
+```
+
+# --seed--
+
+## --seed-contents--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+--fcc-editable-region--
+
+--fcc-editable-region--
+```
+
+# --solutions--
+
+```js
+const minIncomeForDuplex = 60000;
+const minCreditScoreForDuplex = 700;
+
+const minIncomeForCondo = 45000;
+const minCreditScoreForCondo = 680;
+
+const minIncomeForCar = 30000;
+const minCreditScoreForCar = 650;
+
+function getLoanMessage(annualIncome, creditScore) {
+  if(creditScore >= minCreditScoreForDuplex && annualIncome >= minIncomeForDuplex) {
+    return "You qualify for a duplex, condo, and car loan."
+  } else if (annualIncome >= minIncomeForCondo && creditScore >= minCreditScoreForCondo) {
+    return "You qualify for a condo and car loan."
+  } else if (annualIncome >= minIncomeForCar && creditScore >= minCreditScoreForCar) {
+    return "You qualify for a car loan."
+  } else {
+    return "You don't qualify for any loans."
+  }
+}
+
+const duplexLoanMsg = getLoanMessage(85000, 850)
+console.log(duplexLoanMsg)
+
+const condoLoanMsg = getLoanMessage(65000, 690)
+console.log(condoLoanMsg)
+
+const carLoanMsg = getLoanMessage(45000, 660)
+console.log(carLoanMsg)
+
+const noLoanMsg = getLoanMessage(25000, 550)
+console.log(noLoanMsg)
+```
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
new file mode 100644
index 0000000000..4e11751ca0
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-mario-database/5f2c289f164c29556da632fd.md
@@ -0,0 +1,19 @@
+---
+id: 5f2c289f164c29556da632fd
+title: Build a Mario Database
+challengeType: 12
+url: freeCodeCamp/learn-relational-databases-by-building-a-mario-database
+dashedName: build-a-mario-database
+---
+
+# --description--
+
+In this 165-lesson workshop, you will learn the basics of a relational database by creating a PostgreSQL database filled with video game characters.
+
+# --instructions--
+
+# --hints--
+
+# --seed--
+
+# --solutions--
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
new file mode 100644
index 0000000000..8d4c90410d
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfb.md
@@ -0,0 +1,53 @@
+---
+id: 587d7fb3367417b2b2512bfb
+title: How to Use package.json, the Core of Any Node.js Project or npm Package
+challengeType: 2
+forumTopicId: 301528
+dashedName: how-to-use-package-json-the-core-of-any-node-js-project-or-npm-package
+---
+
+# --description--
+
+Working on these challenges will involve you writing your code using one of the following methods:
+
+- Clone <a href="https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">this GitHub repo</a> and complete these challenges locally.
+- Use <a href="https://gitpod.io/?autostart=true#https://github.com/freeCodeCamp/boilerplate-npm/" target="_blank" rel="noopener noreferrer nofollow">our Gitpod starter project</a> to complete these challenges.
+- Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
+
+The `package.json` file is the center of any Node.js project or npm package. It stores information about your project. It consists of a single JSON object where information is stored in key-value pairs. There are only two required fields; `name` and `version`, but it’s good practice to provide additional information.
+
+You can create the `package.json` file from the terminal using the `npm init` command. This will run a guided setup. Using `npm init` with the `-y` flag will generate the file without having it ask any questions, `npm init -y`.
+
+If you look at the file tree of your project, you will find the `package.json` file on the top level of the tree. This is the file that you will be improving in the next couple of challenges.
+
+One of the most common pieces of information in this file is the `author` field. It specifies who created the project, and can consist of a string or an object with contact or other details. An object is recommended for bigger projects, but a simple string like the following example will do for this project.
+
+```json
+"author": "Jane Doe",
+```
+
+# --instructions--
+
+Add your name as the `author` of the project in the `package.json` file.
+
+**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (") and be separated with a comma (,).
+
+If you are using Gitpod, make sure the app is running and the preview window is open. Copy the preview window's URL and paste it into the Solution Link input below.
+
+# --hints--
+
+`package.json` should have a valid "author" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.author, '"author" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
new file mode 100644
index 0000000000..37d15d5261
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb3367417b2b2512bfc.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb3367417b2b2512bfc
+title: Add a Description to Your package.json
+challengeType: 2
+forumTopicId: 301522
+dashedName: add-a-description-to-your-package-json
+---
+
+# --description--
+
+The next part of a good package.json file is the `description` field; where a short, but informative description about your project belongs.
+
+If some day you plan to publish a package to npm, this is the string that should sell your idea to the user when they decide whether to install your package or not. However, that’s not the only use case for the description, it’s a great way to summarize what a project does. It’s just as important in any Node.js project to help other developers, future maintainers or even your future self understand the project quickly.
+
+Regardless of what you plan for your project, a description is definitely recommended. Here's an example:
+
+```json
+"description": "A project that does something awesome",
+```
+
+# --instructions--
+
+Add a `description` to the package.json file of your project.
+
+**Note:** Remember to use double-quotes for field-names (") and commas (,) to separate fields.
+
+# --hints--
+
+package.json should have a valid "description" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.description, '"description" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
new file mode 100644
index 0000000000..a001cdd477
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfd.md
@@ -0,0 +1,75 @@
+---
+id: 587d7fb4367417b2b2512bfd
+title: Add Keywords to Your package.json
+challengeType: 2
+forumTopicId: 301526
+dashedName: add-keywords-to-your-package-json
+---
+
+# --description--
+
+The `keywords` field is where you can describe your project using related keywords. Here's an example:
+
+```json
+"keywords": [ "descriptive", "related", "words" ],
+```
+
+As you can see, this field is structured as an array of double-quoted strings.
+
+# --instructions--
+
+Add an array of suitable strings to the `keywords` field in the package.json file of your project.
+
+One of the keywords should be "freecodecamp".
+
+# --hints--
+
+package.json should have a valid "keywords" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.keywords, '"keywords" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" field should be an Array
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.isArray(packJson.keywords, '"keywords" is not an array');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+"keywords" should include "freecodecamp"
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.include(
+        packJson.keywords,
+        'freecodecamp',
+        '"keywords" does not include "freecodecamp"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
new file mode 100644
index 0000000000..7b09acd042
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bfe.md
@@ -0,0 +1,39 @@
+---
+id: 587d7fb4367417b2b2512bfe
+title: Add a License to Your package.json
+challengeType: 2
+forumTopicId: 301523
+dashedName: add-a-license-to-your-package-json
+---
+
+# --description--
+
+The `license` field is where you inform users of what they are allowed to do with your project.
+
+Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do. Here's an example of the license field:
+
+```json
+"license": "MIT",
+```
+
+# --instructions--
+
+Fill the `license` field in the package.json file of your project as you find suitable.
+
+# --hints--
+
+package.json should have a valid "license" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.license, '"license" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
new file mode 100644
index 0000000000..f2e571faed
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512bff.md
@@ -0,0 +1,37 @@
+---
+id: 587d7fb4367417b2b2512bff
+title: Add a Version to Your package.json
+challengeType: 2
+forumTopicId: 301525
+dashedName: add-a-version-to-your-package-json
+---
+
+# --description--
+
+A `version` is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example:
+
+```json
+"version": "1.2.0",
+```
+
+# --instructions--
+
+Add a `version` to the package.json file of your project.
+
+# --hints--
+
+package.json should have a valid "version" key
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert(packJson.version, '"version" is missing');
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
new file mode 100644
index 0000000000..161c60fe69
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb4367417b2b2512c00.md
@@ -0,0 +1,68 @@
+---
+id: 587d7fb4367417b2b2512c00
+title: Expand Your Project with External Packages from npm
+challengeType: 2
+forumTopicId: 301527
+dashedName: expand-your-project-with-external-packages-from-npm
+---
+
+# --description--
+
+One of the biggest reasons to use a package manager, is their powerful dependency management. Instead of manually having to make sure that you get all dependencies whenever you set up a project on a new computer, npm automatically installs everything for you. But how can npm know exactly what your project needs? Meet the `dependencies` section of your package.json file.
+
+In this section, packages your project requires are stored using the following format:
+
+```json
+"dependencies": {
+  "package-name": "version",
+  "express": "4.14.0"
+}
+
+```
+
+# --instructions--
+
+Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file.
+
+**Note:** `@freecodecamp/example` is a faux package used as a learning tool.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.1.0"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^[\^\~]?1\.1\.0/,
+        'Wrong version of "@freecodecamp/example" installed. It should be 1.1.0'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
new file mode 100644
index 0000000000..deda9b82de
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c01.md
@@ -0,0 +1,64 @@
+---
+id: 587d7fb5367417b2b2512c01
+title: Manage npm Dependencies By Understanding Semantic Versioning
+challengeType: 2
+forumTopicId: 301529
+dashedName: manage-npm-dependencies-by-understanding-semantic-versioning
+---
+
+# --description--
+
+`Versions` of the npm packages in the dependencies section of your package.json file follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes projects can expect if they update.
+
+Knowing SemVer can be useful when you develop software that uses external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things that worked yesterday suddenly don’t work today. This is how Semantic Versioning works according to the official website:
+
+```json
+"package": "MAJOR.MINOR.PATCH"
+```
+
+The MAJOR version should increment when you make incompatible API changes. The MINOR version should increment when you add functionality in a backwards-compatible manner. The PATCH version should increment when you make backwards-compatible bug fixes. This means that PATCHes are bug fixes and MINORs add new features but neither of them break what worked before. Finally, MAJORs add changes that won’t work with earlier versions.
+
+# --instructions--
+
+In the dependencies section of your `package.json` file, change the version of `@freecodecamp/example` to match MAJOR version 1, MINOR version 2 and PATCH version 13
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should be `"1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.equal(
+        packJson.dependencies["@freecodecamp/example"],
+        '1.2.13',
+        'Wrong version of "@freecodecamp/example". It should be 1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
new file mode 100644
index 0000000000..8eae5f51ee
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c02.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c02
+title: Use the Tilde-Character to Always Use the Latest Patch Version of a Dependency
+challengeType: 2
+forumTopicId: 301532
+dashedName: use-the-tilde-character-to-always-use-the-latest-patch-version-of-a-dependency
+---
+
+# --description--
+
+In the last challenge, you told npm to only include a specific version of a package. That’s a useful way to freeze your dependencies if you need to make sure that different parts of your project stay compatible with each other. But in most use cases, you don’t want to miss bug fixes since they often include important security patches and (hopefully) don’t break things in doing so.
+
+To allow an npm dependency to update to the latest PATCH version, you can prefix the dependency’s version with the tilde (`~`) character. Here's an example of how to allow updates to any `1.3.x` version.
+
+```json
+"package": "~1.3.8"
+```
+
+# --instructions--
+
+In the package.json file, your current rule for how npm may upgrade `@freecodecamp/example` is to use a specific version (`1.2.13`). But now, you want to allow the latest `1.2.x` version.
+
+Use the tilde (`~`) character to prefix the version of `@freecodecamp/example` in your dependencies, and allow npm to update it to any new _patch_ release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"~1.2.13"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\~1\.2\.13/,
+        'Wrong version of "@freecodecamp/example". It should be ~1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
new file mode 100644
index 0000000000..adc3014ea4
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c03.md
@@ -0,0 +1,66 @@
+---
+id: 587d7fb5367417b2b2512c03
+title: Use the Caret-Character to Use the Latest Minor Version of a Dependency
+challengeType: 2
+forumTopicId: 301531
+dashedName: use-the-caret-character-to-use-the-latest-minor-version-of-a-dependency
+---
+
+# --description--
+
+Similar to how the tilde we learned about in the last challenge allows npm to install the latest PATCH for a dependency, the caret (`^`) allows npm to install future updates as well. The difference is that the caret will allow both MINOR updates and PATCHes.
+
+Your current version of `@freecodecamp/example` should be `~1.2.13` which allows npm to install to the latest `1.2.x` version. If you were to use the caret (^) as a version prefix instead, npm would be allowed to update to any `1.x.x` version.
+
+```json
+"package": "^1.3.8"
+```
+
+This would allow updates to any `1.x.x` version of the package.
+
+# --instructions--
+
+Use the caret (`^`) to prefix the version of `@freecodecamp/example` in your dependencies and allow npm to update it to any new MINOR release.
+
+**Note:** The version numbers themselves should not be changed.
+
+# --hints--
+
+`"dependencies"` should include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.property(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" does not include "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
+`"@freecodecamp/example"` version should match `"^1.x.x"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.match(
+        packJson.dependencies["@freecodecamp/example"],
+        /^\^1\./,
+        'Wrong version of "@freecodecamp/example". It should be ^1.2.13'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+
diff --git a/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
new file mode 100644
index 0000000000..5f695eed88
--- /dev/null
+++ b/curriculum/challenges/ukrainian/25-front-end-development/workshop-npm-packages/587d7fb5367417b2b2512c04.md
@@ -0,0 +1,43 @@
+---
+id: 587d7fb5367417b2b2512c04
+title: Remove a Package from Your Dependencies
+challengeType: 2
+forumTopicId: 301530
+dashedName: remove-a-package-from-your-dependencies
+---
+
+# --description--
+
+You have now tested a few ways you can manage dependencies of your project by using the package.json's dependencies section. You have also included external packages by adding them to the file and even told npm what types of versions you want, by using special characters such as the tilde or the caret.
+
+But what if you want to remove an external package that you no longer need? You might already have guessed it, just remove the corresponding key-value pair for that package from your dependencies.
+
+This same method applies to removing other fields in your package.json as well.
+
+# --instructions--
+
+Remove the `@freecodecamp/example` package from your dependencies.
+
+**Note:** Make sure you have the right amount of commas after removing it.
+
+# --hints--
+
+`"dependencies"` should not include `"@freecodecamp/example"`.
+
+```js
+(getUserInput) =>
+  $.get(getUserInput('url') + '/_api/package.json').then(
+    (data) => {
+      var packJson = JSON.parse(data);
+      assert.notProperty(
+        packJson.dependencies,
+        '@freecodecamp/example',
+        '"dependencies" still includes "@freecodecamp/example"'
+      );
+    },
+    (xhr) => {
+      throw new Error(xhr.responseText);
+    }
+  );
+```
+