Documentation Typo Fixes for Motoko Base Library Design Guide

[joaolago1113]

Overview

This pull request addresses several typographical errors in the Motoko Base Library's design documentation. Ensuring accuracy and clarity in our documentation is vital for effective communication among developers and for maintaining the high standard of our project.

Changes Made

• Corrected 'encapsultion' to 'encapsulation' in the Classes section. This change clarifies the intended meaning, emphasizing the importance of encapsulation in abstract data types.
• Updated 'valus' to 'values' in the Containers section under the description of the keys iterator. This fix ensures that the documentation accurately represents the functionality of the iterator.
• Fixed 'distinghuish' to 'distinguish' in the Containers section. This modification aids in presenting a clearer rationale for the choice of the put method name over set, especially in the context of sets and other containers.

Impact

These changes, while minor, contribute to the overall readability and professionalism of our documentation. They do not affect the actual functionality of the codebase but are essential for consistent and error-free documentation.

Additional Notes

While reviewing the documentation, I've noticed a few areas where further clarification might be beneficial. I plan to propose additional updates in subsequent pull requests to continuously improve the documentation.

[sa-github-api]

Dear @joaolago1113,

In order to potentially merge your code in this open-source repository and therefore proceed with your contribution, we need to have your approval on DFINITY's CLA.

If you decide to agree with it, please visit this issue and read the instructions there. Once you have signed it, re-trigger the workflow on this PR to see if your code can be merged.

— The DFINITY Foundation

[ggreif]

Obrigado pelas correções! Infelizmente estamos péssimos com a linguagem natural 😜

[joaolago1113]

@ggreif Obrigado! Sempre pronto para mais uma ronda de bug fixing, seja no código ou na língua! 😄🔍

[ggreif]

@joaolago1113 Colega já fechou este, se vc. achar mais, seja convidado de abrir um outro. Obrigado de novo!