Skip to content

docs: fix faq

docs: fix faq #191