## Description 

There's a confusing bit of documentation to follow on the pages "Write a
move package" and "Build and Test packages".

On the instructions to "Write a move package", it states to create a
file called my_module.move. However, in the source code it is referenced
as example.move.

<img width="1038" alt="image"
src="https://github.com/user-attachments/assets/bbb4525c-e6f4-40ec-bb8f-38047c5a74bc"
/>

This can confuse the reader of the document as later on in the "Build
and Test packages" section, that same file is referenced as example.move

<img width="1038" alt="image"
src="https://github.com/user-attachments/assets/abe801a7-47c5-44f9-bf42-653ac225bf98"
/>

I have renamed the my_module references to example for a consistent user
experience.
## Test plan 

I changed the my_module.move markdown to example.move.

---

## Release notes

Check each box that your changes affect. If none of the boxes relate to
your changes, release notes aren't required.

For each box you select, include information after the relevant heading
that describes the impact of your changes that a user might notice and
any actions they must take to implement updates.

- [ ] Protocol: 
- [ ] Nodes (Validators and Full nodes): 
- [ ] gRPC:
- [ ] JSON-RPC: 
- [ ] GraphQL: 
- [ ] CLI: 
- [ ] Rust SDK:

Co-authored-by: Nick Sulistio <nicksulistio@Nicks-MacBook-Pro.local>