Typo Fix

[mmvergara]

I got lazy sorry,

[realstealthninja]

Please do follow the pull request description given to you as it makes it easier for us to review

[realstealthninja]

Nice spotting the typo!

[Panquesito7]

Cool! Thanks. 🎉

[Panquesito7]

Looks like the whole file will need updating to our guidelines, as the CI is complaining about it.
Would you like to work on this, @mmvergara, or create an issue for the same?

[mmvergara]

Looks like the whole file will need updating to our guidelines, as the CI is complaining about it. Would you like to work on this, @mmvergara, or create an issue for the same?

i'd like to work on it but sorry i don't really know how CI works, im kinda new to github. i might ruin something.

[realstealthninja]

Looks like the whole file will need updating to our guidelines, as the CI is complaining about it. Would you like to work on this, @mmvergara, or create an issue for the same?

i'd like to work on it but sorry i don't really know how CI works, im kinda new to github. i might ruin something.

no no he is asking you to fix the whole file and make it look better.
ie documenting code

[mmvergara]

What did i just do lol, sorry i really don't know how the flow in these PR's work 💀

[realstealthninja]

you merged your pr with the main branch! i.e update your pull request so its up to date

[realstealthninja]

when we mean fix the algorithm we mean is document and comment on the algorithm
make it neat and understandable.
try reading the contribution guidelines

[Panquesito7]

1. Please use climits instead of limits.h.
2. Do not use using namespace std. Use using <function> (such as std::cout) or directly their namespace name.
3. Make sure to provide documentation and explanation of the algorithm, author, links, and self-test implementations.

If you need any help with this, let us know! 🙂

[mmvergara]

1. Please use climits instead of limits.h.
2. Do not use using namespace std. Use using <function> (such as std::cout) or directly their namespace name.
3. Make sure to provide documentation and explanation of the algorithm, author, links, and self-test implementations.

If you need any help with this, let us know! 🙂

aight yeah. can someone actually finish this PR for me, sorry i'm not so used to github or C++ or this algorithm (yet).

[Panquesito7]

I'll work on this in the next few days. Thank you for contributing. 🙂