I think at least part of both this challenge and the Add-KeyValue-Pairs challenge should be converted into intro sections. There is a lot of text on these challenges and most of it doesn't actually have to do with the challenge exercise. Could this be split into a challenge and an intro like this?

cc @freeCodeCamp/moderators Thoughts?

I agree with you @dhcodes , this is a bit wordy IMHO.

@dhcodes @raisedadead I think that's an excellent idea and was def getting concerned with the wordiness of it all. If this is an option, I'd gladly do it. I think the information is important, and adds context to the section (otherwise they just become more object and array challenges).

Only the most dedicated campers will probably end up reading it, but hey, at least no one can say we didn't provide the info

This looks good to me!

@no-stack-dub-sack - with the intro done for this section, this PR can close out #12629, too 👍

@HKuz awesome, thanks! Was actually going to go look and see if you had opened one for this section. Perfect! I just added that to the PR text

Ok, consulted w/ @bonham000 and made just a few more edits. @bonham000 if you want to take a look at this PR, let me know what you think. Based on @dhcodes & @raisedadead's suggestion I've modified to add an intro challenge to each section.

For the object section, I pulled the intro material from the first 2 challenges. I don't think this compromises the integrity of either challenge as I repeated the info much more succinctly there.

@raisedadead Same question on this one - once #12720 is merged, will I need to rebase and force update this branch for the all of these changes to merge smoothly? Thanks! You've been a huge help to me lately

Yes, @no-stack-dub-sack and on that note may be the other PR #12720 can be taken up later. In which case we should merge this in and rebase that, which we are going to do in any case as it has conflicts.

Thanks and happy to help!

@dhcodes ok, so I made all the changes you mentioned except for one - see last "outdated" comment above. So I think this should be good. And, you pointing out a few typos gave me a strong hunch that there would be more, so I spellchecked the whole thing and caught several additional typos.

If you and @raisedadead are ok with all of this, I think this section should be in pretty sound shape!

✨ ✨ LGTM. ✨ ✨

Thanks @no-stack-dub-sack

@dhcodes please have a look and merge.

@dhcodes haha, no worries, nice catch yet again, better to get this right! All set

LGTM 👍 💯 🌮 Thanks for all the changes.