Skip to content

Typo in Code Snippet (ordeded_map instead of ordered_map) #949

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
harshbhatt18 opened this issue May 15, 2025 · 2 comments · May be fixed by #950
Closed

Typo in Code Snippet (ordeded_map instead of ordered_map) #949

harshbhatt18 opened this issue May 15, 2025 · 2 comments · May be fixed by #950
Labels
documentation Improvements or additions to documentation move-and-smart-contracts All content under https://aptos.dev/en/build/smart-contracts

Comments

@harshbhatt18
Copy link

Url

https://aptos.dev/en/build/smart-contracts/maps

Describe the content issue

There is a misspelled word in the code snippet within the main function of the 0x42::map_usage module.

use aptos_framework::ordered_map;
let map = ordeded_map::new<u64, u64>();

correct version:

let map = ordered_map::new<u64, u64>();

However, the instantiation uses ordeded_map, which leads to a compilation error due to the typo.

Section

move-and-smart-contracts

@harshbhatt18 harshbhatt18 added the documentation Improvements or additions to documentation label May 15, 2025
@github-actions github-actions bot added the move-and-smart-contracts All content under https://aptos.dev/en/build/smart-contracts label May 15, 2025
Copy link

@aptos-labs/move-eng

jmintuitive added a commit that referenced this issue May 15, 2025
@jmintuitive
Copy link
Collaborator

Created #950 to resolve, thanks for the report! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation move-and-smart-contracts All content under https://aptos.dev/en/build/smart-contracts
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants