How Zapiekanka researches, reviews, and corrects its Polish guides.

Editorial priorities

• Answer the learner's question before promoting the app.
• Use accurate grammatical terms, explain them clearly, and avoid both unexplained jargon and childish simplification.
• Keep sentences concise and connect examples that illustrate the same point.
• Explain meaning and sentence function before presenting large ending tables.
• Show contrasts where more than one form is possible.
• State limitations instead of presenting tendencies as universal rules.
• Keep articles accessible without requiring an account.

Publication and review responsibility

Zapiekanka is the organizational publisher and author of its public learning guides. It is responsible for topic selection, research, English-language structure, technical implementation, publication, and corrections.

Aleksandra Adamska, philologist, reviews the Polish-language explanations and examples credited to her. Review attribution is separate from product ownership and does not extend to unreviewed audio or changing product claims.

Source hierarchy

A citation supports the factual claim drawn from it; it does not transfer authority to unrelated examples or marketing claims.

Polish-language review labels

Use of AI assistance

AI tools may assist with research organization, first-draft structure, code, consistency checks, tables, and alternative explanations. AI output is not treated as a linguistic authority or a substitute for a qualified human reviewer.

Polish examples produced or transformed with AI remain subject to source checking, automated audits, and the visible human-review status. The site should not describe AI-generated speech as a native recording.

• No invented reviewer identities, credentials, quotations, or learner testimonials.
• No citations to sources that do not support the associated claim.
• No silent replacement of uncertainty with absolute wording.
• No claim that an AI system has completed independent native-speaker review.

Examples, translations, and alternatives

Examples are written for a stated learner meaning and should sound plausible in the given context. A translation is an explanation of that use, not a claim that the two sentences match in every context.

When Polish allows alternatives, the guide should explain the difference in meaning, aspect, emphasis, politeness, or register instead of presenting one answer as universally exclusive.

Audio policy

Corrections and update dates

Readers can report errors at [email protected]. Reports should include the URL, exact text, proposed correction, and reasoning or source when available.

Substantive corrections update the page's visible modified date, sitemap date, and Article structured data. Styling-only changes do not need to imply that the linguistic content was re-reviewed.

Commercial boundaries

• A guide should remain useful if the reader never creates an account.
• Product comparisons describe learning jobs and limitations rather than declaring a universal winner.
• Pricing and access claims must match the current product or be omitted.
• Affiliate relationships or paid placements must be disclosed near the relevant recommendation.
• App calls to action must not interrupt access to the article's core answer.

Accessibility and user experience

• Use real heading hierarchy, table captions, semantic links, and keyboard-accessible controls.
• Keep long guides navigable with a table of contents and stable anchors.
• Allow tables to scroll without forcing the whole page to overflow.
• Do not make audio the only way to access an example.
• Use descriptive link text instead of raw paths or vague repeated calls to click.