Skip to content
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

Minor Corrections and Improvements for SoundScape Description #60

Closed
kvdevlopment opened this issue May 13, 2024 · 6 comments · May be fixed by #102
Closed

Minor Corrections and Improvements for SoundScape Description #60

kvdevlopment opened this issue May 13, 2024 · 6 comments · May be fixed by #102
Assignees
Labels
good first issue Good for newcomers gssoc

Comments

@kvdevlopment
Copy link

Description:
The current description of SoundScape provides a comprehensive overview of the project, detailing its functionality, visualizers, usage, contribution guidelines, and references. However, there are a couple of minor corrections and improvements that could enhance its clarity and consistency.

Spectogram Spelling: The term "Spectogram" should be corrected to "Spectrogram" for accuracy.

Visualizer Title Clarification: The title "Frequency v/s Amplitude" could be clarified for better understanding and consistency. It can be rephrased as "Frequency vs. Amplitude" or "Frequency versus Amplitude."

**You can refer the mistake here **
2024-05-14 03_18_40-
2024-05-14 03_19_32-Window

@kvdevlopment
Copy link
Author

Hello @Soumya-Kushwaha
Can you please assign me this issue.

@Jhalak-Gupta
Copy link

I am interested in this task. Pls assign it to me under GSSOC'24 so that I can contribute to this project. I am good enough at my skills to complete this task efficiently.

@RohanJobanputra
Copy link

Hello! i would like to work on this, please assign me.

@RohanJobanputra
Copy link

Hello! i can still notice the unchanged errors in README file, spectogram and v/s precisely. I would request you to assign me the task. Thank You!

@why-Radhika
Copy link

I have made the necessary changes and have created a pull request. Could you please assign this issue to me so that the PR can be merged?

@JyotikaJayani-08
Copy link

#103 Please review the changes and approve.

@Soumya-Kushwaha Soumya-Kushwaha closed this as not planned Won't fix, can't repro, duplicate, stale Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers gssoc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants