docs: fix typo in max term definition (product → sum)

[bhavish00007]

Fixes #723

Changes done:

• Corrected the definition of max term in canonical.md (Line 174)
  • Changed "product of n variables" → "sum of n variables"
  • This aligns with standard logic design terminology.

Screenshots

Not applicable (documentation-only change)

Preview Link(s):

Interactive Book → Logic Design → Canonical Forms

✅️ By submitting this PR, I have verified the following

• Checked to see if a similar PR has already been opened 🤔️
• Reviewed the contributing guidelines 🔍️
• Sample preview link added (see above)
• Tried Squashing the commits into one.

Thank You

Summary by CodeRabbit

• Documentation
  • Corrected the Maxterms definition in the canonical forms guide to state it is the sum of n variables (not the product).
  • Ensures terminology aligns with standard logic design conventions.
  • Clarifies content for readers; examples remain unchanged.
  • No impact on application behavior or features.

[coderabbitai]

Walkthrough

Corrects a definition in docs/logic-design/canonical.md: updates the Maxterms description from “product of n variables” to “sum of n variables.” No other sections or examples were changed.

Changes

Cohort / File(s)	Summary of Changes
Docs correction docs/logic-design/canonical.md	Fixed Maxterms definition: changed “product of n variables” to “sum of n variables”; no other modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks (5 passed)

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly describes the correction of a typo in the max term definition by indicating a change from “product” to “sum,” clearly reflecting the primary documentation update in the pull request.
Linked Issues Check	✅ Passed	The pull request precisely updates docs/logic-design/canonical.md by replacing “product of n variables” with “sum of n variables,” directly fulfilling the requirement of issue #723 to correct the max term definition.
Out of Scope Changes Check	✅ Passed	The changes are confined to a single documentation file (canonical.md) correcting the specified typo, with no unrelated modifications to other files or code, so there are no out-of-scope changes.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/logic-design/canonical.md (1)

174-174: Switch bold style to underscores and tighten wording (markdownlint MD050).

Adopt underscores for strong emphasis and clarify the “i” range.

Apply this diff:

-A max term is defined as the sum of n variables, within the range of 0 ≤ i < 2<sup>n</sup>. The max term is denoted as Mi. In max term, each variable is **complemented**, if its value is assigned to 1, and each variable is **un-complemented** if its value is assigned to 0.
+A max term is defined as the sum of n variables, where i is in the range 0 ≤ i < 2<sup>n</sup>. The max term is denoted as Mi. In a max term, each variable is __complemented__ if its value is assigned to 1, and each variable is __uncomplemented__ if its value is assigned to 0.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0537824 and 388cdc3.

📒 Files selected for processing (1)

• docs/logic-design/canonical.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

docs/logic-design/canonical.md

174-174: Strong style
Expected: underscore; Actual: asterisk

(MD050, strong-style)

---

174-174: Strong style
Expected: underscore; Actual: asterisk

(MD050, strong-style)

---

174-174: Strong style
Expected: underscore; Actual: asterisk

(MD050, strong-style)

---

174-174: Strong style
Expected: underscore; Actual: asterisk

(MD050, strong-style)

🔇 Additional comments (1)

docs/logic-design/canonical.md (1)

174-174: Correct fix: Maxterm is a sum (not a product).

The change aligns with standard logic design terminology.