The file forca.py isn't complete, it's missing some points:

• Words can't be fixed, in 'Forca' game they have to change every time the game starts.
• the logic :)

At first, we need to add all the files done till this point..

Let the games begin!!

In order to make a clearer code, readme can contain sources and more information about this project.
Here is some example, don't need to be the same:

• Project Description: Give a brief overview of what your project is about. Explain its purpose, goals, and any problems it solves.

• Installation: Provide clear instructions on how to install and set up your project. Include any dependencies, libraries, or frameworks required.

• Usage: Explain how to use your project. Provide examples, code snippets, and screenshots if possible. Cover common use cases and provide command-line examples if applicable.

• Configuration: If your project has configuration options, APIs, or settings, explain how to configure and customize these aspects.

• Features: List the key features of your project. This helps users quickly understand what your project offers.

• Documentation: Link to any external documentation, user guides, or tutorials that provide more in-depth information.

• Contributing: If your project is open source and you want to encourage contributions, provide guidelines for how others can contribute, including code style, issue reporting, and pull request processes.

• License: Clearly state the license under which your project is released. This informs users about how they can use and distribute your project.

• Changelog: Provide a history of changes, updates, and bug fixes in your project over time. This helps users understand the development progress.

• Contact Information: Provide a way for users to contact you, whether it's through email, social media, or a dedicated issue tracker.

• Credits: Give credit to any individuals or resources that have contributed to your project, such as libraries, inspiration, or artwork.

• Troubleshooting: Include a section with common issues users might face and solutions to those issues.

• Roadmap: Outline your future plans for the project. This can help users and contributors understand where your project is headed.

• Badges: Include badges for build status, code coverage, documentation status, and more. These give a quick overview of the project's health.

• Examples: Include real-world examples of your project in action, if applicable. This can help users visualize how they might use it.

Organize the code:

• split into functions;

In order to look and feel like a game, we should improve the game display. (even if we're playing in terminal)