(Feat) About us page and fixed typo

[Fagerdahl]

Pull Request Type

Please check the type of change your PR introduces:

• Feature (a new feature for the project)
• Fix (a bug fix)
• Chore (updating grunt tasks etc; no production code change)
• Refactor (refactoring production code)
• Docs (changes to the documentation)
• Style (formatting, missing semi colons, etc; no production code change)
• Test (adding missing tests, refactoring tests; no production code change)

Description

[I have done an about us page]

Motivation and Context

[Why is this change required? What problem does it solve?]

How Has This Been Tested?

[Describe the tests that you ran to verify your changes]

Screenshots (if appropriate):

[]

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have named this PR according to following naming convention: #[issue-number] PR description

Additional Information:

[Add any other information about the PR here]

Related Issues:

[Link any related issues here]

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
kino-next-js	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 3, 2025 7:05pm