Skip to content

fix: corrected faq

fix: corrected faq #28