[
  {
    "slug": "accessible-mathematics-notation-reference",
    "title": "Accessible Mathematics: Notation Reference",
    "description": "Notation Reference for accessible mathematics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Accessible Mathematics",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nNotation Reference for accessible mathematics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation. Prefer real text, MathML, or a native equation object over a screenshot whenever the destination supports structured mathematics.\n\n## Choose the source representation\n\n| Source | Strength | Limitation |\n|---|---|---|\n| Unicode | Selectable and searchable for isolated characters | Cannot express every nested equation structure |\n| LaTeX | Compact editable authoring source | Accessibility depends on the renderer and destination |\n| MathML | Explicit semantic structure for web mathematics | Verbose to author by hand |\n| Image | Broad visual compatibility | Requires alternative text and loses editability |\n\n## Write useful alternative text\n\nDescribe the equation\u0027s purpose, main relationship, and conditions. Do not mechanically list every punctuation mark unless the exact linear reading is essential. For a simple expression, a concise spoken form may be enough. For a complex derivation, provide a nearby text explanation and the editable source.\n\n## Test the real output\n\nUse keyboard navigation, browser zoom, high contrast, text selection, copy and paste, and at least one screen-reader workflow available to the publishing team. Export to PDF when relevant, reopen the file, and verify that equations remain tagged or otherwise understandable.\n\n## Common failures\n\n- An image has alt text such as \u201Cequation\u201D with no mathematical meaning.\n- Visual order and reading order differ.\n- A renderer exposes raw LaTeX without an understandable alternative.\n- Color, position, or font style is the only cue that distinguishes objects.\n- The mobile layout clips a wide equation without a usable scroll or reflow strategy.\n\n## Publishing checklist\n\nKeep the source, rendered form, and plain-language explanation together during review. Confirm focus order, labels, contrast, zoom behavior, copy output, and the fallback shown when JavaScript is unavailable.\n## Test the accessible representation\n\nFor **accessible mathematics notation reference**, keep the visual equation and its semantic or textual alternative synchronized. Read the alternative without looking at the equation: it should preserve the relation, grouping, bounds, scripts, and variable names rather than listing isolated symbols.\n\n## Verification sequence\n\n1. Navigate to the equation using only the keyboard.\n2. Inspect the accessible name or MathML tree.\n3. Listen with at least one screen-reader and browser combination available to the publishing team.\n4. Recheck after conversion to PDF, image, presentation, or another content system.\n\n## When an image is unavoidable\n\nRetain the editable source, provide a concise alternative for simple expressions, and add a longer adjacent explanation for equations whose structure cannot be expressed clearly in a short alt attribute.\n"
  },
  {
    "slug": "approximately-equal-vs-equal",
    "title": "Approximately Equal vs Equal",
    "description": "Know when to use \u2248, =, \u2261, and other relation symbols.",
    "topic": "Comparisons",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nUse \u0060=\u0060 when two expressions have exactly the same value under the stated definitions. Use \u0060\u2248\u0060 when a value is rounded, estimated, measured with limited precision, or produced by an approximation method.\n\n## Meaning of equals\n\nThe equals sign states an exact equality. For example, \u00602\u002B3=5\u0060 and \u0060\\sin^2 x\u002B\\cos^2 x=1\u0060 are exact identities in their stated domains. Do not use \u0060=\u0060 merely because two displayed decimals look similar after rounding.\n\n## Meaning of approximately equal\n\nThe approximately equal sign indicates that two values are close enough for the current purpose but not necessarily identical. For example, \u0060\\pi\\approx3.14159\u0060 records a decimal approximation of an irrational constant.\n\n## Choose the correct relation\n\n| Situation | Recommended sign | Reason |\n|---|---|---|\n| Exact algebraic identity | \u0060=\u0060 | Both sides are mathematically identical |\n| Rounded decimal | \u0060\u2248\u0060 | Digits were truncated or rounded |\n| Measurement | \u0060\u2248\u0060 | Measurement uncertainty limits precision |\n| Numerical method output | \u0060\u2248\u0060 | The computed value approximates an exact solution |\n\n## Worked examples\n\nWrite \u00601/3 = 0.333\u2026\u0060 when the repeating decimal is shown exactly. Write \u00601/3 \u2248 0.333\u0060 when the value is rounded to three decimal places. A calculator display does not automatically justify equality; the notation must reflect the precision represented.\n\n## Common mistakes\n\nDo not replace \u0060\u2248\u0060 with \u0060=\u0060 in a derivation unless the approximation error is zero. Do not use \u0060\u2248\u0060 for definitions; use a definition symbol or explanatory text when introducing notation. Avoid visually similar characters such as \u0060~\u0060 unless the field explicitly defines them.\n\n## Verification checklist\n\nCheck whether any rounding, measurement, truncation, model simplification, or numerical approximation occurred. State the precision or error tolerance when it affects interpretation. Verify the Unicode character and use \u0060\\approx\u0060 in LaTeX.\n## Make the choice from the surrounding expression\n\nFor **approximately equal vs equal**, do not decide from glyph shape alone. Read the operands, the mathematical subject, and the sentence around the notation. The same mark can represent different ideas in algebra, probability, set theory, analysis, or typography.\n\n## Verification questions\n\n1. Does the proposed meaning produce a mathematically valid sentence?\n2. Are the operands the right type for that meaning?\n3. Does a nearby definition or legend establish a local convention?\n4. Would replacing the mark with words preserve the intended statement?\n\n## Publishing check\n\nUse the exact Unicode character or structured command, then inspect the final PDF, page, or presentation at normal and enlarged zoom. A font substitution can make distinct characters look similar even when their encoded identities differ.\n"
  },
  {
    "slug": "dot-product-cross-product-guide",
    "title": "Dot Product vs Cross Product",
    "description": "Compare dot and cross products by output type, geometry, coordinate formulas, units, and common applications in mathematics and physics.",
    "topic": "Linear algebra",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nThe dot product of two vectors returns a scalar. The cross product, in three-dimensional Euclidean space, returns a vector perpendicular to both inputs.\n\n## Dot product\n\nFor vectors \u0060a\u0060 and \u0060b\u0060, the dot product can be written \u0060a\\cdot b=\\|a\\|\\|b\\|\\cos\\theta\u0060. In coordinates, multiply corresponding components and add them. It is useful for angles, projections, orthogonality, and work.\n\n## Cross product\n\nFor three-dimensional vectors, \u0060a\\times b\u0060 is perpendicular to the plane containing \u0060a\u0060 and \u0060b\u0060. Its magnitude is \u0060\\|a\\|\\|b\\|\\sin\\theta\u0060, and its direction follows the chosen orientation or right-hand rule.\n\n## Compare the outputs\n\n| Operation | Output | Zero condition | Common use |\n|---|---|---|---|\n| Dot product | Scalar | Perpendicular vectors | Angle, projection, work |\n| Cross product | Vector | Parallel vectors or a zero vector | Normal vector, torque, oriented area |\n\n## Worked example\n\nLet \u0060a=(1,0,0)\u0060 and \u0060b=(0,1,0)\u0060. Then \u0060a\\cdot b=0\u0060, showing that the vectors are perpendicular. Their cross product is \u0060a\\times b=(0,0,1)\u0060, a unit vector perpendicular to both.\n\n## Common mistakes\n\nDo not use a multiplication dot when a scalar product is not defined. Do not treat the cross product as commutative: \u0060a\\times b=-(b\\times a)\u0060. State the coordinate system and orientation when direction matters.\n\n## Verification checklist\n\nCheck the output type first. For a dot product, verify the result is scalar and test orthogonality. For a cross product, verify perpendicularity by taking dot products with both inputs and compare the magnitude with the parallelogram area.\n## Make the choice from the surrounding expression\n\nFor **dot product cross product guide**, do not decide from glyph shape alone. Read the operands, the mathematical subject, and the sentence around the notation. The same mark can represent different ideas in algebra, probability, set theory, analysis, or typography.\n\n## Verification questions\n\n1. Does the proposed meaning produce a mathematically valid sentence?\n2. Are the operands the right type for that meaning?\n3. Does a nearby definition or legend establish a local convention?\n4. Would replacing the mark with words preserve the intended statement?\n\n## Publishing check\n\nUse the exact Unicode character or structured command, then inspect the final PDF, page, or presentation at normal and enlarged zoom. A font substitution can make distinct characters look similar even when their encoded identities differ.\n"
  },
  {
    "slug": "dot-product-vs-multiplication-dot",
    "title": "Dot Product vs Multiplication Dot",
    "description": "Understand how context distinguishes scalar multiplication, dot products, and decimal dots.",
    "topic": "Comparisons",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nThe centered dot can denote ordinary multiplication or a vector dot product. The surrounding operands and the local definition determine its meaning.\n\n## Multiplication dot\n\nIn arithmetic and algebra, \u0060a\\cdot b\u0060 means multiplication and returns the same kind of scalar quantity produced by the multiplication operation.\n\n## Vector dot product\n\nFor vectors, \u0060\\mathbf{a}\\cdot\\mathbf{b}\u0060 denotes an inner product and returns a scalar. Typography such as bold vectors helps distinguish the operands from ordinary scalars.\n\n## Compare the contexts\n\n| Expression | Likely meaning | Output |\n|---|---|---|\n| \u00603\\cdot4\u0060 | Scalar multiplication | Scalar |\n| \u0060\\mathbf{a}\\cdot\\mathbf{b}\u0060 | Dot product | Scalar |\n| \u0060A\\cdot B\u0060 | Context-dependent | Must be defined |\n\n## Worked example\n\n\u0060(1,2)\\cdot(3,4)=11\u0060 is a vector dot product. By contrast, \u00602\\cdot5=10\u0060 is ordinary multiplication. The same glyph does not make the operations identical.\n\n## Common mistakes\n\nDo not infer the operation from the dot alone. Define vector typography, spaces, matrices, or abstract inner products before use. Do not confuse the dot product with the cross product or element-wise multiplication.\n\n## Verification checklist\n\nIdentify the operand types and expected output type. Check the definition used in the document, then verify the calculation using coordinates or the stated algebraic rule.\n## Make the choice from the surrounding expression\n\nFor **dot product vs multiplication dot**, do not decide from glyph shape alone. Read the operands, the mathematical subject, and the sentence around the notation. The same mark can represent different ideas in algebra, probability, set theory, analysis, or typography.\n\n## Verification questions\n\n1. Does the proposed meaning produce a mathematically valid sentence?\n2. Are the operands the right type for that meaning?\n3. Does a nearby definition or legend establish a local convention?\n4. Would replacing the mark with words preserve the intended statement?\n\n## Publishing check\n\nUse the exact Unicode character or structured command, then inspect the final PDF, page, or presentation at normal and enlarged zoom. A font substitution can make distinct characters look similar even when their encoded identities differ.\n"
  },
  {
    "slug": "equation-copy-paste-troubleshooting",
    "title": "Equation Copy-and-Paste Troubleshooting",
    "description": "Diagnose broken minus signs, missing fonts, flattened equations, escaped backslashes, and damaged scripts after copying notation.",
    "topic": "Troubleshooting",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Identify what was copied\n\nBefore fixing a broken equation, determine whether the source was Unicode text, LaTeX source, MathML, an equation object, or an image. Copying between applications fails when the destination does not understand the original representation.\n\nA line such as \u0060x^2 \u002B y^2 = r^2\u0060 is plain text. The source \u0060\\frac{a}{b}\u0060 is LaTeX. A Word equation is an application object even when it displays familiar characters.\n\n## Match the symptom to the cause\n\n| Symptom | Likely cause | First fix |\n|---|---|---|\n| Backslashes appear literally | LaTeX pasted into plain text | Use a LaTeX-enabled field or render before export |\n| Square boxes replace symbols | Missing font glyphs | Use a Unicode math font or a different output format |\n| Fractions become \u0060a/b\u0060 | Structure was flattened | Paste the equation source or rebuild in an equation editor |\n| Superscripts return to the baseline | Rich formatting was stripped | Use structured math or explicit Unicode only for simple powers |\n| Characters change after PDF copy | PDF font mapping or reading order | Copy from the editable source instead of the PDF |\n\n## Recover LaTeX source\n\nIf the destination supports LaTeX, paste only the expression source and use the correct delimiters:\n\n\u0060\u0060\u0060latex\nInline: $E=mc^2$\nDisplay: \\[E=mc^2\\]\n\u0060\u0060\u0060\n\nIf the application supports a limited command set, simplify unsupported macros before pasting. Test a small expression first rather than transferring a full page of equations.\n\n## Recover Word or office equations\n\nInsert a new equation field before pasting. In Word, a supported linear form such as the following can be converted into professional layout:\n\n\u0060\u0060\u0060text\n\\sqrt(x^2\u002By^2)\n\u0060\u0060\u0060\n\nDo not paste the same text into an ordinary paragraph and expect it to render. If the equation object came from another office application, use \u201Cpaste special\u201D options and keep an editable source copy.\n\n## Repair plain-text symbols\n\nFor isolated signs, replace look-alikes with verified Unicode characters. Check minus, multiplication, degree, prime, Greek letters, and relation symbols carefully. A font change may fix display, but it does not fix an incorrect code point.\n\n## Troubleshoot web output\n\nWhen HTML displays raw MathML tags, confirm that the markup is not escaped and that the browser supports the elements used. When a Markdown site shows raw dollar signs, verify that its renderer actually enables mathematical expressions; CommonMark alone does not define a universal math extension.\n\n## Verify before publishing\n\nOpen the final output on a second device or application. Compare grouping, signs, exponents, roots, matrix dimensions, and equation numbering with the editable source. If meaning could be ambiguous, include a plain-language reading or accessible description alongside the equation.\n"
  },
  {
    "slug": "formula-image-vs-math-markup",
    "title": "Formula Images vs Math Markup",
    "description": "Compare PNG, SVG, LaTeX rendering, and MathML for accessibility, SEO, editing, and portability.",
    "topic": "Web math",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nUse selectable math markup or a native equation object for most equations. Use an image only when the destination cannot preserve mathematical structure, and retain an accessible text alternative and editable source.\n\n## Math markup\n\nLaTeX source, MathML, and native equation objects preserve structure for editing, scaling, search, reuse, and often accessibility. Support differs by platform, so the rendered output must be tested in the target environment.\n\n## Formula images\n\nAn image can preserve appearance across limited systems, but it usually loses direct editing, text selection, responsive reflow, and semantic structure. Low-resolution images also become unreadable when zoomed or printed.\n\n## Compare the choices\n\n| Requirement | Math markup | Image |\n|---|---|---|\n| Editable source | Strong | Separate file required |\n| Search and copy | Usually available | Usually unavailable |\n| Responsive scaling | Strong | Depends on resolution |\n| Screen-reader structure | Possible with MathML/native math | Requires a useful text alternative |\n\n## Worked example\n\nFor \u0060x=(-b\\pm\\sqrt{b^2-4ac})/(2a)\u0060, keep the LaTeX source and render it with a supported engine. If an image is required for an email system, export a high-resolution or vector image and provide text describing the quadratic formula and its variables.\n\n## Common mistakes\n\nDo not use an empty or glyph-by-glyph alt attribute. Do not discard the editable source after exporting. Do not assume an SVG is automatically accessible merely because it scales well.\n\n## Verification checklist\n\nTest zoom, print, copy, search, keyboard navigation, screen-reader output, and fallback behavior. Reopen the exported artifact and compare it with the source.\n## Make the choice from the surrounding expression\n\nFor **formula image vs math markup**, do not decide from glyph shape alone. Read the operands, the mathematical subject, and the sentence around the notation. The same mark can represent different ideas in algebra, probability, set theory, analysis, or typography.\n\n## Verification questions\n\n1. Does the proposed meaning produce a mathematically valid sentence?\n2. Are the operands the right type for that meaning?\n3. Does a nearby definition or legend establish a local convention?\n4. Would replacing the mark with words preserve the intended statement?\n\n## Publishing check\n\nUse the exact Unicode character or structured command, then inspect the final PDF, page, or presentation at normal and enlarged zoom. A font substitution can make distinct characters look similar even when their encoded identities differ.\n"
  },
  {
    "slug": "how-to-calculate-compound-interest",
    "title": "How to Calculate Compound Interest",
    "description": "Calculate compound growth from principal, nominal rate, compounding frequency, and time, then distinguish balance from interest earned.",
    "topic": "Financial mathematics",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **calculate compound interest**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060A = P(1 \u002B r/n)^(nt)\u0060, the result is **A \u2248 1104.94**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nThe standard compound-interest model assumes a fixed nominal annual rate, regular compounding, and no additional deposits or withdrawals. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nRates, periods, and cash-flow timing must use compatible units. Treat the formula as a model with assumptions, not as a guarantee of future returns.\n\n## Step-by-step method\n\n1. Convert the annual percentage rate to a decimal.\n2. Identify compounding periods per year n and time in years t.\n3. Compute the periodic growth factor 1\u002Br/n.\n4. Raise it to nt and multiply by principal P.\n5. Subtract P when the question asks for interest earned rather than final balance.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. Let P=1000, r=0.05, n=12, and t=2.\n2. The periodic factor is 1\u002B0.05/12.\n3. There are 24 compounding periods.\n4. A=1000(1\u002B0.05/12)^24\u22481104.94, so interest earned is about 104.94.\n\nThe result **A \u2248 1104.94** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Entering 5 instead of 0.05 for a 5% rate.\n- Mixing months and years.\n- Reporting the final balance as interest earned.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nRecalculate with a financial calculator and confirm the balance exceeds principal for a positive rate. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [related reviewed reference](/formula/compound-interest/) with the worked input when available. The linked reference is useful for checking notation and assumptions, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-calculate-mean-median-mode",
    "title": "How to Calculate Mean, Median, and Mode",
    "description": "Calculate and compare mean, median, and mode, then choose the measure that matches the distribution and question.",
    "topic": "Statistics",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **calculate mean median mode**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060mean = sum(xi)/n\u0060, the result is **mean=5, median=4.5, mode=4**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nMean uses every value, median is the middle ordered value, and mode is the most frequent value. A data set may have no mode or more than one mode. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nState whether the data are a population or sample and preserve enough precision through intermediate calculations. The reported number should be interpreted with the distribution, not in isolation.\n\n## Step-by-step method\n\n1. List the observations and sort them for median and mode.\n2. Add all values and divide by the count for the mean.\n3. Select the middle value, or average the two middle values, for the median.\n4. Count frequencies to identify the mode.\n5. Compare the measures and note outliers or skew.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. For 2,4,4,4,5,5,7,9, the sum is 40 and n=8, so mean=5.\n2. The middle values are 4 and 5, so median=4.5.\n3. The most frequent value is 4, so mode=4.\n4. The three measures describe different aspects of the same distribution.\n\nThe result **mean=5, median=4.5, mode=4** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Finding a median before sorting.\n- Dividing the sum by the wrong count.\n- Claiming a mode when every value occurs once.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nCheck the sum and count again; inspect the ordered list to confirm the middle positions and frequencies. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/statistics-calculator/) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-calculate-percentage-change",
    "title": "How to Calculate Percentage Change",
    "description": "Calculate percentage increase or decrease from an old value to a new value, with the original value as the reference denominator.",
    "topic": "Applied math",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **calculate percentage change**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060(new - old) / |old| \u00D7 100%\u0060, the result is **25% increase**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nPercentage change compares a difference with the starting value. It is directional: swapping old and new changes both the denominator and the interpretation. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nName the reference quantity, time period, and units. A numerically correct percent can still communicate the wrong comparison when the baseline is ambiguous.\n\n## Step-by-step method\n\n1. Identify the original value and the later value.\n2. Subtract old from new to obtain the signed change.\n3. Divide by the absolute original value when a conventional percent-change magnitude is intended.\n4. Multiply by 100 percent.\n5. Label the result as an increase or decrease and state the base period.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. Suppose a value rises from 80 to 100.\n2. The change is 100 - 80 = 20.\n3. Divide by 80: 20/80 = 0.25.\n4. Multiply by 100%, giving a 25% increase.\n\nThe result **25% increase** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Dividing by the new value instead of the old value.\n- Calling a percentage-point difference a percentage change.\n- Using the formula when the original value is zero without explaining an alternative.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nReverse-check: 80 \u00D7 1.25 = 100. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/percentage-change/?old=80\u0026new=100) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-calculate-probability",
    "title": "How to Calculate Probability",
    "description": "Calculate probability from equally likely outcomes, complements, and conditional information while checking the sample space.",
    "topic": "Probability",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **calculate probability**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060P(A) = favorable outcomes / total outcomes\u0060, the result is **P(A) = 1/6**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nA probability model must define a sample space and an event. The simple count ratio is valid only when elementary outcomes are equally likely. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nThe sample space is the model. Define it before counting, especially when outcomes may not be equally likely or events may overlap.\n\n## Step-by-step method\n\n1. Define the experiment and sample space.\n2. Describe the event without double-counting outcomes.\n3. Decide whether outcomes are equally likely.\n4. Use counting, complements, or conditional probability as appropriate.\n5. Check that the final value lies from zero to one.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. For a fair six-sided die, the sample space is {1,2,3,4,5,6}.\n2. The event of rolling a 4 contains one outcome.\n3. Because all six outcomes are equally likely, P(4)=1/6.\n4. The complement has probability 5/6, and the two add to 1.\n\nThe result **P(A) = 1/6** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Counting outcomes as equally likely when they are not.\n- Adding probabilities of overlapping events without subtracting the overlap.\n- Confusing P(A|B) with P(B|A).\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nConfirm P(A)\u002BP(not A)=1 and ensure no probability is negative or greater than one. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/probability-calculator/) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-calculate-standard-deviation",
    "title": "How to Calculate Standard Deviation",
    "description": "Calculate population or sample standard deviation from deviations, squared deviations, variance, and the correct denominator.",
    "topic": "Statistics",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **calculate standard deviation**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060s = sqrt(sum((xi - xbar)^2)/(n - 1))\u0060, the result is **s \u2248 2.14**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nStandard deviation measures spread in the original units. Choose the population formula when the data are the complete population and the sample formula when estimating population variability from a sample. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nState whether the data are a population or sample and preserve enough precision through intermediate calculations. The reported number should be interpreted with the distribution, not in isolation.\n\n## Step-by-step method\n\n1. Compute the arithmetic mean.\n2. Subtract the mean from every observation.\n3. Square each deviation and add the squares.\n4. Divide by n for a population or n - 1 for a sample.\n5. Take the nonnegative square root of the variance.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. For the sample 2, 4, 4, 4, 5, 5, 7, 9, the mean is 5.\n2. Squared deviations sum to 32.\n3. Divide by n - 1 = 7 to get sample variance 32/7.\n4. The sample standard deviation is sqrt(32/7) \u2248 2.14.\n\nThe result **s \u2248 2.14** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Using n when the task requires sample standard deviation.\n- Averaging absolute deviations instead of squared deviations.\n- Rounding the mean too early.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nSquare the reported standard deviation and compare it with the calculated variance. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/statistics-calculator/) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-calculate-2x2-determinant",
    "title": "How to Calculate a 2\u00D72 Determinant",
    "description": "Calculate the determinant of a 2\u00D72 matrix, interpret zero versus nonzero results, and verify signs and row operations.",
    "topic": "Linear algebra",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **calculate 2x2 determinant**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060det([[a,b],[c,d]]) = ad - bc\u0060, the result is **det = -2**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nThe determinant of a 2\u00D72 matrix is the product of the main diagonal minus the product of the other diagonal. A zero determinant means the matrix is singular. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nDimensions and output type are part of the mathematics. Write shapes beside objects before operating so a syntactically neat calculation does not hide an undefined product.\n\n## Step-by-step method\n\n1. Identify entries a, b, c, and d by position.\n2. Multiply a by d.\n3. Multiply b by c.\n4. Subtract the second product from the first.\n5. Use the result to check invertibility or oriented area scaling.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. For [[1,2],[3,4]], compute ad=1\u00D74=4.\n2. Compute bc=2\u00D73=6.\n3. Subtract: 4-6=-2.\n4. Because the determinant is nonzero, the matrix is invertible.\n\nThe result **det = -2** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Adding the diagonal products instead of subtracting.\n- Reading c and d from the wrong row.\n- Assuming determinant is always positive.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nSwap the rows; the determinant should change sign from -2 to 2. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/determinant-calculator/) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-convert-scientific-notation",
    "title": "How to Convert Scientific Notation",
    "description": "Convert between ordinary decimal form and scientific notation while preserving significant digits and the sign of the exponent.",
    "topic": "Scientific writing",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **convert scientific notation**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u00600.00042 = 4.2 \u00D7 10^-4\u0060, the result is **4.2 \u00D7 10^-4**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nNormalized scientific notation has one nonzero digit before the decimal point and an integer power of ten. Positive exponents represent large magnitudes; negative exponents represent small magnitudes. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nNotation carries scale and precision. Keep the coefficient normalized, preserve significant digits, and distinguish a display convention from a change in measured value.\n\n## Step-by-step method\n\n1. Move the decimal point until the coefficient is at least 1 and less than 10.\n2. Count the number of positions moved.\n3. Use a positive exponent when moving left and a negative exponent when moving right.\n4. Preserve significant trailing zeros when they carry measurement information.\n5. Multiply back by the power of ten to check.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. For 0.00042, move the decimal four positions right to form 4.2.\n2. Moving right produces exponent -4.\n3. Therefore 0.00042 = 4.2\u00D710^-4.\n4. Multiplying 4.2 by 0.0001 returns 0.00042.\n\nThe result **4.2 \u00D7 10^-4** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Reversing the exponent sign.\n- Using a coefficient such as 42 that is not normalized.\n- Dropping significant zeros without considering measurement precision.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nExpand 10^-4 as 0.0001 and multiply by 4.2. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/scientific-notation-converter/) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "copy-math-symbols-safely",
    "title": "How to Copy Math Symbols Without Formatting Problems",
    "description": "Avoid font substitutions, hyphen-versus-minus errors, invisible characters, and broken copy-and-paste workflows.",
    "topic": "Unicode",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Copy the exact character\n\nA math symbol can look correct while being the wrong character. The minus sign \u0060\u2212\u0060 is not the same code point as the keyboard hyphen \u0060-\u0060, and the multiplication sign \u0060\u00D7\u0060 is not the letter \u0060x\u0060. Start from a trusted symbol page and use its Copy button rather than selecting a glyph from an image or PDF.\n\n## Check the destination first\n\nPlain text accepts Unicode characters but does not preserve equation structure. Equation editors, LaTeX documents, and MathML-aware web pages can represent fractions, roots, matrices, and limits more reliably.\n\nUse this rule:\n\n- Copy Unicode for one symbol in prose, labels, messages, or code comments.\n- Copy LaTeX for an editable equation source.\n- Copy MathML for semantic web mathematics.\n- Export SVG or PNG only when the destination cannot render structured math.\n\n## Verify the code point\n\nPaste the character into the Unicode converter or inspect it with a code-point tool. A safe plain-text result should identify the expected name and code point.\n\n\u0060\u0060\u0060text\nExpected: MINUS SIGN, U\u002B2212\nRisky substitute: HYPHEN-MINUS, U\u002B002D\n\u0060\u0060\u0060\n\nFor HTML, use the literal Unicode character or a valid named or numeric reference:\n\n\u0060\u0060\u0060html\n\u003Cspan aria-label=\u0022less than or equal to\u0022\u003E\u0026le;\u003C/span\u003E\n\u0060\u0060\u0060\n\nThe entity should decode to the same intended character.\n\n## Preserve structured expressions\n\nDo not copy a rendered fraction one visual piece at a time. Copy the source instead:\n\n\u0060\u0060\u0060latex\n\\frac{x\u002B1}{x-1}\n\u0060\u0060\u0060\n\nAfter pasting, render it and confirm that the full numerator and denominator remain grouped. The same principle applies to roots, exponents, matrices, cases, and limits.\n\n## Troubleshoot a broken paste\n\nIf a symbol becomes a square box, try a font with broader Unicode coverage. If an equation turns into raw backslashes, the destination is treating LaTeX as plain text. If spacing or line breaks change, paste without formatting and reapply the destination\u2019s equation style.\n\nWhen a PDF paste produces unexpected characters, copy from the original source document or re-enter the expression using Unicode or LaTeX. PDF text extraction can reorder glyphs or substitute characters from embedded fonts.\n\n## Common mistakes\n\n- Copying from a screenshot or raster image.\n- Replacing \u0060\u2264\u0060 with \u0060\u003C\u0060 and \u0060=\u0060 as separate characters.\n- Assuming a visually similar Greek letter is a Latin letter.\n- Pasting rich-text equation objects into plain-text fields.\n- Deleting braces from LaTeX after the paste.\n\n## Verify the final output\n\nCompare the pasted result with the source at three levels: visual appearance, character identity, and mathematical meaning. Test the final document after export, because a symbol that works in the editor can fail in email, PDF conversion, a website font, or another operating system.\n"
  },
  {
    "slug": "latex-macros-safely",
    "title": "How to Create Safe LaTeX Macros",
    "description": "Design small reusable commands without hiding meaning, breaking spacing, or making source files impossible to exchange.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n\\newcommand{\\vect}[1]{\\mathbf{#1}}\n\u0060\u0060\u0060\n\nUse arguments explicitly, choose a distinctive command name, and avoid silently redefining package commands.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Test a macro as a public interface\n\nTreat every reusable macro as a small interface rather than a typing shortcut. Give it a name that describes the mathematical role, document the number and meaning of its arguments, and test it in inline math, display math, section headings, captions, and moving arguments when those contexts are relevant. A macro that silently changes spacing or absorbs punctuation can create errors far from its definition.\n\nKeep the first version narrow. Prefer a command that expands to one semantic unit over a large macro that hides an entire derivation. Compile a minimal document containing normal input, empty or unusual arguments, nested use, and the target journal or renderer. When exchanging source files, include the definitions near the document preamble and provide a plain LaTeX fallback for collaborators who cannot load the same package set.\n\n## Avoid fragile redefinitions\n\nDo not redefine standard commands merely to save characters. A local shortcut can conflict with a class file, package update, or publisher template. Before choosing a name, search the active package documentation and compile with warnings enabled. If an existing command must be wrapped, create a new descriptive command and preserve the original behaviour rather than overwriting it globally.\n"
  },
  {
    "slug": "create-matrix-in-latex",
    "title": "How to Create a Matrix in LaTeX",
    "description": "Build matrices with rows, columns, delimiters, alignment, and common environments.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Load the matrix tools\n\nThe standard matrix environments are provided by \u0060amsmath\u0060 in a full LaTeX document:\n\n\u0060\u0060\u0060latex\n\\documentclass{article}\n\\usepackage{amsmath}\n\\begin{document}\n\\[\n\\begin{bmatrix}\n1 \u0026 2 \\\\\n3 \u0026 4\n\\end{bmatrix}\n\\]\n\\end{document}\n\u0060\u0060\u0060\n\nUse \u0060\u0026\u0060 between columns and \u0060\\\\\u0060 between rows.\n\n## Choose an environment\n\n- \u0060matrix\u0060 has no surrounding delimiter.\n- \u0060pmatrix\u0060 uses parentheses.\n- \u0060bmatrix\u0060 uses square brackets.\n- \u0060Bmatrix\u0060 uses braces.\n- \u0060vmatrix\u0060 uses single vertical bars, commonly for determinants.\n- \u0060Vmatrix\u0060 uses double vertical bars.\n\nChoose the delimiter for mathematical meaning, not decoration.\n\n## Validate rows and columns\n\nEvery row should have the same number of entries unless the environment intentionally includes special formatting. For a three-column matrix, each row needs two \u0060\u0026\u0060 separators:\n\n\u0060\u0060\u0060latex\n\\begin{pmatrix}\na \u0026 b \u0026 c \\\\\nd \u0026 e \u0026 f\n\\end{pmatrix}\n\u0060\u0060\u0060\n\nA misplaced separator can shift entries or produce an alignment error.\n\n## Write augmented matrices\n\nFor a vertical separator inside an array, use an \u0060array\u0060 environment with an explicit column specification:\n\n\u0060\u0060\u0060latex\n\\left[\\begin{array}{cc|c}\n1 \u0026 2 \u0026 3 \\\\\n4 \u0026 5 \u0026 6\n\\end{array}\\right]\n\u0060\u0060\u0060\n\nCheck that the delimiter scales around the complete array.\n\n## Distinguish matrices and determinants\n\nSquare brackets normally denote a matrix, while vertical bars may denote a determinant. Do not replace determinant notation with an absolute-value-looking expression unless the context is unambiguous.\n\n## Troubleshoot errors\n\n\u201CExtra alignment tab\u201D usually means a row contains too many \u0060\u0026\u0060 characters. A missing row break can merge rows. If the environment is undefined, load \u0060amsmath\u0060 or confirm that the web renderer supports it. If delimiters are too small around an array, use matching scalable delimiters.\n\n## Common mistakes\n\n- Using commas instead of column separators.\n- Giving different row lengths accidentally.\n- Forgetting the package in a full LaTeX document.\n- Using \u0060vmatrix\u0060 when ordinary matrix brackets are intended.\n- Typing a large matrix inline where it harms readability.\n\n## Verify the rendered matrix\n\nCount rows and columns in both the source and output. Check each entry\u2019s sign and subscript, then verify the intended operation with a small calculation such as a determinant, trace, or matrix-vector product.\n\n## Editorial test case\n\nThe verification matrix used two rows and three columns, then intentionally removed one \u0060\u0026\u0060 separator and one row break. Those changes reproduced alignment failures and confirmed that entry count, not visual spacing in the source, determines the rendered grid. The same source was also compared with \u0060pmatrix\u0060, \u0060bmatrix\u0060, and \u0060vmatrix\u0060 to confirm that only the delimiters changed.\n## Build a minimal test before the full expression\n\nFor **create matrix in latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "latex-custom-operators",
    "title": "How to Define Custom Math Operators in LaTeX",
    "description": "Create correctly spaced named operators instead of assembling function names from ordinary italic letters.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n\\DeclareMathOperator{\\rank}{rank}\n\u0060\u0060\u0060\n\nDeclare named operators so spacing matches \u0060\\sin\u0060 and \u0060\\log\u0060.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060\\DeclareMathOperator{\\rank}{rank}\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **latex custom operators**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "how-to-differentiate-with-power-rule",
    "title": "How to Differentiate with the Power Rule",
    "description": "Differentiate polynomial terms using the power rule, constants, sums, and a substitution check against a difference quotient.",
    "topic": "Calculus",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **use the power rule derivative**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060d/dx x^n = n x^(n-1)\u0060, the result is **f\u0027(x) = 12x^3 - 4x**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nThe power rule applies term by term to constant powers of x. Products of functions, compositions, and variable exponents require additional rules. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nDifferentation and integration rules have domains and structural triggers. Identify the outer operation before applying a memorized rule, and verify with the inverse operation whenever possible.\n\n## Step-by-step method\n\n1. Rewrite roots and reciprocal powers as exponents when helpful.\n2. Differentiate each term independently.\n3. Multiply by the old exponent.\n4. Reduce the exponent by one.\n5. Simplify and check a numeric slope against a small difference quotient.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. Let f(x)=3x^4 - 2x^2 \u002B 7.\n2. Differentiate 3x^4 to get 12x^3.\n3. Differentiate -2x^2 to get -4x, and the constant 7 to get 0.\n4. Therefore f\u0027(x)=12x^3 - 4x.\n\nThe result **f\u0027(x) = 12x^3 - 4x** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Reducing the exponent without multiplying by it.\n- Applying the power rule directly to sin(x) or e^x.\n- Forgetting that the derivative of a constant is zero.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nAt x=1, the derivative is 8. A small symmetric difference quotient around x=1 should be close to 8. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [related reviewed reference](/formula/power-rule-derivative/) with the worked input when available. The linked reference is useful for checking notation and assumptions, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-factor-quadratic-trinomials",
    "title": "How to Factor Quadratic Trinomials",
    "description": "Factor quadratic trinomials by identifying factor pairs, checking signs, and multiplying the factors back to the original polynomial.",
    "topic": "Algebra",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **factor quadratic trinomials**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060x^2 \u002B 7x \u002B 12 = (x\u002B3)(x\u002B4)\u0060, the result is **(x\u002B3)(x\u002B4)**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nFor a monic trinomial x\u00B2 \u002B bx \u002B c, seek two numbers whose product is c and whose sum is b. For nonmonic quadratics, use grouping or another reliable method. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nKeep every transformation reversible. An algebraic line is not merely formatting: it is a claim that the solution set has not changed. Record restrictions before cancelling factors or applying inverse operations.\n\n## Step-by-step method\n\n1. Take out any greatest common factor first.\n2. List factor pairs of the constant term.\n3. Select the pair whose sum matches the middle coefficient.\n4. Write the two binomial factors.\n5. Expand the factors to verify every coefficient.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. For x\u00B2 \u002B 7x \u002B 12, factor pairs of 12 include 3 and 4.\n2. Because 3\u002B4=7, write (x\u002B3)(x\u002B4).\n3. Expanding gives x\u00B2\u002B4x\u002B3x\u002B12.\n4. Combining middle terms recovers x\u00B2\u002B7x\u002B12.\n\nThe result **(x\u002B3)(x\u002B4)** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Ignoring the greatest common factor.\n- Choosing a pair with the right product but wrong sum.\n- Failing to account for negative signs.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nFOIL the proposed factors and compare all three coefficients. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/polynomial-workbench/) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-find-slope-between-two-points",
    "title": "How to Find Slope Between Two Points",
    "description": "Find slope from two coordinates, interpret its sign, detect vertical lines, and verify the result using rise over run.",
    "topic": "Coordinate geometry",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **find slope between two points**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060m = (y2 - y1) / (x2 - x1)\u0060, the result is **m = 3/2**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nSlope measures vertical change per unit horizontal change. It is defined only when the two x-coordinates differ. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nCoordinate order and geometric meaning must agree. Sketching the points is a fast way to detect a sign or orientation error before relying on the symbolic result.\n\n## Step-by-step method\n\n1. Label the points consistently as (x1,y1) and (x2,y2).\n2. Subtract y-values in the same order used for x-values.\n3. Divide the vertical difference by the horizontal difference.\n4. Simplify the fraction and inspect the sign.\n5. Use the slope to predict another point on the line.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. For (1,2) and (5,8), the rise is 8 - 2 = 6.\n2. The run is 5 - 1 = 4.\n3. Thus m = 6/4 = 3/2.\n4. Moving 2 units right should move 3 units up, which matches the line.\n\nThe result **m = 3/2** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Reversing only one subtraction.\n- Reporting zero for a vertical line instead of undefined slope.\n- Confusing slope with the y-intercept.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nUsing the reversed order gives (2 - 8)/(1 - 5) = -6/-4 = 3/2, the same slope. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/linear-regression-calculator/) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-find-equation-of-line",
    "title": "How to Find the Equation of a Line",
    "description": "Find a line equation from a point and slope or two points, then convert between point-slope, slope-intercept, and standard form.",
    "topic": "Coordinate geometry",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **find equation of a line**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060y - y1 = m(x - x1)\u0060, the result is **y = 2x \u002B 1**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nA nonvertical line is determined by a slope and one point. A vertical line has equation x = constant and cannot be written with a finite slope. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nCoordinate order and geometric meaning must agree. Sketching the points is a fast way to detect a sign or orientation error before relying on the symbolic result.\n\n## Step-by-step method\n\n1. Find the slope if two points are given.\n2. Choose point-slope form using one known point.\n3. Substitute the slope and coordinates.\n4. Simplify to the requested form.\n5. Check that every supplied point satisfies the equation.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. Use points (1,3) and (3,7).\n2. The slope is (7-3)/(3-1)=2.\n3. Point-slope form is y-3=2(x-1).\n4. Simplifying gives y=2x\u002B1, which contains both points.\n\nThe result **y = 2x \u002B 1** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Combining coordinates from different points.\n- Forcing a vertical line into y=mx\u002Bb.\n- Losing a sign while expanding point-slope form.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nSubstitute x=1 to get y=3 and x=3 to get y=7. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/linear-regression-calculator/) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "insert-latex-in-word",
    "title": "How to Insert LaTeX in Microsoft Word",
    "description": "Write LaTeX-style equations in Word and convert them into professional notation.",
    "topic": "Software",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Start inside an equation field\n\nWord does not render LaTeX automatically in an ordinary paragraph. Insert an equation first, place the cursor inside it, and choose the supported linear input format available in your version of Word.\n\nTest the workflow with a small expression before pasting a long derivation:\n\n\u0060\u0060\u0060latex\n\\frac{1}{2}\n\u0060\u0060\u0060\n\nConvert it to professional layout. If the backslashes remain visible, the cursor is probably outside equation mode or the selected input mode does not interpret that syntax.\n\n## Paste supported LaTeX\n\nWord supports a practical subset rather than every package and custom macro used by a full TeX engine. Basic commands are the safest starting point:\n\n\u0060\u0060\u0060latex\n\\sqrt{x^2\u002By^2},\\quad \\alpha\u002B\\beta,\\quad \\sum_{k=1}^{n}k\n\u0060\u0060\u0060\n\nKeep braces around multi-character numerators, denominators, exponents, subscripts, and radicands. Convert one equation at a time when troubleshooting.\n\n## Simplify unsupported source\n\nPackage-specific environments, user-defined commands, and publication macros may not transfer. Replace a custom command with its expanded basic form. Remove document-level commands such as \u0060\\begin{document}\u0060 because Word expects an expression, not a complete LaTeX file.\n\nFor aligned systems or matrices, use structures that Word recognizes or rebuild the layout with Word\u2019s equation tools after transferring the individual expressions.\n\n## Preserve an editable master\n\nKeep the original \u0060.tex\u0060 source. Word conversion may change spacing, command choices, or environment structure even when the rendered equation looks correct. The Word object is a useful document representation, not necessarily a round-trip replacement for the original source.\n\n## Troubleshoot conversion\n\nIf only part of the expression converts, check for unmatched braces and unsupported macros. If symbols change, compare the original command with the resulting Unicode character. If spacing is poor, avoid manual spaces and use equation-aware spacing or Word\u2019s professional layout.\n\nErrors are easier to isolate by reducing the equation to the smallest failing command and adding components back one at a time.\n\n## Common mistakes\n\n- Pasting LaTeX into normal body text.\n- Expecting package declarations to work inside an equation.\n- Removing braces from fractions or roots.\n- Converting a whole LaTeX document instead of one expression.\n- Discarding the original source after a visually successful import.\n\n## Verify the result\n\nCompare every sign, limit, subscript, matrix dimension, and delimiter with the LaTeX source. Save, reopen, and export the Word file to ensure the equation remains editable and renders correctly in the final document.\n"
  },
  {
    "slug": "math-symbols-in-google-docs",
    "title": "How to Insert Math Symbols in Google Docs",
    "description": "Use special characters, equation tools, and copy-paste workflows in Google Docs.",
    "topic": "Software",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Recommended method\n\nFor **Google Docs**, choose the input method according to the complexity of the mathematics. Use Insert \u2192 Special characters for isolated symbols and Insert \u2192 Equation for structured notation.\n\n## Best method by task\n\n| Task | Recommended format |\n|---|---|\n| One standalone symbol | Unicode text or the application\u2019s symbol picker |\n| Fraction, root, matrix, limit, or aligned equation | Native equation object or supported LaTeX input |\n| Content reused in several systems | Keep a separate LaTeX or MathML source |\n| Accessible web publication | Semantic MathML or an accessible renderer |\n\n## Reliable workflow\n\n1. Create a one-line test containing the most demanding structure you need.\n2. Confirm it remains editable after save, reopen, copy, and paste.\n3. Export once to the final delivery format and inspect fonts, line wrapping, and equation placement.\n4. Test on mobile or another device when the document will be shared widely.\n\n## Copy-and-paste checks\n\nPlace the cursor inside the result. If it behaves like one image, the mathematical structure may have been lost. Copy the expression into plain text to identify the underlying Unicode characters, and keep the structured source separately when plain text cannot represent the layout.\n\n## Common mistakes\n\n- Constructing a complex equation from individually positioned characters and spaces.\n- Assuming every keyboard layout or application version supports the same shortcut.\n- Using a hyphen, letter, or decorative glyph in place of the intended mathematical code point.\n- Publishing a screenshot without an editable source or meaningful alternative text.\n\n## Final recommendation\n\nUse the simplest format that preserves the required meaning. Unicode is efficient for isolated symbols; a native equation object, LaTeX, or MathML is safer for structured mathematics in Google Docs.\n## Confirm the character survives sharing and export\n\nGoogle Docs can insert a character through Special characters, an equation object, or ordinary copy and paste. The correct choice depends on whether the symbol is standalone text or part of a structured expression. After insertion, inspect the character in the final font and compare it with its Unicode code point when a look-alike is possible, especially for minus signs, multiplication signs, Greek letters, and set symbols.\n\nShare a test copy with view-only access and export it to PDF. Reopen both versions and check selection, search, copy-and-paste behaviour, baseline alignment, and mobile rendering. When collaborators must edit a complex equation, retain the source notation in a comment or adjacent plain-text field instead of relying on appearance alone.\n"
  },
  {
    "slug": "math-symbols-in-powerpoint",
    "title": "How to Insert Math Symbols in PowerPoint",
    "description": "Use PowerPoint equations, Unicode text, symbol insertion, and copy-paste workflows while preserving readable mathematical formatting.",
    "topic": "Software input",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Recommended method\n\nFor **PowerPoint**, choose the input method according to the complexity of the mathematics. Use Insert \u2192 Equation for structured mathematics and Insert \u2192 Symbol for a single character.\n\n## Best method by task\n\n| Task | Recommended format |\n|---|---|\n| One standalone symbol | Unicode text or the application\u2019s symbol picker |\n| Fraction, root, matrix, limit, or aligned equation | Native equation object or supported LaTeX input |\n| Content reused in several systems | Keep a separate LaTeX or MathML source |\n| Accessible web publication | Semantic MathML or an accessible renderer |\n\n## Reliable workflow\n\n1. Create a one-line test containing the most demanding structure you need.\n2. Confirm it remains editable after save, reopen, copy, and paste.\n3. Export once to the final delivery format and inspect fonts, line wrapping, and equation placement.\n4. Test on mobile or another device when the document will be shared widely.\n\n## Copy-and-paste checks\n\nPlace the cursor inside the result. If it behaves like one image, the mathematical structure may have been lost. Copy the expression into plain text to identify the underlying Unicode characters, and keep the structured source separately when plain text cannot represent the layout.\n\n## Common mistakes\n\n- Constructing a complex equation from individually positioned characters and spaces.\n- Assuming every keyboard layout or application version supports the same shortcut.\n- Using a hyphen, letter, or decorative glyph in place of the intended mathematical code point.\n- Publishing a screenshot without an editable source or meaningful alternative text.\n\n## Final recommendation\n\nUse the simplest format that preserves the required meaning. Unicode is efficient for isolated symbols; a native equation object, LaTeX, or MathML is safer for structured mathematics in PowerPoint.\n## Verify PowerPoint editing and export\n\nUse a native PowerPoint equation for expressions that colleagues may need to edit. Reserve ordinary Unicode text for standalone symbols in titles, labels, and short annotations. After pasting from Word or another editor, click into the object and confirm whether it remains an equation, becomes editable text, or has been flattened into an image.\n\nRun the presentation on the target computer and export a PDF. Check font substitution, line wrapping, baseline alignment, transparency, and cropping around tall radicals or stacked fractions. A slide theme change can recolour symbols or reduce contrast, so test equations against every background used in the deck. Keep the original equation source with the project when a vector image is used for visual consistency.\n"
  },
  {
    "slug": "how-to-integrate-basic-functions",
    "title": "How to Integrate Basic Functions",
    "description": "Find basic antiderivatives term by term, include the constant of integration, and verify by differentiating the result.",
    "topic": "Calculus",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **integrate basic functions**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060\u222B x^n dx = x^(n\u002B1)/(n\u002B1) \u002B C\u0060, the result is **x^4/4 \u002B 2x^2 \u002B C**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nAn indefinite integral asks for a family of antiderivatives. The basic power rule excludes n = -1, which instead gives a logarithm. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nDifferentation and integration rules have domains and structural triggers. Identify the outer operation before applying a memorized rule, and verify with the inverse operation whenever possible.\n\n## Step-by-step method\n\n1. Simplify the integrand and split sums into separate terms.\n2. Increase a power by one.\n3. Divide by the new exponent.\n4. Use special forms for x^-1, exponentials, and trigonometric functions.\n5. Add a single constant C and differentiate to verify.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. Integrate x^3 \u002B 4x.\n2. The antiderivative of x^3 is x^4/4.\n3. The antiderivative of 4x is 2x^2.\n4. Thus the result is x^4/4 \u002B 2x^2 \u002B C.\n\nThe result **x^4/4 \u002B 2x^2 \u002B C** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Using the power formula when n = -1.\n- Omitting the constant of integration.\n- Changing coefficients inconsistently during division.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nDifferentiate x^4/4 \u002B 2x^2 \u002B C; the result is x^3 \u002B 4x. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [related reviewed reference](/formula/integral-power-rule/) with the worked input when available. The linked reference is useful for checking notation and assumptions, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-multiply-matrices",
    "title": "How to Multiply Matrices",
    "description": "Multiply matrices by checking dimensions, taking row-by-column dot products, and verifying the shape and selected entries.",
    "topic": "Linear algebra",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **multiply matrices**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060Cij = sum_k Aik Bkj\u0060, the result is **AB = [[19,22],[43,50]]**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nThe product AB exists when the number of columns of A equals the number of rows of B. The result has the outer dimensions: rows of A by columns of B. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nDimensions and output type are part of the mathematics. Write shapes beside objects before operating so a syntactically neat calculation does not hide an undefined product.\n\n## Step-by-step method\n\n1. Write the dimensions beside each matrix.\n2. Confirm the inner dimensions match.\n3. For each output entry, pair one row of A with one column of B.\n4. Multiply corresponding entries and add the products.\n5. Check the output dimensions and recompute at least one entry.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. Let A=[[1,2],[3,4]] and B=[[5,6],[7,8]].\n2. The first entry is 1\u00D75 \u002B 2\u00D77 = 19.\n3. The first-row second-column entry is 1\u00D76 \u002B 2\u00D78 = 22.\n4. Continuing gives AB=[[19,22],[43,50]].\n\nThe result **AB = [[19,22],[43,50]]** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Multiplying entries position by position.\n- Assuming AB equals BA.\n- Using columns of A with rows of B instead of rows of A with columns of B.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nThe result must be 2\u00D72, and its (2,1) entry is 3\u00D75 \u002B 4\u00D77 = 43. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/matrix-calculator/) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "equation-numbering-latex",
    "title": "How to Number Equations in LaTeX",
    "description": "Use equation, align, labels, references, and selective numbering for technical documents.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n\\begin{equation}E=mc^2\\label{eq:energy}\\end{equation}\n\u0060\u0060\u0060\n\nUse \u0060\\label\u0060 and \u0060\\ref\u0060; do not type equation numbers manually.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060\\begin{equation}E=mc^2\\label{eq:energy}\\end{equation}\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **equation numbering latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "accessible-math-on-web",
    "title": "How to Publish Accessible Math on the Web",
    "description": "Combine semantic markup, readable fallback text, keyboard access, and testing for accessible equations.",
    "topic": "Web math",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Prefer structured mathematics\n\nUse ordinary text for simple symbols and semantic mathematical markup for structured expressions. Native text and MathML can be selected, enlarged, searched, and interpreted more reliably than a screenshot.\n\n\u0060\u0060\u0060html\n\u003Cmath xmlns=\u0022http://www.w3.org/1998/Math/MathML\u0022\u003E\n  \u003Cmsup\u003E\u003Cmi\u003Ex\u003C/mi\u003E\u003Cmn\u003E2\u003C/mn\u003E\u003C/msup\u003E\n  \u003Cmo\u003E\u002B\u003C/mo\u003E\u003Cmsup\u003E\u003Cmi\u003Ey\u003C/mi\u003E\u003Cmn\u003E2\u003C/mn\u003E\u003C/msup\u003E\n  \u003Cmo\u003E=\u003C/mo\u003E\u003Cmsup\u003E\u003Cmi\u003Er\u003C/mi\u003E\u003Cmn\u003E2\u003C/mn\u003E\u003C/msup\u003E\n\u003C/math\u003E\n\u0060\u0060\u0060\n\nA visual renderer can still be used, but keep an accessible representation and readable source.\n\n## Explain notation in context\n\nA screen reader may speak a symbol name without explaining its role in the current subject. Define variables, domains, and unusual conventions in nearby prose. For a central equation, provide a concise reading such as \u201Cx squared plus y squared equals r squared.\u201D\n\n## Make equation images equivalent\n\nUse an image only when structured output is not practical. Its alternative text should communicate the mathematical content, not say \u201Cequation image.\u201D Complex derivations may need a short alt attribute plus a longer description in adjacent text.\n\n\u0060\u0060\u0060html\n\u003Cimg src=\u0022quadratic-formula.svg\u0022\n     alt=\u0022x equals negative b plus or minus the square root of b squared minus four a c, divided by two a\u0022\u003E\n\u0060\u0060\u0060\n\nDo not duplicate a long visible explanation inside the alt attribute.\n\n## Support zoom and reflow\n\nEquations must remain readable at increased text size and narrow widths. Avoid clipping, fixed-height containers, and images that become blurry. For a wide derivation, allow horizontal scrolling inside a clearly focused region rather than forcing the entire page to scroll sideways.\n\n## Preserve keyboard access\n\nCopy buttons, expanders, tabs, and equation editors must work from the keyboard and expose clear focus indicators. A decorative symbol should not receive focus. Interactive math tools need labels, instructions, error messages, and results announced in a predictable order.\n\n## Test with assistive technology\n\nInspect the accessibility tree, navigate headings and controls with a keyboard, and test representative equations with at least one screen reader available to the project. Listen for grouping, superscripts, fractions, and operators rather than checking only whether some speech occurs.\n\n## Common failures\n\n- Rendering every equation to canvas with no alternative.\n- Using color alone to distinguish variables or steps.\n- Providing a generic \u201Cformula\u201D alt text.\n- Hiding visible equations from assistive technology without an equivalent replacement.\n- Allowing mobile overflow to cover controls or text.\n\n## Verify before release\n\nTest the final production page at high zoom, in a narrow viewport, with keyboard-only navigation, and with the site\u2019s actual fonts and scripts. Record the browser, renderer, and assistive technology used so later updates can repeat the same checks.\n## Test the accessible representation\n\nFor **accessible math on web**, keep the visual equation and its semantic or textual alternative synchronized. Read the alternative without looking at the equation: it should preserve the relation, grouping, bounds, scripts, and variable names rather than listing isolated symbols.\n\n## Verification sequence\n\n1. Navigate to the equation using only the keyboard.\n2. Inspect the accessible name or MathML tree.\n3. Listen with at least one screen-reader and browser combination available to the publishing team.\n4. Recheck after conversion to PDF, image, presentation, or another content system.\n\n## When an image is unavoidable\n\nRetain the editable source, provide a concise alternative for simple expressions, and add a longer adjacent explanation for equations whose structure cannot be expressed clearly in a short alt attribute.\n"
  },
  {
    "slug": "mathml-element-reference-guide",
    "title": "How to Read MathML Element References",
    "description": "Understand token, layout, script, table, and semantics elements before constructing accessible web mathematics.",
    "topic": "MathML",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Purpose\n\nHow to Read MathML Element References helps readers interpret how to read mathml element references without relying on the visual shape alone. A useful reference records the name, syntax, semantics, one valid example, and the context in which the notation changes meaning.\n\n## Reference fields to check\n\n| Field | What to verify |\n|---|---|\n| Name and aliases | Search terms used by textbooks, software, and standards |\n| Source syntax | Exact LaTeX command, Unicode code point, or MathML element |\n| Meaning | Object type, operands, result type, and local convention |\n| Example | A complete expression rather than an isolated glyph |\n| Compatibility | Renderer, package, browser, font, and export behavior |\n\n## Examples from MathML\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n\n## Reading workflow\n\nIdentify the outer operator or structure, then read its arguments, scripts, limits, and conditions. Compare the rendered form with the editable source and inspect any package or browser requirement before reusing the notation.\n\n## Common ambiguity checks\n\n- Copying a rendered how to read mathml element references image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in how to read mathml element references.\n- Defining how to read mathml element references macros that hide arguments or conflict with package commands.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the how to read mathml element references example.\n## Match the element to its semantic job\n\nBegin with token elements: use \u0060mi\u0060 for identifiers and symbolic constants, \u0060mn\u0060 for numbers, \u0060mo\u0060 for operators and delimiters, and \u0060mtext\u0060 for natural-language text inside mathematics. Add layout elements only when the visual structure requires them. Fractions, roots, scripts, fenced expressions, and tables should encode the same grouping a reader would use to interpret the formula.\n\nValidate a small MathML fragment before combining it with a larger expression. Inspect the browser accessibility tree, navigate with a screen reader when possible, and compare the spoken order with the mathematical reading order. Do not choose an element only because its default styling looks right; CSS can alter appearance, but incorrect token semantics can still damage navigation, speech, copying, and downstream conversion.\n"
  },
  {
    "slug": "latex-command-reference-guide",
    "title": "How to Read a LaTeX Command Reference",
    "description": "Use command categories, required packages, argument syntax, examples, and rendered output to choose reliable mathematical notation.",
    "topic": "LaTeX Reference",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Read a command entry completely\n\nA useful LaTeX command reference should state the command, required arguments, optional arguments, package, valid math mode, and a minimal example. Copying only the command name often causes errors because braces or an environment are missing.\n\n## Start with a minimal document\n\nTest unfamiliar commands in a small source file:\n\n\u0060\u0060\u0060latex\n\\documentclass{article}\n\\usepackage{amsmath}\n\\begin{document}\n\\[\n  \\frac{a\u002Bb}{c\u002Bd}\n\\]\n\\end{document}\n\u0060\u0060\u0060\n\nA minimal file separates command errors from problems elsewhere in a large project.\n\n## Preserve argument grouping\n\nCommands such as fractions, roots, accents, and operators depend on braces:\n\n\u0060\u0060\u0060latex\n\\frac{x\u002B1}{x-1}\n\\sqrt[n]{x}\n\\vec{v}\n\u0060\u0060\u0060\n\nWithout braces, a command may apply to only the next token. Use explicit grouping when the intended argument contains more than one character.\n\n## Check package requirements\n\nCore commands work in standard LaTeX, while aligned equations, advanced matrices, and many operators rely on packages such as \u0060amsmath\u0060. Package documentation is the authority for environments and options. Do not add packages blindly; identify which command requires each one.\n\n## Compare renderer support\n\nBrowser renderers implement large but not identical subsets of TeX mathematics. A command that compiles in a full LaTeX distribution may fail in KaTeX or another web renderer. Check the renderer\u2019s supported-function list and provide a simpler equivalent where practical.\n\n## Diagnose errors\n\nAn \u201Cundefined control sequence\u201D usually indicates a misspelled command, a missing package, or an unsupported macro. A \u201Cmissing brace\u201D error may be reported after the actual mistake. Reduce the equation to a minimal failing example and restore parts incrementally.\n\n## Common command patterns\n\n- \u0060\\frac{numerator}{denominator}\u0060 for fractions.\n- \u0060x^{2}\u0060 and \u0060a_{n}\u0060 for scripts.\n- \u0060\\sum_{k=1}^{n}\u0060 for bounded operators.\n- \u0060\\left( ... \\right)\u0060 for scalable delimiters.\n- \u0060\\operatorname{rank}\u0060 for named custom operators.\n\n## Verify rendered meaning\n\nSuccessful compilation is not enough. Confirm that limits attach to the intended operator, delimiters enclose the complete expression, and spacing does not imply the wrong multiplication or function application. Keep the minimal example with the content record so future renderer updates can repeat the test.\n\n## Editorial test case\n\nThe command checks used a minimal document and isolated browser-renderer examples rather than a large template. Each example was reduced until one command, its arguments, and any required package remained. That process separates a command error from unrelated document configuration and creates a small regression case that can be rerun after a LaTeX distribution or renderer update.\n## Build a minimal test before the full expression\n\nFor **latex command reference guide**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "how-to-simplify-fractions",
    "title": "How to Simplify Fractions Correctly",
    "description": "Reduce a fraction by finding the greatest common divisor, dividing numerator and denominator by the same factor, and preserving the sign.",
    "topic": "Arithmetic",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **simplify fractions**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u006042/56 = 3/4\u0060, the result is **3/4**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nA fraction is in simplest form when numerator and denominator share no common factor greater than one. The denominator must never be zero. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nExact arithmetic should remain exact until the last display step. A decimal comparison can catch a gross error, but it does not replace proof that numerator and denominator were transformed by the same nonzero factor.\n\n## Step-by-step method\n\n1. Move a negative sign to the numerator or in front of the fraction.\n2. Find the greatest common divisor of the absolute numerator and denominator.\n3. Divide both by that same nonzero divisor.\n4. Confirm the new numerator and denominator are coprime.\n5. Compare decimal values only as a secondary check.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. The greatest common divisor of 42 and 56 is 14.\n2. Divide 42 by 14 to get 3.\n3. Divide 56 by 14 to get 4.\n4. Therefore 42/56 = 3/4, and gcd(3,4)=1.\n\nThe result **3/4** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Dividing the numerator and denominator by different numbers.\n- Reducing across addition, such as cancelling terms in (a\u002Bb)/a.\n- Ignoring a zero denominator.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nCross-multiply: 42 \u00D7 4 and 56 \u00D7 3 both equal 168. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/fraction-simplifier/?value=42%2F56) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-solve-exponential-equations",
    "title": "How to Solve Exponential Equations",
    "description": "Solve exponential equations by matching bases or taking logarithms, then check domain and substitute the result.",
    "topic": "Algebra",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **solve exponential equations**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u00602^(x\u002B1) = 16\u0060, the result is **x = 3**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nIn an exponential equation the variable appears in an exponent. Matching bases is fastest when both sides are powers of a common positive base; otherwise logarithms are usually required. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nKeep every transformation reversible. An algebraic line is not merely formatting: it is a claim that the solution set has not changed. Record restrictions before cancelling factors or applying inverse operations.\n\n## Step-by-step method\n\n1. Isolate the exponential expression.\n2. Rewrite both sides with a common base when possible.\n3. Equate exponents if the bases match and are valid.\n4. Otherwise take logarithms and use the power rule for logs.\n5. Substitute the result into the original equation.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. Rewrite 16 as 2^4.\n2. Then 2^(x\u002B1)=2^4.\n3. Equate exponents: x\u002B1=4.\n4. Therefore x=3, and 2^(3\u002B1)=16.\n\nThe result **x = 3** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Taking logarithms of a nonpositive expression.\n- Equating exponents when the bases are not the same.\n- Dropping parentheses around a compound exponent.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nSubstitute x=3 and confirm the left side equals 16 exactly. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [related reviewed reference](/guides/exponential-logarithmic-notation-reference/) with the worked input when available. The linked reference is useful for checking notation and assumptions, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-solve-linear-equations",
    "title": "How to Solve Linear Equations Step by Step",
    "description": "Solve one-variable linear equations by simplifying both sides, isolating the variable, and checking the result in the original equation.",
    "topic": "Algebra",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **solve linear equations**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u00603x \u002B 7 = 22\u0060, the result is **x = 5**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nA linear equation has the variable only to the first power. After simplifying, it can be written as ax \u002B b = c with a not equal to zero. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nKeep every transformation reversible. An algebraic line is not merely formatting: it is a claim that the solution set has not changed. Record restrictions before cancelling factors or applying inverse operations.\n\n## Step-by-step method\n\n1. Remove parentheses with the distributive property.\n2. Combine like terms on each side.\n3. Move variable terms to one side and constants to the other.\n4. Divide by the nonzero coefficient of the variable.\n5. Substitute the result into the original equation.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. Start with 3x \u002B 7 = 22.\n2. Subtract 7 from both sides to obtain 3x = 15.\n3. Divide both sides by 3, giving x = 5.\n4. Check: 3(5) \u002B 7 = 22, so the solution is valid.\n\nThe result **x = 5** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Changing a sign without applying the same operation to both sides.\n- Dividing before combining like terms.\n- Checking in a simplified line instead of the original equation.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nEvaluate both sides of the original equation at x = 5; both sides must equal 22. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/equation-solver/?q=3x%2B7%3D22) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-solve-linear-inequalities",
    "title": "How to Solve Linear Inequalities",
    "description": "Solve one-variable linear inequalities, reverse the inequality when dividing by a negative, and represent the solution on a number line.",
    "topic": "Algebra",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **solve linear inequalities**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060-2x \u002B 3 \u003E 11\u0060, the result is **x \u003C -4**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nLinear inequalities use the same balancing operations as linear equations, except multiplying or dividing by a negative reverses the inequality direction. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nKeep every transformation reversible. An algebraic line is not merely formatting: it is a claim that the solution set has not changed. Record restrictions before cancelling factors or applying inverse operations.\n\n## Step-by-step method\n\n1. Simplify both sides and combine like terms.\n2. Move variable terms and constants as needed.\n3. When dividing by a negative number, reverse \u003C, \u003E, \u2264, or \u2265.\n4. Write the solution in inequality and interval notation.\n5. Test one value inside and one value outside the proposed set.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. Start with -2x \u002B 3 \u003E 11.\n2. Subtract 3 to get -2x \u003E 8.\n3. Divide by -2 and reverse the sign: x \u003C -4.\n4. A test value x=-5 works, while x=0 does not.\n\nThe result **x \u003C -4** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Forgetting to reverse the sign after division by a negative.\n- Using a closed endpoint for a strict inequality.\n- Treating an inequality solution as one number instead of a set.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nSubstitute x=-5: -2(-5)\u002B3=13\u003E11. Substitute x=0: 3 is not greater than 11. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nThe Equation Solver deliberately does not claim to solve inequalities. Verify the interval with one test value inside it and one outside it, and confirm that dividing by a negative number reversed the inequality sign. This keeps the guide accurate instead of sending an unsupported expression to a calculator.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-solve-quadratic-equations",
    "title": "How to Solve Quadratic Equations",
    "description": "Choose factoring, completing the square, or the quadratic formula, then verify every root in the original quadratic equation.",
    "topic": "Algebra",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **solve quadratic equations**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060x^2 - 5x \u002B 6 = 0\u0060, the result is **x = 2 or x = 3**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nA quadratic equation can be arranged as ax\u00B2 \u002B bx \u002B c = 0 with a nonzero. The discriminant b\u00B2 - 4ac predicts whether real roots are distinct, repeated, or absent. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nKeep every transformation reversible. An algebraic line is not merely formatting: it is a claim that the solution set has not changed. Record restrictions before cancelling factors or applying inverse operations.\n\n## Step-by-step method\n\n1. Move every term to one side so the other side is zero.\n2. Look for a common factor or an easy factor pair.\n3. If factoring is not practical, use completing the square or the quadratic formula.\n4. Keep both plus and minus branches when a square root appears.\n5. Substitute each candidate root into the original equation.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. For x\u00B2 - 5x \u002B 6 = 0, find two numbers with product 6 and sum -5.\n2. The numbers are -2 and -3, so factor as (x - 2)(x - 3) = 0.\n3. Set each factor equal to zero: x = 2 or x = 3.\n4. Both substitutions make the polynomial equal zero.\n\nThe result **x = 2 or x = 3** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Forgetting one root after factoring.\n- Using the quadratic formula with the wrong sign for b.\n- Rounding a root before the final verification.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nThe residuals 2\u00B2 - 5(2) \u002B 6 and 3\u00B2 - 5(3) \u002B 6 are both zero. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/equation-solver/?q=x%5E2-5x%2B6%3D0) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-solve-systems-of-linear-equations",
    "title": "How to Solve Systems of Linear Equations",
    "description": "Solve two-variable linear systems using elimination or substitution, classify the intersection, and check both original equations.",
    "topic": "Algebra",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **solve systems of linear equations**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u00602x \u002B y = 7; x - y = 2\u0060, the result is **x = 3, y = 1**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nA two-equation linear system can have one intersection, no intersection, or infinitely many solutions. Elimination is efficient when coefficients can be made opposites. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nKeep every transformation reversible. An algebraic line is not merely formatting: it is a claim that the solution set has not changed. Record restrictions before cancelling factors or applying inverse operations.\n\n## Step-by-step method\n\n1. Write equations in aligned standard form.\n2. Choose a variable to eliminate.\n3. Multiply an equation only when necessary.\n4. Add or subtract the equations and solve the remaining one-variable equation.\n5. Back-substitute and check the ordered pair in both originals.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. Add 2x \u002B y = 7 and x - y = 2.\n2. The y terms cancel, giving 3x = 9.\n3. So x = 3. Substitute into x - y = 2 to obtain y = 1.\n4. The pair (3,1) satisfies both equations.\n\nThe result **x = 3, y = 1** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Adding equations without aligning like terms.\n- Forgetting to multiply every term in an equation.\n- Checking the solution in only one equation.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\n2(3)\u002B1=7 and 3-1=2. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [matching browser tool](/tools/linear-system-solver/) with the worked input when available. The tool is useful for recomputation and output formatting, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "how-to-type-degree-celsius",
    "title": "How to Type Degrees Celsius Correctly",
    "description": "Format Celsius temperatures consistently in Word, HTML, Unicode, and LaTeX.",
    "topic": "Scientific writing",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nThe **Degree Celsius** symbol is **\u2103**. Copy it as Unicode text, or use \u0060{}^\\\\circ\\\\mathrm{C}\u0060 inside a LaTeX math environment. Its code point is \u0060U\u002B2103\u0060.\n\n## Copy and code formats\n\n| Format | Value | Best use |\n|---|---|---|\n| Unicode text | \u0060\u2103\u0060 | plain text, labels, and search |\n| LaTeX | \u0060{}^\\\\circ\\\\mathrm{C}\u0060 | equations and authoring systems |\n| HTML entity | \u0060\u0026#8451;\u0060 | web source |\n| MathML | \u0060\u003Cmo\u003E\u2103\u003C/mo\u003E\u0060 | semantic web mathematics |\n\n## Windows, macOS, and Word\n\n- **Windows:** Open Character Map and search by name or Unicode U\u002B2103.\n- **macOS:** Open Character Viewer with Control\u2013Command\u2013Space and search by the symbol name.\n- **Microsoft Word:** In an equation, type {}^\\\\circ\\\\mathrm{C} and press Space when Word supports the command.\n\nFor a standalone character, direct Unicode is usually the simplest choice. For limits, fractions, matrices, scripts, or aligned equations, insert the symbol inside a native equation object or LaTeX expression so the surrounding structure remains editable.\n\n## LaTeX and web use\n\nUse \u0060{}^\\\\circ\\\\mathrm{C}\u0060 in math mode. On a UTF-8 web page, the literal character \u0060\u2103\u0060 is valid when it is only an isolated operator or label. Use MathML or a math renderer when the symbol participates in a structured expression.\n\n## Examples\n\n- \u006020\\,{}^\\circ\\mathrm{C}\u0060\n\n## Common mistakes\n\n- Use the actual \u2103 character (U\u002B2103) when copying Degree Celsius; a look-alike letter, punctuation mark, emoji, or image can break search, accessibility, and mathematical parsing.\n- When authoring LaTeX for Degree Celsius, enter {}^\\\\circ\\\\mathrm{C} in math mode and confirm that it renders as \u2103; pasting a visually similar glyph can change the notation or fail in another renderer.\n- Verify that copy and paste preserves \u0060U\u002B2103\u0060 rather than a visually similar character.\n- Define the local mathematical convention when \u0060\u2103\u0060 can have more than one meaning.\n\n## Which format should you choose?\n\nUse Unicode for a single searchable character, LaTeX for editable authoring, and MathML or a native equation object for semantic structured mathematics. Test the final document, PDF, browser, or presentation rather than assuming every application uses the same shortcuts.\n## Choose the input method for this task\n\nFor **how to type degree celsius**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-greek-letters",
    "title": "How to Type Greek Letters",
    "description": "Copy and type uppercase and lowercase Greek letters on Windows, Mac, Word, HTML, and LaTeX, with a complete command table.",
    "topic": "Typing symbols",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nCopy a Greek letter from the table below for plain text. In LaTeX, use commands such as \u0060\\alpha\u0060, \u0060\\beta\u0060, \u0060\\theta\u0060, and \u0060\\Omega\u0060 inside math mode.\n\nGreek uppercase and lowercase letters are different Unicode characters. They may also have different mathematical meanings, so select the exact case and variant used by your source.\n\n## Greek alphabet copy and LaTeX table\n\n| Name | Uppercase | Lowercase | LaTeX lowercase | LaTeX uppercase |\n|---|---:|---:|---|---|\n| Alpha | \u0391 | \u03B1 | \u0060\\alpha\u0060 | Latin \u0060A\u0060 is normally used |\n| Beta | \u0392 | \u03B2 | \u0060\\beta\u0060 | Latin \u0060B\u0060 is normally used |\n| Gamma | \u0393 | \u03B3 | \u0060\\gamma\u0060 | \u0060\\Gamma\u0060 |\n| Delta | \u0394 | \u03B4 | \u0060\\delta\u0060 | \u0060\\Delta\u0060 |\n| Epsilon | \u0395 | \u03B5 | \u0060\\epsilon\u0060 | Latin \u0060E\u0060 is normally used |\n| Zeta | \u0396 | \u03B6 | \u0060\\zeta\u0060 | Latin \u0060Z\u0060 is normally used |\n| Eta | \u0397 | \u03B7 | \u0060\\eta\u0060 | Latin \u0060H\u0060 is normally used |\n| Theta | \u0398 | \u03B8 | \u0060\\theta\u0060 | \u0060\\Theta\u0060 |\n| Iota | \u0399 | \u03B9 | \u0060\\iota\u0060 | Latin \u0060I\u0060 is normally used |\n| Kappa | \u039A | \u03BA | \u0060\\kappa\u0060 | Latin \u0060K\u0060 is normally used |\n| Lambda | \u039B | \u03BB | \u0060\\lambda\u0060 | \u0060\\Lambda\u0060 |\n| Mu | \u039C | \u03BC | \u0060\\mu\u0060 | Latin \u0060M\u0060 is normally used |\n| Nu | \u039D | \u03BD | \u0060\\nu\u0060 | Latin \u0060N\u0060 is normally used |\n| Xi | \u039E | \u03BE | \u0060\\xi\u0060 | \u0060\\Xi\u0060 |\n| Omicron | \u039F | \u03BF | lowercase resembles Latin \u0060o\u0060 | uppercase resembles Latin \u0060O\u0060 |\n| Pi | \u03A0 | \u03C0 | \u0060\\pi\u0060 | \u0060\\Pi\u0060 |\n| Rho | \u03A1 | \u03C1 | \u0060\\rho\u0060 | uppercase resembles Latin \u0060P\u0060 |\n| Sigma | \u03A3 | \u03C3 | \u0060\\sigma\u0060 | \u0060\\Sigma\u0060 |\n| Tau | \u03A4 | \u03C4 | \u0060\\tau\u0060 | uppercase resembles Latin \u0060T\u0060 |\n| Upsilon | \u03A5 | \u03C5 | \u0060\\upsilon\u0060 | \u0060\\Upsilon\u0060 |\n| Phi | \u03A6 | \u03C6 | \u0060\\phi\u0060 | \u0060\\Phi\u0060 |\n| Chi | \u03A7 | \u03C7 | \u0060\\chi\u0060 | uppercase resembles Latin \u0060X\u0060 |\n| Psi | \u03A8 | \u03C8 | \u0060\\psi\u0060 | \u0060\\Psi\u0060 |\n| Omega | \u03A9 | \u03C9 | \u0060\\omega\u0060 | \u0060\\Omega\u0060 |\n\nSome uppercase Greek letters look identical to Latin capitals. Standard LaTeX therefore uses the Latin character directly for those shapes rather than defining a separate common math command.\n\n## Type Greek letters on Windows\n\n### Copy and paste\n\nCopy the exact Unicode character from the table. This is the fastest method for a single letter in normal text.\n\n### Microsoft Word equations\n\nInsert an equation, enter a command such as \u0060\\theta\u0060, and press Space. Use the correct capitalization: \u0060\\omega\u0060 produces \u03C9, while \u0060\\Omega\u0060 produces \u03A9.\n\n### Character Map\n\nOpen Character Map and search within a font that contains Greek and Coptic characters. Character Map is useful when you need to inspect the character name rather than choosing only by appearance.\n\n### Word Unicode conversion\n\nIn compatible Word text, type a hexadecimal code point and press \u0060Alt\u002BX\u0060. For example, \u006003B1\u0060 followed by \u0060Alt\u002BX\u0060 becomes \u03B1. This is a Word feature, not a universal Windows shortcut.\n\n## Type Greek letters on Mac\n\nPress \u0060Control\u002BCommand\u002BSpace\u0060 to open Character Viewer. Search for the letter name, such as **theta** or **omega**, and inspect the result before inserting it.\n\nFor frequent plain-text input, create text replacements for unique shortcuts. For equations, prefer the application\u2019s equation editor or LaTeX input so the letter remains part of a structured expression.\n\n## Greek letters in HTML\n\nLiteral UTF-8 Greek characters are valid in modern HTML:\n\n\u0060\u0060\u0060html\n\u03B1 \u03B2 \u03B3 \u0394 \u03B8 \u03BB \u03C0 \u03A3 \u03C6 \u03A9\n\u0060\u0060\u0060\n\nNamed entities exist for many common Greek letters, such as \u0060\u0026alpha;\u0060, \u0060\u0026theta;\u0060, and \u0060\u0026Omega;\u0060. Numeric references also work, but a literal character is often easier to review in UTF-8 source.\n\n## Greek letters in LaTeX\n\nUse Greek commands in math mode:\n\n\u0060\u0060\u0060latex\n\\alpha \u002B \\beta = \\gamma\n\u0060\u0060\u0060\n\n\u0060\u0060\u0060latex\n\\Delta x = v\\Delta t\n\u0060\u0060\u0060\n\n\u0060\u0060\u0060latex\n\\sum_{i=1}^{n} x_i\n\u0060\u0060\u0060\n\nCheck whether your renderer supports variant commands. Common examples include \u0060\\varepsilon\u0060, \u0060\\vartheta\u0060, \u0060\\varpi\u0060, \u0060\\varrho\u0060, \u0060\\varsigma\u0060, and \u0060\\varphi\u0060. The preferred visual form can differ by field, publisher, and font.\n\n## Troubleshoot and common look-alike problems\n\n- Greek \u0060\u03BD\u0060 can resemble Latin \u0060v\u0060.\n- Greek \u0060\u03C1\u0060 can resemble Latin \u0060p\u0060.\n- Greek \u0060\u03C7\u0060 can resemble Latin \u0060x\u0060.\n- Greek \u0060\u03BF\u0060 and \u0060\u039F\u0060 can resemble Latin \u0060o\u0060 and \u0060O\u0060.\n- Greek \u0060\u0391\u0060, \u0060\u0392\u0060, \u0060\u0395\u0060, \u0060\u0396\u0060, \u0060\u0397\u0060, \u0060\u0399\u0060, \u0060\u039A\u0060, \u0060\u039C\u0060, \u0060\u039D\u0060, \u0060\u039F\u0060, \u0060\u03A1\u0060, \u0060\u03A4\u0060, \u0060\u03A7\u0060, and \u0060\u03A5\u0060 may resemble Latin capitals.\n\nA visual match is not an encoding match. Mixed-script identifiers can break search, code, copy-paste, and accessibility. When identity matters, inspect the Unicode name or code point.\n\n## Choose uppercase, lowercase, or a variant\n\nThe correct form comes from the notation convention, not from appearance alone. For example:\n\n- \u0060\u0394\u0060 often represents change, while \u0060\u03B4\u0060 may represent a small variation;\n- \u0060\u03A3\u0060 is commonly used for summation, while \u0060\u03C3\u0060 may represent standard deviation;\n- \u0060\u03A9\u0060 can represent ohms or a sample space, while \u0060\u03C9\u0060 often represents angular frequency;\n- \u0060\u03A0\u0060 may be a product-related symbol, while \u0060\u03C0\u0060 commonly represents the circle constant.\n\nDefine the symbol when the audience may not know which convention you are using.\n\n## Final check\n\nAfter inserting a Greek letter, verify its case, Unicode identity, mathematical meaning, and behavior in the final export. Use Unicode for plain text and LaTeX or a native equation object for structured mathematics.\n## Choose the input method for this task\n\nFor **how to type greek letters**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-less-than-or-equal",
    "title": "How to Type Less Than or Equal To",
    "description": "Type \u2264 on Windows, Mac, Word, HTML, Unicode, and LaTeX.",
    "topic": "Typing symbols",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nThe less than or equal to symbol is **\u2264**. Copy it directly: \u0060\u2264\u0060. Its Unicode code point is \u0060U\u002B2264\u0060. In LaTeX math mode, use \u0060\\le\u0060.\n\n## Type it on Windows\n\nFor ordinary text, copy the verified Unicode character or open Character Map and search for the symbol name. In Microsoft Word, you can insert it from the Symbol dialog or use a supported Unicode conversion. For a complete equation, insert an equation field and use the documented linear input method.\n\nDo not rely on an undocumented numeric keypad shortcut without verifying the resulting code point; shortcuts vary by application and keyboard settings.\n\n## Type it on macOS\n\nPress \u0060Control\u002BCommand\u002BSpace\u0060 to open Character Viewer, search for **less than or equal to**, and insert the character. Save frequently used symbols to favorites if the macOS version provides that option.\n\nFor structured equations in a LaTeX-aware editor, enter the command rather than pasting a standalone glyph.\n\n## Use it in Word, HTML, and LaTeX\n\nPlain text:\n\n\u0060\u0060\u0060text\n\u2264\n\u0060\u0060\u0060\n\nLaTeX:\n\n\u0060\u0060\u0060latex\n\\le\n\u0060\u0060\u0060\n\nHTML can use the literal UTF-8 character or a verified numeric or named character reference. For a larger equation, preserve the surrounding structure instead of replacing every command with Unicode.\n\n## Meaning and correct usage\n\nLess Than Or Equal To is a mathematical symbol, not merely a visual decoration. Define its role when the field or convention could change its meaning. Keep spacing and grouping consistent with the destination\u2019s equation style.\n\n## Troubleshoot input problems\n\nIf \u0060\u2264\u0060 appears as a square box, change to a font with the glyph. If \u0060\\le\u0060 appears literally, the destination is not rendering LaTeX or the cursor is outside equation mode. If copying from a PDF produces a different character, return to the editable source or use the verified Unicode value \u0060U\u002B2264\u0060.\n\n## Common mistakes\n\n- Replacing \u0060\u2264\u0060 with a visually similar keyboard sequence or letter.\n- Copying the symbol from an image.\n- Using Unicode when the expression needs scalable equation structure.\n- Removing braces or math delimiters around a LaTeX expression.\n- Assuming the same keyboard shortcut works in every application.\n\n## Verify the result\n\nPaste the character into a Unicode inspector and confirm \u0060U\u002B2264\u0060. Render the LaTeX command and compare its meaning, not only its shape. Finally, reopen or export the target document to confirm the symbol survives the full publishing workflow.\n## Choose the input method for this task\n\nFor **how to type less than or equal**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "math-symbols-in-word",
    "title": "How to Type Math Symbols in Microsoft Word",
    "description": "Use equation shortcuts, Unicode conversion, Symbol insertion, and AutoCorrect in Word.",
    "topic": "Software",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Choose the right Word feature\n\nUse **Insert Symbol** or Unicode conversion for a character inside normal text. Use **Insert Equation** for fractions, roots, matrices, limits, and expressions that must scale or align.\n\n| Task | Best Word method |\n|---|---|\n| Insert \u0060\u03C0\u0060, \u0060\u221E\u0060, or \u0060\u2264\u0060 in a sentence | Insert Symbol, copy Unicode, or use a supported Alt\u002BX conversion |\n| Write a fraction or square root | Insert Equation |\n| Build a matrix or aligned system | Insert Equation with a structured template or linear input |\n| Preserve editable math for later changes | Keep the content as a Word equation object |\n\n## Insert one Unicode symbol\n\nPlace the cursor in ordinary text and use **Insert \u2192 Symbol \u2192 More Symbols**, then search by font or character subset. You can also paste a verified character from the symbol reference.\n\nFor supported characters, type the hexadecimal code and press \u0060Alt\u002BX\u0060. For example, entering \u006003C0\u0060 and converting it produces the lowercase pi character \u0060\u03C0\u0060. Confirm the result because the characters before the cursor can affect conversion.\n\n## Enter a structured equation\n\nOpen an equation field, then type a supported linear expression:\n\n\u0060\u0060\u0060text\n\\frac(a\u002Bb)(c\u002Bd)\n\u0060\u0060\u0060\n\nor\n\n\u0060\u0060\u0060text\nx=(-b\u002B-sqrt(b^2-4ac))/(2a)\n\u0060\u0060\u0060\n\nWord can convert supported UnicodeMath or LaTeX-like input into professional layout. Exact commands and conversion behavior depend on the selected equation input format, so test the expression in the installed version of Word.\n\n## Keep text and equations separate\n\nA standalone symbol in a paragraph should usually remain text so it follows the surrounding font and line flow. A complete mathematical expression should remain an equation object. Mixing ordinary spaces, manual superscripts, and inserted symbols often creates inconsistent alignment.\n\n## Troubleshoot Word input\n\nIf a command remains visible, verify that the cursor is inside an equation field and that the expected input mode is active. If \u0060Alt\u002BX\u0060 converts the wrong text, select only the intended hexadecimal digits before pressing the shortcut. If a pasted symbol displays as a box, switch to a font that includes the character.\n\nWhen equations change during export, inspect the PDF and keep the original \u0060.docx\u0060 as the editable source.\n\n## Common mistakes\n\n- Using the Symbol dialog to assemble a fraction character by character.\n- Typing a keyboard hyphen where a mathematical minus sign is required.\n- Applying ordinary superscript formatting instead of an equation exponent.\n- Copying a rendered equation as an image when an editable object is available.\n\n## Verify the document\n\nReopen the file, export a PDF, and inspect the equation at normal zoom. Confirm that all braces were interpreted, matrix rows remain aligned, and the copied Unicode characters retain their intended code points.\n"
  },
  {
    "slug": "math-symbols-on-mac",
    "title": "How to Type Math Symbols on Mac",
    "description": "Type math symbols on macOS with Character Viewer, keyboard input, text replacements, Pages, Keynote, Word, and equation editors.",
    "topic": "Software",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nPress \u0060Control\u002BCommand\u002BSpace\u0060 to open **Character Viewer** on a Mac. Search for a symbol name such as **infinity**, **square root**, **not equal**, **pi**, or **degree**, then insert the exact character.\n\nFor a complete equation, use a native equation object or a LaTeX-compatible editor instead of assembling the equation from individual text symbols.\n\n## Common symbols to copy\n\n| Meaning | Symbol | Unicode | LaTeX |\n|---|---:|---|---|\n| Pi | \u03C0 | \u0060U\u002B03C0\u0060 | \u0060\\pi\u0060 |\n| Infinity | \u221E | \u0060U\u002B221E\u0060 | \u0060\\infty\u0060 |\n| Square root | \u221A | \u0060U\u002B221A\u0060 | \u0060\\sqrt{x}\u0060 |\n| Not equal | \u2260 | \u0060U\u002B2260\u0060 | \u0060\\ne\u0060 |\n| Less than or equal | \u2264 | \u0060U\u002B2264\u0060 | \u0060\\le\u0060 |\n| Greater than or equal | \u2265 | \u0060U\u002B2265\u0060 | \u0060\\ge\u0060 |\n| Plus or minus | \u00B1 | \u0060U\u002B00B1\u0060 | \u0060\\pm\u0060 |\n| Degree | \u00B0 | \u0060U\u002B00B0\u0060 | \u0060^\\circ\u0060 |\n\n## Use Character Viewer\n\n1. Place the cursor where the symbol should appear.\n2. Press \u0060Control\u002BCommand\u002BSpace\u0060.\n3. Search by a descriptive name such as **integral**, **approximately equal**, or **Greek small letter theta**.\n4. Select the result and inspect the preview or name when several similar characters appear.\n5. Insert the character and verify it in the destination font.\n\nCharacter Viewer is preferable to choosing only by appearance because many math symbols have look-alikes. For example, a multiplication sign \u0060\u00D7\u0060 is not the same character as a lowercase \u0060x\u0060.\n\n## Add Math Symbols to Favorites\n\nCharacter Viewer can keep frequently used characters available without a new search. Add symbols you use often to Favorites, then open that collection for faster insertion.\n\nA useful starter set might include \u0060\u03C0\u0060, \u0060\u221E\u0060, \u0060\u221A\u0060, \u0060\u2264\u0060, \u0060\u2265\u0060, \u0060\u2260\u0060, \u0060\u00B1\u0060, \u0060\u2211\u0060, \u0060\u222B\u0060, and \u0060\u00B0\u0060.\n\n## Create text replacements\n\nFor repeated plain-text symbols, add a macOS text replacement in **System Settings \u2192 Keyboard \u2192 Text Replacements**. Examples:\n\n| Shortcut | Replacement |\n|---|---:|\n| \u0060;pi\u0060 | \u03C0 |\n| \u0060;inf\u0060 | \u221E |\n| \u0060;neq\u0060 | \u2260 |\n| \u0060;sqrt\u0060 | \u221A |\n\nUse unusual prefixes so normal words do not trigger a replacement. Text replacement is best for standalone characters, not for complex fractions, matrices, or aligned equations.\n\n## Type equations in Pages and Keynote\n\nPages and Keynote can insert equations through their equation feature. Enter supported LaTeX or MathML source in the equation dialog, then insert the rendered equation as a structured object.\n\nExample:\n\n\u0060\u0060\u0060latex\n\\frac{-b\\pm\\sqrt{b^2-4ac}}{2a}\n\u0060\u0060\u0060\n\nUse a native equation when you need scalable fractions, roots with full radicands, limits, scripts, or matrices. A line of ordinary Unicode text cannot preserve all of that structure reliably.\n\n## Type math in Microsoft Word for Mac\n\nFor prose, insert a Unicode symbol through Character Viewer or paste it. For equations, insert a Word equation and use Word\u2019s supported linear equation input.\n\nExample:\n\n\u0060\u0060\u0060latex\n\\int_0^1 x^2\\,dx\n\u0060\u0060\u0060\n\nEquation input behavior can vary with Word version and the selected input format. Confirm the rendered result before distributing the document.\n\n## Type symbols in code and web content\n\nUse literal UTF-8 characters when the symbol is plain text and your source files are stored as UTF-8. Use LaTeX, MathML, or a math renderer for structured expressions.\n\nFor HTML, you can use a literal symbol or a character reference:\n\n\u0060\u0060\u0060html\n\u003Cspan aria-label=\u0022not equal\u0022\u003E\u2260\u003C/span\u003E\n\u003Cspan\u003E\u0026ne;\u003C/span\u003E\n\u0060\u0060\u0060\n\nFor meaningful equations on the web, MathML provides structure that plain text does not.\n\n## Mac keyboard layouts and Option shortcuts\n\nSome symbols are available through \u0060Option\u0060 key combinations, but the result depends on the active keyboard layout and application. Do not publish a long universal shortcut table without testing the same layout your readers use.\n\nWhen a shortcut is uncertain, Character Viewer, copy-paste, or an equation editor is more reliable.\n\n## Troubleshooting missing or incorrect symbols\n\n- **The symbol appears as a box:** choose a font with broader mathematical character coverage.\n- **A symbol changes after export:** inspect the PDF or presentation and check font substitution.\n- **LaTeX source is shown literally:** make sure it was entered in an equation feature, not ordinary text.\n- **The shortcut inserts another character:** verify the active keyboard input source.\n- **The root bar covers only one character:** use \u0060\\sqrt{...}\u0060 in an equation instead of typing \u0060\u221A\u0060 before plain text.\n\n## Best method by task\n\nUse Character Viewer or copy-paste for one standalone symbol. Use text replacements for a small personal set of frequently typed characters. Use Pages, Keynote, Word, LaTeX, or MathML for structured equations. Test the final exported file because editor previews do not always reveal font and accessibility problems.\n"
  },
  {
    "slug": "math-symbols-on-windows",
    "title": "How to Type Math Symbols on Windows",
    "description": "Type math symbols on Windows with Character Map, Word Alt\u002BX, equation input, copy-paste, and Unicode-aware applications.",
    "topic": "Software",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nFor a single symbol, copy it from a trusted reference or use **Character Map**. In Microsoft Word, you can often type a hexadecimal Unicode value and press \u0060Alt\u002BX\u0060, or insert an equation and enter a supported command such as \u0060\\pi\u0060 or \u0060\\sqrt{x}\u0060.\n\nFor full equations, use Word\u2019s equation editor, LaTeX, MathML, or another structured math editor. Do not build a complex equation from unrelated text characters and spaces.\n\n## Common Windows math symbols\n\n| Meaning | Symbol | Word hexadecimal input | LaTeX |\n|---|---:|---|---|\n| Pi | \u03C0 | \u006003C0\u0060, then \u0060Alt\u002BX\u0060 | \u0060\\pi\u0060 |\n| Infinity | \u221E | \u0060221E\u0060, then \u0060Alt\u002BX\u0060 | \u0060\\infty\u0060 |\n| Square root | \u221A | \u0060221A\u0060, then \u0060Alt\u002BX\u0060 | \u0060\\sqrt{x}\u0060 |\n| Not equal | \u2260 | \u00602260\u0060, then \u0060Alt\u002BX\u0060 | \u0060\\ne\u0060 |\n| Less than or equal | \u2264 | \u00602264\u0060, then \u0060Alt\u002BX\u0060 | \u0060\\le\u0060 |\n| Greater than or equal | \u2265 | \u00602265\u0060, then \u0060Alt\u002BX\u0060 | \u0060\\ge\u0060 |\n| Plus or minus | \u00B1 | \u006000B1\u0060, then \u0060Alt\u002BX\u0060 | \u0060\\pm\u0060 |\n| Degree | \u00B0 | \u006000B0\u0060, then \u0060Alt\u002BX\u0060 | \u0060^\\circ\u0060 |\n\n\u0060Alt\u002BX\u0060 is associated with compatible Microsoft Office text fields. It is not a universal Unicode input shortcut for every Windows application.\n\n## Use Character Map\n\n1. Open the Start menu and search for **Character Map**.\n2. Select a font that contains mathematical symbols.\n3. Enable the advanced view when you need more search options.\n4. Search by character name or browse the relevant range.\n5. Select, copy, and paste the character.\n\nCheck the displayed character name when several symbols look similar. The minus sign \u0060\u2212\u0060, hyphen-minus \u0060-\u0060, and en dash \u0060\u2013\u0060 are different characters.\n\n## Use Alt\u002BX in Microsoft Word\n\nType the hexadecimal Unicode code without \u0060U\u002B\u0060, then press \u0060Alt\u002BX\u0060.\n\nExamples:\n\n- \u0060221E\u0060 \u002B \u0060Alt\u002BX\u0060 \u2192 \u221E\n- \u00602260\u0060 \u002B \u0060Alt\u002BX\u0060 \u2192 \u2260\n- \u006003B8\u0060 \u002B \u0060Alt\u002BX\u0060 \u2192 \u03B8\n\nPressing \u0060Alt\u002BX\u0060 again can convert the character back to its code. If the cursor is beside other hexadecimal characters, select the code first so Word knows which sequence to convert.\n\n## Use Word\u2019s equation editor\n\nInsert an equation before typing LaTeX-style or UnicodeMath input. Examples:\n\n\u0060\u0060\u0060latex\n\\frac{a\u002Bb}{c}\n\u0060\u0060\u0060\n\n\u0060\u0060\u0060latex\n\\sqrt{x^2\u002By^2}\n\u0060\u0060\u0060\n\n\u0060\u0060\u0060latex\n\\sum_{i=1}^{n} i\n\u0060\u0060\u0060\n\nPress Space after supported commands when Word requires conversion. Word is not a complete TeX distribution, so package-specific commands may not work. Use the supported equation syntax and inspect the result.\n\n## Use the touch keyboard and symbol panels\n\nWindows input panels can expose common symbols, but coverage and layout vary. They are useful for frequently used characters, not for locating a precise advanced operator or building a structured equation.\n\nWhen exact identity matters, use Character Map, Word Unicode conversion, or copy from a page that shows the Unicode value.\n\n## Numeric Alt codes are not universal Unicode input\n\nTraditional numeric Alt codes are often repeated in shortcut lists, but their output can depend on the keyboard state, application, and legacy code page. A number that produces a symbol in one field may produce a different character or nothing in another.\n\nPrefer these methods in order:\n\n1. native equation input for equations;\n2. Word \u0060Alt\u002BX\u0060 for known Unicode values in Word;\n3. Character Map or copy-paste for standalone text symbols.\n\n## Use math symbols in browsers, code, and Markdown\n\nFor plain UTF-8 text, paste the literal Unicode character. For structured math in Markdown, use the syntax supported by the site\u2019s renderer, often LaTeX delimiters or fenced math blocks.\n\nFor HTML source:\n\n\u0060\u0060\u0060html\n\u003Cspan\u003E\u03C0r\u00B2\u003C/span\u003E\n\u003Cspan\u003E\u0026pi;r\u0026sup2;\u003C/span\u003E\n\u0060\u0060\u0060\n\nFor a real fraction, root, matrix, or aligned expression, use MathML or a math-rendering library rather than attempting to imitate layout with text.\n\n## Troubleshooting\n\n- **A square appears instead of the symbol:** the selected font may not contain the glyph.\n- **\u0060Alt\u002BX\u0060 does nothing:** the current application may not support Word-style Unicode conversion.\n- **A LaTeX command remains visible:** enter it inside an equation object and confirm the supported input format.\n- **The symbol changes in PDF export:** inspect font substitution and embedded-font behavior.\n- **A copied operator behaves strangely in code:** check the Unicode code point; it may be a look-alike character.\n\n## Best method by task\n\nUse copy-paste or Character Map for one symbol. Use Word \u0060Alt\u002BX\u0060 when you know the code point and are working in Word. Use the equation editor or LaTeX for fractions, matrices, radicals, sums, and other structured expressions. Verify the final document rather than assuming the input method guarantees portable output.\n"
  },
  {
    "slug": "how-to-type-superscript-2",
    "title": "How to Type Superscript 2",
    "description": "Insert \u00B2 in plain text, documents, web pages, and mathematical notation.",
    "topic": "Typing symbols",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nThe **Superscript Two** symbol is **\u00B2**. Copy it as Unicode text, or use \u0060^2\u0060 inside a LaTeX math environment. Its code point is \u0060U\u002B00B2\u0060.\n\n## Copy and code formats\n\n| Format | Value | Best use |\n|---|---|---|\n| Unicode text | \u0060\u00B2\u0060 | plain text, labels, and search |\n| LaTeX | \u0060^2\u0060 | equations and authoring systems |\n| HTML entity | \u0060\u0026sup2;\u0060 | web source |\n| MathML | \u0060\u003Cmo\u003E\u00B2\u003C/mo\u003E\u0060 | semantic web mathematics |\n\n## Windows, macOS, and Word\n\n- **Windows:** Use Character Map or enter U\u002B00B2 in a Unicode-aware app.\n- **macOS:** Open Character Viewer with Control\u2013Command\u2013Space and search by name.\n- **Microsoft Word:** Type ^2 in an equation and press Space.\n\nFor a standalone character, direct Unicode is usually the simplest choice. For limits, fractions, matrices, scripts, or aligned equations, insert the symbol inside a native equation object or LaTeX expression so the surrounding structure remains editable.\n\n## LaTeX and web use\n\nUse \u0060^2\u0060 in math mode. On a UTF-8 web page, the literal character \u0060\u00B2\u0060 is valid when it is only an isolated operator or label. Use MathML or a math renderer when the symbol participates in a structured expression.\n\n## Examples\n\n- \u0060x^2\u0060\n- \u0060m^2\u0060\n\n## Common mistakes\n\n- Use the actual \u00B2 character (U\u002B00B2) when copying Superscript Two; a look-alike letter, punctuation mark, emoji, or image can break search, accessibility, and mathematical parsing.\n- When authoring LaTeX for Superscript Two, enter ^2 in math mode and confirm that it renders as \u00B2; pasting a visually similar glyph can change the notation or fail in another renderer.\n- Verify that copy and paste preserves \u0060U\u002B00B2\u0060 rather than a visually similar character.\n- Define the local mathematical convention when \u0060\u00B2\u0060 can have more than one meaning.\n\n## Which format should you choose?\n\nUse Unicode for a single searchable character, LaTeX for editable authoring, and MathML or a native equation object for semantic structured mathematics. Test the final document, PDF, browser, or presentation rather than assuming every application uses the same shortcuts.\n## Choose the input method for this task\n\nFor **how to type superscript 2**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-therefore-and-because-symbols",
    "title": "How to Type Therefore and Because Symbols",
    "description": "Type and use the therefore and because symbols in Word, Windows, macOS, HTML, Unicode, and LaTeX without confusing their logical roles.",
    "topic": "Logic notation",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nThe **Because Symbol** symbol is **\u2235**. Copy it as Unicode text, or use \u0060\\because\u0060 inside a LaTeX math environment. Its code point is \u0060U\u002B2235\u0060.\n\n## Copy and code formats\n\n| Format | Value | Best use |\n|---|---|---|\n| Unicode text | \u0060\u2235\u0060 | plain text, labels, and search |\n| LaTeX | \u0060\\because\u0060 | equations and authoring systems |\n| HTML entity | \u0060\u0026#8757;\u0060 | web source |\n| MathML | \u0060\u003Cmo\u003E\u2235\u003C/mo\u003E\u0060 | semantic web mathematics |\n\n## Windows, macOS, and Word\n\n- **Windows:** Use Character Map and search for Because Symbol, or paste the Unicode character (U\u002B2235).\n- **macOS:** Open Character Viewer with Control\u2013Command\u2013Space and search for Because Symbol.\n- **Microsoft Word:** In an equation, type \\because and press Space when Word supports the command; otherwise insert the Unicode character.\n\nFor a standalone character, direct Unicode is usually the simplest choice. For limits, fractions, matrices, scripts, or aligned equations, insert the symbol inside a native equation object or LaTeX expression so the surrounding structure remains editable.\n\n## LaTeX and web use\n\nUse \u0060\\because\u0060 in math mode. On a UTF-8 web page, the literal character \u0060\u2235\u0060 is valid when it is only an isolated operator or label. Use MathML or a math renderer when the symbol participates in a structured expression.\n\n## Examples\n\n- \u0060x=2\\ \\because\\ x^2=4\u0060\n\n## Common mistakes\n\n- Use the actual \u2235 character (U\u002B2235) when copying Because Symbol; a look-alike letter, punctuation mark, emoji, or image can break search, accessibility, and mathematical parsing.\n- When authoring LaTeX for Because Symbol, enter \\because in math mode and confirm that it renders as \u2235; pasting a visually similar glyph can change the notation or fail in another renderer.\n- Verify that copy and paste preserves \u0060U\u002B2235\u0060 rather than a visually similar character.\n- Define the local mathematical convention when \u0060\u2235\u0060 can have more than one meaning.\n\n## Which format should you choose?\n\nUse Unicode for a single searchable character, LaTeX for editable authoring, and MathML or a native equation object for semantic structured mathematics. Test the final document, PDF, browser, or presentation rather than assuming every application uses the same shortcuts.\n## Choose the input method for this task\n\nFor **how to type therefore and because symbols**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-angle-symbol",
    "title": "How to Type the Angle Symbol",
    "description": "Insert the angle symbol and write named or measured angles in Unicode, Word, and LaTeX.",
    "topic": "Geometry",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nThe **Angle** symbol is **\u2220**. Copy it as Unicode text, or use \u0060\\angle\u0060 inside a LaTeX math environment. Its code point is \u0060U\u002B2220\u0060.\n\n## Copy and code formats\n\n| Format | Value | Best use |\n|---|---|---|\n| Unicode text | \u0060\u2220\u0060 | plain text, labels, and search |\n| LaTeX | \u0060\\angle\u0060 | equations and authoring systems |\n| HTML entity | \u0060\u0026ang;\u0060 | web source |\n| MathML | \u0060\u003Cmo\u003E\u2220\u003C/mo\u003E\u0060 | semantic web mathematics |\n\n## Windows, macOS, and Word\n\n- **Windows:** Use Character Map or enter U\u002B2220 in a Unicode-aware app.\n- **macOS:** Open Character Viewer with Control\u2013Command\u2013Space and search by name.\n- **Microsoft Word:** Type \\angle in an equation and press Space.\n\nFor a standalone character, direct Unicode is usually the simplest choice. For limits, fractions, matrices, scripts, or aligned equations, insert the symbol inside a native equation object or LaTeX expression so the surrounding structure remains editable.\n\n## LaTeX and web use\n\nUse \u0060\\angle\u0060 in math mode. On a UTF-8 web page, the literal character \u0060\u2220\u0060 is valid when it is only an isolated operator or label. Use MathML or a math renderer when the symbol participates in a structured expression.\n\n## Examples\n\n- \u0060\\angle ABC=60^\\circ\u0060\n\n## Common mistakes\n\n- Use the actual \u2220 character (U\u002B2220) when copying Angle; a look-alike letter, punctuation mark, emoji, or image can break search, accessibility, and mathematical parsing.\n- When authoring LaTeX for Angle, enter \\angle in math mode and confirm that it renders as \u2220; pasting a visually similar glyph can change the notation or fail in another renderer.\n- Verify that copy and paste preserves \u0060U\u002B2220\u0060 rather than a visually similar character.\n- Define the local mathematical convention when \u0060\u2220\u0060 can have more than one meaning.\n\n## Which format should you choose?\n\nUse Unicode for a single searchable character, LaTeX for editable authoring, and MathML or a native equation object for semantic structured mathematics. Test the final document, PDF, browser, or presentation rather than assuming every application uses the same shortcuts.\n## Choose the input method for this task\n\nFor **how to type angle symbol**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-approximately-equal",
    "title": "How to Type the Approximately Equal Symbol",
    "description": "Use the approximately equal sign correctly and avoid confusing it with similarity or asymptotic notation.",
    "topic": "Comparison",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nThe **Approximately Equal To** symbol is **\u2248**. Copy it as Unicode text, or use \u0060\\approx\u0060 inside a LaTeX math environment. Its code point is \u0060U\u002B2248\u0060.\n\n## Copy and code formats\n\n| Format | Value | Best use |\n|---|---|---|\n| Unicode text | \u0060\u2248\u0060 | plain text, labels, and search |\n| LaTeX | \u0060\\approx\u0060 | equations and authoring systems |\n| HTML entity | \u0060\u0026asymp;\u0060 | web source |\n| MathML | \u0060\u003Cmo\u003E\u2248\u003C/mo\u003E\u0060 | semantic web mathematics |\n\n## Windows, macOS, and Word\n\n- **Windows:** Use Character Map or enter U\u002B2248 in a Unicode-aware app.\n- **macOS:** Open Character Viewer with Control\u2013Command\u2013Space and search by name.\n- **Microsoft Word:** Type \\approx in an equation and press Space.\n\nFor a standalone character, direct Unicode is usually the simplest choice. For limits, fractions, matrices, scripts, or aligned equations, insert the symbol inside a native equation object or LaTeX expression so the surrounding structure remains editable.\n\n## LaTeX and web use\n\nUse \u0060\\approx\u0060 in math mode. On a UTF-8 web page, the literal character \u0060\u2248\u0060 is valid when it is only an isolated operator or label. Use MathML or a math renderer when the symbol participates in a structured expression.\n\n## Examples\n\n- \u0060\\pi\\approx 3.14159\u0060\n- \u00601/3\\approx 0.333\u0060\n\n## Common mistakes\n\n- Use the actual \u2248 character (U\u002B2248) when copying Approximately Equal To; a look-alike letter, punctuation mark, emoji, or image can break search, accessibility, and mathematical parsing.\n- When authoring LaTeX for Approximately Equal To, enter \\approx in math mode and confirm that it renders as \u2248; pasting a visually similar glyph can change the notation or fail in another renderer.\n- Verify that copy and paste preserves \u0060U\u002B2248\u0060 rather than a visually similar character.\n- Define the local mathematical convention when \u0060\u2248\u0060 can have more than one meaning.\n\n## Which format should you choose?\n\nUse Unicode for a single searchable character, LaTeX for editable authoring, and MathML or a native equation object for semantic structured mathematics. Test the final document, PDF, browser, or presentation rather than assuming every application uses the same shortcuts.\n## Choose the input method for this task\n\nFor **how to type approximately equal**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-degree-symbol",
    "title": "How to Type the Degree Symbol",
    "description": "Type \u00B0 correctly for angles and temperatures on major platforms.",
    "topic": "Typing symbols",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nThe degree symbol is **\u00B0**. Copy it directly: \u0060\u00B0\u0060. Its Unicode code point is \u0060U\u002B00B0\u0060. In LaTeX math mode, use \u0060^{\\circ}\u0060.\n\n## Type it on Windows\n\nFor ordinary text, copy the verified Unicode character or open Character Map and search for the symbol name. In Microsoft Word, you can insert it from the Symbol dialog or use a supported Unicode conversion. For a complete equation, insert an equation field and use the documented linear input method.\n\nDo not rely on an undocumented numeric keypad shortcut without verifying the resulting code point; shortcuts vary by application and keyboard settings.\n\n## Type it on macOS\n\nPress \u0060Control\u002BCommand\u002BSpace\u0060 to open Character Viewer, search for **degree**, and insert the character. Save frequently used symbols to favorites if the macOS version provides that option.\n\nFor structured equations in a LaTeX-aware editor, enter the command rather than pasting a standalone glyph.\n\n## Use it in Word, HTML, and LaTeX\n\nPlain text:\n\n\u0060\u0060\u0060text\n\u00B0\n\u0060\u0060\u0060\n\nLaTeX:\n\n\u0060\u0060\u0060latex\n^{\\circ}\n\u0060\u0060\u0060\n\nHTML can use the literal UTF-8 character or a verified numeric or named character reference. For a larger equation, preserve the surrounding structure instead of replacing every command with Unicode.\n\n## Meaning and correct usage\n\nDegree is a mathematical symbol, not merely a visual decoration. Define its role when the field or convention could change its meaning. Keep spacing and grouping consistent with the destination\u2019s equation style.\n\n## Troubleshoot input problems\n\nIf \u0060\u00B0\u0060 appears as a square box, change to a font with the glyph. If \u0060^{\\circ}\u0060 appears literally, the destination is not rendering LaTeX or the cursor is outside equation mode. If copying from a PDF produces a different character, return to the editable source or use the verified Unicode value \u0060U\u002B00B0\u0060.\n\n## Common mistakes\n\n- Replacing \u0060\u00B0\u0060 with a visually similar keyboard sequence or letter.\n- Copying the symbol from an image.\n- Using Unicode when the expression needs scalable equation structure.\n- Removing braces or math delimiters around a LaTeX expression.\n- Assuming the same keyboard shortcut works in every application.\n\n## Verify the result\n\nPaste the character into a Unicode inspector and confirm \u0060U\u002B00B0\u0060. Render the LaTeX command and compare its meaning, not only its shape. Finally, reopen or export the target document to confirm the symbol survives the full publishing workflow.\n## Choose the input method for this task\n\nFor **how to type degree symbol**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-infinity-symbol",
    "title": "How to Type the Infinity Symbol",
    "description": "Copy \u221E and insert it with Unicode, Word, Mac, Windows, HTML, and LaTeX.",
    "topic": "Typing symbols",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nThe infinity symbol is **\u221E**. Copy it directly: \u0060\u221E\u0060. Its Unicode code point is \u0060U\u002B221E\u0060. In LaTeX math mode, use \u0060\\infty\u0060.\n\n## Type it on Windows\n\nFor ordinary text, copy the verified Unicode character or open Character Map and search for the symbol name. In Microsoft Word, you can insert it from the Symbol dialog or use a supported Unicode conversion. For a complete equation, insert an equation field and use the documented linear input method.\n\nDo not rely on an undocumented numeric keypad shortcut without verifying the resulting code point; shortcuts vary by application and keyboard settings.\n\n## Type it on macOS\n\nPress \u0060Control\u002BCommand\u002BSpace\u0060 to open Character Viewer, search for **infinity**, and insert the character. Save frequently used symbols to favorites if the macOS version provides that option.\n\nFor structured equations in a LaTeX-aware editor, enter the command rather than pasting a standalone glyph.\n\n## Use it in Word, HTML, and LaTeX\n\nPlain text:\n\n\u0060\u0060\u0060text\n\u221E\n\u0060\u0060\u0060\n\nLaTeX:\n\n\u0060\u0060\u0060latex\n\\infty\n\u0060\u0060\u0060\n\nHTML can use the literal UTF-8 character or a verified numeric or named character reference. For a larger equation, preserve the surrounding structure instead of replacing every command with Unicode.\n\n## Meaning and correct usage\n\nInfinity is a mathematical symbol, not merely a visual decoration. Define its role when the field or convention could change its meaning. Keep spacing and grouping consistent with the destination\u2019s equation style.\n\n## Troubleshoot input problems\n\nIf \u0060\u221E\u0060 appears as a square box, change to a font with the glyph. If \u0060\\infty\u0060 appears literally, the destination is not rendering LaTeX or the cursor is outside equation mode. If copying from a PDF produces a different character, return to the editable source or use the verified Unicode value \u0060U\u002B221E\u0060.\n\n## Common mistakes\n\n- Replacing \u0060\u221E\u0060 with a visually similar keyboard sequence or letter.\n- Copying the symbol from an image.\n- Using Unicode when the expression needs scalable equation structure.\n- Removing braces or math delimiters around a LaTeX expression.\n- Assuming the same keyboard shortcut works in every application.\n\n## Verify the result\n\nPaste the character into a Unicode inspector and confirm \u0060U\u002B221E\u0060. Render the LaTeX command and compare its meaning, not only its shape. Finally, reopen or export the target document to confirm the symbol survives the full publishing workflow.\n## Choose the input method for this task\n\nFor **how to type infinity symbol**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-integral-symbol",
    "title": "How to Type the Integral Symbol",
    "description": "Insert integral signs in Word, Windows, macOS, HTML, Unicode, and LaTeX without losing limits, differentials, or mathematical structure.",
    "topic": "Calculus",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nThe integral symbol is **\u222B**, Unicode \u0060U\u002B222B\u0060. Copy the character for a standalone label, type \u0060\\int\u0060 in LaTeX math mode, or enter \u0060\\int\u0060 inside a Microsoft Word equation and press Space. A complete integral normally needs more than the glyph: it may include limits, an integrand, and a differential such as \u0060dx\u0060.\n\n## Copy and code formats\n\n| Format | Value | Best use |\n|---|---|---|\n| Unicode text | \u0060\u222B\u0060 | search, labels, and short plain-text references |\n| LaTeX | \u0060\\int\u0060 | editable mathematical expressions |\n| HTML entity | \u0060\u0026int;\u0060 | an isolated integral character in HTML source |\n| Decimal reference | \u0060\u0026#8747;\u0060 | HTML generated from numeric code points |\n| MathML operator | \u0060\u003Cmo\u003E\u222B\u003C/mo\u003E\u0060 | one operator inside structured web mathematics |\n\nCopying \u0060\u222B\u0060 does not automatically encode the upper limit, lower limit, integrand, or differential. Use an equation format when those parts matter.\n\n## Type the integral symbol on Windows\n\nOpen **Character Map**, choose a font with mathematical operators, search for \u201Cintegral,\u201D then copy \u0060\u222B\u0060. In applications with Unicode hexadecimal conversion, \u0060222B\u0060 may convert to the character, but the shortcut varies by application and should be tested rather than assumed.\n\nFor a calculation, use the application\u2019s equation editor. A plain character followed by improvised superscripts can look correct while remaining difficult to edit or interpret.\n\n## Type it in Microsoft Word\n\nInsert an equation with **Alt\u002B=**, type \u0060\\int\u0060, and press Space. For a definite integral, enter a structured expression such as:\n\n\u0060\u0060\u0060text\n\\int_0^1 x^2 \\, dx\n\u0060\u0060\u0060\n\nWord converts the command in equation mode. Outside an equation, the backslash text may remain literal. Verify that the lower limit is 0, the upper limit is 1, and the differential belongs to the integrand rather than ordinary prose.\n\n## Type it on macOS\n\nOpen Character Viewer with **Control\u2013Command\u2013Space**, search for \u201Cintegral,\u201D and insert \u0060\u222B\u0060. This is appropriate for a standalone character. In Pages, Keynote, a LaTeX editor, or another equation-aware application, prefer the native equation feature when the integral needs limits, fractions, or several aligned steps.\n\n## Write integrals in LaTeX\n\nUse \u0060\\int\u0060 inside math delimiters:\n\n\u0060\u0060\u0060latex\n\\[\n\\int_0^1 x^2\\,dx\n\\]\n\u0060\u0060\u0060\n\nFor an indefinite integral:\n\n\u0060\u0060\u0060latex\n\\[\n\\int f(x)\\,dx = F(x) \u002B C\n\\]\n\u0060\u0060\u0060\n\nBraces keep multi-character limits together. The small space before \u0060dx\u0060 separates the differential visually from the integrand. Multiple-integral or contour commands may depend on the selected package and renderer.\n\n## Use it in HTML and MathML\n\nA literal UTF-8 \u0060\u222B\u0060, \u0060\u0026int;\u0060, or \u0060\u0026#8747;\u0060 is suitable when the page needs only the character. For a complete accessible expression, use MathML or a tested mathematics renderer. Do not assemble limits with absolute positioning or separate spans whose reading order differs from the visual order.\n\n## Troubleshoot common failures\n\nIf \u0060\\int\u0060 appears as text, confirm that you are in Word equation mode or LaTeX math mode. If the limits attach to the wrong token, group them with braces. If copied text becomes a box, check the selected font. If an equation image is the only representation, provide an equivalent text description or structured markup. A missing \u0060dx\u0060 may not cause a rendering error, but it leaves the variable of integration unclear.\n\n## Common mistakes\n\n- Treating the glyph alone as a complete definite integral.\n- Using a tall letter or image that only resembles \u0060\u222B\u0060.\n- Leaving a multi-token limit ungrouped.\n- Omitting the differential or using a different variable in the differential.\n- Assuming a full LaTeX command set works identically in every browser renderer.\n\n## Verify the result\n\nCopy the displayed operator into a code-point inspector and confirm \u0060U\u002B222B\u0060. For a full expression, read the lower limit, upper limit, integrand, and differential in order. As a mathematical check, evaluate a simple example: \u0060\u222B\u2080\u00B9 x\u00B2 dx\u0060 should equal \u00601/3\u0060. The rendered notation and the computed result should both match the intended expression.\n## Choose the input method for this task\n\nFor **how to type integral symbol**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-not-equal-symbol",
    "title": "How to Type the Not Equal Symbol",
    "description": "Insert \u2260 across common operating systems, editors, web pages, and equations.",
    "topic": "Typing symbols",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nThe not equal symbol is **\u2260**. Copy it directly: \u0060\u2260\u0060. Its Unicode code point is \u0060U\u002B2260\u0060. In LaTeX math mode, use \u0060\\ne\u0060.\n\n## Type it on Windows\n\nFor ordinary text, copy the verified Unicode character or open Character Map and search for the symbol name. In Microsoft Word, you can insert it from the Symbol dialog or use a supported Unicode conversion. For a complete equation, insert an equation field and use the documented linear input method.\n\nDo not rely on an undocumented numeric keypad shortcut without verifying the resulting code point; shortcuts vary by application and keyboard settings.\n\n## Type it on macOS\n\nPress \u0060Control\u002BCommand\u002BSpace\u0060 to open Character Viewer, search for **not equal**, and insert the character. Save frequently used symbols to favorites if the macOS version provides that option.\n\nFor structured equations in a LaTeX-aware editor, enter the command rather than pasting a standalone glyph.\n\n## Use it in Word, HTML, and LaTeX\n\nPlain text:\n\n\u0060\u0060\u0060text\n\u2260\n\u0060\u0060\u0060\n\nLaTeX:\n\n\u0060\u0060\u0060latex\n\\ne\n\u0060\u0060\u0060\n\nHTML can use the literal UTF-8 character or a verified numeric or named character reference. For a larger equation, preserve the surrounding structure instead of replacing every command with Unicode.\n\n## Meaning and correct usage\n\nNot Equal is a mathematical symbol, not merely a visual decoration. Define its role when the field or convention could change its meaning. Keep spacing and grouping consistent with the destination\u2019s equation style.\n\n## Troubleshoot input problems\n\nIf \u0060\u2260\u0060 appears as a square box, change to a font with the glyph. If \u0060\\ne\u0060 appears literally, the destination is not rendering LaTeX or the cursor is outside equation mode. If copying from a PDF produces a different character, return to the editable source or use the verified Unicode value \u0060U\u002B2260\u0060.\n\n## Common mistakes\n\n- Replacing \u0060\u2260\u0060 with a visually similar keyboard sequence or letter.\n- Copying the symbol from an image.\n- Using Unicode when the expression needs scalable equation structure.\n- Removing braces or math delimiters around a LaTeX expression.\n- Assuming the same keyboard shortcut works in every application.\n\n## Verify the result\n\nPaste the character into a Unicode inspector and confirm \u0060U\u002B2260\u0060. Render the LaTeX command and compare its meaning, not only its shape. Finally, reopen or export the target document to confirm the symbol survives the full publishing workflow.\n## Choose the input method for this task\n\nFor **how to type not equal symbol**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-perpendicular-symbol",
    "title": "How to Type the Perpendicular Symbol",
    "description": "Type the perpendicular sign and distinguish it from bottom or contradiction notation.",
    "topic": "Geometry",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nThe **Perpendicular** symbol is **\u22A5**. Copy it as Unicode text, or use \u0060\\perp\u0060 inside a LaTeX math environment. Its code point is \u0060U\u002B22A5\u0060.\n\n## Copy and code formats\n\n| Format | Value | Best use |\n|---|---|---|\n| Unicode text | \u0060\u22A5\u0060 | plain text, labels, and search |\n| LaTeX | \u0060\\perp\u0060 | equations and authoring systems |\n| HTML entity | \u0060\u0026perp;\u0060 | web source |\n| MathML | \u0060\u003Cmo\u003E\u22A5\u003C/mo\u003E\u0060 | semantic web mathematics |\n\n## Windows, macOS, and Word\n\n- **Windows:** Use Character Map or enter U\u002B22A5 in a Unicode-aware app.\n- **macOS:** Open Character Viewer with Control\u2013Command\u2013Space and search by name.\n- **Microsoft Word:** Type \\perp in an equation and press Space.\n\nFor a standalone character, direct Unicode is usually the simplest choice. For limits, fractions, matrices, scripts, or aligned equations, insert the symbol inside a native equation object or LaTeX expression so the surrounding structure remains editable.\n\n## LaTeX and web use\n\nUse \u0060\\perp\u0060 in math mode. On a UTF-8 web page, the literal character \u0060\u22A5\u0060 is valid when it is only an isolated operator or label. Use MathML or a math renderer when the symbol participates in a structured expression.\n\n## Examples\n\n- \u0060AB\\perp CD\u0060\n\n## Common mistakes\n\n- Use the actual \u22A5 character (U\u002B22A5) when copying Perpendicular; a look-alike letter, punctuation mark, emoji, or image can break search, accessibility, and mathematical parsing.\n- When authoring LaTeX for Perpendicular, enter \\perp in math mode and confirm that it renders as \u22A5; pasting a visually similar glyph can change the notation or fail in another renderer.\n- Verify that copy and paste preserves \u0060U\u002B22A5\u0060 rather than a visually similar character.\n- Define the local mathematical convention when \u0060\u22A5\u0060 can have more than one meaning.\n\n## Which format should you choose?\n\nUse Unicode for a single searchable character, LaTeX for editable authoring, and MathML or a native equation object for semantic structured mathematics. Test the final document, PDF, browser, or presentation rather than assuming every application uses the same shortcuts.\n## Choose the input method for this task\n\nFor **how to type perpendicular symbol**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-pi-symbol",
    "title": "How to Type the Pi Symbol",
    "description": "Copy \u03C0 and type the pi symbol on Windows, Mac, Word, Google Docs, HTML, and LaTeX without confusing it with a Latin letter.",
    "topic": "Typing symbols",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nThe lowercase Greek letter pi is **\u03C0**. You can copy it directly here: \u0060\u03C0\u0060.\n\nUse \u0060\u03C0\u0060 when you need a plain-text character. Use \u0060\\pi\u0060 inside a LaTeX math expression. The Unicode code point is \u0060U\u002B03C0\u0060, and the HTML named character reference is \u0060\u0026pi;\u0060.\n\n## Pi formats at a glance\n\n| Format | Input | Result | Best use |\n|---|---|---|---|\n| Unicode | \u0060\u03C0\u0060 | \u03C0 | Plain text, labels, messages, and search |\n| LaTeX | \u0060\\pi\u0060 | \u03C0 | Editable equations |\n| HTML | \u0060\u0026pi;\u0060 or \u0060\u0026#960;\u0060 | \u03C0 | HTML source |\n| MathML | \u0060\u003Cmi\u003E\u03C0\u003C/mi\u003E\u0060 | \u03C0 | Semantic web mathematics |\n\nThe character \u0060\u03C0\u0060 is a Greek letter. In mathematics it commonly represents the circle constant, but the same letter can be used for other quantities when a document defines it differently.\n\n## Type \u03C0 on Windows\n\nThe most reliable Windows method depends on the application.\n\n1. **Copy and paste:** copy \u0060\u03C0\u0060 from this page and paste it into any Unicode-capable field.\n2. **Microsoft Word equation:** insert an equation, type \u0060\\pi\u0060, and press Space. Word converts the command inside the equation object.\n3. **Character Map:** open Character Map, choose a font that includes Greek characters, find Greek small letter pi, and copy it.\n4. **Word Unicode conversion:** in compatible Word text, type \u006003C0\u0060, then press \u0060Alt\u002BX\u0060 to convert the code to \u03C0. Pressing \u0060Alt\u002BX\u0060 again displays the code.\n\nDo not expect a generic numeric Alt code to work consistently across applications. Traditional Alt-code behavior depends on the active code page and is not a universal Unicode input method.\n\n## Type \u03C0 on Mac\n\nPress \u0060Control\u002BCommand\u002BSpace\u0060 to open Character Viewer. Search for **pi**, choose the Greek small letter \u03C0, and insert it.\n\nFor repeated use, you can also add a macOS text replacement, such as replacing a unique shortcut like \u0060;pi\u0060 with \u0060\u03C0\u0060. Choose a shortcut that will not appear naturally in normal writing.\n\nIn equation editors that accept LaTeX-style input, use \u0060\\pi\u0060 rather than inserting the character manually. The equation editor can then apply mathematical spacing and keep the expression editable.\n\n## Type \u03C0 in Word, Google Docs, and presentations\n\n### Microsoft Word\n\nFor a standalone character in prose, paste \u0060\u03C0\u0060 or use \u006003C0\u0060 followed by \u0060Alt\u002BX\u0060. For an equation, insert a Word equation and enter \u0060\\pi\u0060.\n\nExample equation source:\n\n\u0060\u0060\u0060latex\nA=\\pi r^2\n\u0060\u0060\u0060\n\n### Google Docs\n\nFor normal text, paste \u0060\u03C0\u0060. For an equation, choose **Insert \u2192 Equation**, then insert the Greek letter from the equation toolbar or enter it through a supported equation workflow. Google Docs does not treat every LaTeX command exactly like a full LaTeX compiler, so verify the rendered result.\n\n### PowerPoint and Keynote\n\nUse a native equation object when \u03C0 appears inside a fraction, exponent, matrix, or multi-line expression. Use the Unicode character only when it is a simple label or part of ordinary text.\n\n## Use \u03C0 in LaTeX\n\nEnter \u0060\\pi\u0060 in math mode:\n\n\u0060\u0060\u0060latex\nC=2\\pi r\n\u0060\u0060\u0060\n\n\u0060\u0060\u0060latex\nA=\\pi r^2\n\u0060\u0060\u0060\n\nUppercase pi is a different character and command. \u0060\\Pi\u0060 produces **\u03A0**, which is commonly used for product notation or as an uppercase Greek variable. Do not substitute \u03A0 for \u03C0 in the circle formulas above.\n\n## Use \u03C0 in HTML and MathML\n\nFor ordinary HTML text, all of these can represent the same character:\n\n\u0060\u0060\u0060html\n\u03C0\n\u0026pi;\n\u0026#960;\n\u0026#x03C0;\n\u0060\u0060\u0060\n\nA literal UTF-8 character is usually easiest to read in modern source files. A named or numeric reference can be useful when source conventions require it.\n\nInside semantic MathML, pi is normally an identifier:\n\n\u0060\u0060\u0060html\n\u003Cmath\u003E\n  \u003Cmi\u003E\u03C0\u003C/mi\u003E\n  \u003Cmsup\u003E\u003Cmi\u003Er\u003C/mi\u003E\u003Cmn\u003E2\u003C/mn\u003E\u003C/msup\u003E\n\u003C/math\u003E\n\u0060\u0060\u0060\n\nUse \u0060\u003Cmi\u003E\u0060 rather than \u0060\u003Cmo\u003E\u0060 because \u03C0 is functioning as an identifier or constant, not as an operator.\n\n## Pi symbol versus similar characters\n\nDo not replace \u03C0 with any of these:\n\n- Latin lowercase \u0060p\u0060;\n- Greek uppercase \u0060\u03A0\u0060;\n- product operator \u0060\u220F\u0060;\n- an image of the symbol;\n- a decorative font glyph whose underlying character is not U\u002B03C0.\n\nThey may look related, but their encoded identity and mathematical meaning are different. Search, copying, screen readers, and equation conversion can all fail when a look-alike is used.\n\n## Troubleshooting\n\n- **A square or missing glyph appears:** change to a font with Greek character coverage.\n- **\u0060\\pi\u0060 stays as text:** make sure you are inside an equation or LaTeX math environment.\n- **The character changes after export:** inspect the exported PDF or document and confirm that the font is embedded or substituted correctly.\n- **A system reads \u201Cp\u201D:** check that the source contains U\u002B03C0, not the Latin letter.\n\n## Which method should you choose?\n\nUse \u0060\u03C0\u0060 for plain text and copy-paste tasks. Use \u0060\\pi\u0060 for editable LaTeX and compatible equation editors. Use MathML when the expression is published as semantic web mathematics. Always verify the final document or page, because input shortcuts and rendering behavior vary by application.\n## Choose the input method for this task\n\nFor **how to type pi symbol**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-square-root-symbol",
    "title": "How to Type the Square Root Symbol",
    "description": "Copy \u221A and type square roots on Windows, Mac, Word, Google Docs, HTML, MathML, and LaTeX with the correct radicand.",
    "topic": "Typing symbols",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nThe square root symbol is **\u221A**. Copy it here: \u0060\u221A\u0060.\n\nUse the Unicode character only for a standalone symbol or simple plain text. For an expression such as the square root of \u0060x\u002B1\u0060, use \u0060\\sqrt{x\u002B1}\u0060 in LaTeX, a native equation editor, or \u0060\u003Cmsqrt\u003E\u0060 in MathML so the radical bar covers the entire radicand.\n\n## Square-root formats\n\n| Format | Input | Best use |\n|---|---|---|\n| Unicode | \u0060\u221A\u0060 | A standalone radical sign in plain text |\n| LaTeX | \u0060\\sqrt{x\u002B1}\u0060 | Editable mathematical equations |\n| HTML character | \u0060\u0026radic;\u0060 or \u0060\u0026#8730;\u0060 | The literal \u221A character in HTML text |\n| MathML | \u0060\u003Cmsqrt\u003E\u003Cmi\u003Ex\u003C/mi\u003E\u003C/msqrt\u003E\u0060 | Semantic web mathematics |\n\nThe Unicode code point for \u221A is \u0060U\u002B221A\u0060.\n\n## Type \u221A on Windows\n\n- **Copy and paste:** copy \u0060\u221A\u0060 from this page.\n- **Word Unicode conversion:** type \u0060221A\u0060, then press \u0060Alt\u002BX\u0060 in compatible Word text.\n- **Character Map:** search for **square root** or inspect the Mathematical Operators block.\n- **Word equation:** insert an equation and enter \u0060\\sqrt{x}\u0060.\n\nUse the equation method when the expression contains more than a single following character. Typing \u0060\u221Ax\u002B1\u0060 in plain text can be ambiguous: a reader may not know whether the root applies only to \u0060x\u0060 or to \u0060x\u002B1\u0060.\n\n## Type \u221A on Mac\n\nPress \u0060Control\u002BCommand\u002BSpace\u0060 to open Character Viewer, search for **square root**, and insert \u221A.\n\nFor an equation in Pages or Keynote, use the equation feature and enter \u0060\\sqrt{x\u002B1}\u0060. For a standalone symbol in ordinary prose, Character Viewer or copy-paste is appropriate.\n\n## Type a square root in Microsoft Word\n\nInsert an equation and type:\n\n\u0060\u0060\u0060latex\n\\sqrt{x\u002B1}\n\u0060\u0060\u0060\n\nPress Space when required to convert the command. Word creates a structured radical whose bar expands over the radicand.\n\nFor an nth root, use the equation structure supported by Word, for example a command equivalent to:\n\n\u0060\u0060\u0060latex\n\\sqrt[3]{x}\n\u0060\u0060\u0060\n\nVerify the result because Word\u2019s accepted linear syntax can differ from a complete LaTeX installation.\n\n## Type a square root in Google Docs\n\nChoose **Insert \u2192 Equation**, then select the square-root structure from the equation toolbar. Place the full expression inside the root placeholder.\n\nPasting \u0060\u221A\u0060 before text is adequate only when the scope is obvious and no editable equation structure is needed.\n\n## Use square roots in LaTeX\n\nBasic square root:\n\n\u0060\u0060\u0060latex\n\\sqrt{x}\n\u0060\u0060\u0060\n\nRoot of a longer expression:\n\n\u0060\u0060\u0060latex\n\\sqrt{x^2\u002By^2}\n\u0060\u0060\u0060\n\nCube root:\n\n\u0060\u0060\u0060latex\n\\sqrt[3]{x}\n\u0060\u0060\u0060\n\nNested root:\n\n\u0060\u0060\u0060latex\n\\sqrt{1\u002B\\sqrt{x}}\n\u0060\u0060\u0060\n\nAlways group the complete radicand inside braces. \u0060\\sqrt x\u002B1\u0060 normally applies the root only to the next token, not to the whole sum.\n\n## Use square roots in HTML and MathML\n\nA literal character or HTML reference produces only the \u221A glyph:\n\n\u0060\u0060\u0060html\n\u0026radic;x\n\u0060\u0060\u0060\n\nThis does not create a scalable radical bar over a complex expression. For semantic structure, use MathML:\n\n\u0060\u0060\u0060html\n\u003Cmath\u003E\n  \u003Cmsqrt\u003E\n    \u003Cmrow\u003E\u003Cmi\u003Ex\u003C/mi\u003E\u003Cmo\u003E\u002B\u003C/mo\u003E\u003Cmn\u003E1\u003C/mn\u003E\u003C/mrow\u003E\n  \u003C/msqrt\u003E\n\u003C/math\u003E\n\u0060\u0060\u0060\n\nFor an indexed root, MathML uses \u0060\u003Cmroot\u003E\u0060 with the radicand first and the index second.\n\n## Square root versus radical and check mark\n\nDo not confuse:\n\n- square root \u0060\u221A\u0060 (\u0060U\u002B221A\u0060);\n- check mark \u0060\u2713\u0060;\n- radical expressions that include a vinculum over the radicand;\n- the mathematical function \u0060sqrt()\u0060 used in programming languages.\n\nThe term **radical sign** refers to the \u221A shape. A complete radical expression also includes the radicand and sometimes an index.\n\n## Troubleshoot and common mistakes\n\n- Writing \u0060\u221Ax\u002B1\u0060 when you mean \u0060\u221A(x\u002B1)\u0060.\n- Using a check mark instead of the square-root character.\n- Typing a plain \u221A before a fraction or matrix and expecting the bar to scale.\n- Omitting braces in LaTeX around a multi-token radicand.\n- Assuming \u0060sqrt()\u0060 source code is mathematical typesetting.\n\n## Final recommendation\n\nCopy \u0060\u221A\u0060 for a standalone plain-text symbol. Use \u0060\\sqrt{...}\u0060, a native equation object, or MathML for a real mathematical expression. Confirm exactly which terms are under the radical before publishing or submitting the work.\n## Choose the input method for this task\n\nFor **how to type square root symbol**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-subset-symbol",
    "title": "How to Type the Subset Symbol",
    "description": "Type and distinguish subset, proper subset, and subset-or-equal symbols across common platforms.",
    "topic": "Set theory",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nThe **Subset / Proper Subset** symbol is **\u2282**. Copy it as Unicode text, or use \u0060\\subset\u0060 inside a LaTeX math environment. Its code point is \u0060U\u002B2282\u0060.\n\n## Copy and code formats\n\n| Format | Value | Best use |\n|---|---|---|\n| Unicode text | \u0060\u2282\u0060 | plain text, labels, and search |\n| LaTeX | \u0060\\subset\u0060 | equations and authoring systems |\n| HTML entity | \u0060\u0026sub;\u0060 | web source |\n| MathML | \u0060\u003Cmo\u003E\u2282\u003C/mo\u003E\u0060 | semantic web mathematics |\n\n## Windows, macOS, and Word\n\n- **Windows:** Use Character Map or enter U\u002B2282 in a Unicode-aware app.\n- **macOS:** Open Character Viewer with Control\u2013Command\u2013Space and search by name.\n- **Microsoft Word:** Type \\subset in an equation and press Space.\n\nFor a standalone character, direct Unicode is usually the simplest choice. For limits, fractions, matrices, scripts, or aligned equations, insert the symbol inside a native equation object or LaTeX expression so the surrounding structure remains editable.\n\n## LaTeX and web use\n\nUse \u0060\\subset\u0060 in math mode. On a UTF-8 web page, the literal character \u0060\u2282\u0060 is valid when it is only an isolated operator or label. Use MathML or a math renderer when the symbol participates in a structured expression.\n\n## Examples\n\n- \u0060A\\subset B\u0060\n\n## Common mistakes\n\n- Use the actual \u2282 character (U\u002B2282) when copying Subset / Proper Subset; a look-alike letter, punctuation mark, emoji, or image can break search, accessibility, and mathematical parsing.\n- When authoring LaTeX for Subset / Proper Subset, enter \\subset in math mode and confirm that it renders as \u2282; pasting a visually similar glyph can change the notation or fail in another renderer.\n- Verify that copy and paste preserves \u0060U\u002B2282\u0060 rather than a visually similar character.\n- Define the local mathematical convention when \u0060\u2282\u0060 can have more than one meaning.\n\n## Which format should you choose?\n\nUse Unicode for a single searchable character, LaTeX for editable authoring, and MathML or a native equation object for semantic structured mathematics. Test the final document, PDF, browser, or presentation rather than assuming every application uses the same shortcuts.\n## Choose the input method for this task\n\nFor **how to type subset symbol**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "how-to-type-summation-symbol",
    "title": "How to Type the Summation Symbol",
    "description": "Create summation notation with limits in plain text, Word equations, Markdown, and LaTeX.",
    "topic": "Calculus",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nThe **Summation** symbol is **\u2211**. Copy it as Unicode text, or use \u0060\\sum\u0060 inside a LaTeX math environment. Its code point is \u0060U\u002B2211\u0060.\n\n## Copy and code formats\n\n| Format | Value | Best use |\n|---|---|---|\n| Unicode text | \u0060\u2211\u0060 | plain text, labels, and search |\n| LaTeX | \u0060\\sum\u0060 | equations and authoring systems |\n| HTML entity | \u0060\u0026sum;\u0060 | web source |\n| MathML | \u0060\u003Cmo\u003E\u2211\u003C/mo\u003E\u0060 | semantic web mathematics |\n\n## Windows, macOS, and Word\n\n- **Windows:** Use Character Map or enter U\u002B2211 in a Unicode-aware app.\n- **macOS:** Open Character Viewer with Control\u2013Command\u2013Space and search by name.\n- **Microsoft Word:** Type \\sum in an equation and press Space.\n\nFor a standalone character, direct Unicode is usually the simplest choice. For limits, fractions, matrices, scripts, or aligned equations, insert the symbol inside a native equation object or LaTeX expression so the surrounding structure remains editable.\n\n## LaTeX and web use\n\nUse \u0060\\sum\u0060 in math mode. On a UTF-8 web page, the literal character \u0060\u2211\u0060 is valid when it is only an isolated operator or label. Use MathML or a math renderer when the symbol participates in a structured expression.\n\n## Examples\n\n- \u0060\\sum_{i=1}^{n}i\u0060\n- \u0060\\sum_{k=0}^{\\infty}ar^k\u0060\n\n## Common mistakes\n\n- Use the actual \u2211 character (U\u002B2211) when copying Summation; a look-alike letter, punctuation mark, emoji, or image can break search, accessibility, and mathematical parsing.\n- When authoring LaTeX for Summation, enter \\sum in math mode and confirm that it renders as \u2211; pasting a visually similar glyph can change the notation or fail in another renderer.\n- Verify that copy and paste preserves \u0060U\u002B2211\u0060 rather than a visually similar character.\n- Define the local mathematical convention when \u0060\u2211\u0060 can have more than one meaning.\n\n## Which format should you choose?\n\nUse Unicode for a single searchable character, LaTeX for editable authoring, and MathML or a native equation object for semantic structured mathematics. Test the final document, PDF, browser, or presentation rather than assuming every application uses the same shortcuts.\n## Choose the input method for this task\n\nFor **how to type summation symbol**, first decide whether the destination needs one searchable Unicode character or a structured equation. Copy the Unicode character for prose, labels, filenames, and search fields. Use the documented LaTeX command or a native equation object when scripts, fractions, limits, or scalable delimiters are part of the expression.\n\n## Verify the exact character\n\n1. Paste the result into the real destination, not only a preview field.\n2. Inspect the Unicode code point or equation source so a look-alike cannot pass unnoticed.\n3. Reopen the exported document and test selection, search, and copy-and-paste behavior.\n4. When the symbol has several field-specific meanings, define the intended meaning beside its first use.\n\n## Troubleshoot a failed input\n\nIf the shortcut remains literal text, confirm that the cursor is inside the correct equation mode. If a missing-glyph box appears, switch to a font with the required character. If export changes the character, compare the source before and after export and use the Unicode value or structured equation source as the reference.\n"
  },
  {
    "slug": "latex-in-google-docs",
    "title": "How to Use LaTeX-Style Equations in Google Docs",
    "description": "Understand which LaTeX-like shortcuts work in Google Docs and when to use an equation add-on.",
    "topic": "Google Docs",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Recommended method\n\nFor **Google Docs**, choose the input method according to the complexity of the mathematics. Use the built-in equation editor for supported structures or a trusted add-on when a full LaTeX conversion workflow is required.\n\n## Best method by task\n\n| Task | Recommended format |\n|---|---|\n| One standalone symbol | Unicode text or the application\u2019s symbol picker |\n| Fraction, root, matrix, limit, or aligned equation | Native equation object or supported LaTeX input |\n| Content reused in several systems | Keep a separate LaTeX or MathML source |\n| Accessible web publication | Semantic MathML or an accessible renderer |\n\n## Reliable workflow\n\n1. Create a one-line test containing the most demanding structure you need.\n2. Confirm it remains editable after save, reopen, copy, and paste.\n3. Export once to the final delivery format and inspect fonts, line wrapping, and equation placement.\n4. Test on mobile or another device when the document will be shared widely.\n\n## Copy-and-paste checks\n\nPlace the cursor inside the result. If it behaves like one image, the mathematical structure may have been lost. Copy the expression into plain text to identify the underlying Unicode characters, and keep the structured source separately when plain text cannot represent the layout.\n\n## Common mistakes\n\n- Constructing a complex equation from individually positioned characters and spaces.\n- Assuming every keyboard layout or application version supports the same shortcut.\n- Using a hyphen, letter, or decorative glyph in place of the intended mathematical code point.\n- Publishing a screenshot without an editable source or meaningful alternative text.\n\n## Final recommendation\n\nUse the simplest format that preserves the required meaning. Unicode is efficient for isolated symbols; a native equation object, LaTeX, or MathML is safer for structured mathematics in Google Docs.\n## Validate the equation in Google Docs\n\nAfter inserting the expression, close and reopen the document before treating the equation as finished. Confirm that fractions, roots, superscripts, subscripts, and Greek letters still appear inside the equation object rather than as loose text. Export one test page to PDF and select the equation: editable or searchable text is preferable to a flattened screenshot when the document must remain accessible.\n\nGoogle Docs support for LaTeX-style input is not identical to a full TeX engine. Test the exact command in the built-in equation editor, and use an add-on only when the document needs structures the editor cannot represent reliably. Keep the original LaTeX source beside complex equations so another editor can reproduce them later.\n"
  },
  {
    "slug": "math-symbols-in-email",
    "title": "How to Use Math Symbols in Email",
    "description": "Choose between Unicode, plain-text fallbacks, LaTeX source, and attached documents when sending mathematical notation by email.",
    "topic": "Applications",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Recommended method\n\nFor **email**, choose the input method according to the complexity of the mathematics. Prefer plain Unicode for short, unambiguous notation. Attach or link a properly typeset document for complex equations.\n\n## Best method by task\n\n| Task | Recommended format |\n|---|---|\n| One standalone symbol | Unicode text or the application\u2019s symbol picker |\n| Fraction, root, matrix, limit, or aligned equation | Native equation object or supported LaTeX input |\n| Content reused in several systems | Keep a separate LaTeX or MathML source |\n| Accessible web publication | Semantic MathML or an accessible renderer |\n\n## Reliable workflow\n\n1. Create a one-line test containing the most demanding structure you need.\n2. Confirm it remains editable after save, reopen, copy, and paste.\n3. Export once to the final delivery format and inspect fonts, line wrapping, and equation placement.\n4. Test on mobile or another device when the document will be shared widely.\n\n## Copy-and-paste checks\n\nPlace the cursor inside the result. If it behaves like one image, the mathematical structure may have been lost. Copy the expression into plain text to identify the underlying Unicode characters, and keep the structured source separately when plain text cannot represent the layout.\n\n## Common mistakes\n\n- Constructing a complex equation from individually positioned characters and spaces.\n- Assuming every keyboard layout or application version supports the same shortcut.\n- Using a hyphen, letter, or decorative glyph in place of the intended mathematical code point.\n- Publishing a screenshot without an editable source or meaningful alternative text.\n\n## Final recommendation\n\nUse the simplest format that preserves the required meaning. Unicode is efficient for isolated symbols; a native equation object, LaTeX, or MathML is safer for structured mathematics in email.\n## Test the message in the receiving format\n\nEmail clients differ in font coverage, HTML sanitisation, line wrapping, and support for embedded mathematics. For a short standalone symbol, Unicode text is usually the most portable choice. For a multi-line derivation or notation that depends on exact alignment, attach a PDF and include a concise plain-text summary in the message body. Raw LaTeX is appropriate only when the recipient expects source code.\n\nSend a test message to a second account and inspect it in desktop, web, and mobile clients. Verify that minus signs, arrows, subscripts, and Greek letters have not changed, and that copied text retains the intended code points. Avoid using an image as the only carrier of essential information; include the equation in accessible text or describe its meaning nearby.\n"
  },
  {
    "slug": "math-symbols-in-excel",
    "title": "How to Use Math Symbols in Excel",
    "description": "Insert, copy, calculate with, and safely export mathematical symbols in Microsoft Excel cells, formulas, charts, and labels.",
    "topic": "Software input",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Recommended method\n\nFor **Excel**, choose the input method according to the complexity of the mathematics. Use Unicode in labels and cells, but keep calculations in formulas and document the meaning of any decorative notation.\n\n## Best method by task\n\n| Task | Recommended format |\n|---|---|\n| One standalone symbol | Unicode text or the application\u2019s symbol picker |\n| Fraction, root, matrix, limit, or aligned equation | Native equation object or supported LaTeX input |\n| Content reused in several systems | Keep a separate LaTeX or MathML source |\n| Accessible web publication | Semantic MathML or an accessible renderer |\n\n## Reliable workflow\n\n1. Create a one-line test containing the most demanding structure you need.\n2. Confirm it remains editable after save, reopen, copy, and paste.\n3. Export once to the final delivery format and inspect fonts, line wrapping, and equation placement.\n4. Test on mobile or another device when the document will be shared widely.\n\n## Copy-and-paste checks\n\nPlace the cursor inside the result. If it behaves like one image, the mathematical structure may have been lost. Copy the expression into plain text to identify the underlying Unicode characters, and keep the structured source separately when plain text cannot represent the layout.\n\n## Common mistakes\n\n- Constructing a complex equation from individually positioned characters and spaces.\n- Assuming every keyboard layout or application version supports the same shortcut.\n- Using a hyphen, letter, or decorative glyph in place of the intended mathematical code point.\n- Publishing a screenshot without an editable source or meaningful alternative text.\n\n## Final recommendation\n\nUse the simplest format that preserves the required meaning. Unicode is efficient for isolated symbols; a native equation object, LaTeX, or MathML is safer for structured mathematics in Excel.\n## Separate display symbols from calculation syntax\n\nExcel may display a mathematical symbol in a cell even though formulas require a different operator. For example, a typographic multiplication sign is suitable for a label, while a worksheet formula normally uses an asterisk. Keep display notation in headings, chart labels, and explanatory cells; keep calculation syntax inside formulas, named expressions, and imported data transformations.\n\nTest sorting, filtering, CSV export, and copy-and-paste before distributing the workbook. CSV does not preserve fonts or equation objects, and a downstream system may normalize or reject uncommon Unicode characters. When a symbol identifies a unit, category, or status, store a plain-text code in a separate column so the workbook remains machine-readable as well as visually clear.\n"
  },
  {
    "slug": "math-symbols-in-html",
    "title": "How to Use Math Symbols in HTML",
    "description": "Choose between literal Unicode, named entities, numeric references, and MathML.",
    "topic": "Web \u0026 code",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Use UTF-8 and literal Unicode\n\nDeclare UTF-8 early in the document and use the actual character when it is readable in source:\n\n\u0060\u0060\u0060html\n\u003Cmeta charset=\u0022utf-8\u0022\u003E\n\u003Cp\u003Ex \u2264 10, \u03B8 = 45\u00B0, and \u03C0 \u2248 3.14159.\u003C/p\u003E\n\u0060\u0060\u0060\n\nLiteral Unicode is usually clearer than memorizing entities. The file, server headers, editor, and build pipeline must all preserve UTF-8.\n\n## Use references when source constraints require them\n\nNamed or numeric references can represent the same character:\n\n\u0060\u0060\u0060html\n\u003Cp\u003E\u0026pi; \u0026le; \u0026#8734; \u0026#x2212;\u003C/p\u003E\n\u0060\u0060\u0060\n\nVerify the decoded code point. An entity solves source encoding, not mathematical structure; \u0060\u0026radic;\u0060 is still only a standalone radical character.\n\n## Use MathML for structured equations\n\nFor a real fraction or root, use semantic markup rather than visually arranging characters:\n\n\u0060\u0060\u0060html\n\u003Cmath xmlns=\u0022http://www.w3.org/1998/Math/MathML\u0022\u003E\n  \u003Cmfrac\u003E\u003Cmi\u003Ea\u003C/mi\u003E\u003Cmi\u003Eb\u003C/mi\u003E\u003C/mfrac\u003E\n\u003C/math\u003E\n\u0060\u0060\u0060\n\nMathML elements express the roles of numerator, denominator, operators, scripts, and tables. Test the exact elements and browser versions required by the project.\n\n## Add accessible context\n\nDo not hide the meaning in a background image or icon font. Use nearby prose for important equations, and ensure an equation image has an equivalent text alternative. When a symbol\u2019s meaning depends on the field, define it in the surrounding text instead of relying on its spoken character name.\n\n## Style without changing meaning\n\nUse CSS for size, spacing, and overflow, but do not reconstruct formulas with absolute positioning. Provide horizontal scrolling for wide display equations on mobile. Choose fonts with adequate mathematical glyph coverage and test fallback fonts.\n\n## Troubleshoot browser output\n\nIf an entity appears literally, check the ampersand, semicolon, and escaping performed by the template engine. If a symbol becomes a box, inspect font coverage. If MathML tags appear as text, confirm they were not HTML-escaped. If the equation overflows, fix the container rather than shrinking it until unreadable.\n\n## Verify production output\n\nInspect the deployed HTML, not only the source template. Copy symbols back out, examine the accessibility tree, resize the viewport, and test with CSS and JavaScript disabled where practical. Confirm that the output still communicates the same equation when fonts or rendering engines differ.\n\n## Editorial test case\n\nThe review copied the rendered minus sign, hyphen-minus, pi character, and MathML fraction back from the browser into plain text. Code-point inspection confirmed that visual similarity did not make the characters interchangeable. The page was also checked with styling removed so that the mathematical structure remained understandable without relying on color, absolute positioning, or a particular font.\n"
  },
  {
    "slug": "math-symbols-in-presentations",
    "title": "How to Use Math Symbols in Slides",
    "description": "Create readable equations for presentation slides, preserve editability, and avoid low-resolution formula screenshots.",
    "topic": "Applications",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Recommended method\n\nFor **presentation software**, choose the input method according to the complexity of the mathematics. Use native equation objects for formulas and Unicode only for isolated labels or bullets.\n\n## Best method by task\n\n| Task | Recommended format |\n|---|---|\n| One standalone symbol | Unicode text or the application\u2019s symbol picker |\n| Fraction, root, matrix, limit, or aligned equation | Native equation object or supported LaTeX input |\n| Content reused in several systems | Keep a separate LaTeX or MathML source |\n| Accessible web publication | Semantic MathML or an accessible renderer |\n\n## Reliable workflow\n\n1. Create a one-line test containing the most demanding structure you need.\n2. Confirm it remains editable after save, reopen, copy, and paste.\n3. Export once to the final delivery format and inspect fonts, line wrapping, and equation placement.\n4. Test on mobile or another device when the document will be shared widely.\n\n## Copy-and-paste checks\n\nPlace the cursor inside the result. If it behaves like one image, the mathematical structure may have been lost. Copy the expression into plain text to identify the underlying Unicode characters, and keep the structured source separately when plain text cannot represent the layout.\n\n## Common mistakes\n\n- Constructing a complex equation from individually positioned characters and spaces.\n- Assuming every keyboard layout or application version supports the same shortcut.\n- Using a hyphen, letter, or decorative glyph in place of the intended mathematical code point.\n- Publishing a screenshot without an editable source or meaningful alternative text.\n\n## Final recommendation\n\nUse the simplest format that preserves the required meaning. Unicode is efficient for isolated symbols; a native equation object, LaTeX, or MathML is safer for structured mathematics in presentation software.\n## Check the slide at presentation size\n\nA symbol that looks correct while editing can become unreadable on a projector. Run the slide show at full screen, verify contrast from several metres away, and enlarge subscripts, superscripts, fraction bars, and limit annotations until they remain distinguishable. Use a native equation object when the expression may need revision; use SVG only when the slide application preserves vector quality and the source equation is stored separately.\n\nAlso test the exported PDF and any shared web version. Confirm that the equation is not cropped, recoloured, substituted with a missing glyph, or converted into a blurry bitmap. Decorative animation should never separate a mathematical operator from its operands or reveal an equation in an order that changes its meaning.\n"
  },
  {
    "slug": "how-to-use-pythagorean-theorem",
    "title": "How to Use the Pythagorean Theorem",
    "description": "Use the Pythagorean theorem for right triangles, identify the hypotenuse, solve for a missing side, and verify the geometry.",
    "topic": "Geometry",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nTo **use pythagorean theorem**, first classify the problem, preserve the meaning of every transformation, and verify the final result in the original statement. For the worked example \u0060a^2 \u002B b^2 = c^2\u0060, the result is **c = 5**. The method below shows why that result follows rather than presenting it as an unexplained calculator output.\n\n## Identify the problem before calculating\n\nThe theorem applies only to right triangles. The side opposite the right angle is the hypotenuse c and must be the longest side. This classification step matters because a familiar-looking expression can require a different rule when its structure changes. Write down any domain restriction, unit, dimension, or reference value before manipulating the symbols.\n\nA diagram should encode the assumptions used by the formula. Mark the right angle, known lengths, and requested quantity before substituting.\n\n## Step-by-step method\n\n1. Confirm the triangle has a right angle.\n2. Label the hypotenuse c and the legs a and b.\n3. Substitute known side lengths with units.\n4. Solve for the missing squared length, then take the nonnegative square root.\n5. Check that the hypotenuse is longest and the units are sensible.\n\nEach line should answer two questions: what operation was performed, and why that operation preserves or correctly changes the mathematical object. When a calculator or browser tool is used, keep the original input visible so the output can be compared with the source problem.\n\n## Worked example\n\n1. For legs 3 and 4, write 3\u00B2\u002B4\u00B2=c\u00B2.\n2. Compute 9\u002B16=25.\n3. Take the nonnegative square root to get c=5.\n4. The 3-4-5 triangle satisfies the theorem exactly.\n\nThe result **c = 5** is not accepted solely because it looks plausible. The example retains the intermediate quantities that make a sign, denominator, exponent, dimension, or rounding mistake visible.\n\n## Read the visual explanation\n\nThe three diagrams on this page separate the concept, the execution sequence, and the final check. Use the concept diagram to recognize the structure, the workflow diagram while solving, and the verification diagram after obtaining a candidate result. The diagrams are SVG files, so text remains selectable and the graphics stay sharp on mobile screens and when printed.\n\n## Common mistakes\n\n- Using the theorem on a non-right triangle.\n- Calling a leg c.\n- Keeping a negative length after taking a square root.\n\nA reliable correction strategy is to return to the earliest line where the mathematical object changed. Repeating only the final arithmetic often reproduces the same hidden setup error.\n\n## Verify the result\n\nCheck 3\u00B2\u002B4\u00B2=5\u00B2 and confirm 9\u002B16=25. Also inspect whether the answer has the correct sign, scale, units, dimension, and domain. For an equation, substitution is decisive. For an inverse pair such as differentiation and integration, apply the inverse operation. For a statistical or financial result, recompute one intermediate quantity and compare it with an independent method.\n\n## Use the tool without losing the reasoning\n\nOpen the [related reviewed reference](/formula/pythagorean-theorem/) with the worked input when available. The linked reference is useful for checking notation and assumptions, but the page\u0027s decision rule remains necessary: unsupported expressions, ambiguous units, and incorrect assumptions can produce a neat result that answers a different question.\n\nKeep a compact record containing the original problem, the selected method, intermediate values, the final result, and the verification. That record is more useful for study, teaching, and debugging than an isolated answer.\n"
  },
  {
    "slug": "amsmath-align-environment",
    "title": "How to Use the amsmath align Environment",
    "description": "Create readable multi-line derivations with alignment points, numbering control, references, and consistent punctuation.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n\\begin{align}a\u0026=b\u002Bc\\\\\u0026=d\u002Be\\end{align}\n\u0060\u0060\u0060\n\nPlace \u0060\u0026\u0060 before the relation sign and use \u0060align*\u0060 when numbering is not needed.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060\\begin{align}a\u0026=b\u002Bc\\\\\u0026=d\u002Be\\end{align}\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **amsmath align environment**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "accessible-equation-images-alt-text",
    "title": "How to Write Alt Text for Equation Images",
    "description": "Write useful alternative text for mathematical images, decide when MathML is better, and avoid descriptions that overwhelm screen-reader users.",
    "topic": "Accessibility",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## First ask whether an image is necessary\n\nIf the equation can be published as structured text or MathML, prefer that. An image is appropriate when preserving a specific visual layout, exporting from a tool, or supporting a destination that cannot render structured mathematics.\n\nKeep the editable equation source even when the delivered version is SVG or PNG.\n\n## Write alt text for a short equation\n\nFor a short standalone expression, state the equation in a readable order:\n\n\u0060\u0060\u0060html\n\u003Cimg src=\u0022energy.svg\u0022 alt=\u0022E equals m c squared\u0022\u003E\n\u0060\u0060\u0060\n\nInclude signs, grouping, exponents, and fractions. Do not describe colors, fonts, or the fact that it is an image unless those visual properties carry meaning.\n\n## Handle a complex derivation\n\nA long proof or multi-line derivation usually exceeds a useful alt attribute. Use a concise alt value that identifies the content, then provide the full expression or explanation in visible nearby text.\n\n\u0060\u0060\u0060html\n\u003Cimg src=\u0022derivation.svg\u0022 alt=\u0022Derivation of the quadratic formula; full steps follow\u0022\u003E\n\u003Cdiv class=\u0022equation-description\u0022\u003E\u2026complete readable derivation\u2026\u003C/div\u003E\n\u0060\u0060\u0060\n\nThis approach helps all readers and avoids an unmanageably long announcement.\n\n## Avoid duplicate announcements\n\nIf the exact equation is already present as accessible text next to the image, the image may be decorative and use an empty alt attribute. Confirm that hiding it does not remove unique annotations, highlighting, or spatial relationships.\n\nA graph or geometric diagram is not equivalent to its equation alone. Describe the trend, axes, important points, and conclusion that the visual communicates.\n\n## Use consistent spoken terminology\n\nRead symbols in the order required to reconstruct the expression. Say \u201Cless than or equal to,\u201D \u201Copen parenthesis,\u201D or \u201Cthe quantity\u201D when grouping could be ambiguous. Define unusual variables and conventions in the surrounding explanation.\n\n## Test the alternative\n\nNavigate to the image with a screen reader and listen without looking at the graphic. Ask whether a reader can understand the same mathematical claim and whether the description is concise enough to follow. Also verify that the visible long description appears in the correct reading order.\n\n## Common mistakes\n\n- \u0060alt=\u0022equation\u0022\u0060 or \u0060alt=\u0022math image\u0022\u0060.\n- Copying raw LaTeX into alt text without considering how it will be spoken.\n- Omitting a denominator boundary or radical scope.\n- Repeating a full visible paragraph in the alt attribute.\n- Treating a chart or diagram as if a formula alone described it.\n\n## Release checklist\n\nConfirm that the image remains sharp when zoomed, has sufficient contrast, and is not the only source of essential information. Store the original LaTeX or MathML with the asset so the alternative can be corrected when the equation changes.\n## Test the accessible representation\n\nFor **accessible equation images alt text**, keep the visual equation and its semantic or textual alternative synchronized. Read the alternative without looking at the equation: it should preserve the relation, grouping, bounds, scripts, and variable names rather than listing isolated symbols.\n\n## Verification sequence\n\n1. Navigate to the equation using only the keyboard.\n2. Inspect the accessible name or MathML tree.\n3. Listen with at least one screen-reader and browser combination available to the publishing team.\n4. Recheck after conversion to PDF, image, presentation, or another content system.\n\n## When an image is unavoidable\n\nRetain the editable source, provide a concise alternative for simple expressions, and add a longer adjacent explanation for equations whose structure cannot be expressed clearly in a short alt attribute.\n"
  },
  {
    "slug": "latex-cases-environment",
    "title": "How to Write Cases and Piecewise Definitions in LaTeX",
    "description": "Build piecewise functions with correct delimiters, alignment, text conditions, and accessible explanations.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n|x|=\\begin{cases}x,\u0026x\\ge0\\\\-x,\u0026x\u003C0\\end{cases}\n\u0060\u0060\u0060\n\nUse one row separator per case and make the conditions mutually clear.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060|x|=\\begin{cases}x,\u0026x\\ge0\\\\-x,\u0026x\u003C0\\end{cases}\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **latex cases environment**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "chemical-equations-in-latex",
    "title": "How to Write Chemical Equations in LaTeX",
    "description": "Typeset reaction arrows, equilibrium notation, subscripts, charges, states, and annotations while keeping chemical equations readable.",
    "topic": "Chemistry notation",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n2\\mathrm{H_2}\u002B\\mathrm{O_2}\\rightarrow2\\mathrm{H_2O}\n\u0060\u0060\u0060\n\nKeep element symbols upright and use subscripts for atom counts; never change subscripts merely to balance the reaction.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u00602\\mathrm{H_2}\u002B\\mathrm{O_2}\\rightarrow2\\mathrm{H_2O}\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **chemical equations in latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "determinants-in-latex",
    "title": "How to Write Determinants in LaTeX",
    "description": "Format determinant bars, matrices, minors, and named determinant expressions.",
    "topic": "Linear algebra",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n\\det(A)=\\begin{vmatrix}a\u0026b\\\\c\u0026d\\end{vmatrix}=ad-bc\n\u0060\u0060\u0060\n\nUse \u0060\\det\u0060 for the operator and \u0060vmatrix\u0060 only when vertical bars really denote a determinant.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060\\det(A)=\\begin{vmatrix}a\u0026b\\\\c\u0026d\\end{vmatrix}=ad-bc\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **determinants in latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "equations-in-markdown",
    "title": "How to Write Equations in Markdown",
    "description": "Understand inline and block math delimiters and renderer differences across Markdown tools.",
    "topic": "Web \u0026 code",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Markdown does not define universal math syntax\n\nCommonMark defines headings, lists, links, code, and other core constructs, but mathematical delimiters are usually an extension added by the publishing platform. A file that renders equations on one site may show raw dollar signs on another.\n\nIdentify the renderer before choosing syntax. Check its documentation for inline math, display math, supported commands, and escaping behavior.\n\n## Write inline mathematics\n\nA common extension uses single dollar delimiters:\n\n\u0060\u0060\u0060markdown\nThe area is $A=\\pi r^2$ square units.\n\u0060\u0060\u0060\n\nInline math belongs inside a sentence and should be short enough not to disrupt line flow. Avoid placing currency amounts next to ambiguous dollar delimiters without checking the renderer\u2019s parsing rules.\n\n## Write display mathematics\n\nMany renderers accept double dollar signs or bracket delimiters:\n\n\u0060\u0060\u0060markdown\n$$\n\\int_0^1 x^2\\,dx=\\frac{1}{3}\n$$\n\u0060\u0060\u0060\n\nAnother common form is:\n\n\u0060\u0060\u0060latex\n\\[\n\\int_0^1 x^2\\,dx=\\frac{1}{3}\n\\]\n\u0060\u0060\u0060\n\nUse the form documented by the destination. Do not assume both are enabled.\n\n## Check command compatibility\n\nA Markdown renderer may use KaTeX, MathJax, or another engine. Basic commands usually transfer, while package-specific macros may fail. Test matrices, aligned equations, custom operators, and uncommon symbols against the renderer\u2019s supported-command list.\n\nWhen an error occurs, reduce the source to a minimal equation and restore one command at a time.\n\n## Avoid Markdown conflicts\n\nUnderscores, asterisks, pipes, and backticks have Markdown meanings outside math mode. Keep equation delimiters balanced and use fenced code blocks when demonstrating source rather than rendering it. Inside tables, pipes in formulas may require escaping or an alternative layout.\n\n## Provide a fallback\n\nFor environments with no math extension, use readable Unicode for simple expressions, link to a rendered page, or provide an accessible SVG with an equivalent text description. Do not rely on a screenshot as the only representation.\n\n## Troubleshoot raw output\n\nIf the source appears unchanged, confirm that math rendering is enabled and that the file type or page context supports it. If only one equation fails, check braces and unsupported commands. If a static-site build succeeds locally but fails in production, compare plugin versions and configuration.\n\n## Verify the published output\n\nOpen the deployed page rather than relying only on the editor preview. Verify the visual equation, copyable source, mobile overflow, dark mode, and accessible reading. The final output is correct only when the production renderer preserves the intended mathematical structure.\n"
  },
  {
    "slug": "write-fractions-in-latex",
    "title": "How to Write Fractions in LaTeX",
    "description": "Create simple, nested, continued, and display-style fractions with clear examples.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Basic fraction syntax\n\nUse \u0060\\frac\u0060 with two required brace groups:\n\n\u0060\u0060\u0060latex\n\\frac{a}{b}\n\u0060\u0060\u0060\n\nThe first group is the numerator and the second is the denominator. Keep braces even when an argument contains one character; consistent grouping reduces editing errors.\n\n## Fractions inside expressions\n\nA fraction can contain full expressions:\n\n\u0060\u0060\u0060latex\nf(x)=\\frac{x^2\u002B2x\u002B1}{x-1}\n\u0060\u0060\u0060\n\nDo not write \u0060\\frac x^2\u002B2x\u002B1 x-1\u0060; without braces, the command cannot determine the intended boundaries.\n\n## Nested fractions\n\nNested fractions are valid but can become hard to read:\n\n\u0060\u0060\u0060latex\n\\frac{1}{1\u002B\\frac{1}{x}}\n\u0060\u0060\u0060\n\nConsider algebraic simplification when nesting becomes deep. In technical writing, readability matters as much as compact source.\n\n## Inline versus display fractions\n\nInline fractions may render smaller to preserve line height:\n\n\u0060\u0060\u0060latex\nThe ratio is $\\frac{a}{b}$.\n\u0060\u0060\u0060\n\nFor a central calculation, use display math:\n\n\u0060\u0060\u0060latex\n\\[\n\\frac{a\u002Bb}{c\u002Bd}=\\frac{3}{5}\n\\]\n\u0060\u0060\u0060\n\nAvoid forcing display style everywhere; it can disrupt spacing in prose.\n\n## Slash notation and Unicode fractions\n\nUse \u0060a/b\u0060 when linear notation is clearer in plain text or code. Precomposed characters such as \u0060\u00BD\u0060 are convenient but cover only a small set of values and do not generalize to variables or complex expressions.\n\n## Troubleshoot fraction errors\n\nIf only one token appears above the bar, check the numerator braces. If the rest of the document turns into math, check delimiters. If \u0060\\frac\u0060 is printed literally, the destination may not enable LaTeX rendering. An error after the fraction often comes from an unmatched brace inside it.\n\n## Common mistakes\n\n- Omitting one of the two required arguments.\n- Using parentheses instead of braces for command arguments.\n- Losing a negative sign outside the denominator group.\n- Nesting many fractions without simplifying.\n- Assuming a rendered slash means the same structure as \u0060\\frac\u0060.\n\n## Verify the result\n\nRead the rendered expression aloud: identify the full numerator, denominator, and any outer operation. Substitute a simple numeric value and compare the result with a calculator or algebraic simplification to verify that grouping matches the intended formula.\n\n## Editorial test case\n\nThe review example compared \u0060\\frac{a\u002Bb}{c\u002Bd}\u0060 with the ambiguous linear string \u0060a\u002Bb/c\u002Bd\u0060. The structured form preserved the intended numerator and denominator in both a full LaTeX document and a browser renderer. This check matters because a visually plausible slash expression can encode a different order of operations when copied into another system.\n## Build a minimal test before the full expression\n\nFor **write fractions in latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "write-integrals-in-latex",
    "title": "How to Write Integrals in LaTeX",
    "description": "Format definite, indefinite, multiple, contour, and line integrals.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Indefinite integrals\n\nWrite the integral sign with the integrand and differential:\n\n\u0060\u0060\u0060latex\n\\int x^2\\,dx\n\u0060\u0060\u0060\n\nThe small spacing command before \u0060dx\u0060 separates the differential visually without treating it as ordinary multiplication text.\n\n## Definite integrals\n\nAttach lower and upper limits with subscripts and superscripts:\n\n\u0060\u0060\u0060latex\n\\int_{0}^{1} x^2\\,dx\n\u0060\u0060\u0060\n\nIn display math, limits appear clearly around the operator. In inline math, the renderer may place them to the side to preserve line height.\n\n## Group complex bounds and integrands\n\nUse braces whenever a bound or exponent has multiple tokens:\n\n\u0060\u0060\u0060latex\n\\int_{-\\infty}^{\\infty} e^{-x^2}\\,dx\n\u0060\u0060\u0060\n\nKeep the complete exponent grouped. A missing brace can move terms outside the exponential or attach them to the wrong operator.\n\n## Multiple and contour integrals\n\nCommon commands include:\n\n\u0060\u0060\u0060latex\n\\iint_D f(x,y)\\,dA\n\\iiint_V \\rho(x,y,z)\\,dV\n\\oint_C \\mathbf{F}\\cdot d\\mathbf{r}\n\u0060\u0060\u0060\n\nSome multiple-integral commands depend on \u0060amsmath\u0060 or renderer support. Check the package or supported-function list when the command fails.\n\n## Long calculations\n\nFor a derivation with several equality steps, use an aligned display environment rather than inserting manual spaces:\n\n\u0060\u0060\u0060latex\n\\begin{align}\n\\int_0^1 2x\\,dx\n  \u0026= [x^2]_0^1 \\\\\n  \u0026= 1\n\\end{align}\n\u0060\u0060\u0060\n\nDo not break a line between the integral sign and its integrand in a way that obscures scope.\n\n## Troubleshoot integral source\n\nIf a limit attaches to the wrong symbol, check where the subscript appears. If \u0060dx\u0060 is italicized as two variables, use \u0060\\,dx\u0060 or a project-specific upright differential convention. If multiple integrals fail, load the expected package or use repeated \u0060\\int\u0060 commands as a fallback.\n\n## Common mistakes\n\n- Omitting the differential entirely.\n- Leaving multi-token limits ungrouped.\n- Using an integral sign as a decorative symbol without defining the variable and domain.\n- Mixing a contour integral with an ordinary line integral unintentionally.\n- Forgetting the constant of integration for an indefinite integral.\n\n## Verify the mathematics\n\nDifferentiate an antiderivative to recover the integrand, or evaluate a definite integral numerically for a simple test case. Confirm that bounds, region labels, and differentials match the dimension and variables of the problem.\n\n## Editorial test case and error check\n\nThe test expression compared \u0060\\int_0^1 2x\\,dx\u0060 with versions that omitted braces, the differential, or the spacing command. The correct source rendered the limits on the integral and evaluated to 1. The altered examples demonstrated why a source string can compile without an obvious error yet still communicate an incomplete or misleading mathematical operation.\n## Build a minimal test before the full expression\n\nFor **write integrals in latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "limits-in-latex",
    "title": "How to Write Limits in LaTeX",
    "description": "Write one-sided, infinite, and multivariable limits with correct subscript notation.",
    "topic": "Calculus",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n\\lim_{x\\to\\infty}\\frac{1}{x}=0\n\u0060\u0060\u0060\n\nGroup the approach expression after \u0060\\to\u0060; display mode normally places limits above and below.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060\\lim_{x\\to\\infty}\\frac{1}{x}=0\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **limits in latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "limits-sums-products-latex",
    "title": "How to Write Limits, Sums, and Products in LaTeX",
    "description": "Build indexed limits, summations, and products with correct lower and upper bounds in inline and display math.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n\\lim_{n\\to\\infty}\\prod_{k=1}^{n}\\left(1\u002B\\frac{x}{k}\\right)\n\u0060\u0060\u0060\n\nUse scalable delimiters only where size changes, and group all multi-token limits.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060\\lim_{n\\to\\infty}\\prod_{k=1}^{n}\\left(1\u002B\\frac{x}{k}\\right)\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **limits sums products latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "piecewise-functions-in-latex",
    "title": "How to Write Piecewise Functions in LaTeX",
    "description": "Create readable piecewise functions with cases, conditions, alignment, and punctuation.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\nf(x)=\\begin{cases}x^2,\u0026x\\ge0\\\\-x,\u0026x\u003C0\\end{cases}\n\u0060\u0060\u0060\n\nPut text conditions after \u0060\u0026\u0060 so values and conditions align.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060f(x)=\\begin{cases}x^2,\u0026x\\ge0\\\\-x,\u0026x\u003C0\\end{cases}\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **piecewise functions in latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "write-summations-in-latex",
    "title": "How to Write Summations in LaTeX",
    "description": "Add indices, limits, conditions, and aligned multi-line sums.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n\\sum_{i=1}^{n} i = \\frac{n(n\u002B1)}{2}\n\u0060\u0060\u0060\n\nPut limits in braces and use \u0060\\sum\u0060 rather than a Unicode sigma when the expression must scale.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060\\sum_{i=1}^{n} i = \\frac{n(n\u002B1)}{2}\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **write summations in latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "systems-of-equations-in-latex",
    "title": "How to Write Systems of Equations in LaTeX",
    "description": "Build aligned and brace-delimited systems of equations with correct spacing and labels.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n\\begin{cases}x\u002By=3\\\\2x-y=0\\end{cases}\n\u0060\u0060\u0060\n\nUse \u0060cases\u0060 for a left brace and conditions; use \u0060aligned\u0060 when no brace is needed.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060\\begin{cases}x\u002By=3\\\\2x-y=0\\end{cases}\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **systems of equations in latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "trigonometric-functions-latex",
    "title": "How to Write Trigonometric Functions in LaTeX",
    "description": "Format sine, cosine, tangent, inverse functions, powers, and angle units correctly in LaTeX.",
    "topic": "LaTeX",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n\\sin^2\\theta\u002B\\cos^2\\theta=1\n\u0060\u0060\u0060\n\nUse named operators such as \u0060\\sin\u0060, not italic letter sequences like \u0060sin\u0060.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060\\sin^2\\theta\u002B\\cos^2\\theta=1\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **trigonometric functions latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "vectors-in-latex",
    "title": "How to Write Vectors in LaTeX",
    "description": "Choose arrow, bold, component, and unit-vector notation for vectors in LaTeX.",
    "topic": "Linear algebra",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick answer\n\nUse the semantic LaTeX structure shown below instead of arranging individual Unicode characters with spaces.\n\n\u0060\u0060\u0060latex\n\\mathbf{v}=\\begin{bmatrix}v_1\\\\v_2\\end{bmatrix}\n\u0060\u0060\u0060\n\nChoose one vector convention such as bold or arrow notation and use it consistently.\n\n## Build the expression\n\n1. Start with the outer structure: operator, environment, delimiter, or relation.\n2. Put complete multi-token arguments inside braces.\n3. Add limits, scripts, conditions, and text labels only after the structure renders correctly.\n4. Preview the expression in the same renderer or document class used for publication.\n\n## Working example\n\nThe source \u0060\\mathbf{v}=\\begin{bmatrix}v_1\\\\v_2\\end{bmatrix}\u0060 keeps the mathematical grouping explicit. Copy it into the LaTeX editor, change one component at a time, and compare the rendered result after every structural edit.\n\n## Common errors\n\n- Using spaces to simulate alignment instead of an environment designed for alignment.\n- Omitting braces around a numerator, denominator, limit, index, or exponent containing several tokens.\n- Typing the name of a mathematical operator as ordinary italic letters.\n- Copying only the rendered result and losing the editable source.\n\n## Portability checks\n\nKeep a minimal test expression beside the full document. Compile with the intended packages, reopen the exported PDF, and verify line breaks, numbering, fonts, copy-and-paste behavior, and alternative text where required.\n## Build a minimal test before the full expression\n\nFor **vectors in latex**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "inline-vs-display-math",
    "title": "Inline Math vs Display Math",
    "description": "Choose inline or display equations based on length, importance, punctuation, and readability.",
    "topic": "Scientific writing",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## The practical difference\n\nInline math participates in a sentence. Display math occupies its own block and is appropriate when the expression is central, complex, numbered, or easier to read at full width.\n\n| Situation | Choose | Reason |\n|---|---|---|\n| One variable or short relation in prose | Inline | Keeps the sentence continuous |\n| Fraction, matrix, derivation, or long sum | Display | Provides space and clearer grouping |\n| Equation referenced later by number | Display | Supports numbering and labels |\n| Short definition repeated frequently | Inline | Avoids unnecessary vertical interruption |\n\n## Inline examples\n\nUse inline delimiters supported by the destination:\n\n\u0060\u0060\u0060latex\nThe circle has area $A=\\pi r^2$.\n\u0060\u0060\u0060\n\nPunctuation belongs to the sentence. The period follows the inline expression because the equation is part of the grammar.\n\n## Display examples\n\nUse a display block for a central result:\n\n\u0060\u0060\u0060latex\n\\[\nA=\\pi r^2\n\\]\n\u0060\u0060\u0060\n\nFor aligned derivations or numbering, use an appropriate environment:\n\n\u0060\u0060\u0060latex\n\\begin{align}\n(a\u002Bb)^2 \u0026= a^2\u002B2ab\u002Bb^2 \\\\\n(a-b)^2 \u0026= a^2-2ab\u002Bb^2\n\\end{align}\n\u0060\u0060\u0060\n\n## Choose based on complexity\n\nA short fraction may work inline, but nested fractions, tall radicals, and matrices can increase line height and disrupt reading. Display math gives the renderer more space and makes boundaries easier to inspect.\n\nDo not make every symbol a display block. Excessive display math fragments prose and forces unnecessary scrolling, especially on mobile.\n\n## Handle numbering and references\n\nNumber only equations that the text refers to later. Use labels and references rather than typing numbers manually, because automatic numbering remains correct when equations move.\n\n## Troubleshoot layout\n\nIf an inline expression is clipped, inspect line height and font metrics. If a display equation overflows on mobile, place it in a scrollable container or break the derivation at meaningful operators. If raw delimiters appear, the destination has not enabled the expected math extension.\n\n## Common mistakes\n\n- Using display math for a single variable.\n- Placing a large matrix inline.\n- Adding punctuation inside source in a way that changes the equation.\n- Manually spacing a derivation instead of using alignment points.\n- Assuming every Markdown renderer supports the same delimiters.\n\n## Verify the final page\n\nRead the paragraph aloud to confirm inline equations fit its grammar. Test display equations at narrow widths, high zoom, and with copy selection. Confirm that numbering, punctuation, and accessible reading order remain correct in the production renderer.\n## Make the choice from the surrounding expression\n\nFor **inline vs display math**, do not decide from glyph shape alone. Read the operands, the mathematical subject, and the sentence around the notation. The same mark can represent different ideas in algebra, probability, set theory, analysis, or typography.\n\n## Verification questions\n\n1. Does the proposed meaning produce a mathematically valid sentence?\n2. Are the operands the right type for that meaning?\n3. Does a nearby definition or legend establish a local convention?\n4. Would replacing the mark with words preserve the intended statement?\n\n## Publishing check\n\nUse the exact Unicode character or structured command, then inspect the final PDF, page, or presentation at normal and enlarged zoom. A font substitution can make distinct characters look similar even when their encoded identities differ.\n"
  },
  {
    "slug": "latex-documentation-notation-reference",
    "title": "LaTeX Documentation: Notation Reference",
    "description": "Notation Reference for latex documentation: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "LaTeX Documentation",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Purpose\n\nLaTeX Documentation: Notation Reference helps readers interpret latex documentation without relying on the visual shape alone. A useful reference records the name, syntax, semantics, one valid example, and the context in which the notation changes meaning.\n\n## Reference fields to check\n\n| Field | What to verify |\n|---|---|\n| Name and aliases | Search terms used by textbooks, software, and standards |\n| Source syntax | Exact LaTeX command, Unicode code point, or MathML element |\n| Meaning | Object type, operands, result type, and local convention |\n| Example | A complete expression rather than an isolated glyph |\n| Compatibility | Renderer, package, browser, font, and export behavior |\n\n## Examples from LaTeX Documentation\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n\n## Reading workflow\n\nIdentify the outer operator or structure, then read its arguments, scripts, limits, and conditions. Compare the rendered form with the editable source and inspect any package or browser requirement before reusing the notation.\n\n## Common ambiguity checks\n\n- Copying a rendered latex documentation image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in latex documentation.\n- Defining latex documentation macros that hide arguments or conflict with package commands.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the latex documentation example.\n## Build a minimal test before the full expression\n\nFor **latex documentation notation reference**, start with the smallest source that contains the required command or environment. Render it with the same engine used by the final document, then add bounds, labels, alignment, and surrounding text one change at a time. This makes a missing brace, unsupported package, or environment error easy to isolate.\n\n\u0060\u0060\u0060latex\n% Minimal test: keep only the structure being checked\n\\[ x^2 \u002B y^2 = z^2 \\]\n\u0060\u0060\u0060\n\n## Verify structure rather than appearance\n\n1. Confirm that every multi-token argument is grouped with braces.\n2. Check that operators, limits, and text labels use semantic commands rather than manual spacing.\n3. Compile with the intended packages and document class.\n4. Copy from the exported result and confirm that the editable source remains available.\n\n## Portability boundary\n\nA command that works in a full TeX distribution may not work in KaTeX, MathJax, Word, or a Markdown renderer. Keep a fallback expression and record any required package. Convert to MathML only after the LaTeX structure is correct; conversion cannot recover semantics that were omitted from the source.\n"
  },
  {
    "slug": "mathml-authoring-notation-reference",
    "title": "MathML Authoring: Notation Reference",
    "description": "Author semantic MathML with correct token, layout, operator, annotation, accessibility, validation, and browser-testing practices.",
    "topic": "MathML Authoring",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nMathML should describe the **structure of an expression**, not imitate its appearance with spaces or positioned text. Start with a \u0060\u003Cmath\u003E\u0060 root, use token elements for identifiers, numbers, and operators, then combine them with layout elements such as \u0060\u003Cmfrac\u003E\u0060, \u0060\u003Cmsup\u003E\u0060, \u0060\u003Cmsub\u003E\u0060, \u0060\u003Cmsqrt\u003E\u0060, \u0060\u003Cmrow\u003E\u0060, and \u0060\u003Cmtable\u003E\u0060.\n\nA complete fraction can be written as:\n\n\u0060\u0060\u0060html\n\u003Cmath xmlns=\u0022http://www.w3.org/1998/Math/MathML\u0022 display=\u0022block\u0022\u003E\n  \u003Cmfrac\u003E\n    \u003Cmrow\u003E\u003Cmi\u003Ex\u003C/mi\u003E\u003Cmo\u003E\u002B\u003C/mo\u003E\u003Cmn\u003E1\u003C/mn\u003E\u003C/mrow\u003E\n    \u003Cmrow\u003E\u003Cmi\u003Ex\u003C/mi\u003E\u003Cmo\u003E\u2212\u003C/mo\u003E\u003Cmn\u003E1\u003C/mn\u003E\u003C/mrow\u003E\n  \u003C/mfrac\u003E\n\u003C/math\u003E\n\u0060\u0060\u0060\n\nThe numerator and denominator are explicit child subtrees. That structure is what enables mathematical layout, conversion, selection, and assistive-technology interpretation.\n\n## Core MathML element map\n\n| Role | Common elements | Authoring rule |\n|---|---|---|\n| Root | \u0060\u003Cmath\u003E\u0060 | Use one root for each expression and set inline or block display intentionally |\n| Identifiers | \u0060\u003Cmi\u003E\u0060 | Variables, function names, and symbolic identifiers |\n| Numbers | \u0060\u003Cmn\u003E\u0060 | Numeric tokens, including decimals and signed values when modeled appropriately |\n| Operators | \u0060\u003Cmo\u003E\u0060 | Operators, fences, separators, relations, and punctuation with operator semantics |\n| Text | \u0060\u003Cmtext\u003E\u0060 | Short natural-language text that belongs inside an expression |\n| Grouping | \u0060\u003Cmrow\u003E\u0060 | Group siblings when they form one operand or logical unit |\n| Fractions and roots | \u0060\u003Cmfrac\u003E\u0060, \u0060\u003Cmsqrt\u003E\u0060, \u0060\u003Cmroot\u003E\u0060 | Encode the mathematical relationship rather than drawing a bar or radical |\n| Scripts | \u0060\u003Cmsub\u003E\u0060, \u0060\u003Cmsup\u003E\u0060, \u0060\u003Cmsubsup\u003E\u0060 | Keep the base and each script as separate children |\n| Limits | \u0060\u003Cmunder\u003E\u0060, \u0060\u003Cmover\u003E\u0060, \u0060\u003Cmunderover\u003E\u0060 | Use for limits, accents, and annotations whose placement is part of the notation |\n| Tables | \u0060\u003Cmtable\u003E\u0060, \u0060\u003Cmtr\u003E\u0060, \u0060\u003Cmtd\u003E\u0060 | Use for matrices, aligned work, cases, and tabular mathematical layout |\n\n## Token elements are not interchangeable\n\nUse \u0060\u003Cmi\u003Ex\u003C/mi\u003E\u0060 for an identifier, \u0060\u003Cmn\u003E2\u003C/mn\u003E\u0060 for a number, and \u0060\u003Cmo\u003E\u002B\u003C/mo\u003E\u0060 for an operator. They may look similar after rendering, but their roles affect spacing, speech, line breaking, and conversion.\n\nFor example, a minus sign belongs in \u0060\u003Cmo\u003E\u0060:\n\n\u0060\u0060\u0060html\n\u003Cmath xmlns=\u0022http://www.w3.org/1998/Math/MathML\u0022\u003E\n  \u003Cmi\u003Ea\u003C/mi\u003E\u003Cmo\u003E\u2212\u003C/mo\u003E\u003Cmi\u003Eb\u003C/mi\u003E\n\u003C/math\u003E\n\u0060\u0060\u0060\n\nDo not substitute the ASCII hyphen-minus merely because the glyph is available. Preserve the mathematical minus character and operator role so the source remains unambiguous.\n\n## Grouping and child order\n\nMathML is an ordered tree. Child order is significant, and layout elements expect a specific number of children. \u0060\u003Cmfrac\u003E\u0060 requires a numerator followed by a denominator. \u0060\u003Cmsup\u003E\u0060 requires a base followed by an exponent. A missing wrapper can change which tokens belong to an operand.\n\nConsider the distinction between these two structures:\n\n\u0060\u0060\u0060html\n\u003C!-- (a \u002B b)^2 --\u003E\n\u003Cmsup\u003E\n  \u003Cmrow\u003E\u003Cmi\u003Ea\u003C/mi\u003E\u003Cmo\u003E\u002B\u003C/mo\u003E\u003Cmi\u003Eb\u003C/mi\u003E\u003C/mrow\u003E\n  \u003Cmn\u003E2\u003C/mn\u003E\n\u003C/msup\u003E\n\n\u003C!-- a \u002B b^2 --\u003E\n\u003Cmrow\u003E\n  \u003Cmi\u003Ea\u003C/mi\u003E\u003Cmo\u003E\u002B\u003C/mo\u003E\n  \u003Cmsup\u003E\u003Cmi\u003Eb\u003C/mi\u003E\u003Cmn\u003E2\u003C/mn\u003E\u003C/msup\u003E\n\u003C/mrow\u003E\n\u0060\u0060\u0060\n\nThe rendered parentheses are not decoration; they communicate the same grouping already present in the tree.\n\n## Operators, fences, and spacing\n\nPrefer semantic \u0060\u003Cmo\u003E\u0060 content and let the MathML renderer apply operator spacing. Avoid inserting ordinary spaces to push tokens apart. For paired delimiters, encode opening and closing fences as operators, or use authoring output produced by a trusted converter and inspect the resulting tree.\n\nAttributes should be used only when the default operator dictionary or presentation behavior does not express the intended notation. Overriding spacing everywhere creates brittle markup and can make copied or converted expressions harder to understand.\n\n## Semantics and annotations\n\nWhen an application needs to preserve the original LaTeX or another source representation, use a semantic wrapper only when the destination supports it and the annotation is accurate. A typical pattern is:\n\n\u0060\u0060\u0060html\n\u003Cmath xmlns=\u0022http://www.w3.org/1998/Math/MathML\u0022\u003E\n  \u003Csemantics\u003E\n    \u003Cmsup\u003E\u003Cmi\u003Ex\u003C/mi\u003E\u003Cmn\u003E2\u003C/mn\u003E\u003C/msup\u003E\n    \u003Cannotation encoding=\u0022application/x-tex\u0022\u003Ex^2\u003C/annotation\u003E\n  \u003C/semantics\u003E\n\u003C/math\u003E\n\u0060\u0060\u0060\n\nThe first child remains the presentation MathML expression. The annotation is supplemental source, not a substitute for a correct MathML tree.\n\n## Accessibility workflow\n\n1. Keep the expression as real MathML in the document rather than flattening it into an image.\n2. Use surrounding prose to define uncommon symbols, local conventions, and variable meanings.\n3. Test keyboard navigation, selection, zoom, high-contrast presentation, and screen-reader output in the actual publishing environment.\n4. When an image fallback is unavoidable, provide a text alternative that communicates the mathematical relationship, not only the visible glyphs.\n5. Check that hidden fallback text is not announced together with MathML as duplicate content.\n\nMathML alone cannot resolve ambiguous notation. The page still needs definitions such as \u201Clet \u03BC denote the population mean\u201D when a symbol has several accepted meanings.\n\n## Validation and browser testing\n\nA successful visual render is not enough. Use this checklist:\n\n- Confirm that the markup is well-formed XML-compatible MathML where required by the destination.\n- Verify the namespace and root element.\n- Check child counts and ordering for fractions, scripts, roots, and tables.\n- Inspect the DOM to ensure a conversion pipeline did not replace MathML with an image or inaccessible canvas.\n- Compare inline and block rendering.\n- Test long expressions for wrapping and overflow on a narrow mobile viewport.\n- Copy the expression and inspect what survives in plain text, rich text, and a second equation editor.\n- Convert back to LaTeX and compare grouping, bounds, signs, and scripts.\n\n## Common MathML authoring failures\n\n- Using \u0060\u003Cmtext\u003E\u0060 for an entire equation, which removes mathematical structure.\n- Putting numbers or operators inside \u0060\u003Cmi\u003E\u0060 because the final glyph looks acceptable.\n- Omitting \u0060\u003Cmrow\u003E\u0060 when a multi-token expression must act as one child.\n- Drawing a fraction with a table or CSS border rather than \u0060\u003Cmfrac\u003E\u0060.\n- Adding manual spaces instead of preserving operator semantics.\n- Publishing generated MathML without checking unsupported elements or attributes in the target browser.\n- Assuming an annotation repairs an incorrect presentation tree.\n\n## When to use MathML, LaTeX, or Unicode\n\nUse MathML when semantic web markup, browser-native mathematical layout, accessibility, or machine-readable structure is a requirement. Use LaTeX as an authoring and interchange source when the workflow is built around TeX syntax. Use Unicode for isolated characters in ordinary text, such as \u201Cx \u2260 0,\u201D when a full structured expression is unnecessary.\n\nA reliable workflow often keeps LaTeX as editable source, converts to MathML for web publication, and validates both representations. The conversion should preserve mathematical grouping rather than merely reproduce a similar picture.\n"
  },
  {
    "slug": "mean-vs-expected-value-symbols",
    "title": "Mean vs Expected Value Symbols",
    "description": "Compare x\u0304, \u03BC, and E[X] across samples, populations, and random variables.",
    "topic": "Comparisons",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nA sample mean summarizes observed data, while an expected value describes the probability-weighted long-run center of a random variable under a model.\n\n## Sample mean notation\n\nThe sample mean is commonly written \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060. It is computed from a particular dataset and changes when the observations change.\n\n## Expected value notation\n\nThe expected value is commonly written \u0060\\mathbb{E}[X]\u0060. For a discrete random variable, it is the sum of each possible value multiplied by its probability; for a continuous variable, it is defined by an integral when the expectation exists.\n\n## Compare the quantities\n\n| Quantity | Typical notation | Based on | Interpretation |\n|---|---|---|---|\n| Sample mean | \u0060\\bar{x}\u0060 | Observed sample | Descriptive statistic |\n| Population mean | \u0060\\mu\u0060 | Population or model | Fixed parameter |\n| Expected value | \u0060\\mathbb{E}[X]\u0060 | Distribution of \u0060X\u0060 | Probability-weighted center |\n\n## Worked example\n\nFor observations \u00602,4,6\u0060, the sample mean is \u0060\\bar{x}=4\u0060. If a random variable takes \u00602,4,6\u0060 with equal probability, then \u0060\\mathbb{E}[X]=4\u0060. The numbers match in this example, but the symbols identify different objects.\n\n## Common mistakes\n\nDo not use \u0060\\mu\u0060, \u0060\\bar{x}\u0060, and \u0060\\mathbb{E}[X]\u0060 interchangeably without defining the population, sample, and model. An expected value may fail to exist, and a sample mean is not guaranteed to equal the population mean.\n\n## Verification checklist\n\nState whether the quantity comes from observed data or a probability distribution. Define the random variable and sample size. Check weighting, units, and whether the required sum or integral converges.\n## Make the choice from the surrounding expression\n\nFor **mean vs expected value symbols**, do not decide from glyph shape alone. Read the operands, the mathematical subject, and the sentence around the notation. The same mark can represent different ideas in algebra, probability, set theory, analysis, or typography.\n\n## Verification questions\n\n1. Does the proposed meaning produce a mathematically valid sentence?\n2. Are the operands the right type for that meaning?\n3. Does a nearby definition or legend establish a local convention?\n4. Would replacing the mark with words preserve the intended statement?\n\n## Publishing check\n\nUse the exact Unicode character or structured command, then inspect the final PDF, page, or presentation at normal and enlarged zoom. A font substitution can make distinct characters look similar even when their encoded identities differ.\n"
  },
  {
    "slug": "scientific-vs-engineering-notation",
    "title": "Scientific Notation vs Engineering Notation",
    "description": "Compare normalized scientific notation with engineering notation and choose powers of ten that match technical units.",
    "topic": "Scientific writing",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nScientific notation uses one nonzero digit before the decimal point. Engineering notation restricts the exponent to a multiple of three so it aligns with SI prefixes.\n\n## Scientific notation\n\nA nonzero number is written \u0060a\\times10^n\u0060 with \u00601\\le |a|\u003C10\u0060. For example, \u006012,300=1.23\\times10^4\u0060.\n\n## Engineering notation\n\nEngineering notation uses an exponent divisible by three and permits one to three digits before the decimal point. The same value is \u006012.3\\times10^3\u0060, which aligns with the prefix kilo.\n\n## Compare the formats\n\n| Format | Coefficient | Exponent | Best use |\n|---|---|---|---|\n| Scientific | \u00601 \u2264 |a| \u003C 10\u0060 | Any integer | General mathematics and science |\n| Engineering | \u00601 \u2264 |a| \u003C 1000\u0060 | Multiple of 3 | SI prefixes, electronics, engineering |\n\n## Worked example\n\nThe value \u00600.000047\u0060 is \u00604.7\\times10^{-5}\u0060 in scientific notation and \u006047\\times10^{-6}\u0060 in engineering notation. The engineering form pairs naturally with micro (\u0060\u00B5\u0060).\n\n## Common mistakes\n\nDo not change the value when moving the decimal point; adjust the exponent in the opposite direction. Distinguish the multiplication sign from the letter x, and preserve significant figures.\n\n## Verification checklist\n\nConvert the notation back to decimal, check the exponent rule, and verify that the coefficient range matches the chosen format. State units and significant figures.\n## Make the choice from the surrounding expression\n\nFor **scientific vs engineering notation**, do not decide from glyph shape alone. Read the operands, the mathematical subject, and the sentence around the notation. The same mark can represent different ideas in algebra, probability, set theory, analysis, or typography.\n\n## Verification questions\n\n1. Does the proposed meaning produce a mathematically valid sentence?\n2. Are the operands the right type for that meaning?\n3. Does a nearby definition or legend establish a local convention?\n4. Would replacing the mark with words preserve the intended statement?\n\n## Publishing check\n\nUse the exact Unicode character or structured command, then inspect the final PDF, page, or presentation at normal and enlarged zoom. A font substitution can make distinct characters look similar even when their encoded identities differ.\n"
  },
  {
    "slug": "subset-vs-proper-subset",
    "title": "Subset vs Proper Subset",
    "description": "Distinguish \u2286 from \u2282 and avoid notation conventions that cause ambiguity.",
    "topic": "Comparisons",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nA subset relation allows equality between the two sets. A proper subset relation requires the first set to be strictly smaller than the second.\n\n## Subset\n\nWrite \u0060A\\subseteq B\u0060 when every element of \u0060A\u0060 is also an element of \u0060B\u0060. This statement is true when \u0060A=B\u0060.\n\n## Proper subset\n\nMany authors write \u0060A\\subset B\u0060 for a proper subset, but conventions vary: some use \u0060\\subset\u0060 for a non-strict subset. To remove ambiguity, define the convention or write \u0060A\\subseteq B\u0060 together with \u0060A\\ne B\u0060.\n\n## Compare the relations\n\n| Relation | Equality allowed? | Unambiguous LaTeX |\n|---|---|---|\n| Subset | Yes | \u0060A\\subseteq B\u0060 |\n| Proper subset | No | \u0060A\\subsetneq B\u0060 or \u0060A\\subseteq B, A\\ne B\u0060 |\n\n## Worked example\n\nLet \u0060A={1,2}\u0060 and \u0060B={1,2,3}\u0060. Then \u0060A\\subseteq B\u0060 and \u0060A\\subsetneq B\u0060. For \u0060C={1,2}\u0060, \u0060A\\subseteq C\u0060 is true, but \u0060A\\subsetneq C\u0060 is false because the sets are equal.\n\n## Common mistakes\n\nDo not confuse membership \u0060x\\in A\u0060 with subset inclusion \u0060A\\subseteq B\u0060. Do not assume every textbook uses \u0060\\subset\u0060 with the same strictness convention.\n\n## Verification checklist\n\nCheck each element of the first set, then test whether the sets are equal. Use explicit non-strict or strict symbols in technical writing and define any local convention.\n## Make the choice from the surrounding expression\n\nFor **subset vs proper subset**, do not decide from glyph shape alone. Read the operands, the mathematical subject, and the sentence around the notation. The same mark can represent different ideas in algebra, probability, set theory, analysis, or typography.\n\n## Verification questions\n\n1. Does the proposed meaning produce a mathematically valid sentence?\n2. Are the operands the right type for that meaning?\n3. Does a nearby definition or legend establish a local convention?\n4. Would replacing the mark with words preserve the intended statement?\n\n## Publishing check\n\nUse the exact Unicode character or structured command, then inspect the final PDF, page, or presentation at normal and enlarged zoom. A font substitution can make distinct characters look similar even when their encoded identities differ.\n"
  },
  {
    "slug": "unicode-math-blocks-guide",
    "title": "Unicode Mathematical Blocks Explained",
    "description": "Distinguish Mathematical Operators, Supplemental Operators, Arrows, Alphanumeric Symbols, and script characters when searching code points.",
    "topic": "Unicode",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Purpose\n\nUnicode Mathematical Blocks Explained helps readers interpret unicode mathematical blocks explained without relying on the visual shape alone. A useful reference records the name, syntax, semantics, one valid example, and the context in which the notation changes meaning.\n\n## Reference fields to check\n\n| Field | What to verify |\n|---|---|\n| Name and aliases | Search terms used by textbooks, software, and standards |\n| Source syntax | Exact LaTeX command, Unicode code point, or MathML element |\n| Meaning | Object type, operands, result type, and local convention |\n| Example | A complete expression rather than an isolated glyph |\n| Compatibility | Renderer, package, browser, font, and export behavior |\n\n## Examples from Unicode\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## Reading workflow\n\nIdentify the outer operator or structure, then read its arguments, scripts, limits, and conditions. Compare the rendered form with the editable source and inspect any package or browser requirement before reusing the notation.\n\n## Common ambiguity checks\n\n- Copying a rendered unicode mathematical blocks explained image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in unicode mathematical blocks explained.\n- Defining unicode mathematical blocks explained macros that hide arguments or conflict with package commands.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the unicode mathematical blocks explained example.\n## Search by function before searching by block\n\nUnicode blocks are organisational ranges, not guarantees that every character in the range has the same mathematical role. Start with the meaning you need\u2014operator, arrow, relation, letterlike symbol, or styled alphabet\u2014then confirm the character name, code point, general category, and related characters. A visually similar code point from another block may have different spacing, semantics, or compatibility behaviour.\n\nWhen documenting a character, record the literal symbol and its \u0060U\u002B\u0060 value together. Test it in the intended font, browser, editor, export format, and search workflow. Mathematical Alphanumeric Symbols deserve special care because they encode styled letters as distinct characters; use them only when the style itself carries semantic information, not as a substitute for ordinary rich-text formatting.\n"
  },
  {
    "slug": "unicode-mathematics-notation-reference",
    "title": "Unicode Mathematics: Notation Reference",
    "description": "Choose, verify, copy, normalize, and publish Unicode mathematical characters without confusing code points, glyphs, operators, or structured equations.",
    "topic": "Unicode Mathematics",
    "updated": "2026-07-27",
    "indexable": false,
    "markdown": "## Quick answer\n\nA Unicode mathematical character is identified by its **code point and official character name**, not by how a font draws it. Before copying a symbol, verify the code point, meaning, and destination. Use Unicode for standalone characters and compact linear notation; use LaTeX, MathML, or a native equation object when the expression needs fractions, matrices, scalable delimiters, alignment, or explicit semantic structure.\n\nFor example:\n\n| Character | Code point | Unicode name | Typical role |\n|---|---|---|---|\n| \u0060\u2212\u0060 | \u0060U\u002B2212\u0060 | MINUS SIGN | Mathematical subtraction or negative sign |\n| \u0060-\u0060 | \u0060U\u002B002D\u0060 | HYPHEN-MINUS | ASCII hyphen and compatibility character |\n| \u0060\u00D7\u0060 | \u0060U\u002B00D7\u0060 | MULTIPLICATION SIGN | Multiplication, dimensions, or cross-like notation by convention |\n| \u0060x\u0060 | \u0060U\u002B0078\u0060 | LATIN SMALL LETTER X | Variable or ordinary letter |\n| \u0060\u2208\u0060 | \u0060U\u002B2208\u0060 | ELEMENT OF | Set membership |\n| \u0060\u03B5\u0060 | \u0060U\u002B03B5\u0060 | GREEK SMALL LETTER EPSILON | Greek letter with field-dependent meaning |\n\nThe minus sign and hyphen-minus can look similar, but they are different characters and can behave differently in search, line breaking, speech, and data processing.\n\n## Character identity checklist\n\nFor every symbol, record these fields:\n\n1. **Visible character** \u2014 the exact text that will be copied.\n2. **Code point** \u2014 for example, \u0060U\u002B221E\u0060 for infinity.\n3. **Unicode name** \u2014 a stable identifier for the encoded character.\n4. **Mathematical meaning** \u2014 defined by the surrounding field and document, not by Unicode alone.\n5. **LaTeX or MathML equivalent** \u2014 useful when the destination requires structured mathematics.\n6. **Look-alikes** \u2014 letters, punctuation, or compatibility characters that may render similarly.\n7. **Font and platform support** \u2014 whether the intended glyph appears in the target environment.\n\nA font can change shape without changing the code point. Conversely, two different code points can be drawn almost identically. Always inspect the underlying character when correctness matters.\n\n## Common look-alike problems\n\n### Minus sign versus hyphen-minus\n\nUse \u0060\u2212\u0060 (\u0060U\u002B2212\u0060) for mathematical minus in Unicode text. Use \u0060-\u0060 (\u0060U\u002B002D\u0060) for ordinary ASCII compatibility, hyphenation, command-line options, and many programming-language operators. Source code may require ASCII even when published mathematical prose should use the mathematical sign.\n\n### Multiplication sign versus letter x\n\n\u0060\u00D7\u0060 (\u0060U\u002B00D7\u0060) is not the letter \u0060x\u0060. The letter can be a variable; the multiplication sign is an operator. In vector notation, a cross product may also be written with \u0060\u00D7\u0060, but its meaning must be defined by context.\n\n### Greek letters versus Latin letters\n\nGreek \u0060\u03BD\u0060 and Latin \u0060v\u0060, Greek \u0060\u03C1\u0060 and Latin \u0060p\u0060, or Greek \u0060\u03BF\u0060 and Latin \u0060o\u0060 can be difficult to distinguish in some fonts. They are different characters and will not compare equal in search, code, identifiers, or data processing.\n\n### Mathematical alphanumeric symbols\n\nUnicode includes mathematical bold, italic, script, Fraktur, double-struck, and monospace characters. These are encoded for mathematical semantics and legacy round-tripping, not as a general substitute for styling ordinary prose. Do not turn a heading into mathematical bold Unicode merely to imitate a font style.\n\n## Normalization and combining characters\n\nUnicode normalization can make canonically equivalent text compare consistently, but normalization does not make unrelated look-alikes equal. A precomposed character and a base-plus-combining-mark sequence may render similarly while containing different code-point sequences.\n\nBefore storing searchable notation:\n\n\u0060\u0060\u0060text\n1. Preserve the original input for audit or round-trip needs.\n2. Apply a documented normalization policy where appropriate.\n3. Compare code points, not screenshots.\n4. Test search and copy behavior after normalization.\n\u0060\u0060\u0060\n\nDo not normalize blindly when a system relies on exact byte sequences, cryptographic signatures, source-code identifiers, or a format-specific convention.\n\n## Plain-text strengths and limits\n\nUnicode is effective for:\n\n- single symbols such as \u0060\u03C0\u0060, \u0060\u221E\u0060, \u0060\u2264\u0060, \u0060\u2211\u0060, and \u0060\u2202\u0060;\n- short linear statements such as \u0060x \u2265 0\u0060;\n- filenames, labels, chat messages, and compact notes;\n- searchable text where the destination preserves the characters;\n- source data that explicitly records code points.\n\nUnicode alone is not a complete equation-layout language. Expressions such as nested fractions, multirow matrices, aligned derivations, piecewise cases, and large operators with limits need a structured representation. Superscript characters such as \u0060\u00B2\u0060 cover only a small subset of possible exponents and should not be treated as a general replacement for real scripts.\n\n## Input and copy workflow\n\n1. Search by symbol name, meaning, code point, or LaTeX command.\n2. Copy the character from a verified reference instead of from an image.\n3. Paste it into the target application.\n4. Inspect the code point or character information when a look-alike is possible.\n5. Save, reopen, search, and export the document.\n6. Test the result on a second device or font if the audience is broad.\n\nOn Windows or macOS, character pickers can help locate encoded symbols, but the input shortcut does not determine the character\u2019s mathematical meaning. In Word and similar editors, a Unicode character in body text is different from a structured equation object even when the screen appearance is similar.\n\n## Storage, search, and programming considerations\n\nUse UTF-8 consistently for web pages, JSON, CSV, source files, and APIs unless a system has a documented alternative. When exporting CSV, test that spreadsheet software preserves the encoding. When generating HTML, keep the actual character or a valid character reference; do not double-escape it into visible entity text.\n\nFor search and identifiers:\n\n- decide whether look-alikes should remain distinct;\n- store the code point and Unicode name alongside the glyph when identity matters;\n- avoid silently replacing mathematical signs with ASCII approximations;\n- make normalization behavior explicit;\n- test case folding separately from Unicode normalization;\n- provide aliases so users can search for \u201Cnot equal,\u201D \u0060\u2260\u0060, \u0060U\u002B2260\u0060, or \u0060\\ne\u0060.\n\n## Accessibility and pronunciation\n\nAssistive technologies may announce the Unicode name or infer a role from context, but a symbol can still be ambiguous. Define variables and unusual notation in nearby prose. A sentence such as \u201CLet \u03C3 denote population standard deviation\u201D is more reliable than expecting the character alone to communicate the convention.\n\nDo not publish an unexplained row of symbols as the only representation of a formula. For complex expressions, use MathML or another accessible equation format and retain readable surrounding explanation.\n\n## Verification checklist\n\n- The copied code point matches the intended Unicode name.\n- The symbol is not a visually similar letter or punctuation mark.\n- The destination preserves UTF-8 and does not replace the character.\n- Search finds the saved character after reopening the document.\n- The chosen font has a readable glyph and acceptable fallback.\n- Plain text is sufficient for the expression\u2019s structure.\n- LaTeX and MathML mappings have been checked when converting formats.\n- Nearby prose defines field-specific meaning and pronunciation where needed.\n\n## When to switch formats\n\nStay with Unicode for an isolated symbol or a short linear expression. Switch to LaTeX when authors need compact editable source, reusable macros, or publishing workflows based on TeX. Switch to MathML for semantic web mathematics and browser-accessible structure. Use a native equation object when a word processor must preserve editing, layout, and accessibility inside the document.\n\nThe safest choice is determined by the destination and the mathematical structure\u2014not by which representation is shortest to type.\n"
  },
  {
    "slug": "unicode-vs-latex-vs-mathml",
    "title": "Unicode vs LaTeX vs MathML",
    "description": "Compare the three main ways to represent mathematical notation on the web and in documents.",
    "topic": "Formats",
    "updated": "2026-07-27",
    "indexable": true,
    "markdown": "## Quick decision\n\nChoose **Unicode** for isolated characters such as \u0060\u03C0\u0060, \u0060\u2264\u0060, or \u0060\u221E\u0060. Choose **LaTeX** when you are authoring an equation and need concise editable source. Choose **MathML** when a web page needs structured mathematical markup that browsers and assistive technology can inspect.\n\nThe three formats are not interchangeable text styles. They represent different layers of a publishing workflow: Unicode identifies characters, LaTeX describes authoring commands, and MathML describes the structure of an expression.\n\n## Comparison table\n\n| Need | Choose | Example | Main limitation |\n|---|---|---|---|\n| Insert one symbol in ordinary text | Unicode | \u0060\u03C0\u0060 | A character alone does not encode a complete equation structure |\n| Write or edit a complex equation | LaTeX | \u0060\\frac{-b\\pm\\sqrt{b^2-4ac}}{2a}\u0060 | Requires a renderer or application that understands LaTeX |\n| Publish semantic mathematics on the web | MathML | \u0060\u003Cmath\u003E\u003Cmi\u003Ex\u003C/mi\u003E\u003Cmo\u003E=\u003C/mo\u003E\u003Cmn\u003E2\u003C/mn\u003E\u003C/math\u003E\u0060 | More verbose to author by hand |\n| Send a fallback through plain text | Unicode plus words | \u0060x \u2264 5\u0060 | Layout is limited to what Unicode characters can express |\n\n## The same expression in three formats\n\nFor the fraction \u201Cone half,\u201D Unicode can only approximate the idea with a precomposed character or linear text:\n\n\u0060\u0060\u0060text\n\u00BD\n1/2\n\u0060\u0060\u0060\n\nLaTeX keeps the numerator and denominator editable:\n\n\u0060\u0060\u0060latex\n\\frac{1}{2}\n\u0060\u0060\u0060\n\nMathML exposes the fraction structure directly:\n\n\u0060\u0060\u0060html\n\u003Cmath xmlns=\u0022http://www.w3.org/1998/Math/MathML\u0022\u003E\u003Cmfrac\u003E\u003Cmn\u003E1\u003C/mn\u003E\u003Cmn\u003E2\u003C/mn\u003E\u003C/mfrac\u003E\u003C/math\u003E\n\u0060\u0060\u0060\n\nA renderer may make the LaTeX and MathML output look nearly identical, but their source and downstream uses remain different.\n\n## How to choose for a document\n\nStart with the destination. A chat message, filename, or code comment usually needs Unicode. A paper written in Overleaf or another TeX workflow needs LaTeX. A standards-oriented web page benefits from MathML, often generated from LaTeX rather than typed manually.\n\nThen check whether the expression must remain editable. A copied glyph is adequate for \u0060\u00B1\u0060, but not for a fraction whose numerator will change. Finally, test the actual software: support for LaTeX commands and MathML rendering varies by product.\n\n## Conversion risks\n\nConversion is not always lossless. A Unicode minus sign \u0060\u2212\u0060 can be replaced accidentally by the ASCII hyphen \u0060-\u0060. A LaTeX macro may have no direct MathML equivalent without expansion. A visual converter may preserve appearance while losing equation semantics.\n\nDo not convert structured mathematics into an image until the final delivery format requires one. Keep the editable source beside any exported PNG, SVG, or PDF.\n\n## Common mistakes\n\n- Choosing a format only because the rendered result looks correct.\n- Assuming every application accepts arbitrary LaTeX commands.\n- Using Unicode superscripts as a replacement for general exponents.\n- Pasting MathML into a field that accepts only plain text.\n- Treating an image of an equation as equivalent to structured mathematics.\n\n## Verify the output\n\nRender the LaTeX, inspect the MathML in a browser, and copy the Unicode text into the final application. Confirm that signs, fractions, roots, limits, and grouping still mean the same thing. When accessibility matters, also inspect the accessibility tree or test with assistive technology instead of relying only on visual appearance.\n## Make the choice from the surrounding expression\n\nFor **unicode vs latex vs mathml**, do not decide from glyph shape alone. Read the operands, the mathematical subject, and the sentence around the notation. The same mark can represent different ideas in algebra, probability, set theory, analysis, or typography.\n\n## Verification questions\n\n1. Does the proposed meaning produce a mathematically valid sentence?\n2. Are the operands the right type for that meaning?\n3. Does a nearby definition or legend establish a local convention?\n4. Would replacing the mark with words preserve the intended statement?\n\n## Publishing check\n\nUse the exact Unicode character or structured command, then inspect the final PDF, page, or presentation at normal and enlarged zoom. A font substitution can make distinct characters look similar even when their encoded identities differ.\n"
  },
  {
    "slug": "numerical-error-notation",
    "title": "Absolute, Relative, and Truncation Error Notation",
    "description": "Distinguish exact values, approximations, residuals, absolute error, relative error, and numerical tolerance.",
    "topic": "Numerical Methods",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Distinguish exact values, approximations, residuals, absolute error, relative error, and numerical tolerance.\n\n## Core notation for Absolute, Relative, and Truncation Error Notation\n\nIn numerical methods, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for absolute, relative, and truncation error notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n\n## Practical workflow\n\nStart from \u0060\\texttt{U\u002B2212}\u0060 and write one sentence that says it means \u201Cidentifier for the mathematical minus sign.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for absolute, relative, and truncation error notation rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the absolute, relative, and truncation error notation notation.\n\n## Failure checks\n\n- Copying a rendered absolute, relative, and truncation error notation image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in absolute, relative, and truncation error notation.\n- Defining absolute, relative, and truncation error notation macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the absolute, relative, and truncation error notation source selectable and editable. For an isolated character in absolute, relative, and truncation error notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of absolute, relative, and truncation error notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the absolute, relative, and truncation error notation example.\n- Confirm every symbol used in absolute, relative, and truncation error notation has one defined meaning in the local context.\n- Reopen the exported file for **Absolute, Relative, and Truncation Error Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "latex-accents-vectors",
    "title": "Accents, Vectors, Hats, and Bars in LaTeX",
    "description": "Apply accents to the correct mathematical object and choose notation that remains legible for long expressions.",
    "topic": "LaTeX",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Apply accents to the correct mathematical object and choose notation that remains legible for long expressions.\n\n## Core notation for Accents, Vectors, Hats, and Bars in LaTeX\n\nIn latex, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for accents, vectors, hats, and bars in latex; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## Practical workflow\n\nStart from \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 and write one sentence that says it means \u201Csemantic operator element.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for accents, vectors, hats, and bars in latex rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the accents, vectors, hats, and bars in latex notation.\n\n## Failure checks\n\n- Copying a rendered accents, vectors, hats, and bars in latex image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in accents, vectors, hats, and bars in latex.\n- Defining accents, vectors, hats, and bars in latex macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the accents, vectors, hats, and bars in latex source selectable and editable. For an isolated character in accents, vectors, hats, and bars in latex, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of accents, vectors, hats, and bars in latex is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the accents, vectors, hats, and bars in latex example.\n- Confirm every symbol used in accents, vectors, hats, and bars in latex has one defined meaning in the local context.\n- Reopen the exported file for **Accents, Vectors, Hats, and Bars in LaTeX** and compare it with the editable source.\n"
  },
  {
    "slug": "accessible-math-in-pdf",
    "title": "Accessible Mathematical Content in PDF",
    "description": "Plan source equations, tagging, alternative descriptions, and verification steps for more accessible mathematical PDFs.",
    "topic": "Accessibility",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Plan source equations, tagging, alternative descriptions, and verification steps for more accessible mathematical PDFs.\n\n## Core notation for Accessible Mathematical Content in PDF\n\nIn accessibility, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for accessible mathematical content in pdf; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n\n## Practical workflow\n\nStart from \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 and write one sentence that says it means \u201Creusable semantic notation command.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for accessible mathematical content in pdf rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the accessible mathematical content in pdf notation.\n\n## Failure checks\n\n- Copying a rendered accessible mathematical content in pdf image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in accessible mathematical content in pdf.\n- Defining accessible mathematical content in pdf macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the accessible mathematical content in pdf source selectable and editable. For an isolated character in accessible mathematical content in pdf, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of accessible mathematical content in pdf is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the accessible mathematical content in pdf example.\n- Confirm every symbol used in accessible mathematical content in pdf has one defined meaning in the local context.\n- Reopen the exported file for **Accessible Mathematical Content in PDF** and compare it with the editable source.\n"
  },
  {
    "slug": "accessible-mathematics-common-errors",
    "title": "Accessible Mathematics: Common Errors and Verification",
    "description": "Common Errors and Verification for accessible mathematics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Accessible Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Accessible Mathematics: Common Errors and Verification explains structured markup, spoken math, keyboard use, alternative text, and testing.\n\n## Core notation for Accessible Mathematics: Common Errors and Verification\n\nIn accessible mathematics, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for accessible mathematics: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n\n## Errors that change the meaning\n\n- **Problem:** Copying a rendered image when editable notation is required. **Correction:** write the missing accessible mathematics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using a look-alike unicode character with different semantics. **Correction:** write the missing accessible mathematics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Defining macros that hide arguments or conflict with package commands. **Correction:** write the missing accessible mathematics: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the accessible mathematics: common errors and verification expression. Then check the accessible mathematics: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced accessible mathematics: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the accessible mathematics: common errors and verification example.\n\n## Accessibility and portability\n\nKeep the accessible mathematics: common errors and verification source selectable and editable. For an isolated character in accessible mathematics: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of accessible mathematics: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the accessible mathematics: common errors and verification example.\n- Confirm every symbol used in accessible mathematics: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Accessible Mathematics: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "accessible-mathematics-latex-formatting",
    "title": "Accessible Mathematics: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for accessible mathematics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Accessible Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Accessible Mathematics: LaTeX Formatting Guide explains structured markup, spoken math, keyboard use, alternative text, and testing.\n\n## Core notation for Accessible Mathematics\n\nIn accessible mathematics, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for accessible mathematics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## LaTeX patterns that preserve the structure\n\nFor accessible mathematics: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\n\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\n\\text{\u201Cx squared plus one\u201D}\n\u0060\u0060\u0060\n\nFor accessible mathematics, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In accessible mathematics, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Keep editable source with the rendered result.\n- Use semantic commands for accessible mathematics rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the accessible mathematics notation.\n\n## Renderer and export checks\n\nRender one demanding accessible mathematics example in the actual destination. For accessible mathematics, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the accessible mathematics source selectable and editable. For an isolated character in accessible mathematics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of accessible mathematics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the accessible mathematics example.\n- Confirm every symbol used in accessible mathematics has one defined meaning in the local context.\n- Reopen the exported file for **Accessible Mathematics: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "graph-adjacency-matrix-guide",
    "title": "Adjacency Matrices and Graph Notation",
    "description": "Connect graph edges with matrix entries, row sums, directed degrees, weights, and spectral calculations.",
    "topic": "Graph Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Connect graph edges with matrix entries, row sums, directed degrees, weights, and spectral calculations.\n\n## Core notation for Adjacency Matrices and Graph Notation\n\nIn graph theory, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for adjacency matrices and graph notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n| Norm | \u0060\\lVert x\\rVert_2\u0060 | Euclidean length of vector x |\n| Matrix product | \u0060C=AB\u0060 | composition with inner dimensions matched |\n| Transpose | \u0060A^{\\mathsf T}\u0060 | rows and columns exchanged |\n\n## Practical workflow\n\nStart from \u0060A=U\\Sigma V^{\\mathsf T}\u0060 and write one sentence that says it means \u201Csingular value decomposition.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Failure checks\n\n- Multiplying matrices whose inner dimensions do not agree.\n- Treating elementwise multiplication as matrix multiplication.\n- Assuming an inverse exists without checking rank or determinant.\n\n## Accessibility and portability\n\nKeep the adjacency matrices and graph notation source selectable and editable. For an isolated character in adjacency matrices and graph notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of adjacency matrices and graph notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in adjacency matrices and graph notation has one defined meaning in the local context.\n- Reopen the exported file for **Adjacency Matrices and Graph Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "optimization-argmin-argmax",
    "title": "Arg Min and Arg Max Explained",
    "description": "Separate the optimizing input from the minimum or maximum objective value and include domains and constraints.",
    "topic": "Optimization",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Separate the optimizing input from the minimum or maximum objective value and include domains and constraints.\n\n## Core notation for Arg Min and Arg Max Explained\n\nIn optimization, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for arg min and arg max explained; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Dual bound | \u0060d^\\star\\le p^\\star\u0060 | weak duality for a minimization primal |\n| Optimization problem | \u0060\\min_x f(x)\\quad\\text{s.t.}\\quad g_i(x)\\le 0\u0060 | minimize an objective over a constrained feasible set |\n| Lagrangian | \u0060\\mathcal{L}(x,\\lambda)=f(x)\u002B\\sum_i\\lambda_i g_i(x)\u0060 | objective plus weighted constraints |\n| Stationarity | \u0060\\nabla_x\\mathcal{L}(x,\\lambda)=0\u0060 | first-order stationarity condition |\n\n## Practical workflow\n\nStart from \u0060d^\\star\\le p^\\star\u0060 and write one sentence that says it means \u201Cweak duality for a minimization primal.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State minimization versus maximization and all constraint directions.\n- Separate an optimizer from the attained objective value.\n- Declare convexity and constraint-qualification assumptions.\n\n## Failure checks\n\n- Reversing a constraint sign without changing the multiplier convention.\n- Writing min when the result required is argmin.\n- Claiming kkt conditions are sufficient without convexity.\n\n## Accessibility and portability\n\nKeep the arg min and arg max explained source selectable and editable. For an isolated character in arg min and arg max explained, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of arg min and arg max explained is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in arg min and arg max explained has one defined meaning in the local context.\n- Reopen the exported file for **Arg Min and Arg Max Explained** and compare it with the editable source.\n"
  },
  {
    "slug": "latex-delimiter-sizing",
    "title": "Automatic and Manual Delimiter Sizing in LaTeX",
    "description": "Choose between left/right sizing and explicit delimiter sizes for fractions, matrices, sets, and nested expressions.",
    "topic": "LaTeX",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Choose between left/right sizing and explicit delimiter sizes for fractions, matrices, sets, and nested expressions.\n\n## Core notation for Automatic and Manual Delimiter Sizing in LaTeX\n\nIn latex, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for automatic and manual delimiter sizing in latex; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n\n## Practical workflow\n\nStart from \u0060\\texttt{U\u002B2212}\u0060 and write one sentence that says it means \u201Cidentifier for the mathematical minus sign.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for automatic and manual delimiter sizing in latex rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the automatic and manual delimiter sizing in latex notation.\n\n## Failure checks\n\n- Copying a rendered automatic and manual delimiter sizing in latex image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in automatic and manual delimiter sizing in latex.\n- Defining automatic and manual delimiter sizing in latex macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the automatic and manual delimiter sizing in latex source selectable and editable. For an isolated character in automatic and manual delimiter sizing in latex, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of automatic and manual delimiter sizing in latex is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the automatic and manual delimiter sizing in latex example.\n- Confirm every symbol used in automatic and manual delimiter sizing in latex has one defined meaning in the local context.\n- Reopen the exported file for **Automatic and Manual Delimiter Sizing in LaTeX** and compare it with the editable source.\n"
  },
  {
    "slug": "basis-coordinate-change",
    "title": "Basis and Coordinate Changes",
    "description": "Separate vectors from coordinate columns and define change-of-basis matrices.",
    "topic": "Linear Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Separate vectors from coordinate columns and define change-of-basis matrices.\n\n## Core notation for Basis and Coordinate Changes\n\nIn linear algebra, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for basis and coordinate changes; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Matrix product | \u0060C=AB\u0060 | composition with inner dimensions matched |\n| Transpose | \u0060A^{\\mathsf T}\u0060 | rows and columns exchanged |\n| Inverse | \u0060A^{-1}A=I\u0060 | inverse relation when A is nonsingular |\n| Eigenpair | \u0060Av=\\lambda v\u0060 | v is an eigenvector with eigenvalue \u03BB |\n\n## Practical workflow\n\nStart from \u0060C=AB\u0060 and write one sentence that says it means \u201Ccomposition with inner dimensions matched.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Failure checks\n\n- Multiplying matrices whose inner dimensions do not agree.\n- Treating elementwise multiplication as matrix multiplication.\n- Assuming an inverse exists without checking rank or determinant.\n\n## Accessibility and portability\n\nKeep the basis and coordinate changes source selectable and editable. For an isolated character in basis and coordinate changes, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of basis and coordinate changes is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in basis and coordinate changes has one defined meaning in the local context.\n- Reopen the exported file for **Basis and Coordinate Changes** and compare it with the editable source.\n"
  },
  {
    "slug": "vector-matrix-bold-notation",
    "title": "Bold, Arrow, and Matrix Notation for Vectors",
    "description": "Choose a consistent visual convention for vectors, matrices, scalars, and coordinate components.",
    "topic": "Linear algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Choose a consistent visual convention for vectors, matrices, scalars, and coordinate components.\n\n## Core notation for Bold, Arrow, and Matrix Notation for Vectors\n\nIn linear algebra, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for bold, arrow, and matrix notation for vectors; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Eigenpair | \u0060Av=\\lambda v\u0060 | v is an eigenvector with eigenvalue \u03BB |\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n| Norm | \u0060\\lVert x\\rVert_2\u0060 | Euclidean length of vector x |\n| Matrix product | \u0060C=AB\u0060 | composition with inner dimensions matched |\n\n## Practical workflow\n\nStart from \u0060Av=\\lambda v\u0060 and write one sentence that says it means \u201Cv is an eigenvector with eigenvalue \u03BB.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Failure checks\n\n- Multiplying matrices whose inner dimensions do not agree.\n- Treating elementwise multiplication as matrix multiplication.\n- Assuming an inverse exists without checking rank or determinant.\n\n## Accessibility and portability\n\nKeep the bold, arrow, and matrix notation for vectors source selectable and editable. For an isolated character in bold, arrow, and matrix notation for vectors, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of bold, arrow, and matrix notation for vectors is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in bold, arrow, and matrix notation for vectors has one defined meaning in the local context.\n- Reopen the exported file for **Bold, Arrow, and Matrix Notation for Vectors** and compare it with the editable source.\n"
  },
  {
    "slug": "branch-cuts-complex-log",
    "title": "Branch Cuts and Complex Logarithms",
    "description": "State principal branches, arguments, cuts, and multivalued functions.",
    "topic": "Complex Analysis",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "State principal branches, arguments, cuts, and multivalued functions.\n\n## Core notation for Branch Cuts and Complex Logarithms\n\nIn complex analysis, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for branch cuts and complex logarithms; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Closure | \u0060\\overline{A}\u0060 | A together with its limit points |\n| Interior | \u0060A^\\circ\u0060 | largest open set contained in A |\n| Continuity | \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 | topological continuity criterion |\n| Complex logarithm | \u0060\\Log z=\\ln|z|\u002Bi\\Arg z\u0060 | a selected logarithm branch |\n\n## Practical workflow\n\nStart from \u0060\\overline{A}\u0060 and write one sentence that says it means \u201CA together with its limit points.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the ambient space and topology.\n- Distinguish local from global properties.\n- Declare contour orientation and branch choices.\n\n## Failure checks\n\n- Using closed and bounded as a universal compactness criterion.\n- Crossing a branch cut without changing the selected argument.\n- Omitting hypotheses from a convergence or interchange theorem.\n\n## Accessibility and portability\n\nKeep the branch cuts and complex logarithms source selectable and editable. For an isolated character in branch cuts and complex logarithms, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of branch cuts and complex logarithms is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in branch cuts and complex logarithms has one defined meaning in the local context.\n- Reopen the exported file for **Branch Cuts and Complex Logarithms** and compare it with the editable source.\n"
  },
  {
    "slug": "bra-ket-notation-guide",
    "title": "Bra\u2013Ket Notation Guide",
    "description": "Read kets, bras, inner products, outer products, expectation values, and projectors.",
    "topic": "Quantum Mechanics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Read kets, bras, inner products, outer products, expectation values, and projectors.\n\n## Core notation for Bra\u2013Ket Notation\n\nIn quantum mechanics, the notation usually represents states, bras, kets, operators, observables, amplitudes, and Hilbert-space conventions. The table below gives a compact starting set for bra\u2013ket notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Normalization | \u0060\\langle\\psi\\mid\\psi\\rangle=1\u0060 | unit norm state |\n| State | \u0060\\lvert\\psi\\rangle\u0060 | ket representing a quantum state |\n| Dual state | \u0060\\langle\\psi\\rvert\u0060 | bra dual to the ket |\n| Inner product | \u0060\\langle\\phi\\mid\\psi\\rangle\u0060 | complex amplitude between states |\n\n## Practical workflow\n\nStart from \u0060\\langle\\psi\\mid\\psi\\rangle=1\u0060 and write one sentence that says it means \u201Cunit norm state.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish operators from scalar eigenvalues typographically.\n- State normalization and basis conventions.\n- Keep complex conjugation and adjoints explicit.\n\n## Failure checks\n\n- Reversing bra and ket order in a complex inner product.\n- Treating noncommuting operators as ordinary scalars.\n- Omitting normalization before interpreting probabilities.\n\n## Accessibility and portability\n\nKeep the bra\u2013ket notation source selectable and editable. For an isolated character in bra\u2013ket notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of bra\u2013ket notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify state normalization.\n- Check operator hermiticity when representing an observable.\n- Test the expression in a finite-dimensional basis.\n- Confirm every symbol used in bra\u2013ket notation has one defined meaning in the local context.\n- Reopen the exported file for **Bra\u2013Ket Notation Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "calculus-symbols-explained",
    "title": "Calculus Symbols Explained",
    "description": "Understand limits, derivatives, partial derivatives, integrals, sums, and nabla notation.",
    "topic": "Reference",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "# Calculus Symbols Explained\n\nUnderstand limits, derivatives, partial derivatives, integrals, sums, and nabla notation. This guide focuses on reliable methods that preserve the intended character or mathematical structure when the text is copied, published, or shared.\n\n## Quick answer\n\nThe fastest option is to copy this character: **\u222B**. For a real mathematical equation, use the LaTeX form \u0060\\int\u0060 when your editor supports math rendering. Plain Unicode is ideal for short text, while LaTeX or an equation editor is better for structured notation.\n\n## Choose the right format\n\nUse **Unicode** when the symbol must remain a normal text character in an email, title, spreadsheet, or social post. Use **LaTeX** when the expression contains fractions, roots, limits, stacked scripts, or other two-dimensional notation. Use **HTML entities or numeric references** when the symbol is part of a web page and escaping or source-code clarity matters. Use **MathML** when semantic browser-accessible mathematics is required.\n\n| Format | Value | Best for |\n|---|---|---|\n| Character | \u0060\u222B\u0060 | Plain text and quick copy |\n| Unicode | \u0060U\u002B222B\u0060 | Character lookup and encoding |\n| LaTeX | \u0060\\int\u0060 | Equations and technical writing |\n| HTML | \u0060\u0026int;\u0060 | Web pages |\n| MathML | \u0060\u0026lt;mo\u0026gt;\u222B\u0026lt;/mo\u0026gt;\u0060 | Semantic web mathematics |\n\n## Windows\n\nOpen **Character Map**, search for the symbol name, select the character, and copy it. In Microsoft Word and some Office applications, you can also type the hexadecimal Unicode value and press **Alt\u002BX**. Application support varies, so verify the result before relying on a shortcut in a different editor.\n\n## Mac\n\nPress **Control\u2013Command\u2013Space** to open Character Viewer. Search for the English symbol name, then double-click the result. Frequently used characters can be added to Favorites. In equation-capable applications, prefer the app\u2019s math editor when the character is part of a larger formula.\n\n## Microsoft Word\n\nPress **Alt\u002B=** to open an equation, type \u0060\\int\u0060, and press Space when Word recognizes the command. For plain text, use **Insert \u2192 Symbol \u2192 More Symbols**, or paste the Unicode character. The equation route is preferable when scripts, fractions, limits, or alignment are involved.\n\n## Google Docs\n\nChoose **Insert \u2192 Special characters**, search by name, or draw an approximate shape. For equations, choose **Insert \u2192 Equation** and use the available notation controls. Google Docs supports a useful subset of equation shortcuts, but it does not behave exactly like a full LaTeX system.\n\n## HTML and web pages\n\nA literal UTF-8 character is usually the clearest choice when the document declares UTF-8. Named entities can improve readability for common characters, while numeric references are a dependable fallback. Keep the symbol in meaningful text rather than using a background image, because text is selectable, searchable, and more accessible.\n\n\u0060\u0060\u0060html\n\u003Cspan aria-label=\u0022Integral\u0022\u003E\u222B\u003C/span\u003E\n\u003Cspan\u003E\u0026int;\u003C/span\u003E\n\u0060\u0060\u0060\n\n## LaTeX example\n\n\u0060\u0060\u0060latex\n\\int\n\u0060\u0060\u0060\n\nWhen the symbol is an operator or relation, place it in math mode and allow LaTeX to apply the correct spacing. Avoid forcing a mathematical expression into a sequence of unrelated Unicode characters when semantic structure matters.\n\n## Common mistakes\n\nDo not substitute a visually similar letter, punctuation mark, or image. Similar-looking characters may have different Unicode values and meanings. Also avoid copying from a decorative font that changes the glyph without changing the underlying character. Finally, check whether the surrounding context requires a specific convention; several mathematical symbols have meanings that vary by field or textbook.\n\n## Related resources\n\nUse the symbol page for definitions, examples, copy controls, and platform-specific input methods. Browse the relevant category for nearby notation, or open the LaTeX editor to test a complete formula before publishing it.\n"
  },
  {
    "slug": "cash-flow-sign-convention",
    "title": "Cash-Flow Signs and Timeline Notation",
    "description": "Represent inflows, outflows, payment timing, annuity type, and discount periods on a consistent financial timeline.",
    "topic": "Financial Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Represent inflows, outflows, payment timing, annuity type, and discount periods on a consistent financial timeline.\n\n## Core notation for Cash-Flow Signs and Timeline Notation\n\nIn financial mathematics, the notation usually represents cash flows, dates, rates, compounding periods, discount factors, and sign conventions. The table below gives a compact starting set for cash-flow signs and timeline notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Net present value | \u0060NPV=\\sum_{t=0}^{n}\\frac{C_t}{(1\u002Br)^t}\u0060 | discounted sum of dated cash flows |\n| Effective rate | \u00601\u002Br_{\\mathrm{eff}}=(1\u002Br_m/m)^m\u0060 | effective annual rate from a nominal rate |\n| Continuous growth | \u0060FV=PV\\,e^{rt}\u0060 | continuous compounding model |\n| Annuity | \u0060PV=C\\frac{1-(1\u002Br)^{-n}}{r}\u0060 | present value of level end-of-period payments |\n\n## Practical workflow\n\nStart from \u0060NPV=\\sum_{t=0}^{n}\\frac{C_t}{(1\u002Br)^t}\u0060 and write one sentence that says it means \u201Cdiscounted sum of dated cash flows.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State nominal versus effective rates.\n- Align each rate with its compounding period.\n- Declare whether inflows or outflows are positive.\n\n## Failure checks\n\n- Using an annual rate with monthly periods without conversion.\n- Mixing beginning-of-period and end-of-period cash flows.\n- Comparing returns computed with different day-count conventions.\n\n## Accessibility and portability\n\nKeep the cash-flow signs and timeline notation source selectable and editable. For an isolated character in cash-flow signs and timeline notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of cash-flow signs and timeline notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Draw a dated cash-flow timeline.\n- Convert all rates to a common period.\n- Verify the zero-rate limit.\n- Confirm every symbol used in cash-flow signs and timeline notation has one defined meaning in the local context.\n- Reopen the exported file for **Cash-Flow Signs and Timeline Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "chemical-equations-common-errors",
    "title": "Chemical Equations: Common Errors and Verification",
    "description": "Common Errors and Verification for chemical equations: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Chemical Equations",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Chemical Equations: Common Errors and Verification explains species, states, coefficients, charge, equilibrium arrows, and conservation.\n\n## Core notation for Chemical Equations: Common Errors and Verification\n\nIn chemical equations, the notation usually represents species, stoichiometric coefficients, charges, states, reaction arrows, and units. The table below gives a compact starting set for chemical equations: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Charge | \u0060\\mathrm{SO_4^{2-}}\u0060 | species with a two-minus charge |\n| State label | \u0060\\mathrm{H_2O(l)}\u0060 | chemical species with physical state |\n| Reaction | \u00602H_2\u002BO_2\\rightarrow 2H_2O\u0060 | balanced reaction with stoichiometric coefficients |\n| Equilibrium | \u0060A\\rightleftharpoons B\u0060 | reversible process or equilibrium |\n\n## Errors that change the meaning\n\n- **Problem:** Changing a subscript to balance an equation. **Correction:** write the missing chemical equations: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Typesetting element symbols as ordinary italic variables. **Correction:** write the missing chemical equations: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Placing ionic charge before the atom count. **Correction:** write the missing chemical equations: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the chemical equations: common errors and verification expression. Then check the chemical equations: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced chemical equations: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Count each element on both sides.\n- Check net charge balance.\n- Verify coefficients are in the smallest intended ratio.\n\n## Accessibility and portability\n\nKeep the chemical equations: common errors and verification source selectable and editable. For an isolated character in chemical equations: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of chemical equations: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Count each element on both sides.\n- Check net charge balance.\n- Verify coefficients are in the smallest intended ratio.\n- Confirm every symbol used in chemical equations: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Chemical Equations: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "chemical-equations-latex-formatting",
    "title": "Chemical Equations: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for chemical equations: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Chemical Equations",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Chemical Equations: LaTeX Formatting Guide explains species, states, coefficients, charge, equilibrium arrows, and conservation.\n\n## Core notation for Chemical Equations\n\nIn chemical equations, the notation usually represents species, stoichiometric coefficients, charges, states, reaction arrows, and units. The table below gives a compact starting set for chemical equations; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Concentration | \u0060c=\\frac{n}{V}\u0060 | amount concentration |\n| Rate law | \u0060r=k[A]^m[B]^n\u0060 | empirical reaction-rate relation |\n| Charge | \u0060\\mathrm{SO_4^{2-}}\u0060 | species with a two-minus charge |\n| State label | \u0060\\mathrm{H_2O(l)}\u0060 | chemical species with physical state |\n\n## LaTeX patterns that preserve the structure\n\nFor chemical equations: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nc=\\frac{n}{V}\nr=k[A]^m[B]^n\n\\mathrm{SO_4^{2-}}\n\u0060\u0060\u0060\n\nFor chemical equations, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In chemical equations, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Use upright roman letters for element symbols.\n- Keep subscripts, coefficients, and charges in their proper positions.\n- State physical states and reaction conditions when relevant.\n\n## Renderer and export checks\n\nRender one demanding chemical equations example in the actual destination. For chemical equations, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the chemical equations source selectable and editable. For an isolated character in chemical equations, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of chemical equations is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Count each element on both sides.\n- Check net charge balance.\n- Verify coefficients are in the smallest intended ratio.\n- Confirm every symbol used in chemical equations has one defined meaning in the local context.\n- Reopen the exported file for **Chemical Equations: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "chemical-equations-notation-reference",
    "title": "Chemical Equations: Notation Reference",
    "description": "Notation Reference for chemical equations: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Chemical Equations",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Chemical Equations: Notation Reference explains species, states, coefficients, charge, equilibrium arrows, and conservation.\n\n## Core notation for Chemical Equations\n\nIn chemical equations, the notation usually represents species, stoichiometric coefficients, charges, states, reaction arrows, and units. The table below gives a compact starting set for chemical equations; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Equilibrium | \u0060A\\rightleftharpoons B\u0060 | reversible process or equilibrium |\n| Concentration | \u0060c=\\frac{n}{V}\u0060 | amount concentration |\n| Rate law | \u0060r=k[A]^m[B]^n\u0060 | empirical reaction-rate relation |\n| Charge | \u0060\\mathrm{SO_4^{2-}}\u0060 | species with a two-minus charge |\n\n## How to read a complete expression\n\nRead \u0060A\\rightleftharpoons B\u0060 as \u201Creversible process or equilibrium.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in chemical equations from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- Use upright roman letters for element symbols.\n- Keep subscripts, coefficients, and charges in their proper positions.\n- State physical states and reaction conditions when relevant.\n\n## Cross-checks before reuse\n\n- Count each element on both sides.\n- Check net charge balance.\n- Verify coefficients are in the smallest intended ratio.\n\n## Accessibility and portability\n\nKeep the chemical equations source selectable and editable. For an isolated character in chemical equations, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of chemical equations is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Count each element on both sides.\n- Check net charge balance.\n- Verify coefficients are in the smallest intended ratio.\n- Confirm every symbol used in chemical equations has one defined meaning in the local context.\n- Reopen the exported file for **Chemical Equations: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "classical-mechanics-common-errors",
    "title": "Classical Mechanics: Common Errors and Verification",
    "description": "Common Errors and Verification for classical mechanics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Classical Mechanics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Classical Mechanics: Common Errors and Verification explains position, velocity, acceleration, forces, energy, momentum, and units.\n\n## Core notation for Classical Mechanics: Common Errors and Verification\n\nIn classical mechanics, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for classical mechanics: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Ohm law | \u0060V=IR\u0060 | voltage-current-resistance relation |\n| Wave relation | \u0060v=f\\lambda\u0060 | wave speed equals frequency times wavelength |\n| First law | \u0060\\Delta U=Q-W\u0060 | internal-energy change under the stated work sign convention |\n| Newton law | \u0060\\sum F=ma\u0060 | net force equals mass times acceleration |\n\n## Errors that change the meaning\n\n- **Problem:** Adding quantities with incompatible units. **Correction:** write the missing classical mechanics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Dropping vector direction when only magnitudes were given. **Correction:** write the missing classical mechanics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Mixing peak, rms, angular-frequency, and ordinary-frequency values. **Correction:** write the missing classical mechanics: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the classical mechanics: common errors and verification expression. Then check the classical mechanics: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced classical mechanics: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n\n## Accessibility and portability\n\nKeep the classical mechanics: common errors and verification source selectable and editable. For an isolated character in classical mechanics: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of classical mechanics: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in classical mechanics: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Classical Mechanics: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "classical-mechanics-latex-formatting",
    "title": "Classical Mechanics: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for classical mechanics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Classical Mechanics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Classical Mechanics: LaTeX Formatting Guide explains position, velocity, acceleration, forces, energy, momentum, and units.\n\n## Core notation for Classical Mechanics\n\nIn classical mechanics, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for classical mechanics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| First law | \u0060\\Delta U=Q-W\u0060 | internal-energy change under the stated work sign convention |\n| Newton law | \u0060\\sum F=ma\u0060 | net force equals mass times acceleration |\n| Energy | \u0060E=T\u002BV\u0060 | total mechanical energy as kinetic plus potential energy |\n| Momentum | \u0060p=mv\u0060 | linear momentum in a nonrelativistic model |\n\n## LaTeX patterns that preserve the structure\n\nFor classical mechanics: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\Delta U=Q-W\n\\sum F=ma\nE=T\u002BV\n\u0060\u0060\u0060\n\nFor classical mechanics, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In classical mechanics, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the coordinate axes and positive directions.\n- Attach si or other units to every measured quantity.\n- Declare the work, heat, voltage, and current sign conventions.\n\n## Renderer and export checks\n\nRender one demanding classical mechanics example in the actual destination. For classical mechanics, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the classical mechanics source selectable and editable. For an isolated character in classical mechanics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of classical mechanics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in classical mechanics has one defined meaning in the local context.\n- Reopen the exported file for **Classical Mechanics: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "classical-mechanics-notation-reference",
    "title": "Classical Mechanics: Notation Reference",
    "description": "Notation Reference for classical mechanics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Classical Mechanics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Classical Mechanics: Notation Reference explains position, velocity, acceleration, forces, energy, momentum, and units.\n\n## Core notation for Classical Mechanics\n\nIn classical mechanics, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for classical mechanics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Newton law | \u0060\\sum F=ma\u0060 | net force equals mass times acceleration |\n| Energy | \u0060E=T\u002BV\u0060 | total mechanical energy as kinetic plus potential energy |\n| Momentum | \u0060p=mv\u0060 | linear momentum in a nonrelativistic model |\n| Ohm law | \u0060V=IR\u0060 | voltage-current-resistance relation |\n\n## How to read a complete expression\n\nRead \u0060\\sum F=ma\u0060 as \u201Cnet force equals mass times acceleration.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in classical mechanics from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the coordinate axes and positive directions.\n- Attach si or other units to every measured quantity.\n- Declare the work, heat, voltage, and current sign conventions.\n\n## Cross-checks before reuse\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n\n## Accessibility and portability\n\nKeep the classical mechanics source selectable and editable. For an isolated character in classical mechanics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of classical mechanics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in classical mechanics has one defined meaning in the local context.\n- Reopen the exported file for **Classical Mechanics: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "coding-rate-capacity-notation",
    "title": "Coding Rate and Channel Capacity",
    "description": "Define symbols for code length, rate, entropy, capacity, and error probability.",
    "topic": "Information Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Define symbols for code length, rate, entropy, capacity, and error probability.\n\n## Core notation for Coding Rate and Channel Capacity\n\nIn information theory, the notation usually represents random variables, alphabets, distributions, code lengths, channels, and logarithm bases. The table below gives a compact starting set for coding rate and channel capacity; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Chain rule | \u0060H(X,Y)=H(X)\u002BH(Y\\mid X)\u0060 | joint entropy decomposition |\n| Entropy | \u0060H(X)=-\\sum_x p(x)\\log p(x)\u0060 | average uncertainty of X |\n| Conditional entropy | \u0060H(X\\mid Y)\u0060 | uncertainty remaining after observing Y |\n| Mutual information | \u0060I(X;Y)=H(X)-H(X\\mid Y)\u0060 | shared information between X and Y |\n\n## Practical workflow\n\nStart from \u0060H(X,Y)=H(X)\u002BH(Y\\mid X)\u0060 and write one sentence that says it means \u201Cjoint entropy decomposition.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the logarithm base and resulting unit.\n- Distinguish entropy, cross-entropy, and kl divergence.\n- Specify discrete sums versus continuous integrals.\n\n## Failure checks\n\n- Assuming kl divergence is symmetric.\n- Mixing bits and nats in one calculation.\n- Using 0 log 0 without the standard limiting convention.\n\n## Accessibility and portability\n\nKeep the coding rate and channel capacity source selectable and editable. For an isolated character in coding rate and channel capacity, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of coding rate and channel capacity is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities normalize.\n- Test deterministic and uniform distributions.\n- Confirm the order of p and q in every divergence.\n- Confirm every symbol used in coding rate and channel capacity has one defined meaning in the local context.\n- Reopen the exported file for **Coding Rate and Channel Capacity** and compare it with the editable source.\n"
  },
  {
    "slug": "combinatorics-common-errors",
    "title": "Combinatorics: Common Errors and Verification",
    "description": "Common Errors and Verification for combinatorics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Combinatorics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Combinatorics: Common Errors and Verification explains permutations, combinations, bijections, generating functions, and counting arguments.\n\n## Core notation for Combinatorics: Common Errors and Verification\n\nIn combinatorics, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for combinatorics: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n| Graph | \u0060G=(V,E)\u0060 | vertices and edges |\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n\n## Errors that change the meaning\n\n- **Problem:** Switching index origins halfway through a recurrence. **Correction:** write the missing combinatorics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Counting permutations when combinations are required. **Correction:** write the missing combinatorics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using equality where modular congruence is intended. **Correction:** write the missing combinatorics: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the combinatorics: common errors and verification expression. Then check the combinatorics: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced combinatorics: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n\n## Accessibility and portability\n\nKeep the combinatorics: common errors and verification source selectable and editable. For an isolated character in combinatorics: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of combinatorics: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in combinatorics: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Combinatorics: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "combinatorics-latex-formatting",
    "title": "Combinatorics: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for combinatorics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Combinatorics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Combinatorics: LaTeX Formatting Guide explains permutations, combinations, bijections, generating functions, and counting arguments.\n\n## Core notation for Combinatorics\n\nIn combinatorics, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for combinatorics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n\n## LaTeX patterns that preserve the structure\n\nFor combinatorics: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\na\\equiv b\\pmod m\np(x)=\\sum_{k=0}^{n}a_kx^k\n\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\n\u0060\u0060\u0060\n\nFor combinatorics, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In combinatorics, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Renderer and export checks\n\nRender one demanding combinatorics example in the actual destination. For combinatorics, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the combinatorics source selectable and editable. For an isolated character in combinatorics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of combinatorics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in combinatorics has one defined meaning in the local context.\n- Reopen the exported file for **Combinatorics: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "combinatorics-notation-reference",
    "title": "Combinatorics: Notation Reference",
    "description": "Notation Reference for combinatorics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Combinatorics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Combinatorics: Notation Reference explains permutations, combinations, bijections, generating functions, and counting arguments.\n\n## Core notation for Combinatorics\n\nIn combinatorics, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for combinatorics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n| Graph | \u0060G=(V,E)\u0060 | vertices and edges |\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n\n## How to read a complete expression\n\nRead \u0060(a_n)_{n\\ge0}\u0060 as \u201Cindexed family of terms.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in combinatorics from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Cross-checks before reuse\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n\n## Accessibility and portability\n\nKeep the combinatorics source selectable and editable. For an isolated character in combinatorics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of combinatorics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in combinatorics has one defined meaning in the local context.\n- Reopen the exported file for **Combinatorics: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "common-distributions-common-errors",
    "title": "Common Probability Distributions: Common Errors and Verification",
    "description": "Common Errors and Verification for common probability distributions: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable no",
    "topic": "Common Probability Distributions",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Common Probability Distributions: Common Errors and Verification explains parameters, support, moments, modeling assumptions, and notation.\n\n## Core notation for Common Probability Distributions: Common Errors and Verification\n\nIn common probability distributions, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for common probability distributions: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Expectation | \u0060\\mathbb{E}[X]\u0060 | mean of a random variable under its distribution |\n| Variance | \u0060\\operatorname{Var}(X)=\\mathbb{E}[(X-\\mathbb{E}X)^2]\u0060 | spread around the expectation |\n| Bayes rule | \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 | posterior proportional to likelihood times prior |\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n\n## Errors that change the meaning\n\n- **Problem:** Dropping the condition after applying a conditional identity. **Correction:** write the missing common probability distributions: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Confusing a probability mass with a probability density. **Correction:** write the missing common probability distributions: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using the same distribution name with incompatible parameter orders. **Correction:** write the missing common probability distributions: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the common probability distributions: common errors and verification expression. Then check the common probability distributions: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced common probability distributions: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n\n## Accessibility and portability\n\nKeep the common probability distributions: common errors and verification source selectable and editable. For an isolated character in common probability distributions: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of common probability distributions: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in common probability distributions: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Common Probability Distributions: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "common-distributions-latex-formatting",
    "title": "Common Probability Distributions: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for common probability distributions: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Common Probability Distributions",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Common Probability Distributions: LaTeX Formatting Guide explains parameters, support, moments, modeling assumptions, and notation.\n\n## Core notation for Common Probability Distributions\n\nIn common probability distributions, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for common probability distributions; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n| Expectation | \u0060\\mathbb{E}[X]\u0060 | mean of a random variable under its distribution |\n| Variance | \u0060\\operatorname{Var}(X)=\\mathbb{E}[(X-\\mathbb{E}X)^2]\u0060 | spread around the expectation |\n\n## LaTeX patterns that preserve the structure\n\nFor common probability distributions: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nP(A)\nP(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\n\\mathbb{E}[X]\n\u0060\u0060\u0060\n\nFor common probability distributions, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In common probability distributions, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Renderer and export checks\n\nRender one demanding common probability distributions example in the actual destination. For common probability distributions, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the common probability distributions source selectable and editable. For an isolated character in common probability distributions, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of common probability distributions is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in common probability distributions has one defined meaning in the local context.\n- Reopen the exported file for **Common Probability Distributions: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "common-distributions-notation-reference",
    "title": "Common Probability Distributions: Notation Reference",
    "description": "Notation Reference for common probability distributions: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Common Probability Distributions",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Common Probability Distributions: Notation Reference explains parameters, support, moments, modeling assumptions, and notation.\n\n## Core notation for Common Probability Distributions\n\nIn common probability distributions, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for common probability distributions; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n| Expectation | \u0060\\mathbb{E}[X]\u0060 | mean of a random variable under its distribution |\n| Variance | \u0060\\operatorname{Var}(X)=\\mathbb{E}[(X-\\mathbb{E}X)^2]\u0060 | spread around the expectation |\n\n## How to read a complete expression\n\nRead \u0060P(A)\u0060 as \u201Cprobability assigned to event A.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in common probability distributions from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Cross-checks before reuse\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n\n## Accessibility and portability\n\nKeep the common probability distributions source selectable and editable. For an isolated character in common probability distributions, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of common probability distributions is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in common probability distributions has one defined meaning in the local context.\n- Reopen the exported file for **Common Probability Distributions: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "common-statistics-symbols",
    "title": "Common Statistics Symbols Explained",
    "description": "Understand sample and population notation for means, variance, probability, and estimators.",
    "topic": "Reference",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "# Common Statistics Symbols Explained\n\nUnderstand sample and population notation for means, variance, probability, and estimators. This guide focuses on reliable methods that preserve the intended character or mathematical structure when the text is copied, published, or shared.\n\n## Quick answer\n\nThe fastest option is to copy this character: **x\u0304**. For a real mathematical equation, use the LaTeX form \u0060\\bar{x}\u0060 when your editor supports math rendering. Plain Unicode is ideal for short text, while LaTeX or an equation editor is better for structured notation.\n\n## Choose the right format\n\nUse **Unicode** when the symbol must remain a normal text character in an email, title, spreadsheet, or social post. Use **LaTeX** when the expression contains fractions, roots, limits, stacked scripts, or other two-dimensional notation. Use **HTML entities or numeric references** when the symbol is part of a web page and escaping or source-code clarity matters. Use **MathML** when semantic browser-accessible mathematics is required.\n\n| Format | Value | Best for |\n|---|---|---|\n| Character | \u0060x\u0304\u0060 | Plain text and quick copy |\n| Unicode | \u0060U\u002B0078 \u002B U\u002B0304\u0060 | Character lookup and encoding |\n| LaTeX | \u0060\\bar{x}\u0060 | Equations and technical writing |\n| HTML | \u0060x\u0026#772;\u0060 | Web pages |\n| MathML | \u0060\u0026lt;mover\u0026gt;\u0026lt;mi\u0026gt;x\u0026lt;/mi\u0026gt;\u0026lt;mo\u0026gt;\u00AF\u0026lt;/mo\u0026gt;\u0026lt;/mover\u0026gt;\u0060 | Semantic web mathematics |\n\n## Windows\n\nOpen **Character Map**, search for the symbol name, select the character, and copy it. In Microsoft Word and some Office applications, you can also type the hexadecimal Unicode value and press **Alt\u002BX**. Application support varies, so verify the result before relying on a shortcut in a different editor.\n\n## Mac\n\nPress **Control\u2013Command\u2013Space** to open Character Viewer. Search for the English symbol name, then double-click the result. Frequently used characters can be added to Favorites. In equation-capable applications, prefer the app\u2019s math editor when the character is part of a larger formula.\n\n## Microsoft Word\n\nPress **Alt\u002B=** to open an equation, type \u0060\\bar{x}\u0060, and press Space when Word recognizes the command. For plain text, use **Insert \u2192 Symbol \u2192 More Symbols**, or paste the Unicode character. The equation route is preferable when scripts, fractions, limits, or alignment are involved.\n\n## Google Docs\n\nChoose **Insert \u2192 Special characters**, search by name, or draw an approximate shape. For equations, choose **Insert \u2192 Equation** and use the available notation controls. Google Docs supports a useful subset of equation shortcuts, but it does not behave exactly like a full LaTeX system.\n\n## HTML and web pages\n\nA literal UTF-8 character is usually the clearest choice when the document declares UTF-8. Named entities can improve readability for common characters, while numeric references are a dependable fallback. Keep the symbol in meaningful text rather than using a background image, because text is selectable, searchable, and more accessible.\n\n\u0060\u0060\u0060html\n\u003Cspan aria-label=\u0022Sample Mean\u0022\u003Ex\u0304\u003C/span\u003E\n\u003Cspan\u003Ex\u0026#772;\u003C/span\u003E\n\u0060\u0060\u0060\n\n## LaTeX example\n\n\u0060\u0060\u0060latex\n\\bar{x}\n\u0060\u0060\u0060\n\nWhen the symbol is an operator or relation, place it in math mode and allow LaTeX to apply the correct spacing. Avoid forcing a mathematical expression into a sequence of unrelated Unicode characters when semantic structure matters.\n\n## Common mistakes\n\nDo not substitute a visually similar letter, punctuation mark, or image. Similar-looking characters may have different Unicode values and meanings. Also avoid copying from a decorative font that changes the glyph without changing the underlying character. Finally, check whether the surrounding context requires a specific convention; several mathematical symbols have meanings that vary by field or textbook.\n\n## Related resources\n\nUse the symbol page for definitions, examples, copy controls, and platform-specific input methods. Browse the relevant category for nearby notation, or open the LaTeX editor to test a complete formula before publishing it.\n"
  },
  {
    "slug": "commutator-anticommutator-notation",
    "title": "Commutator and Anticommutator Notation",
    "description": "Distinguish commutators, anticommutators, ordering, and algebra conventions.",
    "topic": "Quantum Mechanics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Distinguish commutators, anticommutators, ordering, and algebra conventions.\n\n## Core notation for Commutator and Anticommutator Notation\n\nIn quantum mechanics, the notation usually represents states, bras, kets, operators, observables, amplitudes, and Hilbert-space conventions. The table below gives a compact starting set for commutator and anticommutator notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Dual state | \u0060\\langle\\psi\\rvert\u0060 | bra dual to the ket |\n| Inner product | \u0060\\langle\\phi\\mid\\psi\\rangle\u0060 | complex amplitude between states |\n| Expectation | \u0060\\langle A\\rangle=\\langle\\psi\\rvert\\hat A\\lvert\\psi\\rangle\u0060 | expected value of observable A |\n| Commutator | \u0060[\\hat A,\\hat B]=\\hat A\\hat B-\\hat B\\hat A\u0060 | operator noncommutativity |\n\n## Practical workflow\n\nStart from \u0060\\langle\\psi\\rvert\u0060 and write one sentence that says it means \u201Cbra dual to the ket.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish operators from scalar eigenvalues typographically.\n- State normalization and basis conventions.\n- Keep complex conjugation and adjoints explicit.\n\n## Failure checks\n\n- Reversing bra and ket order in a complex inner product.\n- Treating noncommuting operators as ordinary scalars.\n- Omitting normalization before interpreting probabilities.\n\n## Accessibility and portability\n\nKeep the commutator and anticommutator notation source selectable and editable. For an isolated character in commutator and anticommutator notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of commutator and anticommutator notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify state normalization.\n- Check operator hermiticity when representing an observable.\n- Test the expression in a finite-dimensional basis.\n- Confirm every symbol used in commutator and anticommutator notation has one defined meaning in the local context.\n- Reopen the exported file for **Commutator and Anticommutator Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "compactness-connectedness-notation",
    "title": "Compactness and Connectedness Notation",
    "description": "Document compact, connected, path-connected, and component notation without relying on overloaded abbreviations.",
    "topic": "Topology",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Document compact, connected, path-connected, and component notation without relying on overloaded abbreviations.\n\n## Core notation for Compactness and Connectedness Notation\n\nIn topology, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for compactness and connectedness notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Interior | \u0060A^\\circ\u0060 | largest open set contained in A |\n| Continuity | \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 | topological continuity criterion |\n| Complex logarithm | \u0060\\Log z=\\ln|z|\u002Bi\\Arg z\u0060 | a selected logarithm branch |\n| Residue theorem | \u0060\\oint_\\gamma f(z)\\,dz=2\\pi i\\sum_k\\operatorname{Res}(f,z_k)\u0060 | contour integral from enclosed residues |\n\n## Practical workflow\n\nStart from \u0060A^\\circ\u0060 and write one sentence that says it means \u201Clargest open set contained in A.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the ambient space and topology.\n- Distinguish local from global properties.\n- Declare contour orientation and branch choices.\n\n## Failure checks\n\n- Using closed and bounded as a universal compactness criterion.\n- Crossing a branch cut without changing the selected argument.\n- Omitting hypotheses from a convergence or interchange theorem.\n\n## Accessibility and portability\n\nKeep the compactness and connectedness notation source selectable and editable. For an isolated character in compactness and connectedness notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of compactness and connectedness notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in compactness and connectedness notation has one defined meaning in the local context.\n- Reopen the exported file for **Compactness and Connectedness Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "complex-exponential-euler",
    "title": "Complex Exponentials and Euler\u2019s Formula",
    "description": "Relate rectangular, polar, exponential, modulus, and argument forms.",
    "topic": "Complex Analysis",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Relate rectangular, polar, exponential, modulus, and argument forms.\n\n## Core notation for Complex Exponentials and Euler\u2019s Formula\n\nIn complex analysis, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for complex exponentials and euler\u2019s formula; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Interior | \u0060A^\\circ\u0060 | largest open set contained in A |\n| Continuity | \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 | topological continuity criterion |\n| Complex logarithm | \u0060\\Log z=\\ln|z|\u002Bi\\Arg z\u0060 | a selected logarithm branch |\n| Residue theorem | \u0060\\oint_\\gamma f(z)\\,dz=2\\pi i\\sum_k\\operatorname{Res}(f,z_k)\u0060 | contour integral from enclosed residues |\n\n## Practical workflow\n\nStart from \u0060A^\\circ\u0060 and write one sentence that says it means \u201Clargest open set contained in A.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the ambient space and topology.\n- Distinguish local from global properties.\n- Declare contour orientation and branch choices.\n\n## Failure checks\n\n- Using closed and bounded as a universal compactness criterion.\n- Crossing a branch cut without changing the selected argument.\n- Omitting hypotheses from a convergence or interchange theorem.\n\n## Accessibility and portability\n\nKeep the complex exponentials and euler\u2019s formula source selectable and editable. For an isolated character in complex exponentials and euler\u2019s formula, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of complex exponentials and euler\u2019s formula is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in complex exponentials and euler\u2019s formula has one defined meaning in the local context.\n- Reopen the exported file for **Complex Exponentials and Euler\u2019s Formula** and compare it with the editable source.\n"
  },
  {
    "slug": "complex-number-notation-guide",
    "title": "Complex Number Notation and Polar Form",
    "description": "Write complex numbers in rectangular, polar, and exponential form and keep the imaginary unit visually distinct.",
    "topic": "Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Write complex numbers in rectangular, polar, and exponential form and keep the imaginary unit visually distinct.\n\n## Core notation for Complex Number Notation and Polar Form\n\nIn algebra, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for complex number notation and polar form; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n\n## Practical workflow\n\nStart from \u0060\\frac{a}{b}\u0060 and write one sentence that says it means \u201Cstructured two-dimensional fraction.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for complex number notation and polar form rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the complex number notation and polar form notation.\n\n## Failure checks\n\n- Copying a rendered complex number notation and polar form image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in complex number notation and polar form.\n- Defining complex number notation and polar form macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the complex number notation and polar form source selectable and editable. For an isolated character in complex number notation and polar form, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of complex number notation and polar form is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the complex number notation and polar form example.\n- Confirm every symbol used in complex number notation and polar form has one defined meaning in the local context.\n- Reopen the exported file for **Complex Number Notation and Polar Form** and compare it with the editable source.\n"
  },
  {
    "slug": "conditional-entropy-chain-rule",
    "title": "Conditional Entropy and Chain Rules",
    "description": "Write conditional entropy, joint entropy, and information chain rules consistently.",
    "topic": "Information Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Write conditional entropy, joint entropy, and information chain rules consistently.\n\n## Core notation for Conditional Entropy and Chain Rules\n\nIn information theory, the notation usually represents random variables, alphabets, distributions, code lengths, channels, and logarithm bases. The table below gives a compact starting set for conditional entropy and chain rules; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Mutual information | \u0060I(X;Y)=H(X)-H(X\\mid Y)\u0060 | shared information between X and Y |\n| KL divergence | \u0060D_{\\mathrm{KL}}(P\\Vert Q)=\\sum_x p(x)\\log\\frac{p(x)}{q(x)}\u0060 | directed divergence from Q to P |\n| Channel capacity | \u0060C=\\max_{p(x)}I(X;Y)\u0060 | maximum mutual information over input distributions |\n| Chain rule | \u0060H(X,Y)=H(X)\u002BH(Y\\mid X)\u0060 | joint entropy decomposition |\n\n## Practical workflow\n\nStart from \u0060I(X;Y)=H(X)-H(X\\mid Y)\u0060 and write one sentence that says it means \u201Cshared information between X and Y.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the logarithm base and resulting unit.\n- Distinguish entropy, cross-entropy, and kl divergence.\n- Specify discrete sums versus continuous integrals.\n\n## Failure checks\n\n- Assuming kl divergence is symmetric.\n- Mixing bits and nats in one calculation.\n- Using 0 log 0 without the standard limiting convention.\n\n## Accessibility and portability\n\nKeep the conditional entropy and chain rules source selectable and editable. For an isolated character in conditional entropy and chain rules, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of conditional entropy and chain rules is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities normalize.\n- Test deterministic and uniform distributions.\n- Confirm the order of p and q in every divergence.\n- Confirm every symbol used in conditional entropy and chain rules has one defined meaning in the local context.\n- Reopen the exported file for **Conditional Entropy and Chain Rules** and compare it with the editable source.\n"
  },
  {
    "slug": "confidence-interval-notation",
    "title": "Confidence Interval Notation",
    "description": "State estimator, standard error, critical value, confidence level, and assumptions.",
    "topic": "Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "State estimator, standard error, critical value, confidence level, and assumptions.\n\n## Core notation for Confidence Interval Notation\n\nIn statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for confidence interval notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n| Correlation | \u0060r=\\frac{\\operatorname{cov}(X,Y)}{s_Xs_Y}\u0060 | standardized linear association |\n\n## Practical workflow\n\nStart from \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 and write one sentence that says it means \u201Can unbiased variance estimate under the usual assumptions.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Failure checks\n\n- Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate.\n- Reporting a standard deviation as though it were a standard error.\n- Rounding intermediate values so aggressively that the final result changes.\n\n## Accessibility and portability\n\nKeep the confidence interval notation source selectable and editable. For an isolated character in confidence interval notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of confidence interval notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in confidence interval notation has one defined meaning in the local context.\n- Reopen the exported file for **Confidence Interval Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "unicode-confusable-math-symbols",
    "title": "Confusable Mathematical Symbols",
    "description": "Compare minus and hyphen, multiplication and letter x, Greek and Latin letters, and visually similar relation symbols.",
    "topic": "Unicode",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Compare minus and hyphen, multiplication and letter x, Greek and Latin letters, and visually similar relation symbols.\n\n## Core notation for Confusable Mathematical Symbols\n\nIn unicode, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for confusable mathematical symbols; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## Practical workflow\n\nStart from \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 and write one sentence that says it means \u201Csemantic operator element.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for confusable mathematical symbols rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the confusable mathematical symbols notation.\n\n## Failure checks\n\n- Copying a rendered confusable mathematical symbols image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in confusable mathematical symbols.\n- Defining confusable mathematical symbols macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the confusable mathematical symbols source selectable and editable. For an isolated character in confusable mathematical symbols, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of confusable mathematical symbols is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the confusable mathematical symbols example.\n- Confirm every symbol used in confusable mathematical symbols has one defined meaning in the local context.\n- Reopen the exported file for **Confusable Mathematical Symbols** and compare it with the editable source.\n"
  },
  {
    "slug": "continuity-homeomorphism-notation",
    "title": "Continuity and Homeomorphism Notation",
    "description": "Separate continuous maps, embeddings, quotient maps, and homeomorphisms in topology writing.",
    "topic": "Topology",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Separate continuous maps, embeddings, quotient maps, and homeomorphisms in topology writing.\n\n## Core notation for Continuity and Homeomorphism Notation\n\nIn topology, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for continuity and homeomorphism notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Residue theorem | \u0060\\oint_\\gamma f(z)\\,dz=2\\pi i\\sum_k\\operatorname{Res}(f,z_k)\u0060 | contour integral from enclosed residues |\n| Open ball | \u0060B_r(x)=\\{y:d(x,y)\u003Cr\\}\u0060 | points within radius r of x |\n| Closure | \u0060\\overline{A}\u0060 | A together with its limit points |\n| Interior | \u0060A^\\circ\u0060 | largest open set contained in A |\n\n## Practical workflow\n\nStart from \u0060\\oint_\\gamma f(z)\\,dz=2\\pi i\\sum_k\\operatorname{Res}(f,z_k)\u0060 and write one sentence that says it means \u201Ccontour integral from enclosed residues.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the ambient space and topology.\n- Distinguish local from global properties.\n- Declare contour orientation and branch choices.\n\n## Failure checks\n\n- Using closed and bounded as a universal compactness criterion.\n- Crossing a branch cut without changing the selected argument.\n- Omitting hypotheses from a convergence or interchange theorem.\n\n## Accessibility and portability\n\nKeep the continuity and homeomorphism notation source selectable and editable. For an isolated character in continuity and homeomorphism notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of continuity and homeomorphism notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in continuity and homeomorphism notation has one defined meaning in the local context.\n- Reopen the exported file for **Continuity and Homeomorphism Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "iterative-method-convergence",
    "title": "Convergence Notation for Iterative Methods",
    "description": "Use iteration counters, residual norms, tolerance tests, convergence rates, and stopping conditions consistently.",
    "topic": "Numerical Methods",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Use iteration counters, residual norms, tolerance tests, convergence rates, and stopping conditions consistently.\n\n## Core notation for Convergence Notation for Iterative Methods\n\nIn numerical methods, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for convergence notation for iterative methods; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## Practical workflow\n\nStart from \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 and write one sentence that says it means \u201Csemantic operator element.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for convergence notation for iterative methods rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the convergence notation for iterative methods notation.\n\n## Failure checks\n\n- Copying a rendered convergence notation for iterative methods image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in convergence notation for iterative methods.\n- Defining convergence notation for iterative methods macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the convergence notation for iterative methods source selectable and editable. For an isolated character in convergence notation for iterative methods, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of convergence notation for iterative methods is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the convergence notation for iterative methods example.\n- Confirm every symbol used in convergence notation for iterative methods has one defined meaning in the local context.\n- Reopen the exported file for **Convergence Notation for Iterative Methods** and compare it with the editable source.\n"
  },
  {
    "slug": "convex-functions-jensen",
    "title": "Convex Functions and Jensen\u2019s Inequality",
    "description": "Check convexity domains, weights, expectations, and equality cases.",
    "topic": "Optimization",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Check convexity domains, weights, expectations, and equality cases.\n\n## Core notation for Convex Functions and Jensen\u2019s Inequality\n\nIn optimization, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for convex functions and jensen\u2019s inequality; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Argmin | \u0060x^\\star\\in\\operatorname*{arg\\,min}_x f(x)\u0060 | a minimizer rather than the minimum value |\n| Dual bound | \u0060d^\\star\\le p^\\star\u0060 | weak duality for a minimization primal |\n| Optimization problem | \u0060\\min_x f(x)\\quad\\text{s.t.}\\quad g_i(x)\\le 0\u0060 | minimize an objective over a constrained feasible set |\n| Lagrangian | \u0060\\mathcal{L}(x,\\lambda)=f(x)\u002B\\sum_i\\lambda_i g_i(x)\u0060 | objective plus weighted constraints |\n\n## Practical workflow\n\nStart from \u0060x^\\star\\in\\operatorname*{arg\\,min}_x f(x)\u0060 and write one sentence that says it means \u201Ca minimizer rather than the minimum value.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State minimization versus maximization and all constraint directions.\n- Separate an optimizer from the attained objective value.\n- Declare convexity and constraint-qualification assumptions.\n\n## Failure checks\n\n- Reversing a constraint sign without changing the multiplier convention.\n- Writing min when the result required is argmin.\n- Claiming kkt conditions are sufficient without convexity.\n\n## Accessibility and portability\n\nKeep the convex functions and jensen\u2019s inequality source selectable and editable. For an isolated character in convex functions and jensen\u2019s inequality, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of convex functions and jensen\u2019s inequality is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in convex functions and jensen\u2019s inequality has one defined meaning in the local context.\n- Reopen the exported file for **Convex Functions and Jensen\u2019s Inequality** and compare it with the editable source.\n"
  },
  {
    "slug": "convexity-notation-guide",
    "title": "Convexity and Jensen Notation",
    "description": "Use convex combinations, epigraphs, Hessians, inequalities, and expectation notation without losing assumptions.",
    "topic": "Optimization",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Use convex combinations, epigraphs, Hessians, inequalities, and expectation notation without losing assumptions.\n\n## Core notation for Convexity and Jensen Notation\n\nIn optimization, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for convexity and jensen notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Stationarity | \u0060\\nabla_x\\mathcal{L}(x,\\lambda)=0\u0060 | first-order stationarity condition |\n| Complementarity | \u0060\\lambda_i g_i(x)=0\u0060 | active-constraint relationship |\n| Argmin | \u0060x^\\star\\in\\operatorname*{arg\\,min}_x f(x)\u0060 | a minimizer rather than the minimum value |\n| Dual bound | \u0060d^\\star\\le p^\\star\u0060 | weak duality for a minimization primal |\n\n## Practical workflow\n\nStart from \u0060\\nabla_x\\mathcal{L}(x,\\lambda)=0\u0060 and write one sentence that says it means \u201Cfirst-order stationarity condition.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State minimization versus maximization and all constraint directions.\n- Separate an optimizer from the attained objective value.\n- Declare convexity and constraint-qualification assumptions.\n\n## Failure checks\n\n- Reversing a constraint sign without changing the multiplier convention.\n- Writing min when the result required is argmin.\n- Claiming kkt conditions are sufficient without convexity.\n\n## Accessibility and portability\n\nKeep the convexity and jensen notation source selectable and editable. For an isolated character in convexity and jensen notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of convexity and jensen notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in convexity and jensen notation has one defined meaning in the local context.\n- Reopen the exported file for **Convexity and Jensen Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "coordinate-geometry-common-errors",
    "title": "Coordinate Geometry: Common Errors and Verification",
    "description": "Common Errors and Verification for coordinate geometry: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Coordinate Geometry",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Coordinate Geometry: Common Errors and Verification explains points, slopes, distances, midpoint formulas, lines, circles, and coordinate conventions.\n\n## Core notation for Coordinate Geometry: Common Errors and Verification\n\nIn coordinate geometry, the notation usually represents points, lines, angles, lengths, coordinates, transformations, and orientation. The table below gives a compact starting set for coordinate geometry: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sine rule | \u0060\\frac{a}{\\sin A}=\\frac{b}{\\sin B}=\\frac{c}{\\sin C}\u0060 | side-angle relation in a triangle |\n| Dot product | \u0060u\\cdot v=\\lVert u\\rVert\\lVert v\\rVert\\cos\\theta\u0060 | angle relation for vectors |\n| Area | \u0060A=\\frac12 ab\\sin C\u0060 | triangle area from two sides and included angle |\n| Distance | \u0060d=\\sqrt{(x_2-x_1)^2\u002B(y_2-y_1)^2}\u0060 | Euclidean distance in the plane |\n\n## Errors that change the meaning\n\n- **Problem:** Feeding degree values into a radian-based function. **Correction:** write the missing coordinate geometry: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using slope formulas for vertical lines without a special case. **Correction:** write the missing coordinate geometry: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Discarding orientation when a signed area or angle is required. **Correction:** write the missing coordinate geometry: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the coordinate geometry: common errors and verification expression. Then check the coordinate geometry: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced coordinate geometry: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n\n## Accessibility and portability\n\nKeep the coordinate geometry: common errors and verification source selectable and editable. For an isolated character in coordinate geometry: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of coordinate geometry: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n- Confirm every symbol used in coordinate geometry: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Coordinate Geometry: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "coordinate-geometry-latex-formatting",
    "title": "Coordinate Geometry: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for coordinate geometry: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Coordinate Geometry",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Coordinate Geometry: LaTeX Formatting Guide explains points, slopes, distances, midpoint formulas, lines, circles, and coordinate conventions.\n\n## Core notation for Coordinate Geometry\n\nIn coordinate geometry, the notation usually represents points, lines, angles, lengths, coordinates, transformations, and orientation. The table below gives a compact starting set for coordinate geometry; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Area | \u0060A=\\frac12 ab\\sin C\u0060 | triangle area from two sides and included angle |\n| Distance | \u0060d=\\sqrt{(x_2-x_1)^2\u002B(y_2-y_1)^2}\u0060 | Euclidean distance in the plane |\n| Line | \u0060y=mx\u002Bb\u0060 | slope-intercept form |\n| Pythagorean relation | \u0060a^2\u002Bb^2=c^2\u0060 | right-triangle side relation |\n\n## LaTeX patterns that preserve the structure\n\nFor coordinate geometry: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nA=\\frac12 ab\\sin C\nd=\\sqrt{(x_2-x_1)^2\u002B(y_2-y_1)^2}\ny=mx\u002Bb\n\u0060\u0060\u0060\n\nFor coordinate geometry, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In coordinate geometry, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State degrees versus radians.\n- Name the coordinate system and orientation.\n- Distinguish directed angles, lengths, and vectors.\n\n## Renderer and export checks\n\nRender one demanding coordinate geometry example in the actual destination. For coordinate geometry, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the coordinate geometry source selectable and editable. For an isolated character in coordinate geometry, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of coordinate geometry is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n- Confirm every symbol used in coordinate geometry has one defined meaning in the local context.\n- Reopen the exported file for **Coordinate Geometry: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "coordinate-geometry-notation-reference",
    "title": "Coordinate Geometry: Notation Reference",
    "description": "Notation Reference for coordinate geometry: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Coordinate Geometry",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Coordinate Geometry: Notation Reference explains points, slopes, distances, midpoint formulas, lines, circles, and coordinate conventions.\n\n## Core notation for Coordinate Geometry\n\nIn coordinate geometry, the notation usually represents points, lines, angles, lengths, coordinates, transformations, and orientation. The table below gives a compact starting set for coordinate geometry; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Distance | \u0060d=\\sqrt{(x_2-x_1)^2\u002B(y_2-y_1)^2}\u0060 | Euclidean distance in the plane |\n| Line | \u0060y=mx\u002Bb\u0060 | slope-intercept form |\n| Pythagorean relation | \u0060a^2\u002Bb^2=c^2\u0060 | right-triangle side relation |\n| Sine rule | \u0060\\frac{a}{\\sin A}=\\frac{b}{\\sin B}=\\frac{c}{\\sin C}\u0060 | side-angle relation in a triangle |\n\n## How to read a complete expression\n\nRead \u0060d=\\sqrt{(x_2-x_1)^2\u002B(y_2-y_1)^2}\u0060 as \u201CEuclidean distance in the plane.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in coordinate geometry from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State degrees versus radians.\n- Name the coordinate system and orientation.\n- Distinguish directed angles, lengths, and vectors.\n\n## Cross-checks before reuse\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n\n## Accessibility and portability\n\nKeep the coordinate geometry source selectable and editable. For an isolated character in coordinate geometry, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of coordinate geometry is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n- Confirm every symbol used in coordinate geometry has one defined meaning in the local context.\n- Reopen the exported file for **Coordinate Geometry: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "covariance-correlation-matrix",
    "title": "Covariance and Correlation Matrices",
    "description": "Interpret diagonal entries, scales, symmetry, and positive semidefiniteness.",
    "topic": "Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Interpret diagonal entries, scales, symmetry, and positive semidefiniteness.\n\n## Core notation for Covariance and Correlation Matrices\n\nIn statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for covariance and correlation matrices; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sample mean | \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 | the arithmetic mean of n observations |\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n\n## Practical workflow\n\nStart from \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 and write one sentence that says it means \u201Cthe arithmetic mean of n observations.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Failure checks\n\n- Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate.\n- Reporting a standard deviation as though it were a standard error.\n- Rounding intermediate values so aggressively that the final result changes.\n\n## Accessibility and portability\n\nKeep the covariance and correlation matrices source selectable and editable. For an isolated character in covariance and correlation matrices, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of covariance and correlation matrices is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in covariance and correlation matrices has one defined meaning in the local context.\n- Reopen the exported file for **Covariance and Correlation Matrices** and compare it with the editable source.\n"
  },
  {
    "slug": "covariant-derivative-notation",
    "title": "Covariant Derivative Notation",
    "description": "Distinguish partial, covariant, directional, and Lie derivatives.",
    "topic": "Tensor Calculus",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Distinguish partial, covariant, directional, and Lie derivatives.\n\n## Core notation for Covariant Derivative Notation\n\nIn tensor calculus, the notation usually represents tensor components, index positions, coordinate charts, bases, and contraction rules. The table below gives a compact starting set for covariant derivative notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Contraction | \u0060T^{i}{}_{ik}\u0060 | summation over a repeated upper-lower index |\n| Metric lowering | \u0060v_i=g_{ij}v^j\u0060 | lowering an index with the metric |\n| Metric raising | \u0060v^i=g^{ij}v_j\u0060 | raising an index with the inverse metric |\n| Covariant derivative | \u0060\\nabla_i v^j\u0060 | coordinate-aware derivative of a vector field |\n\n## Practical workflow\n\nStart from \u0060T^{i}{}_{ik}\u0060 and write one sentence that says it means \u201Csummation over a repeated upper-lower index.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Declare the index range and summation convention.\n- Keep upper and lower index roles consistent.\n- State the metric signature and coordinate chart.\n\n## Failure checks\n\n- Repeating an index more than twice in one monomial.\n- Contracting two upper indices without a metric.\n- Moving an index without applying the metric tensor.\n\n## Accessibility and portability\n\nKeep the covariant derivative notation source selectable and editable. For an isolated character in covariant derivative notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of covariant derivative notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify each free index appears once on both sides.\n- Check that dummy indices may be renamed consistently.\n- Test the expression in a simple coordinate system.\n- Confirm every symbol used in covariant derivative notation has one defined meaning in the local context.\n- Reopen the exported file for **Covariant Derivative Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "latex-error-debugging",
    "title": "Debugging LaTeX Math Errors",
    "description": "Isolate missing braces, environments, packages, commands, and delimiter mismatches.",
    "topic": "LaTeX",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Isolate missing braces, environments, packages, commands, and delimiter mismatches.\n\n## Core notation for Debugging LaTeX Math Errors\n\nIn latex, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for debugging latex math errors; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n\n## Practical workflow\n\nStart from \u0060\\text{\u201Cx squared plus one\u201D}\u0060 and write one sentence that says it means \u201Cplain-language reading when a text alternative is needed.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for debugging latex math errors rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the debugging latex math errors notation.\n\n## Failure checks\n\n- Copying a rendered debugging latex math errors image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in debugging latex math errors.\n- Defining debugging latex math errors macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the debugging latex math errors source selectable and editable. For an isolated character in debugging latex math errors, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of debugging latex math errors is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the debugging latex math errors example.\n- Confirm every symbol used in debugging latex math errors has one defined meaning in the local context.\n- Reopen the exported file for **Debugging LaTeX Math Errors** and compare it with the editable source.\n"
  },
  {
    "slug": "derivative-rules-common-errors",
    "title": "Derivative Rules: Common Errors and Verification",
    "description": "Common Errors and Verification for derivative rules: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Derivative Rules",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Derivative Rules: Common Errors and Verification explains power, product, quotient, chain, implicit, and higher-order derivatives.\n\n## Core notation for Derivative Rules: Common Errors and Verification\n\nIn derivative rules, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for derivative rules: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n\n## Errors that change the meaning\n\n- **Problem:** Dropping an absolute value in a substitution jacobian. **Correction:** write the missing derivative rules: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Interchanging a limit, sum, derivative, or integral without conditions. **Correction:** write the missing derivative rules: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Omitting boundary terms after integration by parts. **Correction:** write the missing derivative rules: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the derivative rules: common errors and verification expression. Then check the derivative rules: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced derivative rules: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the derivative rules: common errors and verification source selectable and editable. For an isolated character in derivative rules: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of derivative rules: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in derivative rules: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Derivative Rules: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "derivative-rules-latex-formatting",
    "title": "Derivative Rules: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for derivative rules: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Derivative Rules",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Derivative Rules: LaTeX Formatting Guide explains power, product, quotient, chain, implicit, and higher-order derivatives.\n\n## Core notation for Derivative Rules\n\nIn derivative rules, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for derivative rules; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n\n## LaTeX patterns that preserve the structure\n\nFor derivative rules: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nf\\\u0027(x)=\\frac{df}{dx}\n\\nabla f\n\\int_a^b f(x)\\,dx\n\u0060\u0060\u0060\n\nFor derivative rules, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In derivative rules, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Renderer and export checks\n\nRender one demanding derivative rules example in the actual destination. For derivative rules, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the derivative rules source selectable and editable. For an isolated character in derivative rules, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of derivative rules is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in derivative rules has one defined meaning in the local context.\n- Reopen the exported file for **Derivative Rules: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "derivative-rules-notation-reference",
    "title": "Derivative Rules: Notation Reference",
    "description": "Notation Reference for derivative rules: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Derivative Rules",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Derivative Rules: Notation Reference explains power, product, quotient, chain, implicit, and higher-order derivatives.\n\n## Core notation for Derivative Rules\n\nIn derivative rules, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for derivative rules; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n\n## How to read a complete expression\n\nRead \u0060\\nabla\\cdot F\u0060 as \u201Clocal source strength of a vector field.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in derivative rules from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Cross-checks before reuse\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the derivative rules source selectable and editable. For an isolated character in derivative rules, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of derivative rules is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in derivative rules has one defined meaning in the local context.\n- Reopen the exported file for **Derivative Rules: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "descriptive-statistics-common-errors",
    "title": "Descriptive Statistics: Common Errors and Verification",
    "description": "Common Errors and Verification for descriptive statistics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Descriptive Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Descriptive Statistics: Common Errors and Verification explains center, spread, quantiles, outliers, samples, and reporting conventions.\n\n## Core notation for Descriptive Statistics: Common Errors and Verification\n\nIn descriptive statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for descriptive statistics: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Correlation | \u0060r=\\frac{\\operatorname{cov}(X,Y)}{s_Xs_Y}\u0060 | standardized linear association |\n| Observation | \u0060x_i\u0060 | the i-th measured or observed value |\n| Sample mean | \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 | the arithmetic mean of n observations |\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n\n## Errors that change the meaning\n\n- **Problem:** Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate. **Correction:** write the missing descriptive statistics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Reporting a standard deviation as though it were a standard error. **Correction:** write the missing descriptive statistics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Rounding intermediate values so aggressively that the final result changes. **Correction:** write the missing descriptive statistics: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the descriptive statistics: common errors and verification expression. Then check the descriptive statistics: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced descriptive statistics: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n\n## Accessibility and portability\n\nKeep the descriptive statistics: common errors and verification source selectable and editable. For an isolated character in descriptive statistics: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of descriptive statistics: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in descriptive statistics: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Descriptive Statistics: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "descriptive-statistics-latex-formatting",
    "title": "Descriptive Statistics: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for descriptive statistics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Descriptive Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Descriptive Statistics: LaTeX Formatting Guide explains center, spread, quantiles, outliers, samples, and reporting conventions.\n\n## Core notation for Descriptive Statistics\n\nIn descriptive statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for descriptive statistics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Correlation | \u0060r=\\frac{\\operatorname{cov}(X,Y)}{s_Xs_Y}\u0060 | standardized linear association |\n| Observation | \u0060x_i\u0060 | the i-th measured or observed value |\n| Sample mean | \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 | the arithmetic mean of n observations |\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n\n## LaTeX patterns that preserve the structure\n\nFor descriptive statistics: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nr=\\frac{\\operatorname{cov}(X,Y)}{s_Xs_Y}\nx_i\n\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\n\u0060\u0060\u0060\n\nFor descriptive statistics, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In descriptive statistics, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Renderer and export checks\n\nRender one demanding descriptive statistics example in the actual destination. For descriptive statistics, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the descriptive statistics source selectable and editable. For an isolated character in descriptive statistics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of descriptive statistics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in descriptive statistics has one defined meaning in the local context.\n- Reopen the exported file for **Descriptive Statistics: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "descriptive-statistics-guide",
    "title": "Descriptive Statistics: Mean, Median, Mode, Variance, and Standard Deviation",
    "description": "Choose the correct descriptive statistic, distinguish population and sample formulas, and avoid common data-entry mistakes.",
    "topic": "Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Choose the correct descriptive statistic, distinguish population and sample formulas, and avoid common data-entry mistakes.\n\n## Core notation for Descriptive Statistics: Mean, Median, Mode, Variance, and Standard Deviation\n\nIn statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for descriptive statistics: mean, median, mode, variance, and standard deviation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sample mean | \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 | the arithmetic mean of n observations |\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n\n## Practical workflow\n\nStart from \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 and write one sentence that says it means \u201Cthe arithmetic mean of n observations.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Failure checks\n\n- Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate.\n- Reporting a standard deviation as though it were a standard error.\n- Rounding intermediate values so aggressively that the final result changes.\n\n## Accessibility and portability\n\nKeep the descriptive statistics: mean, median, mode, variance, and standard deviation source selectable and editable. For an isolated character in descriptive statistics: mean, median, mode, variance, and standard deviation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of descriptive statistics: mean, median, mode, variance, and standard deviation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in descriptive statistics: mean, median, mode, variance, and standard deviation has one defined meaning in the local context.\n- Reopen the exported file for **Descriptive Statistics: Mean, Median, Mode, Variance, and Standard Deviation** and compare it with the editable source.\n"
  },
  {
    "slug": "descriptive-statistics-notation-reference",
    "title": "Descriptive Statistics: Notation Reference",
    "description": "Notation Reference for descriptive statistics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Descriptive Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Descriptive Statistics: Notation Reference explains center, spread, quantiles, outliers, samples, and reporting conventions.\n\n## Core notation for Descriptive Statistics\n\nIn descriptive statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for descriptive statistics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n| Correlation | \u0060r=\\frac{\\operatorname{cov}(X,Y)}{s_Xs_Y}\u0060 | standardized linear association |\n\n## How to read a complete expression\n\nRead \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 as \u201Can unbiased variance estimate under the usual assumptions.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in descriptive statistics from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Cross-checks before reuse\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n\n## Accessibility and portability\n\nKeep the descriptive statistics source selectable and editable. For an isolated character in descriptive statistics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of descriptive statistics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in descriptive statistics has one defined meaning in the local context.\n- Reopen the exported file for **Descriptive Statistics: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "differential-equations-common-errors",
    "title": "Differential Equations: Common Errors and Verification",
    "description": "Common Errors and Verification for differential equations: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Differential Equations",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Differential Equations: Common Errors and Verification explains initial conditions, boundary conditions, solution families, and stability.\n\n## Core notation for Differential Equations: Common Errors and Verification\n\nIn differential equations, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for differential equations: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n\n## Errors that change the meaning\n\n- **Problem:** Dropping an absolute value in a substitution jacobian. **Correction:** write the missing differential equations: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Interchanging a limit, sum, derivative, or integral without conditions. **Correction:** write the missing differential equations: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Omitting boundary terms after integration by parts. **Correction:** write the missing differential equations: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the differential equations: common errors and verification expression. Then check the differential equations: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced differential equations: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the differential equations: common errors and verification source selectable and editable. For an isolated character in differential equations: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of differential equations: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in differential equations: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Differential Equations: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "differential-equations-latex-formatting",
    "title": "Differential Equations: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for differential equations: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Differential Equations",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Differential Equations: LaTeX Formatting Guide explains initial conditions, boundary conditions, solution families, and stability.\n\n## Core notation for Differential Equations\n\nIn differential equations, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for differential equations; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n\n## LaTeX patterns that preserve the structure\n\nFor differential equations: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\lim_{x\\to a}f(x)=L\nf\\\u0027(x)=\\frac{df}{dx}\n\\nabla f\n\u0060\u0060\u0060\n\nFor differential equations, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In differential equations, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Renderer and export checks\n\nRender one demanding differential equations example in the actual destination. For differential equations, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the differential equations source selectable and editable. For an isolated character in differential equations, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of differential equations is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in differential equations has one defined meaning in the local context.\n- Reopen the exported file for **Differential Equations: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "differential-equations-notation-reference",
    "title": "Differential Equations: Notation Reference",
    "description": "Notation Reference for differential equations: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Differential Equations",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Differential Equations: Notation Reference explains initial conditions, boundary conditions, solution families, and stability.\n\n## Core notation for Differential Equations\n\nIn differential equations, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for differential equations; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n\n## How to read a complete expression\n\nRead \u0060\\nabla\\cdot F\u0060 as \u201Clocal source strength of a vector field.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in differential equations from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Cross-checks before reuse\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the differential equations source selectable and editable. For an isolated character in differential equations, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of differential equations is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in differential equations has one defined meaning in the local context.\n- Reopen the exported file for **Differential Equations: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "dimensional-analysis-guide",
    "title": "Dimensional Analysis Guide",
    "description": "Check quantities, dimensions, units, prefixes, products, and powers.",
    "topic": "Scientific Writing",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Check quantities, dimensions, units, prefixes, products, and powers.\n\n## Core notation for Dimensional Analysis\n\nIn scientific writing, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for dimensional analysis; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Continuity | \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 | topological continuity criterion |\n| Complex logarithm | \u0060\\Log z=\\ln|z|\u002Bi\\Arg z\u0060 | a selected logarithm branch |\n| Residue theorem | \u0060\\oint_\\gamma f(z)\\,dz=2\\pi i\\sum_k\\operatorname{Res}(f,z_k)\u0060 | contour integral from enclosed residues |\n| Open ball | \u0060B_r(x)=\\{y:d(x,y)\u003Cr\\}\u0060 | points within radius r of x |\n\n## Practical workflow\n\nStart from \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 and write one sentence that says it means \u201Ctopological continuity criterion.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the ambient space and topology.\n- Distinguish local from global properties.\n- Declare contour orientation and branch choices.\n\n## Failure checks\n\n- Using closed and bounded as a universal compactness criterion.\n- Crossing a branch cut without changing the selected argument.\n- Omitting hypotheses from a convergence or interchange theorem.\n\n## Accessibility and portability\n\nKeep the dimensional analysis source selectable and editable. For an isolated character in dimensional analysis, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of dimensional analysis is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in dimensional analysis has one defined meaning in the local context.\n- Reopen the exported file for **Dimensional Analysis Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "eigenvalue-eigenvector-notation",
    "title": "Eigenvalue and Eigenvector Notation",
    "description": "Define right and left eigenvectors, multiplicities, normalization, and spectra.",
    "topic": "Linear Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Define right and left eigenvectors, multiplicities, normalization, and spectra.\n\n## Core notation for Eigenvalue and Eigenvector Notation\n\nIn linear algebra, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for eigenvalue and eigenvector notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n| Norm | \u0060\\lVert x\\rVert_2\u0060 | Euclidean length of vector x |\n| Matrix product | \u0060C=AB\u0060 | composition with inner dimensions matched |\n| Transpose | \u0060A^{\\mathsf T}\u0060 | rows and columns exchanged |\n\n## Practical workflow\n\nStart from \u0060A=U\\Sigma V^{\\mathsf T}\u0060 and write one sentence that says it means \u201Csingular value decomposition.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Failure checks\n\n- Multiplying matrices whose inner dimensions do not agree.\n- Treating elementwise multiplication as matrix multiplication.\n- Assuming an inverse exists without checking rank or determinant.\n\n## Accessibility and portability\n\nKeep the eigenvalue and eigenvector notation source selectable and editable. For an isolated character in eigenvalue and eigenvector notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of eigenvalue and eigenvector notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in eigenvalue and eigenvector notation has one defined meaning in the local context.\n- Reopen the exported file for **Eigenvalue and Eigenvector Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "eigenvalues-eigenvectors-common-errors",
    "title": "Eigenvalues and Eigenvectors: Common Errors and Verification",
    "description": "Common Errors and Verification for eigenvalues and eigenvectors: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notati",
    "topic": "Eigenvalues and Eigenvectors",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Eigenvalues and Eigenvectors: Common Errors and Verification explains characteristic equations, multiplicity, bases, and interpretation.\n\n## Core notation for Eigenvalues and Eigenvectors: Common Errors and Verification\n\nIn eigenvalues and eigenvectors, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for eigenvalues and eigenvectors: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Transpose | \u0060A^{\\mathsf T}\u0060 | rows and columns exchanged |\n| Inverse | \u0060A^{-1}A=I\u0060 | inverse relation when A is nonsingular |\n| Eigenpair | \u0060Av=\\lambda v\u0060 | v is an eigenvector with eigenvalue \u03BB |\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n\n## Errors that change the meaning\n\n- **Problem:** Multiplying matrices whose inner dimensions do not agree. **Correction:** write the missing eigenvalues and eigenvectors: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Treating elementwise multiplication as matrix multiplication. **Correction:** write the missing eigenvalues and eigenvectors: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Assuming an inverse exists without checking rank or determinant. **Correction:** write the missing eigenvalues and eigenvectors: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the eigenvalues and eigenvectors: common errors and verification expression. Then check the eigenvalues and eigenvectors: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced eigenvalues and eigenvectors: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n\n## Accessibility and portability\n\nKeep the eigenvalues and eigenvectors: common errors and verification source selectable and editable. For an isolated character in eigenvalues and eigenvectors: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of eigenvalues and eigenvectors: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in eigenvalues and eigenvectors: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Eigenvalues and Eigenvectors: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "eigenvalues-eigenvectors-latex-formatting",
    "title": "Eigenvalues and Eigenvectors: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for eigenvalues and eigenvectors: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Eigenvalues and Eigenvectors",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Eigenvalues and Eigenvectors: LaTeX Formatting Guide explains characteristic equations, multiplicity, bases, and interpretation.\n\n## Core notation for Eigenvalues and Eigenvectors\n\nIn eigenvalues and eigenvectors, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for eigenvalues and eigenvectors; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Matrix product | \u0060C=AB\u0060 | composition with inner dimensions matched |\n| Transpose | \u0060A^{\\mathsf T}\u0060 | rows and columns exchanged |\n| Inverse | \u0060A^{-1}A=I\u0060 | inverse relation when A is nonsingular |\n| Eigenpair | \u0060Av=\\lambda v\u0060 | v is an eigenvector with eigenvalue \u03BB |\n\n## LaTeX patterns that preserve the structure\n\nFor eigenvalues and eigenvectors: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nC=AB\nA^{\\mathsf T}\nA^{-1}A=I\n\u0060\u0060\u0060\n\nFor eigenvalues and eigenvectors, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In eigenvalues and eigenvectors, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Renderer and export checks\n\nRender one demanding eigenvalues and eigenvectors example in the actual destination. For eigenvalues and eigenvectors, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the eigenvalues and eigenvectors source selectable and editable. For an isolated character in eigenvalues and eigenvectors, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of eigenvalues and eigenvectors is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in eigenvalues and eigenvectors has one defined meaning in the local context.\n- Reopen the exported file for **Eigenvalues and Eigenvectors: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "eigenvalues-eigenvectors-notation-reference",
    "title": "Eigenvalues and Eigenvectors: Notation Reference",
    "description": "Notation Reference for eigenvalues and eigenvectors: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Eigenvalues and Eigenvectors",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Eigenvalues and Eigenvectors: Notation Reference explains characteristic equations, multiplicity, bases, and interpretation.\n\n## Core notation for Eigenvalues and Eigenvectors\n\nIn eigenvalues and eigenvectors, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for eigenvalues and eigenvectors; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Eigenpair | \u0060Av=\\lambda v\u0060 | v is an eigenvector with eigenvalue \u03BB |\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n| Norm | \u0060\\lVert x\\rVert_2\u0060 | Euclidean length of vector x |\n| Matrix product | \u0060C=AB\u0060 | composition with inner dimensions matched |\n\n## How to read a complete expression\n\nRead \u0060Av=\\lambda v\u0060 as \u201Cv is an eigenvector with eigenvalue \u03BB.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in eigenvalues and eigenvectors from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Cross-checks before reuse\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n\n## Accessibility and portability\n\nKeep the eigenvalues and eigenvectors source selectable and editable. For an isolated character in eigenvalues and eigenvectors, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of eigenvalues and eigenvectors is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in eigenvalues and eigenvectors has one defined meaning in the local context.\n- Reopen the exported file for **Eigenvalues and Eigenvectors: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "einstein-summation-guide",
    "title": "Einstein Summation Convention",
    "description": "Apply repeated-index summation while checking free indexes and dimensions.",
    "topic": "Tensor Calculus",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Apply repeated-index summation while checking free indexes and dimensions.\n\n## Core notation for Einstein Summation Convention\n\nIn tensor calculus, the notation usually represents tensor components, index positions, coordinate charts, bases, and contraction rules. The table below gives a compact starting set for einstein summation convention; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Covariant derivative | \u0060\\nabla_i v^j\u0060 | coordinate-aware derivative of a vector field |\n| Einstein sum | \u0060a_i b^i\u0060 | implicit sum over the repeated index |\n| Tensor component | \u0060T^{i}{}_{jk}\u0060 | one contravariant and two covariant indices |\n| Contraction | \u0060T^{i}{}_{ik}\u0060 | summation over a repeated upper-lower index |\n\n## Practical workflow\n\nStart from \u0060\\nabla_i v^j\u0060 and write one sentence that says it means \u201Ccoordinate-aware derivative of a vector field.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Declare the index range and summation convention.\n- Keep upper and lower index roles consistent.\n- State the metric signature and coordinate chart.\n\n## Failure checks\n\n- Repeating an index more than twice in one monomial.\n- Contracting two upper indices without a metric.\n- Moving an index without applying the metric tensor.\n\n## Accessibility and portability\n\nKeep the einstein summation convention source selectable and editable. For an isolated character in einstein summation convention, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of einstein summation convention is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify each free index appears once on both sides.\n- Check that dummy indices may be renamed consistently.\n- Test the expression in a simple coordinate system.\n- Confirm every symbol used in einstein summation convention has one defined meaning in the local context.\n- Reopen the exported file for **Einstein Summation Convention** and compare it with the editable source.\n"
  },
  {
    "slug": "electricity-circuits-common-errors",
    "title": "Electricity and Circuits: Common Errors and Verification",
    "description": "Common Errors and Verification for electricity and circuits: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Electricity and Circuits",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Electricity and Circuits: Common Errors and Verification explains voltage, current, resistance, power, sign conventions, and SI units.\n\n## Core notation for Electricity and Circuits: Common Errors and Verification\n\nIn electricity and circuits, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for electricity and circuits: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Ohm law | \u0060V=IR\u0060 | voltage-current-resistance relation |\n| Wave relation | \u0060v=f\\lambda\u0060 | wave speed equals frequency times wavelength |\n| First law | \u0060\\Delta U=Q-W\u0060 | internal-energy change under the stated work sign convention |\n| Newton law | \u0060\\sum F=ma\u0060 | net force equals mass times acceleration |\n\n## Errors that change the meaning\n\n- **Problem:** Adding quantities with incompatible units. **Correction:** write the missing electricity and circuits: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Dropping vector direction when only magnitudes were given. **Correction:** write the missing electricity and circuits: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Mixing peak, rms, angular-frequency, and ordinary-frequency values. **Correction:** write the missing electricity and circuits: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the electricity and circuits: common errors and verification expression. Then check the electricity and circuits: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced electricity and circuits: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n\n## Accessibility and portability\n\nKeep the electricity and circuits: common errors and verification source selectable and editable. For an isolated character in electricity and circuits: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of electricity and circuits: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in electricity and circuits: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Electricity and Circuits: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "electricity-circuits-latex-formatting",
    "title": "Electricity and Circuits: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for electricity and circuits: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Electricity and Circuits",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Electricity and Circuits: LaTeX Formatting Guide explains voltage, current, resistance, power, sign conventions, and SI units.\n\n## Core notation for Electricity and Circuits\n\nIn electricity and circuits, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for electricity and circuits; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Momentum | \u0060p=mv\u0060 | linear momentum in a nonrelativistic model |\n| Ohm law | \u0060V=IR\u0060 | voltage-current-resistance relation |\n| Wave relation | \u0060v=f\\lambda\u0060 | wave speed equals frequency times wavelength |\n| First law | \u0060\\Delta U=Q-W\u0060 | internal-energy change under the stated work sign convention |\n\n## LaTeX patterns that preserve the structure\n\nFor electricity and circuits: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\np=mv\nV=IR\nv=f\\lambda\n\u0060\u0060\u0060\n\nFor electricity and circuits, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In electricity and circuits, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the coordinate axes and positive directions.\n- Attach si or other units to every measured quantity.\n- Declare the work, heat, voltage, and current sign conventions.\n\n## Renderer and export checks\n\nRender one demanding electricity and circuits example in the actual destination. For electricity and circuits, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the electricity and circuits source selectable and editable. For an isolated character in electricity and circuits, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of electricity and circuits is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in electricity and circuits has one defined meaning in the local context.\n- Reopen the exported file for **Electricity and Circuits: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "electricity-circuits-notation-reference",
    "title": "Electricity and Circuits: Notation Reference",
    "description": "Notation Reference for electricity and circuits: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Electricity and Circuits",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Electricity and Circuits: Notation Reference explains voltage, current, resistance, power, sign conventions, and SI units.\n\n## Core notation for Electricity and Circuits\n\nIn electricity and circuits, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for electricity and circuits; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Energy | \u0060E=T\u002BV\u0060 | total mechanical energy as kinetic plus potential energy |\n| Momentum | \u0060p=mv\u0060 | linear momentum in a nonrelativistic model |\n| Ohm law | \u0060V=IR\u0060 | voltage-current-resistance relation |\n| Wave relation | \u0060v=f\\lambda\u0060 | wave speed equals frequency times wavelength |\n\n## How to read a complete expression\n\nRead \u0060E=T\u002BV\u0060 as \u201Ctotal mechanical energy as kinetic plus potential energy.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in electricity and circuits from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the coordinate axes and positive directions.\n- Attach si or other units to every measured quantity.\n- Declare the work, heat, voltage, and current sign conventions.\n\n## Cross-checks before reuse\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n\n## Accessibility and portability\n\nKeep the electricity and circuits source selectable and editable. For an isolated character in electricity and circuits, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of electricity and circuits is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in electricity and circuits has one defined meaning in the local context.\n- Reopen the exported file for **Electricity and Circuits: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "entropy-cross-entropy-kl",
    "title": "Entropy, Cross-Entropy, and KL Divergence",
    "description": "Compare related information measures, logarithm bases, and direction conventions.",
    "topic": "Information Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Compare related information measures, logarithm bases, and direction conventions.\n\n## Core notation for Entropy, Cross-Entropy, and KL Divergence\n\nIn information theory, the notation usually represents random variables, alphabets, distributions, code lengths, channels, and logarithm bases. The table below gives a compact starting set for entropy, cross-entropy, and kl divergence; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Channel capacity | \u0060C=\\max_{p(x)}I(X;Y)\u0060 | maximum mutual information over input distributions |\n| Chain rule | \u0060H(X,Y)=H(X)\u002BH(Y\\mid X)\u0060 | joint entropy decomposition |\n| Entropy | \u0060H(X)=-\\sum_x p(x)\\log p(x)\u0060 | average uncertainty of X |\n| Conditional entropy | \u0060H(X\\mid Y)\u0060 | uncertainty remaining after observing Y |\n\n## Practical workflow\n\nStart from \u0060C=\\max_{p(x)}I(X;Y)\u0060 and write one sentence that says it means \u201Cmaximum mutual information over input distributions.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the logarithm base and resulting unit.\n- Distinguish entropy, cross-entropy, and kl divergence.\n- Specify discrete sums versus continuous integrals.\n\n## Failure checks\n\n- Assuming kl divergence is symmetric.\n- Mixing bits and nats in one calculation.\n- Using 0 log 0 without the standard limiting convention.\n\n## Accessibility and portability\n\nKeep the entropy, cross-entropy, and kl divergence source selectable and editable. For an isolated character in entropy, cross-entropy, and kl divergence, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of entropy, cross-entropy, and kl divergence is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities normalize.\n- Test deterministic and uniform distributions.\n- Confirm the order of p and q in every divergence.\n- Confirm every symbol used in entropy, cross-entropy, and kl divergence has one defined meaning in the local context.\n- Reopen the exported file for **Entropy, Cross-Entropy, and KL Divergence** and compare it with the editable source.\n"
  },
  {
    "slug": "equation-accessibility-checklist",
    "title": "Equation Accessibility Checklist",
    "description": "Preserve semantic source, reading order, labels, alternatives, zoom, and keyboard access.",
    "topic": "Accessibility",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Preserve semantic source, reading order, labels, alternatives, zoom, and keyboard access.\n\n## Core notation for Equation Accessibility Checklist\n\nIn accessibility, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for equation accessibility checklist; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n\n## Practical workflow\n\nStart from \u0060\\frac{a}{b}\u0060 and write one sentence that says it means \u201Cstructured two-dimensional fraction.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for equation accessibility checklist rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the equation accessibility checklist notation.\n\n## Failure checks\n\n- Copying a rendered equation accessibility checklist image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in equation accessibility checklist.\n- Defining equation accessibility checklist macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the equation accessibility checklist source selectable and editable. For an isolated character in equation accessibility checklist, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of equation accessibility checklist is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the equation accessibility checklist example.\n- Confirm every symbol used in equation accessibility checklist has one defined meaning in the local context.\n- Reopen the exported file for **Equation Accessibility Checklist** and compare it with the editable source.\n"
  },
  {
    "slug": "latex-packages-for-math",
    "title": "Essential LaTeX Packages for Mathematics",
    "description": "Understand when core LaTeX is enough and when amsmath, amssymb, mathtools, physics, or specialized packages are appropriate.",
    "topic": "LaTeX",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Understand when core LaTeX is enough and when amsmath, amssymb, mathtools, physics, or specialized packages are appropriate.\n\n## Core notation for Essential LaTeX Packages for Mathematics\n\nIn latex, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for essential latex packages for mathematics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n\n## Practical workflow\n\nStart from \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 and write one sentence that says it means \u201Cmulti-line alignment at relation signs.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for essential latex packages for mathematics rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the essential latex packages for mathematics notation.\n\n## Failure checks\n\n- Copying a rendered essential latex packages for mathematics image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in essential latex packages for mathematics.\n- Defining essential latex packages for mathematics macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the essential latex packages for mathematics source selectable and editable. For an isolated character in essential latex packages for mathematics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of essential latex packages for mathematics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the essential latex packages for mathematics example.\n- Confirm every symbol used in essential latex packages for mathematics has one defined meaning in the local context.\n- Reopen the exported file for **Essential LaTeX Packages for Mathematics** and compare it with the editable source.\n"
  },
  {
    "slug": "probability-expectation-notation",
    "title": "Expectation, Variance, and Conditional Notation",
    "description": "Read random variables, distributions, events, conditioning bars, expectations, moments, and covariance precisely.",
    "topic": "Probability",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Read random variables, distributions, events, conditioning bars, expectations, moments, and covariance precisely.\n\n## Core notation for Expectation, Variance, and Conditional Notation\n\nIn probability, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for expectation, variance, and conditional notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Bayes rule | \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 | posterior proportional to likelihood times prior |\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n\n## Practical workflow\n\nStart from \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 and write one sentence that says it means \u201Cposterior proportional to likelihood times prior.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Failure checks\n\n- Dropping the condition after applying a conditional identity.\n- Confusing a probability mass with a probability density.\n- Using the same distribution name with incompatible parameter orders.\n\n## Accessibility and portability\n\nKeep the expectation, variance, and conditional notation source selectable and editable. For an isolated character in expectation, variance, and conditional notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of expectation, variance, and conditional notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in expectation, variance, and conditional notation has one defined meaning in the local context.\n- Reopen the exported file for **Expectation, Variance, and Conditional Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "exponential-logarithmic-common-errors",
    "title": "Exponential and Logarithmic Notation: Common Errors and Verification",
    "description": "Common Errors and Verification for exponential and logarithmic notation: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portabl",
    "topic": "Exponential and Logarithmic Notation",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Exponential and Logarithmic Notation: Common Errors and Verification explains bases, domains, inverse relationships, units, and growth models.\n\n## Core notation for Exponential and Logarithmic Notation: Common Errors and Verification\n\nIn exponential and logarithmic notation, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for exponential and logarithmic notation: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n\n## Errors that change the meaning\n\n- **Problem:** Copying a rendered image when editable notation is required. **Correction:** write the missing exponential and logarithmic notation: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using a look-alike unicode character with different semantics. **Correction:** write the missing exponential and logarithmic notation: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Defining macros that hide arguments or conflict with package commands. **Correction:** write the missing exponential and logarithmic notation: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the exponential and logarithmic notation: common errors and verification expression. Then check the exponential and logarithmic notation: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced exponential and logarithmic notation: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the exponential and logarithmic notation: common errors and verification example.\n\n## Accessibility and portability\n\nKeep the exponential and logarithmic notation: common errors and verification source selectable and editable. For an isolated character in exponential and logarithmic notation: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of exponential and logarithmic notation: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the exponential and logarithmic notation: common errors and verification example.\n- Confirm every symbol used in exponential and logarithmic notation: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Exponential and Logarithmic Notation: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "exponential-logarithmic-latex-formatting",
    "title": "Exponential and Logarithmic Notation: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for exponential and logarithmic notation: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notati",
    "topic": "Exponential and Logarithmic Notation",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Exponential and Logarithmic Notation: LaTeX Formatting Guide explains bases, domains, inverse relationships, units, and growth models.\n\n## Core notation for Exponential and Logarithmic Notation\n\nIn exponential and logarithmic notation, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for exponential and logarithmic notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n\n## LaTeX patterns that preserve the structure\n\nFor exponential and logarithmic notation: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\n\\text{\u201Cx squared plus one\u201D}\n\\newcommand{\\vect}[1]{\\mathbf{#1}}\n\u0060\u0060\u0060\n\nFor exponential and logarithmic notation, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In exponential and logarithmic notation, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Keep editable source with the rendered result.\n- Use semantic commands for exponential and logarithmic notation rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the exponential and logarithmic notation notation.\n\n## Renderer and export checks\n\nRender one demanding exponential and logarithmic notation example in the actual destination. For exponential and logarithmic notation, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the exponential and logarithmic notation source selectable and editable. For an isolated character in exponential and logarithmic notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of exponential and logarithmic notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the exponential and logarithmic notation example.\n- Confirm every symbol used in exponential and logarithmic notation has one defined meaning in the local context.\n- Reopen the exported file for **Exponential and Logarithmic Notation: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "exponential-logarithmic-notation-reference",
    "title": "Exponential and Logarithmic Notation: Notation Reference",
    "description": "Notation Reference for exponential and logarithmic notation: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Exponential and Logarithmic Notation",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Exponential and Logarithmic Notation: Notation Reference explains bases, domains, inverse relationships, units, and growth models.\n\n## Core notation for Exponential and Logarithmic Notation\n\nIn exponential and logarithmic notation, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for exponential and logarithmic notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## How to read a complete expression\n\nRead \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 as \u201Csemantic operator element.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in exponential and logarithmic notation from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- Keep editable source with the rendered result.\n- Use semantic commands for exponential and logarithmic notation rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the exponential and logarithmic notation notation.\n\n## Cross-checks before reuse\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the exponential and logarithmic notation example.\n\n## Accessibility and portability\n\nKeep the exponential and logarithmic notation source selectable and editable. For an isolated character in exponential and logarithmic notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of exponential and logarithmic notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the exponential and logarithmic notation example.\n- Confirm every symbol used in exponential and logarithmic notation has one defined meaning in the local context.\n- Reopen the exported file for **Exponential and Logarithmic Notation: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "financial-mathematics-common-errors",
    "title": "Financial Mathematics: Common Errors and Verification",
    "description": "Common Errors and Verification for financial mathematics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Financial Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Financial Mathematics: Common Errors and Verification explains rates, periods, cash-flow timing, compounding, discounting, and units.\n\n## Core notation for Financial Mathematics: Common Errors and Verification\n\nIn financial mathematics, the notation usually represents cash flows, dates, rates, compounding periods, discount factors, and sign conventions. The table below gives a compact starting set for financial mathematics: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Annuity | \u0060PV=C\\frac{1-(1\u002Br)^{-n}}{r}\u0060 | present value of level end-of-period payments |\n| Return | \u0060R=\\frac{V_1-V_0\u002BC}{V_0}\u0060 | holding-period return with cash flow C |\n| Present value | \u0060PV=\\frac{FV}{(1\u002Br)^n}\u0060 | discounted value under periodic compounding |\n| Net present value | \u0060NPV=\\sum_{t=0}^{n}\\frac{C_t}{(1\u002Br)^t}\u0060 | discounted sum of dated cash flows |\n\n## Errors that change the meaning\n\n- **Problem:** Using an annual rate with monthly periods without conversion. **Correction:** write the missing financial mathematics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Mixing beginning-of-period and end-of-period cash flows. **Correction:** write the missing financial mathematics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Comparing returns computed with different day-count conventions. **Correction:** write the missing financial mathematics: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the financial mathematics: common errors and verification expression. Then check the financial mathematics: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced financial mathematics: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Draw a dated cash-flow timeline.\n- Convert all rates to a common period.\n- Verify the zero-rate limit.\n\n## Accessibility and portability\n\nKeep the financial mathematics: common errors and verification source selectable and editable. For an isolated character in financial mathematics: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of financial mathematics: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Draw a dated cash-flow timeline.\n- Convert all rates to a common period.\n- Verify the zero-rate limit.\n- Confirm every symbol used in financial mathematics: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Financial Mathematics: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "financial-mathematics-latex-formatting",
    "title": "Financial Mathematics: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for financial mathematics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Financial Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Financial Mathematics: LaTeX Formatting Guide explains rates, periods, cash-flow timing, compounding, discounting, and units.\n\n## Core notation for Financial Mathematics\n\nIn financial mathematics, the notation usually represents cash flows, dates, rates, compounding periods, discount factors, and sign conventions. The table below gives a compact starting set for financial mathematics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Annuity | \u0060PV=C\\frac{1-(1\u002Br)^{-n}}{r}\u0060 | present value of level end-of-period payments |\n| Return | \u0060R=\\frac{V_1-V_0\u002BC}{V_0}\u0060 | holding-period return with cash flow C |\n| Present value | \u0060PV=\\frac{FV}{(1\u002Br)^n}\u0060 | discounted value under periodic compounding |\n| Net present value | \u0060NPV=\\sum_{t=0}^{n}\\frac{C_t}{(1\u002Br)^t}\u0060 | discounted sum of dated cash flows |\n\n## LaTeX patterns that preserve the structure\n\nFor financial mathematics: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nPV=C\\frac{1-(1\u002Br)^{-n}}{r}\nR=\\frac{V_1-V_0\u002BC}{V_0}\nPV=\\frac{FV}{(1\u002Br)^n}\n\u0060\u0060\u0060\n\nFor financial mathematics, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In financial mathematics, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State nominal versus effective rates.\n- Align each rate with its compounding period.\n- Declare whether inflows or outflows are positive.\n\n## Renderer and export checks\n\nRender one demanding financial mathematics example in the actual destination. For financial mathematics, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the financial mathematics source selectable and editable. For an isolated character in financial mathematics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of financial mathematics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Draw a dated cash-flow timeline.\n- Convert all rates to a common period.\n- Verify the zero-rate limit.\n- Confirm every symbol used in financial mathematics has one defined meaning in the local context.\n- Reopen the exported file for **Financial Mathematics: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "financial-mathematics-notation-reference",
    "title": "Financial Mathematics: Notation Reference",
    "description": "Notation Reference for financial mathematics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Financial Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Financial Mathematics: Notation Reference explains rates, periods, cash-flow timing, compounding, discounting, and units.\n\n## Core notation for Financial Mathematics\n\nIn financial mathematics, the notation usually represents cash flows, dates, rates, compounding periods, discount factors, and sign conventions. The table below gives a compact starting set for financial mathematics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Return | \u0060R=\\frac{V_1-V_0\u002BC}{V_0}\u0060 | holding-period return with cash flow C |\n| Present value | \u0060PV=\\frac{FV}{(1\u002Br)^n}\u0060 | discounted value under periodic compounding |\n| Net present value | \u0060NPV=\\sum_{t=0}^{n}\\frac{C_t}{(1\u002Br)^t}\u0060 | discounted sum of dated cash flows |\n| Effective rate | \u00601\u002Br_{\\mathrm{eff}}=(1\u002Br_m/m)^m\u0060 | effective annual rate from a nominal rate |\n\n## How to read a complete expression\n\nRead \u0060R=\\frac{V_1-V_0\u002BC}{V_0}\u0060 as \u201Cholding-period return with cash flow C.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in financial mathematics from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State nominal versus effective rates.\n- Align each rate with its compounding period.\n- Declare whether inflows or outflows are positive.\n\n## Cross-checks before reuse\n\n- Draw a dated cash-flow timeline.\n- Convert all rates to a common period.\n- Verify the zero-rate limit.\n\n## Accessibility and portability\n\nKeep the financial mathematics source selectable and editable. For an isolated character in financial mathematics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of financial mathematics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Draw a dated cash-flow timeline.\n- Convert all rates to a common period.\n- Verify the zero-rate limit.\n- Confirm every symbol used in financial mathematics has one defined meaning in the local context.\n- Reopen the exported file for **Financial Mathematics: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "finite-difference-notation",
    "title": "Finite-Difference Notation",
    "description": "Read forward, backward, and central differences, grid spacing, stencil coefficients, and boundary handling.",
    "topic": "Numerical Methods",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Read forward, backward, and central differences, grid spacing, stencil coefficients, and boundary handling.\n\n## Core notation for Finite-Difference Notation\n\nIn numerical methods, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for finite-difference notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n\n## Practical workflow\n\nStart from \u0060\\text{\u201Cx squared plus one\u201D}\u0060 and write one sentence that says it means \u201Cplain-language reading when a text alternative is needed.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for finite-difference notation rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the finite-difference notation notation.\n\n## Failure checks\n\n- Copying a rendered finite-difference notation image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in finite-difference notation.\n- Defining finite-difference notation macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the finite-difference notation source selectable and editable. For an isolated character in finite-difference notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of finite-difference notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the finite-difference notation example.\n- Confirm every symbol used in finite-difference notation has one defined meaning in the local context.\n- Reopen the exported file for **Finite-Difference Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "unicode-font-fallback-math",
    "title": "Font Fallback for Mathematical Unicode",
    "description": "Test whether selected fonts cover operators, arrows, alphabets, combining marks, and specialized scientific symbols.",
    "topic": "Unicode",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Test whether selected fonts cover operators, arrows, alphabets, combining marks, and specialized scientific symbols.\n\n## Core notation for Font Fallback for Mathematical Unicode\n\nIn unicode, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for font fallback for mathematical unicode; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n\n## Practical workflow\n\nStart from \u0060\\texttt{U\u002B2212}\u0060 and write one sentence that says it means \u201Cidentifier for the mathematical minus sign.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for font fallback for mathematical unicode rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the font fallback for mathematical unicode notation.\n\n## Failure checks\n\n- Copying a rendered font fallback for mathematical unicode image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in font fallback for mathematical unicode.\n- Defining font fallback for mathematical unicode macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the font fallback for mathematical unicode source selectable and editable. For an isolated character in font fallback for mathematical unicode, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of font fallback for mathematical unicode is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the font fallback for mathematical unicode example.\n- Confirm every symbol used in font fallback for mathematical unicode has one defined meaning in the local context.\n- Reopen the exported file for **Font Fallback for Mathematical Unicode** and compare it with the editable source.\n"
  },
  {
    "slug": "formula-documentation-checklist",
    "title": "Formula Documentation Checklist",
    "description": "Document variables, domains, units, assumptions, edge cases, and examples.",
    "topic": "Scientific Writing",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Document variables, domains, units, assumptions, edge cases, and examples.\n\n## Core notation for Formula Documentation Checklist\n\nIn scientific writing, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for formula documentation checklist; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n\n## Practical workflow\n\nStart from \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 and write one sentence that says it means \u201Cmulti-line alignment at relation signs.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for formula documentation checklist rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the formula documentation checklist notation.\n\n## Failure checks\n\n- Copying a rendered formula documentation checklist image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in formula documentation checklist.\n- Defining formula documentation checklist macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the formula documentation checklist source selectable and editable. For an isolated character in formula documentation checklist, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of formula documentation checklist is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the formula documentation checklist example.\n- Confirm every symbol used in formula documentation checklist has one defined meaning in the local context.\n- Reopen the exported file for **Formula Documentation Checklist** and compare it with the editable source.\n"
  },
  {
    "slug": "fourier-transform-conventions",
    "title": "Fourier Transform Conventions",
    "description": "Compare angular-frequency, ordinary-frequency, normalization, and sign conventions.",
    "topic": "Analysis",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "## Quick answer\n\nFourier transform formulas differ mainly in the sign of the exponential, whether frequency is measured as ordinary frequency \u0060f\u0060 or angular frequency \u0060\\omega\u0060, and where normalization factors are placed. A transform pair is valid only when the forward and inverse conventions are used together.\n\n## Angular-frequency convention\n\nOne common pair is\n\n\u0060\u0060\u0060latex\nF(\\omega)=\\int_{-\\infty}^{\\infty} f(t)e^{-i\\omega t}\\,dt\n\u0060\u0060\u0060\n\n\u0060\u0060\u0060latex\nf(t)=\\frac{1}{2\\pi}\\int_{-\\infty}^{\\infty}F(\\omega)e^{i\\omega t}\\,d\\omega\n\u0060\u0060\u0060\n\n## Ordinary-frequency convention\n\nWith frequency \u0060\\nu\u0060 measured in cycles per unit time, the exponential often contains \u00602\\pi\u0060:\n\n\u0060\u0060\u0060latex\nF(\\nu)=\\int_{-\\infty}^{\\infty} f(t)e^{-2\\pi i\\nu t}\\,dt\n\u0060\u0060\u0060\n\nThe inverse then uses \u0060e^{2\\pi i\\nu t}\u0060 without an additional \u00602\\pi\u0060 normalization factor.\n\n## Symmetric normalization\n\nSome mathematics and physics references split normalization symmetrically, placing \u00601/\\sqrt{2\\pi}\u0060 in both directions. This can simplify identities but changes every transform table and theorem statement consistently.\n\n## Common mistakes\n\nDo not mix a forward transform from one convention with an inverse transform from another. State the sign, frequency variable, normalization, and dimensional units before applying a transform table.\n\n## Verification checklist\n\nTransform a simple Gaussian or delta distribution using the declared convention, apply the inverse, and confirm that the original function is recovered with the expected constants.\n"
  },
  {
    "slug": "mathml-fractions-roots",
    "title": "Fractions and Roots in MathML",
    "description": "Build structured fractions, square roots, and indexed roots without relying on visual slash characters.",
    "topic": "MathML",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Build structured fractions, square roots, and indexed roots without relying on visual slash characters.\n\n## Core notation for Fractions and Roots in MathML\n\nIn mathml, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for fractions and roots in mathml; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n\n## Practical workflow\n\nStart from \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 and write one sentence that says it means \u201Creusable semantic notation command.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for fractions and roots in mathml rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the fractions and roots in mathml notation.\n\n## Failure checks\n\n- Copying a rendered fractions and roots in mathml image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in fractions and roots in mathml.\n- Defining fractions and roots in mathml macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the fractions and roots in mathml source selectable and editable. For an isolated character in fractions and roots in mathml, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of fractions and roots in mathml is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the fractions and roots in mathml example.\n- Confirm every symbol used in fractions and roots in mathml has one defined meaning in the local context.\n- Reopen the exported file for **Fractions and Roots in MathML** and compare it with the editable source.\n"
  },
  {
    "slug": "generating-functions-guide",
    "title": "Generating Functions Guide",
    "description": "Translate sequences into ordinary or exponential generating functions.",
    "topic": "Discrete Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Translate sequences into ordinary or exponential generating functions.\n\n## Core notation for Generating Functions\n\nIn discrete mathematics, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for generating functions; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n\n## Practical workflow\n\nStart from \u0060a\\equiv b\\pmod m\u0060 and write one sentence that says it means \u201Ca and b have the same residue modulo m.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Failure checks\n\n- Switching index origins halfway through a recurrence.\n- Counting permutations when combinations are required.\n- Using equality where modular congruence is intended.\n\n## Accessibility and portability\n\nKeep the generating functions source selectable and editable. For an isolated character in generating functions, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of generating functions is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in generating functions has one defined meaning in the local context.\n- Reopen the exported file for **Generating Functions Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "gradient-descent-notation",
    "title": "Gradient Descent Notation and Step Sizes",
    "description": "Document iterates, gradients, learning rates, stopping criteria, and constrained updates in optimization algorithms.",
    "topic": "Optimization",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Document iterates, gradients, learning rates, stopping criteria, and constrained updates in optimization algorithms.\n\n## Core notation for Gradient Descent Notation and Step Sizes\n\nIn optimization, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for gradient descent notation and step sizes; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Dual bound | \u0060d^\\star\\le p^\\star\u0060 | weak duality for a minimization primal |\n| Optimization problem | \u0060\\min_x f(x)\\quad\\text{s.t.}\\quad g_i(x)\\le 0\u0060 | minimize an objective over a constrained feasible set |\n| Lagrangian | \u0060\\mathcal{L}(x,\\lambda)=f(x)\u002B\\sum_i\\lambda_i g_i(x)\u0060 | objective plus weighted constraints |\n| Stationarity | \u0060\\nabla_x\\mathcal{L}(x,\\lambda)=0\u0060 | first-order stationarity condition |\n\n## Practical workflow\n\nStart from \u0060d^\\star\\le p^\\star\u0060 and write one sentence that says it means \u201Cweak duality for a minimization primal.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State minimization versus maximization and all constraint directions.\n- Separate an optimizer from the attained objective value.\n- Declare convexity and constraint-qualification assumptions.\n\n## Failure checks\n\n- Reversing a constraint sign without changing the multiplier convention.\n- Writing min when the result required is argmin.\n- Claiming kkt conditions are sufficient without convexity.\n\n## Accessibility and portability\n\nKeep the gradient descent notation and step sizes source selectable and editable. For an isolated character in gradient descent notation and step sizes, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of gradient descent notation and step sizes is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in gradient descent notation and step sizes has one defined meaning in the local context.\n- Reopen the exported file for **Gradient Descent Notation and Step Sizes** and compare it with the editable source.\n"
  },
  {
    "slug": "vector-calculus-operators",
    "title": "Gradient, Divergence, Curl, and Laplacian",
    "description": "Distinguish scalar and vector outputs, coordinate systems, and operator domains.",
    "topic": "Vector Calculus",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Distinguish scalar and vector outputs, coordinate systems, and operator domains.\n\n## Core notation for Gradient, Divergence, Curl, and Laplacian\n\nIn vector calculus, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for gradient, divergence, curl, and laplacian; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n\n## Practical workflow\n\nStart from \u0060\\lim_{x\\to a}f(x)=L\u0060 and write one sentence that says it means \u201Cvalue approached near a.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Failure checks\n\n- Dropping an absolute value in a substitution jacobian.\n- Interchanging a limit, sum, derivative, or integral without conditions.\n- Omitting boundary terms after integration by parts.\n\n## Accessibility and portability\n\nKeep the gradient, divergence, curl, and laplacian source selectable and editable. For an isolated character in gradient, divergence, curl, and laplacian, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of gradient, divergence, curl, and laplacian is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in gradient, divergence, curl, and laplacian has one defined meaning in the local context.\n- Reopen the exported file for **Gradient, Divergence, Curl, and Laplacian** and compare it with the editable source.\n"
  },
  {
    "slug": "graph-theory-notation-guide",
    "title": "Graph Theory Notation Guide",
    "description": "Read vertex, edge, path, cycle, degree, neighborhood, adjacency, and induced-subgraph notation consistently.",
    "topic": "Graph Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Read vertex, edge, path, cycle, degree, neighborhood, adjacency, and induced-subgraph notation consistently.\n\n## Core notation for Graph Theory Notation\n\nIn graph theory, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for graph theory notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n\n## Practical workflow\n\nStart from \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 and write one sentence that says it means \u201Cpolynomial with coefficients a_k.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Failure checks\n\n- Switching index origins halfway through a recurrence.\n- Counting permutations when combinations are required.\n- Using equality where modular congruence is intended.\n\n## Accessibility and portability\n\nKeep the graph theory notation source selectable and editable. For an isolated character in graph theory notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of graph theory notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in graph theory notation has one defined meaning in the local context.\n- Reopen the exported file for **Graph Theory Notation Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "graph-theory-common-errors",
    "title": "Graph Theory: Common Errors and Verification",
    "description": "Common Errors and Verification for graph theory: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Graph Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Graph Theory: Common Errors and Verification explains vertices, edges, paths, degrees, adjacency, and directed conventions.\n\n## Core notation for Graph Theory: Common Errors and Verification\n\nIn graph theory, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for graph theory: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n\n## Errors that change the meaning\n\n- **Problem:** Switching index origins halfway through a recurrence. **Correction:** write the missing graph theory: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Counting permutations when combinations are required. **Correction:** write the missing graph theory: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using equality where modular congruence is intended. **Correction:** write the missing graph theory: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the graph theory: common errors and verification expression. Then check the graph theory: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced graph theory: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n\n## Accessibility and portability\n\nKeep the graph theory: common errors and verification source selectable and editable. For an isolated character in graph theory: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of graph theory: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in graph theory: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Graph Theory: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "graph-theory-latex-formatting",
    "title": "Graph Theory: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for graph theory: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Graph Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Graph Theory: LaTeX Formatting Guide explains vertices, edges, paths, degrees, adjacency, and directed conventions.\n\n## Core notation for Graph Theory\n\nIn graph theory, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for graph theory; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n\n## LaTeX patterns that preserve the structure\n\nFor graph theory: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\np(x)=\\sum_{k=0}^{n}a_kx^k\n\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\n(a_n)_{n\\ge0}\n\u0060\u0060\u0060\n\nFor graph theory, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In graph theory, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Renderer and export checks\n\nRender one demanding graph theory example in the actual destination. For graph theory, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the graph theory source selectable and editable. For an isolated character in graph theory, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of graph theory is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in graph theory has one defined meaning in the local context.\n- Reopen the exported file for **Graph Theory: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "graph-theory-notation-reference",
    "title": "Graph Theory: Notation Reference",
    "description": "Notation Reference for graph theory: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Graph Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Graph Theory: Notation Reference explains vertices, edges, paths, degrees, adjacency, and directed conventions.\n\n## Core notation for Graph Theory\n\nIn graph theory, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for graph theory; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n\n## How to read a complete expression\n\nRead \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 as \u201Cpolynomial with coefficients a_k.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in graph theory from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Cross-checks before reuse\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n\n## Accessibility and portability\n\nKeep the graph theory source selectable and editable. For an isolated character in graph theory, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of graph theory is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in graph theory has one defined meaning in the local context.\n- Reopen the exported file for **Graph Theory: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "greek-alphabet-symbols-names",
    "title": "Greek Alphabet Symbols and Names",
    "description": "Review uppercase and lowercase Greek letters, names, common uses, and LaTeX commands.",
    "topic": "Reference",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "# Greek Alphabet Symbols and Names\n\nReview uppercase and lowercase Greek letters, names, common uses, and LaTeX commands. This guide focuses on reliable methods that preserve the intended character or mathematical structure when the text is copied, published, or shared.\n\n## Quick answer\n\nThe fastest option is to copy this character: **\u03C0**. For a real mathematical equation, use the LaTeX form \u0060\\pi\u0060 when your editor supports math rendering. Plain Unicode is ideal for short text, while LaTeX or an equation editor is better for structured notation.\n\n## Choose the right format\n\nUse **Unicode** when the symbol must remain a normal text character in an email, title, spreadsheet, or social post. Use **LaTeX** when the expression contains fractions, roots, limits, stacked scripts, or other two-dimensional notation. Use **HTML entities or numeric references** when the symbol is part of a web page and escaping or source-code clarity matters. Use **MathML** when semantic browser-accessible mathematics is required.\n\n| Format | Value | Best for |\n|---|---|---|\n| Character | \u0060\u03C0\u0060 | Plain text and quick copy |\n| Unicode | \u0060U\u002B03C0\u0060 | Character lookup and encoding |\n| LaTeX | \u0060\\pi\u0060 | Equations and technical writing |\n| HTML | \u0060\u0026pi;\u0060 | Web pages |\n| MathML | \u0060\u0026lt;mo\u0026gt;\u03C0\u0026lt;/mo\u0026gt;\u0060 | Semantic web mathematics |\n\n## Windows\n\nOpen **Character Map**, search for the symbol name, select the character, and copy it. In Microsoft Word and some Office applications, you can also type the hexadecimal Unicode value and press **Alt\u002BX**. Application support varies, so verify the result before relying on a shortcut in a different editor.\n\n## Mac\n\nPress **Control\u2013Command\u2013Space** to open Character Viewer. Search for the English symbol name, then double-click the result. Frequently used characters can be added to Favorites. In equation-capable applications, prefer the app\u2019s math editor when the character is part of a larger formula.\n\n## Microsoft Word\n\nPress **Alt\u002B=** to open an equation, type \u0060\\pi\u0060, and press Space when Word recognizes the command. For plain text, use **Insert \u2192 Symbol \u2192 More Symbols**, or paste the Unicode character. The equation route is preferable when scripts, fractions, limits, or alignment are involved.\n\n## Google Docs\n\nChoose **Insert \u2192 Special characters**, search by name, or draw an approximate shape. For equations, choose **Insert \u2192 Equation** and use the available notation controls. Google Docs supports a useful subset of equation shortcuts, but it does not behave exactly like a full LaTeX system.\n\n## HTML and web pages\n\nA literal UTF-8 character is usually the clearest choice when the document declares UTF-8. Named entities can improve readability for common characters, while numeric references are a dependable fallback. Keep the symbol in meaningful text rather than using a background image, because text is selectable, searchable, and more accessible.\n\n\u0060\u0060\u0060html\n\u003Cspan aria-label=\u0022Pi\u0022\u003E\u03C0\u003C/span\u003E\n\u003Cspan\u003E\u0026pi;\u003C/span\u003E\n\u0060\u0060\u0060\n\n## LaTeX example\n\n\u0060\u0060\u0060latex\n\\pi\n\u0060\u0060\u0060\n\nWhen the symbol is an operator or relation, place it in math mode and allow LaTeX to apply the correct spacing. Avoid forcing a mathematical expression into a sequence of unrelated Unicode characters when semantic structure matters.\n\n## Common mistakes\n\nDo not substitute a visually similar letter, punctuation mark, or image. Similar-looking characters may have different Unicode values and meanings. Also avoid copying from a decorative font that changes the glyph without changing the underlying character. Finally, check whether the surrounding context requires a specific convention; several mathematical symbols have meanings that vary by field or textbook.\n\n## Related resources\n\nUse the symbol page for definitions, examples, copy controls, and platform-specific input methods. Browse the relevant category for nearby notation, or open the LaTeX editor to test a complete formula before publishing it.\n"
  },
  {
    "slug": "greek-letters-in-physics",
    "title": "Greek Letters Commonly Used in Physics",
    "description": "Learn the most common Greek letters in physics, their typical meanings, pronunciation, LaTeX commands, and context-dependent exceptions.",
    "topic": "Physics notation",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Learn the most common Greek letters in physics, their typical meanings, pronunciation, LaTeX commands, and context-dependent exceptions. This guide focuses on reliable, editable output rather than visual shortcuts. The exact menu names can vary by application version, but the underlying choice remains the same: use Unicode for isolated characters and structured math for complete expressions.\n\n## Choose the right representation\n\nMathematical notation can be stored as ordinary Unicode text, structured equation markup, or an image. Unicode is convenient for isolated symbols and short labels. LaTeX and MathML preserve structure for fractions, matrices, scripts, and aligned equations. Images should be a last resort because they are harder to edit, search, resize, and make accessible.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Create the notation\n\nStart in the native equation editor when the destination application provides one. Native editors understand mathematical grouping, spacing, and baseline alignment better than manual character placement. When importing text, separate semantic content from presentation: identify operators, variables, units, subscripts, and conditions before deciding how they should look.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Check meaning and ambiguity\n\nThe same visible character can carry several meanings across algebra, statistics, physics, and chemistry. Define uncommon notation and review nearby variables before converting formats. Plain Unicode cannot always distinguish multiplication from a dot product, a hyphen from a minus sign, or a decorative letter from a mathematical constant.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Preserve accessibility\n\nUse real text or structured math whenever possible. Provide a concise spoken description for an image and include the surrounding purpose of the equation rather than reading every punctuation mark mechanically. Keyboard focus, selectable text, sufficient contrast, and responsive layout are also part of accessible mathematical communication.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Test the final output\n\nCopy the result into the actual destination, save and reopen the file, then inspect desktop, mobile, print, and exported PDF views. Confirm that fonts contain every symbol, line breaks do not split expressions incorrectly, and superscripts remain attached to the intended base. For web pages, test without JavaScript and with browser zoom.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Use a repeatable workflow\n\nKeep the source notation in a plain, version-controlled format when possible. Record the LaTeX command, Unicode code point, and intended meaning for symbols that appear frequently. A repeatable workflow reduces silent substitutions and makes later updates easier when the content moves between Word, HTML, Markdown, presentation software, and publishing systems.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Final checklist\n\n1. Confirm the mathematical meaning in context.\n2. Prefer native equation markup for structured expressions.\n3. Verify Unicode and LaTeX independently.\n4. Test copying, exporting, zooming, and screen-reader output.\n5. Keep an editable source version for future correction.\n"
  },
  {
    "slug": "greens-stokes-divergence-theorems",
    "title": "Green, Stokes, and Divergence Theorems",
    "description": "Compare dimensions, domains, boundaries, orientations, and integrands across the three theorems.",
    "topic": "Vector Calculus",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Compare dimensions, domains, boundaries, orientations, and integrands across the three theorems.\n\n## Core notation for Green, Stokes, and Divergence Theorems\n\nIn vector calculus, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for green, stokes, and divergence theorems; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n\n## Practical workflow\n\nStart from \u0060\\nabla\\cdot F\u0060 and write one sentence that says it means \u201Clocal source strength of a vector field.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Failure checks\n\n- Dropping an absolute value in a substitution jacobian.\n- Interchanging a limit, sum, derivative, or integral without conditions.\n- Omitting boundary terms after integration by parts.\n\n## Accessibility and portability\n\nKeep the green, stokes, and divergence theorems source selectable and editable. For an isolated character in green, stokes, and divergence theorems, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of green, stokes, and divergence theorems is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in green, stokes, and divergence theorems has one defined meaning in the local context.\n- Reopen the exported file for **Green, Stokes, and Divergence Theorems** and compare it with the editable source.\n"
  },
  {
    "slug": "hypothesis-testing-symbols",
    "title": "Hypothesis Testing Symbols",
    "description": "Distinguish hypotheses, statistics, p-values, significance levels, power, and errors.",
    "topic": "Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Distinguish hypotheses, statistics, p-values, significance levels, power, and errors.\n\n## Core notation for Hypothesis Testing Symbols\n\nIn statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for hypothesis testing symbols; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n| Correlation | \u0060r=\\frac{\\operatorname{cov}(X,Y)}{s_Xs_Y}\u0060 | standardized linear association |\n| Observation | \u0060x_i\u0060 | the i-th measured or observed value |\n\n## Practical workflow\n\nStart from \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 and write one sentence that says it means \u201Cestimated sampling variability of an estimator.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Failure checks\n\n- Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate.\n- Reporting a standard deviation as though it were a standard error.\n- Rounding intermediate values so aggressively that the final result changes.\n\n## Accessibility and portability\n\nKeep the hypothesis testing symbols source selectable and editable. For an isolated character in hypothesis testing symbols, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of hypothesis testing symbols is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in hypothesis testing symbols has one defined meaning in the local context.\n- Reopen the exported file for **Hypothesis Testing Symbols** and compare it with the editable source.\n"
  },
  {
    "slug": "inclusion-exclusion-guide",
    "title": "Inclusion\u2013Exclusion Principle",
    "description": "Apply inclusion\u2013exclusion to two, three, and many finite sets.",
    "topic": "Discrete Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Apply inclusion\u2013exclusion to two, three, and many finite sets.\n\n## Core notation for Inclusion\u2013Exclusion Principle\n\nIn discrete mathematics, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for inclusion\u2013exclusion principle; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n\n## Practical workflow\n\nStart from \u0060a\\equiv b\\pmod m\u0060 and write one sentence that says it means \u201Ca and b have the same residue modulo m.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Failure checks\n\n- Switching index origins halfway through a recurrence.\n- Counting permutations when combinations are required.\n- Using equality where modular congruence is intended.\n\n## Accessibility and portability\n\nKeep the inclusion\u2013exclusion principle source selectable and editable. For an isolated character in inclusion\u2013exclusion principle, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of inclusion\u2013exclusion principle is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in inclusion\u2013exclusion principle has one defined meaning in the local context.\n- Reopen the exported file for **Inclusion\u2013Exclusion Principle** and compare it with the editable source.\n"
  },
  {
    "slug": "information-theory-common-errors",
    "title": "Information Theory: Common Errors and Verification",
    "description": "Common Errors and Verification for information theory: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Information Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Information Theory: Common Errors and Verification explains entropy, conditional entropy, mutual information, divergence, and logarithm bases.\n\n## Core notation for Information Theory: Common Errors and Verification\n\nIn information theory, the notation usually represents random variables, alphabets, distributions, code lengths, channels, and logarithm bases. The table below gives a compact starting set for information theory: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Mutual information | \u0060I(X;Y)=H(X)-H(X\\mid Y)\u0060 | shared information between X and Y |\n| KL divergence | \u0060D_{\\mathrm{KL}}(P\\Vert Q)=\\sum_x p(x)\\log\\frac{p(x)}{q(x)}\u0060 | directed divergence from Q to P |\n| Channel capacity | \u0060C=\\max_{p(x)}I(X;Y)\u0060 | maximum mutual information over input distributions |\n| Chain rule | \u0060H(X,Y)=H(X)\u002BH(Y\\mid X)\u0060 | joint entropy decomposition |\n\n## Errors that change the meaning\n\n- **Problem:** Assuming kl divergence is symmetric. **Correction:** write the missing information theory: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Mixing bits and nats in one calculation. **Correction:** write the missing information theory: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using 0 log 0 without the standard limiting convention. **Correction:** write the missing information theory: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the information theory: common errors and verification expression. Then check the information theory: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced information theory: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Verify probabilities normalize.\n- Test deterministic and uniform distributions.\n- Confirm the order of p and q in every divergence.\n\n## Accessibility and portability\n\nKeep the information theory: common errors and verification source selectable and editable. For an isolated character in information theory: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of information theory: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities normalize.\n- Test deterministic and uniform distributions.\n- Confirm the order of p and q in every divergence.\n- Confirm every symbol used in information theory: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Information Theory: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "information-theory-latex-formatting",
    "title": "Information Theory: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for information theory: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Information Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Information Theory: LaTeX Formatting Guide explains entropy, conditional entropy, mutual information, divergence, and logarithm bases.\n\n## Core notation for Information Theory\n\nIn information theory, the notation usually represents random variables, alphabets, distributions, code lengths, channels, and logarithm bases. The table below gives a compact starting set for information theory; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| KL divergence | \u0060D_{\\mathrm{KL}}(P\\Vert Q)=\\sum_x p(x)\\log\\frac{p(x)}{q(x)}\u0060 | directed divergence from Q to P |\n| Channel capacity | \u0060C=\\max_{p(x)}I(X;Y)\u0060 | maximum mutual information over input distributions |\n| Chain rule | \u0060H(X,Y)=H(X)\u002BH(Y\\mid X)\u0060 | joint entropy decomposition |\n| Entropy | \u0060H(X)=-\\sum_x p(x)\\log p(x)\u0060 | average uncertainty of X |\n\n## LaTeX patterns that preserve the structure\n\nFor information theory: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nD_{\\mathrm{KL}}(P\\Vert Q)=\\sum_x p(x)\\log\\frac{p(x)}{q(x)}\nC=\\max_{p(x)}I(X;Y)\nH(X,Y)=H(X)\u002BH(Y\\mid X)\n\u0060\u0060\u0060\n\nFor information theory, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In information theory, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the logarithm base and resulting unit.\n- Distinguish entropy, cross-entropy, and kl divergence.\n- Specify discrete sums versus continuous integrals.\n\n## Renderer and export checks\n\nRender one demanding information theory example in the actual destination. For information theory, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the information theory source selectable and editable. For an isolated character in information theory, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of information theory is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities normalize.\n- Test deterministic and uniform distributions.\n- Confirm the order of p and q in every divergence.\n- Confirm every symbol used in information theory has one defined meaning in the local context.\n- Reopen the exported file for **Information Theory: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "information-theory-notation-reference",
    "title": "Information Theory: Notation Reference",
    "description": "Notation Reference for information theory: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Information Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Information Theory: Notation Reference explains entropy, conditional entropy, mutual information, divergence, and logarithm bases.\n\n## Core notation for Information Theory\n\nIn information theory, the notation usually represents random variables, alphabets, distributions, code lengths, channels, and logarithm bases. The table below gives a compact starting set for information theory; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| KL divergence | \u0060D_{\\mathrm{KL}}(P\\Vert Q)=\\sum_x p(x)\\log\\frac{p(x)}{q(x)}\u0060 | directed divergence from Q to P |\n| Channel capacity | \u0060C=\\max_{p(x)}I(X;Y)\u0060 | maximum mutual information over input distributions |\n| Chain rule | \u0060H(X,Y)=H(X)\u002BH(Y\\mid X)\u0060 | joint entropy decomposition |\n| Entropy | \u0060H(X)=-\\sum_x p(x)\\log p(x)\u0060 | average uncertainty of X |\n\n## How to read a complete expression\n\nRead \u0060D_{\\mathrm{KL}}(P\\Vert Q)=\\sum_x p(x)\\log\\frac{p(x)}{q(x)}\u0060 as \u201Cdirected divergence from Q to P.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in information theory from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the logarithm base and resulting unit.\n- Distinguish entropy, cross-entropy, and kl divergence.\n- Specify discrete sums versus continuous integrals.\n\n## Cross-checks before reuse\n\n- Verify probabilities normalize.\n- Test deterministic and uniform distributions.\n- Confirm the order of p and q in every divergence.\n\n## Accessibility and portability\n\nKeep the information theory source selectable and editable. For an isolated character in information theory, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of information theory is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities normalize.\n- Test deterministic and uniform distributions.\n- Confirm the order of p and q in every divergence.\n- Confirm every symbol used in information theory has one defined meaning in the local context.\n- Reopen the exported file for **Information Theory: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "integral-techniques-common-errors",
    "title": "Integral Techniques: Common Errors and Verification",
    "description": "Common Errors and Verification for integral techniques: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Integral Techniques",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Integral Techniques: Common Errors and Verification explains substitution, parts, partial fractions, bounds, and constants of integration.\n\n## Core notation for Integral Techniques: Common Errors and Verification\n\nIn integral techniques, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for integral techniques: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n\n## Errors that change the meaning\n\n- **Problem:** Dropping an absolute value in a substitution jacobian. **Correction:** write the missing integral techniques: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Interchanging a limit, sum, derivative, or integral without conditions. **Correction:** write the missing integral techniques: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Omitting boundary terms after integration by parts. **Correction:** write the missing integral techniques: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the integral techniques: common errors and verification expression. Then check the integral techniques: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced integral techniques: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the integral techniques: common errors and verification source selectable and editable. For an isolated character in integral techniques: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of integral techniques: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in integral techniques: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Integral Techniques: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "integral-techniques-latex-formatting",
    "title": "Integral Techniques: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for integral techniques: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Integral Techniques",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Integral Techniques: LaTeX Formatting Guide explains substitution, parts, partial fractions, bounds, and constants of integration.\n\n## Core notation for Integral Techniques\n\nIn integral techniques, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for integral techniques; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n\n## LaTeX patterns that preserve the structure\n\nFor integral techniques: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\nabla\\cdot F\nf(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\n\\lim_{x\\to a}f(x)=L\n\u0060\u0060\u0060\n\nFor integral techniques, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In integral techniques, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Renderer and export checks\n\nRender one demanding integral techniques example in the actual destination. For integral techniques, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the integral techniques source selectable and editable. For an isolated character in integral techniques, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of integral techniques is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in integral techniques has one defined meaning in the local context.\n- Reopen the exported file for **Integral Techniques: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "integral-techniques-notation-reference",
    "title": "Integral Techniques: Notation Reference",
    "description": "Notation Reference for integral techniques: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Integral Techniques",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Integral Techniques: Notation Reference explains substitution, parts, partial fractions, bounds, and constants of integration.\n\n## Core notation for Integral Techniques\n\nIn integral techniques, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for integral techniques; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n\n## How to read a complete expression\n\nRead \u0060\\int_a^b f(x)\\,dx\u0060 as \u201Caccumulated quantity over an interval.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in integral techniques from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Cross-checks before reuse\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the integral techniques source selectable and editable. For an isolated character in integral techniques, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of integral techniques is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in integral techniques has one defined meaning in the local context.\n- Reopen the exported file for **Integral Techniques: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "financial-math-rate-conventions",
    "title": "Interest Rate Conventions in Formulas",
    "description": "Match nominal, effective, periodic, simple, compound, and continuously compounded rates with the correct time units.",
    "topic": "Financial Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Match nominal, effective, periodic, simple, compound, and continuously compounded rates with the correct time units.\n\n## Core notation for Interest Rate Conventions in Formulas\n\nIn financial mathematics, the notation usually represents cash flows, dates, rates, compounding periods, discount factors, and sign conventions. The table below gives a compact starting set for interest rate conventions in formulas; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Annuity | \u0060PV=C\\frac{1-(1\u002Br)^{-n}}{r}\u0060 | present value of level end-of-period payments |\n| Return | \u0060R=\\frac{V_1-V_0\u002BC}{V_0}\u0060 | holding-period return with cash flow C |\n| Present value | \u0060PV=\\frac{FV}{(1\u002Br)^n}\u0060 | discounted value under periodic compounding |\n| Net present value | \u0060NPV=\\sum_{t=0}^{n}\\frac{C_t}{(1\u002Br)^t}\u0060 | discounted sum of dated cash flows |\n\n## Practical workflow\n\nStart from \u0060PV=C\\frac{1-(1\u002Br)^{-n}}{r}\u0060 and write one sentence that says it means \u201Cpresent value of level end-of-period payments.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State nominal versus effective rates.\n- Align each rate with its compounding period.\n- Declare whether inflows or outflows are positive.\n\n## Failure checks\n\n- Using an annual rate with monthly periods without conversion.\n- Mixing beginning-of-period and end-of-period cash flows.\n- Comparing returns computed with different day-count conventions.\n\n## Accessibility and portability\n\nKeep the interest rate conventions in formulas source selectable and editable. For an isolated character in interest rate conventions in formulas, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of interest rate conventions in formulas is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Draw a dated cash-flow timeline.\n- Convert all rates to a common period.\n- Verify the zero-rate limit.\n- Confirm every symbol used in interest rate conventions in formulas has one defined meaning in the local context.\n- Reopen the exported file for **Interest Rate Conventions in Formulas** and compare it with the editable source.\n"
  },
  {
    "slug": "topology-interior-closure-boundary",
    "title": "Interior, Closure, and Boundary Symbols",
    "description": "Read interior, closure, frontier, accumulation point, and derived-set notation consistently.",
    "topic": "Topology",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Read interior, closure, frontier, accumulation point, and derived-set notation consistently.\n\n## Core notation for Interior, Closure, and Boundary Symbols\n\nIn topology, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for interior, closure, and boundary symbols; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Open ball | \u0060B_r(x)=\\{y:d(x,y)\u003Cr\\}\u0060 | points within radius r of x |\n| Closure | \u0060\\overline{A}\u0060 | A together with its limit points |\n| Interior | \u0060A^\\circ\u0060 | largest open set contained in A |\n| Continuity | \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 | topological continuity criterion |\n\n## Practical workflow\n\nStart from \u0060B_r(x)=\\{y:d(x,y)\u003Cr\\}\u0060 and write one sentence that says it means \u201Cpoints within radius r of x.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the ambient space and topology.\n- Distinguish local from global properties.\n- Declare contour orientation and branch choices.\n\n## Failure checks\n\n- Using closed and bounded as a universal compactness criterion.\n- Crossing a branch cut without changing the selected argument.\n- Omitting hypotheses from a convergence or interchange theorem.\n\n## Accessibility and portability\n\nKeep the interior, closure, and boundary symbols source selectable and editable. For an isolated character in interior, closure, and boundary symbols, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of interior, closure, and boundary symbols is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in interior, closure, and boundary symbols has one defined meaning in the local context.\n- Reopen the exported file for **Interior, Closure, and Boundary Symbols** and compare it with the editable source.\n"
  },
  {
    "slug": "interval-notation-guide",
    "title": "Interval Notation: Parentheses, Brackets, and Infinity",
    "description": "Represent open, closed, half-open, and unbounded intervals without confusing interval notation with ordered pairs.",
    "topic": "Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Represent open, closed, half-open, and unbounded intervals without confusing interval notation with ordered pairs.\n\n## Core notation for Interval Notation: Parentheses, Brackets, and Infinity\n\nIn algebra, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for interval notation: parentheses, brackets, and infinity; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n\n## Practical workflow\n\nStart from \u0060\\text{\u201Cx squared plus one\u201D}\u0060 and write one sentence that says it means \u201Cplain-language reading when a text alternative is needed.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for interval notation: parentheses, brackets, and infinity rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the interval notation: parentheses, brackets, and infinity notation.\n\n## Failure checks\n\n- Copying a rendered interval notation: parentheses, brackets, and infinity image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in interval notation: parentheses, brackets, and infinity.\n- Defining interval notation: parentheses, brackets, and infinity macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the interval notation: parentheses, brackets, and infinity source selectable and editable. For an isolated character in interval notation: parentheses, brackets, and infinity, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of interval notation: parentheses, brackets, and infinity is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the interval notation: parentheses, brackets, and infinity example.\n- Confirm every symbol used in interval notation: parentheses, brackets, and infinity has one defined meaning in the local context.\n- Reopen the exported file for **Interval Notation: Parentheses, Brackets, and Infinity** and compare it with the editable source.\n"
  },
  {
    "slug": "jacobian-hessian-notation",
    "title": "Jacobian and Hessian Notation",
    "description": "Choose matrix orientation and index conventions for first and second derivatives.",
    "topic": "Calculus",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Choose matrix orientation and index conventions for first and second derivatives.\n\n## Core notation for Jacobian and Hessian Notation\n\nIn calculus, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for jacobian and hessian notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n\n## Practical workflow\n\nStart from \u0060\\nabla f\u0060 and write one sentence that says it means \u201Cvector of first partial derivatives.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Failure checks\n\n- Dropping an absolute value in a substitution jacobian.\n- Interchanging a limit, sum, derivative, or integral without conditions.\n- Omitting boundary terms after integration by parts.\n\n## Accessibility and portability\n\nKeep the jacobian and hessian notation source selectable and editable. For an isolated character in jacobian and hessian notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of jacobian and hessian notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in jacobian and hessian notation has one defined meaning in the local context.\n- Reopen the exported file for **Jacobian and Hessian Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "kkt-conditions-guide",
    "title": "KKT Conditions Guide",
    "description": "Separate stationarity, primal feasibility, dual feasibility, and complementary slackness.",
    "topic": "Optimization",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Separate stationarity, primal feasibility, dual feasibility, and complementary slackness.\n\n## Core notation for KKT Conditions\n\nIn optimization, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for kkt conditions; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Dual bound | \u0060d^\\star\\le p^\\star\u0060 | weak duality for a minimization primal |\n| Optimization problem | \u0060\\min_x f(x)\\quad\\text{s.t.}\\quad g_i(x)\\le 0\u0060 | minimize an objective over a constrained feasible set |\n| Lagrangian | \u0060\\mathcal{L}(x,\\lambda)=f(x)\u002B\\sum_i\\lambda_i g_i(x)\u0060 | objective plus weighted constraints |\n| Stationarity | \u0060\\nabla_x\\mathcal{L}(x,\\lambda)=0\u0060 | first-order stationarity condition |\n\n## Practical workflow\n\nStart from \u0060d^\\star\\le p^\\star\u0060 and write one sentence that says it means \u201Cweak duality for a minimization primal.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State minimization versus maximization and all constraint directions.\n- Separate an optimizer from the attained objective value.\n- Declare convexity and constraint-qualification assumptions.\n\n## Failure checks\n\n- Reversing a constraint sign without changing the multiplier convention.\n- Writing min when the result required is argmin.\n- Claiming kkt conditions are sufficient without convexity.\n\n## Accessibility and portability\n\nKeep the kkt conditions source selectable and editable. For an isolated character in kkt conditions, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of kkt conditions is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in kkt conditions has one defined meaning in the local context.\n- Reopen the exported file for **KKT Conditions Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "latex-documentation-common-errors",
    "title": "LaTeX Documentation: Common Errors and Verification",
    "description": "Common Errors and Verification for latex documentation: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "LaTeX Documentation",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "LaTeX Documentation: Common Errors and Verification explains commands, environments, packages, macros, errors, and portable examples.\n\n## Core notation for LaTeX Documentation: Common Errors and Verification\n\nIn latex documentation, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for latex documentation: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n\n## Errors that change the meaning\n\n- **Problem:** Copying a rendered image when editable notation is required. **Correction:** write the missing latex documentation: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using a look-alike unicode character with different semantics. **Correction:** write the missing latex documentation: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Defining macros that hide arguments or conflict with package commands. **Correction:** write the missing latex documentation: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the latex documentation: common errors and verification expression. Then check the latex documentation: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced latex documentation: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the latex documentation: common errors and verification example.\n\n## Accessibility and portability\n\nKeep the latex documentation: common errors and verification source selectable and editable. For an isolated character in latex documentation: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of latex documentation: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the latex documentation: common errors and verification example.\n- Confirm every symbol used in latex documentation: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **LaTeX Documentation: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "latex-documentation-latex-formatting",
    "title": "LaTeX Documentation: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for latex documentation: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "LaTeX Documentation",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "LaTeX Documentation: LaTeX Formatting Guide explains commands, environments, packages, macros, errors, and portable examples.\n\n## Core notation for LaTeX Documentation\n\nIn latex documentation, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for latex documentation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n\n## LaTeX patterns that preserve the structure\n\nFor latex documentation: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\text{\u201Cx squared plus one\u201D}\n\\newcommand{\\vect}[1]{\\mathbf{#1}}\n\\frac{a}{b}\n\u0060\u0060\u0060\n\nFor latex documentation, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In latex documentation, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Keep editable source with the rendered result.\n- Use semantic commands for latex documentation rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the latex documentation notation.\n\n## Renderer and export checks\n\nRender one demanding latex documentation example in the actual destination. For latex documentation, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the latex documentation source selectable and editable. For an isolated character in latex documentation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of latex documentation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the latex documentation example.\n- Confirm every symbol used in latex documentation has one defined meaning in the local context.\n- Reopen the exported file for **LaTeX Documentation: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "latex-to-unicode-when-to-use",
    "title": "LaTeX to Unicode: When Conversion Works",
    "description": "Learn when a LaTeX expression can become readable Unicode text, which structures are lost, and how to review the converted result.",
    "topic": "Format conversion",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Learn when a LaTeX expression can become readable Unicode text, which structures are lost, and how to review the converted result.\n\n## Core notation for LaTeX to Unicode: When Conversion Works\n\nIn format conversion, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for latex to unicode: when conversion works; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n\n## Practical workflow\n\nStart from \u0060\\frac{a}{b}\u0060 and write one sentence that says it means \u201Cstructured two-dimensional fraction.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for latex to unicode: when conversion works rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the latex to unicode: when conversion works notation.\n\n## Failure checks\n\n- Copying a rendered latex to unicode: when conversion works image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in latex to unicode: when conversion works.\n- Defining latex to unicode: when conversion works macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the latex to unicode: when conversion works source selectable and editable. For an isolated character in latex to unicode: when conversion works, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of latex to unicode: when conversion works is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the latex to unicode: when conversion works example.\n- Confirm every symbol used in latex to unicode: when conversion works has one defined meaning in the local context.\n- Reopen the exported file for **LaTeX to Unicode: When Conversion Works** and compare it with the editable source.\n"
  },
  {
    "slug": "lagrange-multiplier-workflow",
    "title": "Lagrange Multiplier Workflow",
    "description": "Set up objectives, equality constraints, multipliers, and second-order checks.",
    "topic": "Optimization",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Set up objectives, equality constraints, multipliers, and second-order checks.\n\n## Core notation for Lagrange Multiplier Workflow\n\nIn optimization, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for lagrange multiplier workflow; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Optimization problem | \u0060\\min_x f(x)\\quad\\text{s.t.}\\quad g_i(x)\\le 0\u0060 | minimize an objective over a constrained feasible set |\n| Lagrangian | \u0060\\mathcal{L}(x,\\lambda)=f(x)\u002B\\sum_i\\lambda_i g_i(x)\u0060 | objective plus weighted constraints |\n| Stationarity | \u0060\\nabla_x\\mathcal{L}(x,\\lambda)=0\u0060 | first-order stationarity condition |\n| Complementarity | \u0060\\lambda_i g_i(x)=0\u0060 | active-constraint relationship |\n\n## Practical workflow\n\nStart from \u0060\\min_x f(x)\\quad\\text{s.t.}\\quad g_i(x)\\le 0\u0060 and write one sentence that says it means \u201Cminimize an objective over a constrained feasible set.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State minimization versus maximization and all constraint directions.\n- Separate an optimizer from the attained objective value.\n- Declare convexity and constraint-qualification assumptions.\n\n## Failure checks\n\n- Reversing a constraint sign without changing the multiplier convention.\n- Writing min when the result required is argmin.\n- Claiming kkt conditions are sufficient without convexity.\n\n## Accessibility and portability\n\nKeep the lagrange multiplier workflow source selectable and editable. For an isolated character in lagrange multiplier workflow, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of lagrange multiplier workflow is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in lagrange multiplier workflow has one defined meaning in the local context.\n- Reopen the exported file for **Lagrange Multiplier Workflow** and compare it with the editable source.\n"
  },
  {
    "slug": "laplace-transform-region-convergence",
    "title": "Laplace Transform and Convergence",
    "description": "Record transform variables, regions of convergence, initial values, and inversion assumptions.",
    "topic": "Analysis",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Record transform variables, regions of convergence, initial values, and inversion assumptions.\n\n## Core notation for Laplace Transform and Convergence\n\nIn analysis, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for laplace transform and convergence; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Open ball | \u0060B_r(x)=\\{y:d(x,y)\u003Cr\\}\u0060 | points within radius r of x |\n| Closure | \u0060\\overline{A}\u0060 | A together with its limit points |\n| Interior | \u0060A^\\circ\u0060 | largest open set contained in A |\n| Continuity | \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 | topological continuity criterion |\n\n## Practical workflow\n\nStart from \u0060B_r(x)=\\{y:d(x,y)\u003Cr\\}\u0060 and write one sentence that says it means \u201Cpoints within radius r of x.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the ambient space and topology.\n- Distinguish local from global properties.\n- Declare contour orientation and branch choices.\n\n## Failure checks\n\n- Using closed and bounded as a universal compactness criterion.\n- Crossing a branch cut without changing the selected argument.\n- Omitting hypotheses from a convergence or interchange theorem.\n\n## Accessibility and portability\n\nKeep the laplace transform and convergence source selectable and editable. For an isolated character in laplace transform and convergence, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of laplace transform and convergence is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in laplace transform and convergence has one defined meaning in the local context.\n- Reopen the exported file for **Laplace Transform and Convergence** and compare it with the editable source.\n"
  },
  {
    "slug": "least-squares-common-errors",
    "title": "Least Squares: Common Errors and Verification",
    "description": "Common Errors and Verification for least squares: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Least Squares",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Least Squares: Common Errors and Verification explains design matrices, residuals, normal equations, rank, and diagnostics.\n\n## Core notation for Least Squares: Common Errors and Verification\n\nIn least squares, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for least squares: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sample mean | \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 | the arithmetic mean of n observations |\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n\n## Errors that change the meaning\n\n- **Problem:** Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate. **Correction:** write the missing least squares: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Reporting a standard deviation as though it were a standard error. **Correction:** write the missing least squares: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Rounding intermediate values so aggressively that the final result changes. **Correction:** write the missing least squares: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the least squares: common errors and verification expression. Then check the least squares: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced least squares: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n\n## Accessibility and portability\n\nKeep the least squares: common errors and verification source selectable and editable. For an isolated character in least squares: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of least squares: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in least squares: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Least Squares: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "least-squares-latex-formatting",
    "title": "Least Squares: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for least squares: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Least Squares",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Least Squares: LaTeX Formatting Guide explains design matrices, residuals, normal equations, rank, and diagnostics.\n\n## Core notation for Least Squares\n\nIn least squares, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for least squares; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Observation | \u0060x_i\u0060 | the i-th measured or observed value |\n| Sample mean | \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 | the arithmetic mean of n observations |\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n\n## LaTeX patterns that preserve the structure\n\nFor least squares: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nx_i\n\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\ns^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\n\u0060\u0060\u0060\n\nFor least squares, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In least squares, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Renderer and export checks\n\nRender one demanding least squares example in the actual destination. For least squares, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the least squares source selectable and editable. For an isolated character in least squares, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of least squares is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in least squares has one defined meaning in the local context.\n- Reopen the exported file for **Least Squares: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "least-squares-notation-reference",
    "title": "Least Squares: Notation Reference",
    "description": "Notation Reference for least squares: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Least Squares",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Least Squares: Notation Reference explains design matrices, residuals, normal equations, rank, and diagnostics.\n\n## Core notation for Least Squares\n\nIn least squares, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for least squares; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sample mean | \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 | the arithmetic mean of n observations |\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n\n## How to read a complete expression\n\nRead \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 as \u201Cthe arithmetic mean of n observations.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in least squares from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Cross-checks before reuse\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n\n## Accessibility and portability\n\nKeep the least squares source selectable and editable. For an isolated character in least squares, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of least squares is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in least squares has one defined meaning in the local context.\n- Reopen the exported file for **Least Squares: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "line-surface-volume-integrals",
    "title": "Line, Surface, and Volume Integrals",
    "description": "Format paths, parameterizations, measures, normals, and oriented boundaries.",
    "topic": "Vector Calculus",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Format paths, parameterizations, measures, normals, and oriented boundaries.\n\n## Core notation for Line, Surface, and Volume Integrals\n\nIn vector calculus, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for line, surface, and volume integrals; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n\n## Practical workflow\n\nStart from \u0060\\int_a^b f(x)\\,dx\u0060 and write one sentence that says it means \u201Caccumulated quantity over an interval.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Failure checks\n\n- Dropping an absolute value in a substitution jacobian.\n- Interchanging a limit, sum, derivative, or integral without conditions.\n- Omitting boundary terms after integration by parts.\n\n## Accessibility and portability\n\nKeep the line, surface, and volume integrals source selectable and editable. For an isolated character in line, surface, and volume integrals, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of line, surface, and volume integrals is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in line, surface, and volume integrals has one defined meaning in the local context.\n- Reopen the exported file for **Line, Surface, and Volume Integrals** and compare it with the editable source.\n"
  },
  {
    "slug": "linear-programming-standard-form",
    "title": "Linear Programming Standard Form",
    "description": "Translate objectives and constraints into a consistent matrix convention.",
    "topic": "Optimization",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Translate objectives and constraints into a consistent matrix convention.\n\n## Core notation for Linear Programming Standard Form\n\nIn optimization, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for linear programming standard form; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Optimization problem | \u0060\\min_x f(x)\\quad\\text{s.t.}\\quad g_i(x)\\le 0\u0060 | minimize an objective over a constrained feasible set |\n| Lagrangian | \u0060\\mathcal{L}(x,\\lambda)=f(x)\u002B\\sum_i\\lambda_i g_i(x)\u0060 | objective plus weighted constraints |\n| Stationarity | \u0060\\nabla_x\\mathcal{L}(x,\\lambda)=0\u0060 | first-order stationarity condition |\n| Complementarity | \u0060\\lambda_i g_i(x)=0\u0060 | active-constraint relationship |\n\n## Practical workflow\n\nStart from \u0060\\min_x f(x)\\quad\\text{s.t.}\\quad g_i(x)\\le 0\u0060 and write one sentence that says it means \u201Cminimize an objective over a constrained feasible set.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State minimization versus maximization and all constraint directions.\n- Separate an optimizer from the attained objective value.\n- Declare convexity and constraint-qualification assumptions.\n\n## Failure checks\n\n- Reversing a constraint sign without changing the multiplier convention.\n- Writing min when the result required is argmin.\n- Claiming kkt conditions are sufficient without convexity.\n\n## Accessibility and portability\n\nKeep the linear programming standard form source selectable and editable. For an isolated character in linear programming standard form, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of linear programming standard form is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in linear programming standard form has one defined meaning in the local context.\n- Reopen the exported file for **Linear Programming Standard Form** and compare it with the editable source.\n"
  },
  {
    "slug": "regression-notation-guide",
    "title": "Linear Regression Notation Guide",
    "description": "Distinguish observed responses, fitted values, residuals, coefficients, design matrices, and uncertainty estimates.",
    "topic": "Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Distinguish observed responses, fitted values, residuals, coefficients, design matrices, and uncertainty estimates.\n\n## Core notation for Linear Regression Notation\n\nIn statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for linear regression notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n| Correlation | \u0060r=\\frac{\\operatorname{cov}(X,Y)}{s_Xs_Y}\u0060 | standardized linear association |\n| Observation | \u0060x_i\u0060 | the i-th measured or observed value |\n\n## Practical workflow\n\nStart from \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 and write one sentence that says it means \u201Cestimated sampling variability of an estimator.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Failure checks\n\n- Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate.\n- Reporting a standard deviation as though it were a standard error.\n- Rounding intermediate values so aggressively that the final result changes.\n\n## Accessibility and portability\n\nKeep the linear regression notation source selectable and editable. For an isolated character in linear regression notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of linear regression notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in linear regression notation has one defined meaning in the local context.\n- Reopen the exported file for **Linear Regression Notation Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "logic-symbols-explained",
    "title": "Logic Symbols Explained",
    "description": "Read quantifiers, conjunctions, disjunctions, implications, and equivalence symbols.",
    "topic": "Reference",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "# Logic Symbols Explained\n\nRead quantifiers, conjunctions, disjunctions, implications, and equivalence symbols. This guide focuses on reliable methods that preserve the intended character or mathematical structure when the text is copied, published, or shared.\n\n## Quick answer\n\nThe fastest option is to copy this character: **\u2200**. For a real mathematical equation, use the LaTeX form \u0060\\forall\u0060 when your editor supports math rendering. Plain Unicode is ideal for short text, while LaTeX or an equation editor is better for structured notation.\n\n## Choose the right format\n\nUse **Unicode** when the symbol must remain a normal text character in an email, title, spreadsheet, or social post. Use **LaTeX** when the expression contains fractions, roots, limits, stacked scripts, or other two-dimensional notation. Use **HTML entities or numeric references** when the symbol is part of a web page and escaping or source-code clarity matters. Use **MathML** when semantic browser-accessible mathematics is required.\n\n| Format | Value | Best for |\n|---|---|---|\n| Character | \u0060\u2200\u0060 | Plain text and quick copy |\n| Unicode | \u0060U\u002B2200\u0060 | Character lookup and encoding |\n| LaTeX | \u0060\\forall\u0060 | Equations and technical writing |\n| HTML | \u0060\u0026forall;\u0060 | Web pages |\n| MathML | \u0060\u0026lt;mo\u0026gt;\u2200\u0026lt;/mo\u0026gt;\u0060 | Semantic web mathematics |\n\n## Windows\n\nOpen **Character Map**, search for the symbol name, select the character, and copy it. In Microsoft Word and some Office applications, you can also type the hexadecimal Unicode value and press **Alt\u002BX**. Application support varies, so verify the result before relying on a shortcut in a different editor.\n\n## Mac\n\nPress **Control\u2013Command\u2013Space** to open Character Viewer. Search for the English symbol name, then double-click the result. Frequently used characters can be added to Favorites. In equation-capable applications, prefer the app\u2019s math editor when the character is part of a larger formula.\n\n## Microsoft Word\n\nPress **Alt\u002B=** to open an equation, type \u0060\\forall\u0060, and press Space when Word recognizes the command. For plain text, use **Insert \u2192 Symbol \u2192 More Symbols**, or paste the Unicode character. The equation route is preferable when scripts, fractions, limits, or alignment are involved.\n\n## Google Docs\n\nChoose **Insert \u2192 Special characters**, search by name, or draw an approximate shape. For equations, choose **Insert \u2192 Equation** and use the available notation controls. Google Docs supports a useful subset of equation shortcuts, but it does not behave exactly like a full LaTeX system.\n\n## HTML and web pages\n\nA literal UTF-8 character is usually the clearest choice when the document declares UTF-8. Named entities can improve readability for common characters, while numeric references are a dependable fallback. Keep the symbol in meaningful text rather than using a background image, because text is selectable, searchable, and more accessible.\n\n\u0060\u0060\u0060html\n\u003Cspan aria-label=\u0022For All\u0022\u003E\u2200\u003C/span\u003E\n\u003Cspan\u003E\u0026forall;\u003C/span\u003E\n\u0060\u0060\u0060\n\n## LaTeX example\n\n\u0060\u0060\u0060latex\n\\forall\n\u0060\u0060\u0060\n\nWhen the symbol is an operator or relation, place it in math mode and allow LaTeX to apply the correct spacing. Avoid forcing a mathematical expression into a sequence of unrelated Unicode characters when semantic structure matters.\n\n## Common mistakes\n\nDo not substitute a visually similar letter, punctuation mark, or image. Similar-looking characters may have different Unicode values and meanings. Also avoid copying from a decorative font that changes the glyph without changing the underlying character. Finally, check whether the surrounding context requires a specific convention; several mathematical symbols have meanings that vary by field or textbook.\n\n## Related resources\n\nUse the symbol page for definitions, examples, copy controls, and platform-specific input methods. Browse the relevant category for nearby notation, or open the LaTeX editor to test a complete formula before publishing it.\n"
  },
  {
    "slug": "logistic-regression-notation",
    "title": "Logistic Regression Notation",
    "description": "Separate linear predictors, odds, probabilities, coefficients, and likelihood.",
    "topic": "Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Separate linear predictors, odds, probabilities, coefficients, and likelihood.\n\n## Core notation for Logistic Regression Notation\n\nIn statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for logistic regression notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n| Correlation | \u0060r=\\frac{\\operatorname{cov}(X,Y)}{s_Xs_Y}\u0060 | standardized linear association |\n| Observation | \u0060x_i\u0060 | the i-th measured or observed value |\n\n## Practical workflow\n\nStart from \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 and write one sentence that says it means \u201Cestimated sampling variability of an estimator.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Failure checks\n\n- Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate.\n- Reporting a standard deviation as though it were a standard error.\n- Rounding intermediate values so aggressively that the final result changes.\n\n## Accessibility and portability\n\nKeep the logistic regression notation source selectable and editable. For an isolated character in logistic regression notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of logistic regression notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in logistic regression notation has one defined meaning in the local context.\n- Reopen the exported file for **Logistic Regression Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "model-error-metrics",
    "title": "MSE, RMSE, and MAE Compared",
    "description": "Choose prediction error metrics by units, sensitivity to outliers, optimization behavior, and reporting context.",
    "topic": "Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Choose prediction error metrics by units, sensitivity to outliers, optimization behavior, and reporting context.\n\n## Core notation for MSE, RMSE, and MAE Compared\n\nIn statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for mse, rmse, and mae compared; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sample mean | \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 | the arithmetic mean of n observations |\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n\n## Practical workflow\n\nStart from \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 and write one sentence that says it means \u201Cthe arithmetic mean of n observations.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Failure checks\n\n- Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate.\n- Reporting a standard deviation as though it were a standard error.\n- Rounding intermediate values so aggressively that the final result changes.\n\n## Accessibility and portability\n\nKeep the mse, rmse, and mae compared source selectable and editable. For an isolated character in mse, rmse, and mae compared, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of mse, rmse, and mae compared is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in mse, rmse, and mae compared has one defined meaning in the local context.\n- Reopen the exported file for **MSE, RMSE, and MAE Compared** and compare it with the editable source.\n"
  },
  {
    "slug": "markov-chain-notation",
    "title": "Markov Chain Notation",
    "description": "Define states, transition matrices, distributions, stationarity, and time indexes.",
    "topic": "Probability",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Define states, transition matrices, distributions, stationarity, and time indexes.\n\n## Core notation for Markov Chain Notation\n\nIn probability, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for markov chain notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Bayes rule | \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 | posterior proportional to likelihood times prior |\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n\n## Practical workflow\n\nStart from \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 and write one sentence that says it means \u201Cposterior proportional to likelihood times prior.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Failure checks\n\n- Dropping the condition after applying a conditional identity.\n- Confusing a probability mass with a probability density.\n- Using the same distribution name with incompatible parameter orders.\n\n## Accessibility and portability\n\nKeep the markov chain notation source selectable and editable. For an isolated character in markov chain notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of markov chain notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in markov chain notation has one defined meaning in the local context.\n- Reopen the exported file for **Markov Chain Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "math-fonts-unicode-compatibility",
    "title": "Math Fonts and Unicode Compatibility",
    "description": "Understand why a symbol may render differently across systems and how to choose fonts and fallback strategies for mathematical text.",
    "topic": "Publishing",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Understand why a symbol may render differently across systems and how to choose fonts and fallback strategies for mathematical text.\n\n## Core notation for Math Fonts and Unicode Compatibility\n\nIn publishing, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for math fonts and unicode compatibility; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## Practical workflow\n\nStart from \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 and write one sentence that says it means \u201Csemantic operator element.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for math fonts and unicode compatibility rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the math fonts and unicode compatibility notation.\n\n## Failure checks\n\n- Copying a rendered math fonts and unicode compatibility image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in math fonts and unicode compatibility.\n- Defining math fonts and unicode compatibility macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the math fonts and unicode compatibility source selectable and editable. For an isolated character in math fonts and unicode compatibility, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of math fonts and unicode compatibility is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the math fonts and unicode compatibility example.\n- Confirm every symbol used in math fonts and unicode compatibility has one defined meaning in the local context.\n- Reopen the exported file for **Math Fonts and Unicode Compatibility** and compare it with the editable source.\n"
  },
  {
    "slug": "mathml-authoring-common-errors",
    "title": "MathML Authoring: Common Errors and Verification",
    "description": "Common Errors and Verification for mathml authoring: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "MathML Authoring",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "MathML Authoring: Common Errors and Verification explains presentation structure, semantics, accessibility, browser testing, and fallbacks.\n\n## Core notation for MathML Authoring: Common Errors and Verification\n\nIn mathml authoring, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for mathml authoring: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n\n## Errors that change the meaning\n\n- **Problem:** Copying a rendered image when editable notation is required. **Correction:** write the missing mathml authoring: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using a look-alike unicode character with different semantics. **Correction:** write the missing mathml authoring: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Defining macros that hide arguments or conflict with package commands. **Correction:** write the missing mathml authoring: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the mathml authoring: common errors and verification expression. Then check the mathml authoring: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced mathml authoring: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the mathml authoring: common errors and verification example.\n\n## Accessibility and portability\n\nKeep the mathml authoring: common errors and verification source selectable and editable. For an isolated character in mathml authoring: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of mathml authoring: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the mathml authoring: common errors and verification example.\n- Confirm every symbol used in mathml authoring: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **MathML Authoring: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "mathml-authoring-latex-formatting",
    "title": "MathML Authoring: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for mathml authoring: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "MathML Authoring",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "MathML Authoring: LaTeX Formatting Guide explains presentation structure, semantics, accessibility, browser testing, and fallbacks.\n\n## Core notation for MathML Authoring\n\nIn mathml authoring, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for mathml authoring; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## LaTeX patterns that preserve the structure\n\nFor mathml authoring: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\n\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\n\\text{\u201Cx squared plus one\u201D}\n\u0060\u0060\u0060\n\nFor mathml authoring, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In mathml authoring, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Keep editable source with the rendered result.\n- Use semantic commands for mathml authoring rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the mathml authoring notation.\n\n## Renderer and export checks\n\nRender one demanding mathml authoring example in the actual destination. For mathml authoring, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the mathml authoring source selectable and editable. For an isolated character in mathml authoring, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of mathml authoring is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the mathml authoring example.\n- Confirm every symbol used in mathml authoring has one defined meaning in the local context.\n- Reopen the exported file for **MathML Authoring: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "mathml-basics-for-web",
    "title": "MathML Basics for Web Authors",
    "description": "Understand semantic MathML structure, browser support, fallbacks, and accessibility considerations.",
    "topic": "Web math",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "## Quick answer\n\nUnderstand semantic MathML structure, browser support, fallbacks, and accessibility considerations. The safest choice is to preserve semantic math whenever the destination supports equations, and use Unicode only for short standalone characters.\n\n## Recommended methods\n\n### LaTeX and equation editors\n\nUse an equation editor for structured notation. LaTeX keeps operators, limits, scripts, fractions, and spacing connected to the mathematical meaning. Copy the exact command from the symbol reference, preview it, and verify that the target platform uses a compatible math engine.\n\n### Unicode text\n\nUnicode is convenient for a single symbol in a message, heading, spreadsheet label, or plain-text note. Confirm that the selected font contains the glyph and that a visually similar character was not substituted. Unicode text does not automatically encode complex relationships such as a numerator over a denominator.\n\n### Word, Windows, and macOS\n\nIn Microsoft Word, insert an equation before entering LaTeX-like commands. On Windows, Character Map and the emoji/symbol panel can insert individual characters. On macOS, Character Viewer is useful for searching by the English Unicode name. Always test copy and paste in the final application.\n\n## Common mistakes\n\n1. Replacing a mathematical symbol with punctuation that only looks similar.\n2. Mixing Unicode characters with equation-editor markup without checking baseline and spacing.\n3. Copying hidden directional or formatting characters from a web page.\n4. Assuming the same shortcut works in normal text and in an equation field.\n\n## HTML and accessible publishing\n\nFor a single character, place the Unicode symbol directly in UTF-8 HTML and include surrounding words that explain its meaning. For a formula, prefer MathML or a renderer that exposes semantic MathML to assistive technology. Do not publish important equations only as unlabeled images.\n\n## Final check\n\nVerify the symbol, meaning, font, spacing, and spoken description in the final output. If the notation could be interpreted in more than one way, define it in the sentence before the equation.\n\n## Practical verification workflow\n\nBefore publishing, test the notation in the exact application and export format your readers will use. Copy the source into a clean document, save it, reopen it, and verify that the expression remains editable. Compare the original source with the exported PDF or HTML so that substituted fonts, missing glyphs, broken braces, and incorrect line breaks are caught early.\n\nFor web content, inspect the page at narrow mobile widths, at 200 percent browser zoom, and with keyboard-only navigation. Confirm that symbols can be selected and copied as text. When an equation is rendered by JavaScript, keep a meaningful text fallback and avoid placing essential explanation only inside the visual formula. For office documents, check both normal view and presentation or print view because equation spacing can change during export.\n\nFinally, ask a second reviewer to read the notation in context. The reviewer should confirm not only that the symbol looks correct, but also that its mathematical meaning, units, sign convention, and surrounding explanation are unambiguous. Store the editable source beside the published version so future corrections do not depend on reverse-engineering an image.\n"
  },
  {
    "slug": "mathml-semantics-annotation",
    "title": "MathML Semantics and Annotations",
    "description": "Preserve alternate representations such as LaTeX while keeping presentation MathML available to browsers and assistive technology.",
    "topic": "MathML",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Preserve alternate representations such as LaTeX while keeping presentation MathML available to browsers and assistive technology.\n\n## Core notation for MathML Semantics and Annotations\n\nIn mathml, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for mathml semantics and annotations; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## Practical workflow\n\nStart from \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 and write one sentence that says it means \u201Csemantic operator element.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for mathml semantics and annotations rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the mathml semantics and annotations notation.\n\n## Failure checks\n\n- Copying a rendered mathml semantics and annotations image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in mathml semantics and annotations.\n- Defining mathml semantics and annotations macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the mathml semantics and annotations source selectable and editable. For an isolated character in mathml semantics and annotations, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of mathml semantics and annotations is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the mathml semantics and annotations example.\n- Confirm every symbol used in mathml semantics and annotations has one defined meaning in the local context.\n- Reopen the exported file for **MathML Semantics and Annotations** and compare it with the editable source.\n"
  },
  {
    "slug": "mathml-to-latex-conversion-guide",
    "title": "MathML to LaTeX Conversion Guide",
    "description": "Understand which MathML structures convert cleanly to LaTeX, where semantic information is lost, and how to review converted equations.",
    "topic": "Format conversion",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Understand which MathML structures convert cleanly to LaTeX, where semantic information is lost, and how to review converted equations. This guide focuses on reliable, editable output rather than visual shortcuts. The exact menu names can vary by application version, but the underlying choice remains the same: use Unicode for isolated characters and structured math for complete expressions.\n\n## Choose the right representation\n\nMathematical notation can be stored as ordinary Unicode text, structured equation markup, or an image. Unicode is convenient for isolated symbols and short labels. LaTeX and MathML preserve structure for fractions, matrices, scripts, and aligned equations. Images should be a last resort because they are harder to edit, search, resize, and make accessible.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Create the notation\n\nStart in the native equation editor when the destination application provides one. Native editors understand mathematical grouping, spacing, and baseline alignment better than manual character placement. When importing text, separate semantic content from presentation: identify operators, variables, units, subscripts, and conditions before deciding how they should look.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Check meaning and ambiguity\n\nThe same visible character can carry several meanings across algebra, statistics, physics, and chemistry. Define uncommon notation and review nearby variables before converting formats. Plain Unicode cannot always distinguish multiplication from a dot product, a hyphen from a minus sign, or a decorative letter from a mathematical constant.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Preserve accessibility\n\nUse real text or structured math whenever possible. Provide a concise spoken description for an image and include the surrounding purpose of the equation rather than reading every punctuation mark mechanically. Keyboard focus, selectable text, sufficient contrast, and responsive layout are also part of accessible mathematical communication.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Test the final output\n\nCopy the result into the actual destination, save and reopen the file, then inspect desktop, mobile, print, and exported PDF views. Confirm that fonts contain every symbol, line breaks do not split expressions incorrectly, and superscripts remain attached to the intended base. For web pages, test without JavaScript and with browser zoom.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Use a repeatable workflow\n\nKeep the source notation in a plain, version-controlled format when possible. Record the LaTeX command, Unicode code point, and intended meaning for symbols that appear frequently. A repeatable workflow reduces silent substitutions and makes later updates easier when the content moves between Word, HTML, Markdown, presentation software, and publishing systems.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Final checklist\n\n1. Confirm the mathematical meaning in context.\n2. Prefer native equation markup for structured expressions.\n3. Verify Unicode and LaTeX independently.\n4. Test copying, exporting, zooming, and screen-reader output.\n5. Keep an editable source version for future correction.\n"
  },
  {
    "slug": "mathml-matrices-tables",
    "title": "Matrices and Tables in MathML",
    "description": "Represent matrix rows and cells with predictable grouping, delimiters, and accessible source order.",
    "topic": "MathML",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Represent matrix rows and cells with predictable grouping, delimiters, and accessible source order.\n\n## Core notation for Matrices and Tables in MathML\n\nIn mathml, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for matrices and tables in mathml; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## Practical workflow\n\nStart from \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 and write one sentence that says it means \u201Csemantic operator element.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for matrices and tables in mathml rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the matrices and tables in mathml notation.\n\n## Failure checks\n\n- Copying a rendered matrices and tables in mathml image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in matrices and tables in mathml.\n- Defining matrices and tables in mathml macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the matrices and tables in mathml source selectable and editable. For an isolated character in matrices and tables in mathml, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of matrices and tables in mathml is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the matrices and tables in mathml example.\n- Confirm every symbol used in matrices and tables in mathml has one defined meaning in the local context.\n- Reopen the exported file for **Matrices and Tables in MathML** and compare it with the editable source.\n"
  },
  {
    "slug": "matrix-algebra-common-errors",
    "title": "Matrix Algebra: Common Errors and Verification",
    "description": "Common Errors and Verification for matrix algebra: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Matrix Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Matrix Algebra: Common Errors and Verification explains dimensions, products, inverses, determinants, rank, and transposes.\n\n## Core notation for Matrix Algebra: Common Errors and Verification\n\nIn matrix algebra, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for matrix algebra: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Inverse | \u0060A^{-1}A=I\u0060 | inverse relation when A is nonsingular |\n| Eigenpair | \u0060Av=\\lambda v\u0060 | v is an eigenvector with eigenvalue \u03BB |\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n| Norm | \u0060\\lVert x\\rVert_2\u0060 | Euclidean length of vector x |\n\n## Errors that change the meaning\n\n- **Problem:** Multiplying matrices whose inner dimensions do not agree. **Correction:** write the missing matrix algebra: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Treating elementwise multiplication as matrix multiplication. **Correction:** write the missing matrix algebra: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Assuming an inverse exists without checking rank or determinant. **Correction:** write the missing matrix algebra: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the matrix algebra: common errors and verification expression. Then check the matrix algebra: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced matrix algebra: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n\n## Accessibility and portability\n\nKeep the matrix algebra: common errors and verification source selectable and editable. For an isolated character in matrix algebra: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of matrix algebra: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in matrix algebra: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Matrix Algebra: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "matrix-algebra-latex-formatting",
    "title": "Matrix Algebra: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for matrix algebra: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Matrix Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Matrix Algebra: LaTeX Formatting Guide explains dimensions, products, inverses, determinants, rank, and transposes.\n\n## Core notation for Matrix Algebra\n\nIn matrix algebra, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for matrix algebra; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n| Norm | \u0060\\lVert x\\rVert_2\u0060 | Euclidean length of vector x |\n| Matrix product | \u0060C=AB\u0060 | composition with inner dimensions matched |\n| Transpose | \u0060A^{\\mathsf T}\u0060 | rows and columns exchanged |\n\n## LaTeX patterns that preserve the structure\n\nFor matrix algebra: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nA=U\\Sigma V^{\\mathsf T}\n\\lVert x\\rVert_2\nC=AB\n\u0060\u0060\u0060\n\nFor matrix algebra, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In matrix algebra, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Renderer and export checks\n\nRender one demanding matrix algebra example in the actual destination. For matrix algebra, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the matrix algebra source selectable and editable. For an isolated character in matrix algebra, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of matrix algebra is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in matrix algebra has one defined meaning in the local context.\n- Reopen the exported file for **Matrix Algebra: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "matrix-algebra-notation-reference",
    "title": "Matrix Algebra: Notation Reference",
    "description": "Notation Reference for matrix algebra: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Matrix Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Matrix Algebra: Notation Reference explains dimensions, products, inverses, determinants, rank, and transposes.\n\n## Core notation for Matrix Algebra\n\nIn matrix algebra, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for matrix algebra; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Transpose | \u0060A^{\\mathsf T}\u0060 | rows and columns exchanged |\n| Inverse | \u0060A^{-1}A=I\u0060 | inverse relation when A is nonsingular |\n| Eigenpair | \u0060Av=\\lambda v\u0060 | v is an eigenvector with eigenvalue \u03BB |\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n\n## How to read a complete expression\n\nRead \u0060A^{\\mathsf T}\u0060 as \u201Crows and columns exchanged.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in matrix algebra from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Cross-checks before reuse\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n\n## Accessibility and portability\n\nKeep the matrix algebra source selectable and editable. For an isolated character in matrix algebra, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of matrix algebra is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in matrix algebra has one defined meaning in the local context.\n- Reopen the exported file for **Matrix Algebra: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "matrix-decompositions-overview",
    "title": "Matrix Decomposition Notation",
    "description": "Compare LU, QR, eigenvalue, singular-value, and Cholesky decompositions.",
    "topic": "Linear Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Compare LU, QR, eigenvalue, singular-value, and Cholesky decompositions.\n\n## Core notation for Matrix Decomposition Notation\n\nIn linear algebra, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for matrix decomposition notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Norm | \u0060\\lVert x\\rVert_2\u0060 | Euclidean length of vector x |\n| Matrix product | \u0060C=AB\u0060 | composition with inner dimensions matched |\n| Transpose | \u0060A^{\\mathsf T}\u0060 | rows and columns exchanged |\n| Inverse | \u0060A^{-1}A=I\u0060 | inverse relation when A is nonsingular |\n\n## Practical workflow\n\nStart from \u0060\\lVert x\\rVert_2\u0060 and write one sentence that says it means \u201CEuclidean length of vector x.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Failure checks\n\n- Multiplying matrices whose inner dimensions do not agree.\n- Treating elementwise multiplication as matrix multiplication.\n- Assuming an inverse exists without checking rank or determinant.\n\n## Accessibility and portability\n\nKeep the matrix decomposition notation source selectable and editable. For an isolated character in matrix decomposition notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of matrix decomposition notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in matrix decomposition notation has one defined meaning in the local context.\n- Reopen the exported file for **Matrix Decomposition Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "matrix-operations-guide",
    "title": "Matrix Operations: Add, Multiply, Transpose, and Check Dimensions",
    "description": "Understand the dimension rules behind matrix addition, multiplication, and transposition before using an online calculator.",
    "topic": "Linear algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Understand the dimension rules behind matrix addition, multiplication, and transposition before using an online calculator.\n\n## Core notation for Matrix Operations: Add, Multiply, Transpose, and Check Dimensions\n\nIn linear algebra, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for matrix operations: add, multiply, transpose, and check dimensions; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Eigenpair | \u0060Av=\\lambda v\u0060 | v is an eigenvector with eigenvalue \u03BB |\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n| Norm | \u0060\\lVert x\\rVert_2\u0060 | Euclidean length of vector x |\n| Matrix product | \u0060C=AB\u0060 | composition with inner dimensions matched |\n\n## Practical workflow\n\nStart from \u0060Av=\\lambda v\u0060 and write one sentence that says it means \u201Cv is an eigenvector with eigenvalue \u03BB.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Failure checks\n\n- Multiplying matrices whose inner dimensions do not agree.\n- Treating elementwise multiplication as matrix multiplication.\n- Assuming an inverse exists without checking rank or determinant.\n\n## Accessibility and portability\n\nKeep the matrix operations: add, multiply, transpose, and check dimensions source selectable and editable. For an isolated character in matrix operations: add, multiply, transpose, and check dimensions, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of matrix operations: add, multiply, transpose, and check dimensions is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in matrix operations: add, multiply, transpose, and check dimensions has one defined meaning in the local context.\n- Reopen the exported file for **Matrix Operations: Add, Multiply, Transpose, and Check Dimensions** and compare it with the editable source.\n"
  },
  {
    "slug": "uncertainty-significant-digits",
    "title": "Measurement Uncertainty and Significant Digits",
    "description": "Round estimates and uncertainties without implying unsupported precision.",
    "topic": "Scientific Writing",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Round estimates and uncertainties without implying unsupported precision.\n\n## Core notation for Measurement Uncertainty and Significant Digits\n\nIn scientific writing, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for measurement uncertainty and significant digits; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n\n## Practical workflow\n\nStart from \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 and write one sentence that says it means \u201Cmulti-line alignment at relation signs.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for measurement uncertainty and significant digits rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the measurement uncertainty and significant digits notation.\n\n## Failure checks\n\n- Copying a rendered measurement uncertainty and significant digits image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in measurement uncertainty and significant digits.\n- Defining measurement uncertainty and significant digits macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the measurement uncertainty and significant digits source selectable and editable. For an isolated character in measurement uncertainty and significant digits, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of measurement uncertainty and significant digits is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the measurement uncertainty and significant digits example.\n- Confirm every symbol used in measurement uncertainty and significant digits has one defined meaning in the local context.\n- Reopen the exported file for **Measurement Uncertainty and Significant Digits** and compare it with the editable source.\n"
  },
  {
    "slug": "metric-tensor-raising-lowering",
    "title": "Metric Tensor and Index Raising",
    "description": "Use a metric and inverse metric to raise, lower, and contract indexes.",
    "topic": "Tensor Calculus",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Use a metric and inverse metric to raise, lower, and contract indexes.\n\n## Core notation for Metric Tensor and Index Raising\n\nIn tensor calculus, the notation usually represents tensor components, index positions, coordinate charts, bases, and contraction rules. The table below gives a compact starting set for metric tensor and index raising; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Tensor component | \u0060T^{i}{}_{jk}\u0060 | one contravariant and two covariant indices |\n| Contraction | \u0060T^{i}{}_{ik}\u0060 | summation over a repeated upper-lower index |\n| Metric lowering | \u0060v_i=g_{ij}v^j\u0060 | lowering an index with the metric |\n| Metric raising | \u0060v^i=g^{ij}v_j\u0060 | raising an index with the inverse metric |\n\n## Practical workflow\n\nStart from \u0060T^{i}{}_{jk}\u0060 and write one sentence that says it means \u201Cone contravariant and two covariant indices.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Declare the index range and summation convention.\n- Keep upper and lower index roles consistent.\n- State the metric signature and coordinate chart.\n\n## Failure checks\n\n- Repeating an index more than twice in one monomial.\n- Contracting two upper indices without a metric.\n- Moving an index without applying the metric tensor.\n\n## Accessibility and portability\n\nKeep the metric tensor and index raising source selectable and editable. For an isolated character in metric tensor and index raising, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of metric tensor and index raising is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify each free index appears once on both sides.\n- Check that dummy indices may be renamed consistently.\n- Test the expression in a simple coordinate system.\n- Confirm every symbol used in metric tensor and index raising has one defined meaning in the local context.\n- Reopen the exported file for **Metric Tensor and Index Raising** and compare it with the editable source.\n"
  },
  {
    "slug": "multivariable-taylor-guide",
    "title": "Multivariable Taylor Expansion",
    "description": "Write gradient, Hessian, remainder, and local approximation terms.",
    "topic": "Analysis",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Write gradient, Hessian, remainder, and local approximation terms.\n\n## Core notation for Multivariable Taylor Expansion\n\nIn analysis, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for multivariable taylor expansion; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n\n## Practical workflow\n\nStart from \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 and write one sentence that says it means \u201Clocal polynomial approximation with remainder.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Failure checks\n\n- Dropping an absolute value in a substitution jacobian.\n- Interchanging a limit, sum, derivative, or integral without conditions.\n- Omitting boundary terms after integration by parts.\n\n## Accessibility and portability\n\nKeep the multivariable taylor expansion source selectable and editable. For an isolated character in multivariable taylor expansion, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of multivariable taylor expansion is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in multivariable taylor expansion has one defined meaning in the local context.\n- Reopen the exported file for **Multivariable Taylor Expansion** and compare it with the editable source.\n"
  },
  {
    "slug": "mutual-information-notation",
    "title": "Mutual Information Notation",
    "description": "Relate joint, marginal, conditional distributions, entropy, and mutual information.",
    "topic": "Information Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Relate joint, marginal, conditional distributions, entropy, and mutual information.\n\n## Core notation for Mutual Information Notation\n\nIn information theory, the notation usually represents random variables, alphabets, distributions, code lengths, channels, and logarithm bases. The table below gives a compact starting set for mutual information notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Chain rule | \u0060H(X,Y)=H(X)\u002BH(Y\\mid X)\u0060 | joint entropy decomposition |\n| Entropy | \u0060H(X)=-\\sum_x p(x)\\log p(x)\u0060 | average uncertainty of X |\n| Conditional entropy | \u0060H(X\\mid Y)\u0060 | uncertainty remaining after observing Y |\n| Mutual information | \u0060I(X;Y)=H(X)-H(X\\mid Y)\u0060 | shared information between X and Y |\n\n## Practical workflow\n\nStart from \u0060H(X,Y)=H(X)\u002BH(Y\\mid X)\u0060 and write one sentence that says it means \u201Cjoint entropy decomposition.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the logarithm base and resulting unit.\n- Distinguish entropy, cross-entropy, and kl divergence.\n- Specify discrete sums versus continuous integrals.\n\n## Failure checks\n\n- Assuming kl divergence is symmetric.\n- Mixing bits and nats in one calculation.\n- Using 0 log 0 without the standard limiting convention.\n\n## Accessibility and portability\n\nKeep the mutual information notation source selectable and editable. For an isolated character in mutual information notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of mutual information notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities normalize.\n- Test deterministic and uniform distributions.\n- Confirm the order of p and q in every divergence.\n- Confirm every symbol used in mutual information notation has one defined meaning in the local context.\n- Reopen the exported file for **Mutual Information Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "npv-irr-guide",
    "title": "NPV and IRR Notation Explained",
    "description": "Understand discounted cash-flow equations, root-finding, multiple IRRs, and the role of the discount rate.",
    "topic": "Financial Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Understand discounted cash-flow equations, root-finding, multiple IRRs, and the role of the discount rate.\n\n## Core notation for NPV and IRR Notation Explained\n\nIn financial mathematics, the notation usually represents cash flows, dates, rates, compounding periods, discount factors, and sign conventions. The table below gives a compact starting set for npv and irr notation explained; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Effective rate | \u00601\u002Br_{\\mathrm{eff}}=(1\u002Br_m/m)^m\u0060 | effective annual rate from a nominal rate |\n| Continuous growth | \u0060FV=PV\\,e^{rt}\u0060 | continuous compounding model |\n| Annuity | \u0060PV=C\\frac{1-(1\u002Br)^{-n}}{r}\u0060 | present value of level end-of-period payments |\n| Return | \u0060R=\\frac{V_1-V_0\u002BC}{V_0}\u0060 | holding-period return with cash flow C |\n\n## Practical workflow\n\nStart from \u00601\u002Br_{\\mathrm{eff}}=(1\u002Br_m/m)^m\u0060 and write one sentence that says it means \u201Ceffective annual rate from a nominal rate.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State nominal versus effective rates.\n- Align each rate with its compounding period.\n- Declare whether inflows or outflows are positive.\n\n## Failure checks\n\n- Using an annual rate with monthly periods without conversion.\n- Mixing beginning-of-period and end-of-period cash flows.\n- Comparing returns computed with different day-count conventions.\n\n## Accessibility and portability\n\nKeep the npv and irr notation explained source selectable and editable. For an isolated character in npv and irr notation explained, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of npv and irr notation explained is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Draw a dated cash-flow timeline.\n- Convert all rates to a common period.\n- Verify the zero-rate limit.\n- Confirm every symbol used in npv and irr notation explained has one defined meaning in the local context.\n- Reopen the exported file for **NPV and IRR Notation Explained** and compare it with the editable source.\n"
  },
  {
    "slug": "normal-distribution-notation",
    "title": "Normal Distribution Notation",
    "description": "Write parameters, standardization, density, cumulative probabilities, and quantiles.",
    "topic": "Probability",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Write parameters, standardization, density, cumulative probabilities, and quantiles.\n\n## Core notation for Normal Distribution Notation\n\nIn probability, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for normal distribution notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Variance | \u0060\\operatorname{Var}(X)=\\mathbb{E}[(X-\\mathbb{E}X)^2]\u0060 | spread around the expectation |\n| Bayes rule | \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 | posterior proportional to likelihood times prior |\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n\n## Practical workflow\n\nStart from \u0060\\operatorname{Var}(X)=\\mathbb{E}[(X-\\mathbb{E}X)^2]\u0060 and write one sentence that says it means \u201Cspread around the expectation.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Failure checks\n\n- Dropping the condition after applying a conditional identity.\n- Confusing a probability mass with a probability density.\n- Using the same distribution name with incompatible parameter orders.\n\n## Accessibility and portability\n\nKeep the normal distribution notation source selectable and editable. For an isolated character in normal distribution notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of normal distribution notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in normal distribution notation has one defined meaning in the local context.\n- Reopen the exported file for **Normal Distribution Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "number-theory-common-errors",
    "title": "Number Theory: Common Errors and Verification",
    "description": "Common Errors and Verification for number theory: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Number Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Number Theory: Common Errors and Verification explains divisibility, congruences, primes, gcd, modular inverses, and proof notation.\n\n## Core notation for Number Theory: Common Errors and Verification\n\nIn number theory, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for number theory: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n\n## Errors that change the meaning\n\n- **Problem:** Switching index origins halfway through a recurrence. **Correction:** write the missing number theory: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Counting permutations when combinations are required. **Correction:** write the missing number theory: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using equality where modular congruence is intended. **Correction:** write the missing number theory: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the number theory: common errors and verification expression. Then check the number theory: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced number theory: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n\n## Accessibility and portability\n\nKeep the number theory: common errors and verification source selectable and editable. For an isolated character in number theory: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of number theory: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in number theory: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Number Theory: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "number-theory-latex-formatting",
    "title": "Number Theory: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for number theory: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Number Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Number Theory: LaTeX Formatting Guide explains divisibility, congruences, primes, gcd, modular inverses, and proof notation.\n\n## Core notation for Number Theory\n\nIn number theory, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for number theory; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n\n## LaTeX patterns that preserve the structure\n\nFor number theory: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\np(x)=\\sum_{k=0}^{n}a_kx^k\n\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\n(a_n)_{n\\ge0}\n\u0060\u0060\u0060\n\nFor number theory, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In number theory, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Renderer and export checks\n\nRender one demanding number theory example in the actual destination. For number theory, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the number theory source selectable and editable. For an isolated character in number theory, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of number theory is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in number theory has one defined meaning in the local context.\n- Reopen the exported file for **Number Theory: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "number-theory-notation-reference",
    "title": "Number Theory: Notation Reference",
    "description": "Notation Reference for number theory: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Number Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Number Theory: Notation Reference explains divisibility, congruences, primes, gcd, modular inverses, and proof notation.\n\n## Core notation for Number Theory\n\nIn number theory, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for number theory; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n| Graph | \u0060G=(V,E)\u0060 | vertices and edges |\n\n## How to read a complete expression\n\nRead \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 as \u201Cnumber of k-subsets of an n-set.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in number theory from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Cross-checks before reuse\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n\n## Accessibility and portability\n\nKeep the number theory source selectable and editable. For an isolated character in number theory, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of number theory is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in number theory has one defined meaning in the local context.\n- Reopen the exported file for **Number Theory: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "numerical-integration-guide",
    "title": "Numerical Integration Notation",
    "description": "Compare rectangle, trapezoidal, Simpson, adaptive, and quadrature notation while tracking nodes and weights.",
    "topic": "Numerical Methods",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Compare rectangle, trapezoidal, Simpson, adaptive, and quadrature notation while tracking nodes and weights.\n\n## Core notation for Numerical Integration Notation\n\nIn numerical methods, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for numerical integration notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n\n## Practical workflow\n\nStart from \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 and write one sentence that says it means \u201Clocal polynomial approximation with remainder.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Failure checks\n\n- Dropping an absolute value in a substitution jacobian.\n- Interchanging a limit, sum, derivative, or integral without conditions.\n- Omitting boundary terms after integration by parts.\n\n## Accessibility and portability\n\nKeep the numerical integration notation source selectable and editable. For an isolated character in numerical integration notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of numerical integration notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in numerical integration notation has one defined meaning in the local context.\n- Reopen the exported file for **Numerical Integration Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "numerical-integration-common-errors",
    "title": "Numerical Integration: Common Errors and Verification",
    "description": "Common Errors and Verification for numerical integration: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Numerical Integration",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Numerical Integration: Common Errors and Verification explains step size, composite rules, error estimates, and smoothness assumptions.\n\n## Core notation for Numerical Integration: Common Errors and Verification\n\nIn numerical integration, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for numerical integration: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n\n## Errors that change the meaning\n\n- **Problem:** Dropping an absolute value in a substitution jacobian. **Correction:** write the missing numerical integration: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Interchanging a limit, sum, derivative, or integral without conditions. **Correction:** write the missing numerical integration: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Omitting boundary terms after integration by parts. **Correction:** write the missing numerical integration: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the numerical integration: common errors and verification expression. Then check the numerical integration: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced numerical integration: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the numerical integration: common errors and verification source selectable and editable. For an isolated character in numerical integration: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of numerical integration: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in numerical integration: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Numerical Integration: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "numerical-integration-latex-formatting",
    "title": "Numerical Integration: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for numerical integration: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Numerical Integration",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Numerical Integration: LaTeX Formatting Guide explains step size, composite rules, error estimates, and smoothness assumptions.\n\n## Core notation for Numerical Integration\n\nIn numerical integration, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for numerical integration; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n\n## LaTeX patterns that preserve the structure\n\nFor numerical integration: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nf(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\n\\lim_{x\\to a}f(x)=L\nf\\\u0027(x)=\\frac{df}{dx}\n\u0060\u0060\u0060\n\nFor numerical integration, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In numerical integration, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Renderer and export checks\n\nRender one demanding numerical integration example in the actual destination. For numerical integration, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the numerical integration source selectable and editable. For an isolated character in numerical integration, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of numerical integration is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in numerical integration has one defined meaning in the local context.\n- Reopen the exported file for **Numerical Integration: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "numerical-integration-notation-reference",
    "title": "Numerical Integration: Notation Reference",
    "description": "Notation Reference for numerical integration: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Numerical Integration",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Numerical Integration: Notation Reference explains step size, composite rules, error estimates, and smoothness assumptions.\n\n## Core notation for Numerical Integration\n\nIn numerical integration, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for numerical integration; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n\n## How to read a complete expression\n\nRead \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 as \u201Clocal polynomial approximation with remainder.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in numerical integration from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Cross-checks before reuse\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the numerical integration source selectable and editable. For an isolated character in numerical integration, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of numerical integration is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in numerical integration has one defined meaning in the local context.\n- Reopen the exported file for **Numerical Integration: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "numerical-root-finding-common-errors",
    "title": "Numerical Root Finding: Common Errors and Verification",
    "description": "Common Errors and Verification for numerical root finding: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Numerical Root Finding",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Numerical Root Finding: Common Errors and Verification explains initial guesses, convergence tests, tolerances, and failure modes.\n\n## Core notation for Numerical Root Finding: Common Errors and Verification\n\nIn numerical root finding, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for numerical root finding: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n\n## Errors that change the meaning\n\n- **Problem:** Dropping an absolute value in a substitution jacobian. **Correction:** write the missing numerical root finding: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Interchanging a limit, sum, derivative, or integral without conditions. **Correction:** write the missing numerical root finding: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Omitting boundary terms after integration by parts. **Correction:** write the missing numerical root finding: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the numerical root finding: common errors and verification expression. Then check the numerical root finding: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced numerical root finding: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the numerical root finding: common errors and verification source selectable and editable. For an isolated character in numerical root finding: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of numerical root finding: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in numerical root finding: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Numerical Root Finding: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "numerical-root-finding-latex-formatting",
    "title": "Numerical Root Finding: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for numerical root finding: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Numerical Root Finding",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Numerical Root Finding: LaTeX Formatting Guide explains initial guesses, convergence tests, tolerances, and failure modes.\n\n## Core notation for Numerical Root Finding\n\nIn numerical root finding, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for numerical root finding; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n\n## LaTeX patterns that preserve the structure\n\nFor numerical root finding: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\nabla f\n\\int_a^b f(x)\\,dx\n\\nabla\\cdot F\n\u0060\u0060\u0060\n\nFor numerical root finding, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In numerical root finding, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Renderer and export checks\n\nRender one demanding numerical root finding example in the actual destination. For numerical root finding, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the numerical root finding source selectable and editable. For an isolated character in numerical root finding, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of numerical root finding is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in numerical root finding has one defined meaning in the local context.\n- Reopen the exported file for **Numerical Root Finding: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "numerical-root-finding-notation-reference",
    "title": "Numerical Root Finding: Notation Reference",
    "description": "Notation Reference for numerical root finding: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Numerical Root Finding",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Numerical Root Finding: Notation Reference explains initial guesses, convergence tests, tolerances, and failure modes.\n\n## Core notation for Numerical Root Finding\n\nIn numerical root finding, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for numerical root finding; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n\n## How to read a complete expression\n\nRead \u0060\\int_a^b f(x)\\,dx\u0060 as \u201Caccumulated quantity over an interval.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in numerical root finding from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Cross-checks before reuse\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the numerical root finding source selectable and editable. For an isolated character in numerical root finding, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of numerical root finding is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in numerical root finding has one defined meaning in the local context.\n- Reopen the exported file for **Numerical Root Finding: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "ode-solution-method-notation",
    "title": "ODE Solution Method Notation",
    "description": "Document state variables, derivatives, step sizes, stages, local error, and numerical approximations for ODE solvers.",
    "topic": "Differential Equations",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Document state variables, derivatives, step sizes, stages, local error, and numerical approximations for ODE solvers.\n\n## Core notation for ODE Solution Method Notation\n\nIn differential equations, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for ode solution method notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n\n## Practical workflow\n\nStart from \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 and write one sentence that says it means \u201Clocal polynomial approximation with remainder.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Failure checks\n\n- Dropping an absolute value in a substitution jacobian.\n- Interchanging a limit, sum, derivative, or integral without conditions.\n- Omitting boundary terms after integration by parts.\n\n## Accessibility and portability\n\nKeep the ode solution method notation source selectable and editable. For an isolated character in ode solution method notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of ode solution method notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in ode solution method notation has one defined meaning in the local context.\n- Reopen the exported file for **ODE Solution Method Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "topology-open-closed-sets",
    "title": "Open and Closed Set Notation",
    "description": "Distinguish open sets, closed sets, complements, neighborhoods, interiors, closures, and boundaries.",
    "topic": "Topology",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Distinguish open sets, closed sets, complements, neighborhoods, interiors, closures, and boundaries.\n\n## Core notation for Open and Closed Set Notation\n\nIn topology, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for open and closed set notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Continuity | \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 | topological continuity criterion |\n| Complex logarithm | \u0060\\Log z=\\ln|z|\u002Bi\\Arg z\u0060 | a selected logarithm branch |\n| Residue theorem | \u0060\\oint_\\gamma f(z)\\,dz=2\\pi i\\sum_k\\operatorname{Res}(f,z_k)\u0060 | contour integral from enclosed residues |\n| Open ball | \u0060B_r(x)=\\{y:d(x,y)\u003Cr\\}\u0060 | points within radius r of x |\n\n## Practical workflow\n\nStart from \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 and write one sentence that says it means \u201Ctopological continuity criterion.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the ambient space and topology.\n- Distinguish local from global properties.\n- Declare contour orientation and branch choices.\n\n## Failure checks\n\n- Using closed and bounded as a universal compactness criterion.\n- Crossing a branch cut without changing the selected argument.\n- Omitting hypotheses from a convergence or interchange theorem.\n\n## Accessibility and portability\n\nKeep the open and closed set notation source selectable and editable. For an isolated character in open and closed set notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of open and closed set notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in open and closed set notation has one defined meaning in the local context.\n- Reopen the exported file for **Open and Closed Set Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "optimization-constraints-kkt",
    "title": "Optimization Constraints and KKT Notation",
    "description": "Read primal feasibility, dual feasibility, stationarity, complementary slackness, and multiplier signs.",
    "topic": "Optimization",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Read primal feasibility, dual feasibility, stationarity, complementary slackness, and multiplier signs.\n\n## Core notation for Optimization Constraints and KKT Notation\n\nIn optimization, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for optimization constraints and kkt notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Optimization problem | \u0060\\min_x f(x)\\quad\\text{s.t.}\\quad g_i(x)\\le 0\u0060 | minimize an objective over a constrained feasible set |\n| Lagrangian | \u0060\\mathcal{L}(x,\\lambda)=f(x)\u002B\\sum_i\\lambda_i g_i(x)\u0060 | objective plus weighted constraints |\n| Stationarity | \u0060\\nabla_x\\mathcal{L}(x,\\lambda)=0\u0060 | first-order stationarity condition |\n| Complementarity | \u0060\\lambda_i g_i(x)=0\u0060 | active-constraint relationship |\n\n## Practical workflow\n\nStart from \u0060\\min_x f(x)\\quad\\text{s.t.}\\quad g_i(x)\\le 0\u0060 and write one sentence that says it means \u201Cminimize an objective over a constrained feasible set.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State minimization versus maximization and all constraint directions.\n- Separate an optimizer from the attained objective value.\n- Declare convexity and constraint-qualification assumptions.\n\n## Failure checks\n\n- Reversing a constraint sign without changing the multiplier convention.\n- Writing min when the result required is argmin.\n- Claiming kkt conditions are sufficient without convexity.\n\n## Accessibility and portability\n\nKeep the optimization constraints and kkt notation source selectable and editable. For an isolated character in optimization constraints and kkt notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of optimization constraints and kkt notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in optimization constraints and kkt notation has one defined meaning in the local context.\n- Reopen the exported file for **Optimization Constraints and KKT Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "duality-optimization-notation",
    "title": "Optimization Duality Notation",
    "description": "Distinguish primal variables, dual variables, bounds, gaps, and strong duality.",
    "topic": "Optimization",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Distinguish primal variables, dual variables, bounds, gaps, and strong duality.\n\n## Core notation for Optimization Duality Notation\n\nIn optimization, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for optimization duality notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Lagrangian | \u0060\\mathcal{L}(x,\\lambda)=f(x)\u002B\\sum_i\\lambda_i g_i(x)\u0060 | objective plus weighted constraints |\n| Stationarity | \u0060\\nabla_x\\mathcal{L}(x,\\lambda)=0\u0060 | first-order stationarity condition |\n| Complementarity | \u0060\\lambda_i g_i(x)=0\u0060 | active-constraint relationship |\n| Argmin | \u0060x^\\star\\in\\operatorname*{arg\\,min}_x f(x)\u0060 | a minimizer rather than the minimum value |\n\n## Practical workflow\n\nStart from \u0060\\mathcal{L}(x,\\lambda)=f(x)\u002B\\sum_i\\lambda_i g_i(x)\u0060 and write one sentence that says it means \u201Cobjective plus weighted constraints.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State minimization versus maximization and all constraint directions.\n- Separate an optimizer from the attained objective value.\n- Declare convexity and constraint-qualification assumptions.\n\n## Failure checks\n\n- Reversing a constraint sign without changing the multiplier convention.\n- Writing min when the result required is argmin.\n- Claiming kkt conditions are sufficient without convexity.\n\n## Accessibility and portability\n\nKeep the optimization duality notation source selectable and editable. For an isolated character in optimization duality notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of optimization duality notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in optimization duality notation has one defined meaning in the local context.\n- Reopen the exported file for **Optimization Duality Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "optimization-models-common-errors",
    "title": "Optimization Models: Common Errors and Verification",
    "description": "Common Errors and Verification for optimization models: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Optimization Models",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Optimization Models: Common Errors and Verification explains objectives, constraints, feasible sets, gradients, duality, and KKT conditions.\n\n## Core notation for Optimization Models: Common Errors and Verification\n\nIn optimization models, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for optimization models: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Lagrangian | \u0060\\mathcal{L}(x,\\lambda)=f(x)\u002B\\sum_i\\lambda_i g_i(x)\u0060 | objective plus weighted constraints |\n| Stationarity | \u0060\\nabla_x\\mathcal{L}(x,\\lambda)=0\u0060 | first-order stationarity condition |\n| Complementarity | \u0060\\lambda_i g_i(x)=0\u0060 | active-constraint relationship |\n| Argmin | \u0060x^\\star\\in\\operatorname*{arg\\,min}_x f(x)\u0060 | a minimizer rather than the minimum value |\n\n## Errors that change the meaning\n\n- **Problem:** Reversing a constraint sign without changing the multiplier convention. **Correction:** write the missing optimization models: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Writing min when the result required is argmin. **Correction:** write the missing optimization models: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Claiming kkt conditions are sufficient without convexity. **Correction:** write the missing optimization models: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the optimization models: common errors and verification expression. Then check the optimization models: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced optimization models: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n\n## Accessibility and portability\n\nKeep the optimization models: common errors and verification source selectable and editable. For an isolated character in optimization models: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of optimization models: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in optimization models: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Optimization Models: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "optimization-models-latex-formatting",
    "title": "Optimization Models: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for optimization models: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Optimization Models",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Optimization Models: LaTeX Formatting Guide explains objectives, constraints, feasible sets, gradients, duality, and KKT conditions.\n\n## Core notation for Optimization Models\n\nIn optimization models, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for optimization models; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Stationarity | \u0060\\nabla_x\\mathcal{L}(x,\\lambda)=0\u0060 | first-order stationarity condition |\n| Complementarity | \u0060\\lambda_i g_i(x)=0\u0060 | active-constraint relationship |\n| Argmin | \u0060x^\\star\\in\\operatorname*{arg\\,min}_x f(x)\u0060 | a minimizer rather than the minimum value |\n| Dual bound | \u0060d^\\star\\le p^\\star\u0060 | weak duality for a minimization primal |\n\n## LaTeX patterns that preserve the structure\n\nFor optimization models: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\nabla_x\\mathcal{L}(x,\\lambda)=0\n\\lambda_i g_i(x)=0\nx^\\star\\in\\operatorname*{arg\\,min}_x f(x)\n\u0060\u0060\u0060\n\nFor optimization models, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In optimization models, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State minimization versus maximization and all constraint directions.\n- Separate an optimizer from the attained objective value.\n- Declare convexity and constraint-qualification assumptions.\n\n## Renderer and export checks\n\nRender one demanding optimization models example in the actual destination. For optimization models, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the optimization models source selectable and editable. For an isolated character in optimization models, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of optimization models is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in optimization models has one defined meaning in the local context.\n- Reopen the exported file for **Optimization Models: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "optimization-models-notation-reference",
    "title": "Optimization Models: Notation Reference",
    "description": "Notation Reference for optimization models: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Optimization Models",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Optimization Models: Notation Reference explains objectives, constraints, feasible sets, gradients, duality, and KKT conditions.\n\n## Core notation for Optimization Models\n\nIn optimization models, the notation usually represents decision variables, objectives, constraints, feasible sets, multipliers, and optimality conditions. The table below gives a compact starting set for optimization models; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Argmin | \u0060x^\\star\\in\\operatorname*{arg\\,min}_x f(x)\u0060 | a minimizer rather than the minimum value |\n| Dual bound | \u0060d^\\star\\le p^\\star\u0060 | weak duality for a minimization primal |\n| Optimization problem | \u0060\\min_x f(x)\\quad\\text{s.t.}\\quad g_i(x)\\le 0\u0060 | minimize an objective over a constrained feasible set |\n| Lagrangian | \u0060\\mathcal{L}(x,\\lambda)=f(x)\u002B\\sum_i\\lambda_i g_i(x)\u0060 | objective plus weighted constraints |\n\n## How to read a complete expression\n\nRead \u0060x^\\star\\in\\operatorname*{arg\\,min}_x f(x)\u0060 as \u201Ca minimizer rather than the minimum value.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in optimization models from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State minimization versus maximization and all constraint directions.\n- Separate an optimizer from the attained objective value.\n- Declare convexity and constraint-qualification assumptions.\n\n## Cross-checks before reuse\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n\n## Accessibility and portability\n\nKeep the optimization models source selectable and editable. For an isolated character in optimization models, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of optimization models is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Evaluate feasibility before optimality.\n- Verify multiplier signs and complementary slackness.\n- Compare primal and dual objective values.\n- Confirm every symbol used in optimization models has one defined meaning in the local context.\n- Reopen the exported file for **Optimization Models: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "orthogonality-projection-guide",
    "title": "Orthogonality and Projection",
    "description": "Write inner products, orthogonal complements, projection matrices, and residuals.",
    "topic": "Linear Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Write inner products, orthogonal complements, projection matrices, and residuals.\n\n## Core notation for Orthogonality and Projection\n\nIn linear algebra, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for orthogonality and projection; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Transpose | \u0060A^{\\mathsf T}\u0060 | rows and columns exchanged |\n| Inverse | \u0060A^{-1}A=I\u0060 | inverse relation when A is nonsingular |\n| Eigenpair | \u0060Av=\\lambda v\u0060 | v is an eigenvector with eigenvalue \u03BB |\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n\n## Practical workflow\n\nStart from \u0060A^{\\mathsf T}\u0060 and write one sentence that says it means \u201Crows and columns exchanged.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Failure checks\n\n- Multiplying matrices whose inner dimensions do not agree.\n- Treating elementwise multiplication as matrix multiplication.\n- Assuming an inverse exists without checking rank or determinant.\n\n## Accessibility and portability\n\nKeep the orthogonality and projection source selectable and editable. For an isolated character in orthogonality and projection, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of orthogonality and projection is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in orthogonality and projection has one defined meaning in the local context.\n- Reopen the exported file for **Orthogonality and Projection** and compare it with the editable source.\n"
  },
  {
    "slug": "pde-boundary-condition-notation",
    "title": "PDE Boundary and Initial Condition Notation",
    "description": "Separate the differential equation from initial values, Dirichlet data, Neumann data, domains, and boundary operators.",
    "topic": "Differential Equations",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Separate the differential equation from initial values, Dirichlet data, Neumann data, domains, and boundary operators.\n\n## Core notation for PDE Boundary and Initial Condition Notation\n\nIn differential equations, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for pde boundary and initial condition notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n\n## Practical workflow\n\nStart from \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 and write one sentence that says it means \u201Cinstantaneous rate of change.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Failure checks\n\n- Dropping an absolute value in a substitution jacobian.\n- Interchanging a limit, sum, derivative, or integral without conditions.\n- Omitting boundary terms after integration by parts.\n\n## Accessibility and portability\n\nKeep the pde boundary and initial condition notation source selectable and editable. For an isolated character in pde boundary and initial condition notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of pde boundary and initial condition notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in pde boundary and initial condition notation has one defined meaning in the local context.\n- Reopen the exported file for **PDE Boundary and Initial Condition Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "permutations-combinations-probability",
    "title": "Permutations, Combinations, and Binomial Probability",
    "description": "Decide whether order matters, calculate selections or arrangements, and connect combinations to binomial probability.",
    "topic": "Probability",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Decide whether order matters, calculate selections or arrangements, and connect combinations to binomial probability.\n\n## Core notation for Permutations, Combinations, and Binomial Probability\n\nIn probability, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for permutations, combinations, and binomial probability; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Bayes rule | \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 | posterior proportional to likelihood times prior |\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n\n## Practical workflow\n\nStart from \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 and write one sentence that says it means \u201Cposterior proportional to likelihood times prior.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Failure checks\n\n- Dropping the condition after applying a conditional identity.\n- Confusing a probability mass with a probability density.\n- Using the same distribution name with incompatible parameter orders.\n\n## Accessibility and portability\n\nKeep the permutations, combinations, and binomial probability source selectable and editable. For an isolated character in permutations, combinations, and binomial probability, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of permutations, combinations, and binomial probability is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in permutations, combinations, and binomial probability has one defined meaning in the local context.\n- Reopen the exported file for **Permutations, Combinations, and Binomial Probability** and compare it with the editable source.\n"
  },
  {
    "slug": "pigeonhole-principle-notation",
    "title": "Pigeonhole Principle Notation",
    "description": "State finite counting assumptions and ceiling/floor bounds clearly.",
    "topic": "Discrete Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "State finite counting assumptions and ceiling/floor bounds clearly.\n\n## Core notation for Pigeonhole Principle Notation\n\nIn discrete mathematics, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for pigeonhole principle notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n\n## Practical workflow\n\nStart from \u0060a\\equiv b\\pmod m\u0060 and write one sentence that says it means \u201Ca and b have the same residue modulo m.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Failure checks\n\n- Switching index origins halfway through a recurrence.\n- Counting permutations when combinations are required.\n- Using equality where modular congruence is intended.\n\n## Accessibility and portability\n\nKeep the pigeonhole principle notation source selectable and editable. For an isolated character in pigeonhole principle notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of pigeonhole principle notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in pigeonhole principle notation has one defined meaning in the local context.\n- Reopen the exported file for **Pigeonhole Principle Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "poisson-process-notation",
    "title": "Poisson Process Notation",
    "description": "Relate counts, rates, waiting times, increments, and exponential distributions.",
    "topic": "Probability",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Relate counts, rates, waiting times, increments, and exponential distributions.\n\n## Core notation for Poisson Process Notation\n\nIn probability, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for poisson process notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Bayes rule | \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 | posterior proportional to likelihood times prior |\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n\n## Practical workflow\n\nStart from \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 and write one sentence that says it means \u201Cposterior proportional to likelihood times prior.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Failure checks\n\n- Dropping the condition after applying a conditional identity.\n- Confusing a probability mass with a probability density.\n- Using the same distribution name with incompatible parameter orders.\n\n## Accessibility and portability\n\nKeep the poisson process notation source selectable and editable. For an isolated character in poisson process notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of poisson process notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in poisson process notation has one defined meaning in the local context.\n- Reopen the exported file for **Poisson Process Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "polynomial-expansion-factorization",
    "title": "Polynomial Expansion, Evaluation, and Factorization",
    "description": "Work with polynomial coefficients, derivatives, antiderivatives, roots, and factored forms while preserving exact notation.",
    "topic": "Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Work with polynomial coefficients, derivatives, antiderivatives, roots, and factored forms while preserving exact notation.\n\n## Core notation for Polynomial Expansion, Evaluation, and Factorization\n\nIn algebra, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for polynomial expansion, evaluation, and factorization; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Graph | \u0060G=(V,E)\u0060 | vertices and edges |\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n\n## Practical workflow\n\nStart from \u0060G=(V,E)\u0060 and write one sentence that says it means \u201Cvertices and edges.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Failure checks\n\n- Switching index origins halfway through a recurrence.\n- Counting permutations when combinations are required.\n- Using equality where modular congruence is intended.\n\n## Accessibility and portability\n\nKeep the polynomial expansion, evaluation, and factorization source selectable and editable. For an isolated character in polynomial expansion, evaluation, and factorization, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of polynomial expansion, evaluation, and factorization is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in polynomial expansion, evaluation, and factorization has one defined meaning in the local context.\n- Reopen the exported file for **Polynomial Expansion, Evaluation, and Factorization** and compare it with the editable source.\n"
  },
  {
    "slug": "polynomial-roots-common-errors",
    "title": "Polynomial Roots: Common Errors and Verification",
    "description": "Common Errors and Verification for polynomial roots: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Polynomial Roots",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Polynomial Roots: Common Errors and Verification explains multiplicity, factorization, complex roots, coefficients, and numerical verification.\n\n## Core notation for Polynomial Roots: Common Errors and Verification\n\nIn polynomial roots, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for polynomial roots: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Graph | \u0060G=(V,E)\u0060 | vertices and edges |\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n\n## Errors that change the meaning\n\n- **Problem:** Switching index origins halfway through a recurrence. **Correction:** write the missing polynomial roots: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Counting permutations when combinations are required. **Correction:** write the missing polynomial roots: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using equality where modular congruence is intended. **Correction:** write the missing polynomial roots: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the polynomial roots: common errors and verification expression. Then check the polynomial roots: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced polynomial roots: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n\n## Accessibility and portability\n\nKeep the polynomial roots: common errors and verification source selectable and editable. For an isolated character in polynomial roots: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of polynomial roots: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in polynomial roots: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Polynomial Roots: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "polynomial-roots-latex-formatting",
    "title": "Polynomial Roots: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for polynomial roots: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Polynomial Roots",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Polynomial Roots: LaTeX Formatting Guide explains multiplicity, factorization, complex roots, coefficients, and numerical verification.\n\n## Core notation for Polynomial Roots\n\nIn polynomial roots, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for polynomial roots; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n| Graph | \u0060G=(V,E)\u0060 | vertices and edges |\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n\n## LaTeX patterns that preserve the structure\n\nFor polynomial roots: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\na_n=a_{n-1}\u002Ba_{n-2}\nG=(V,E)\na\\equiv b\\pmod m\n\u0060\u0060\u0060\n\nFor polynomial roots, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In polynomial roots, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Renderer and export checks\n\nRender one demanding polynomial roots example in the actual destination. For polynomial roots, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the polynomial roots source selectable and editable. For an isolated character in polynomial roots, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of polynomial roots is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in polynomial roots has one defined meaning in the local context.\n- Reopen the exported file for **Polynomial Roots: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "polynomial-roots-notation-reference",
    "title": "Polynomial Roots: Notation Reference",
    "description": "Notation Reference for polynomial roots: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Polynomial Roots",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Polynomial Roots: Notation Reference explains multiplicity, factorization, complex roots, coefficients, and numerical verification.\n\n## Core notation for Polynomial Roots\n\nIn polynomial roots, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for polynomial roots; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n| Graph | \u0060G=(V,E)\u0060 | vertices and edges |\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n\n## How to read a complete expression\n\nRead \u0060(a_n)_{n\\ge0}\u0060 as \u201Cindexed family of terms.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in polynomial roots from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Cross-checks before reuse\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n\n## Accessibility and portability\n\nKeep the polynomial roots source selectable and editable. For an isolated character in polynomial roots, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of polynomial roots is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in polynomial roots has one defined meaning in the local context.\n- Reopen the exported file for **Polynomial Roots: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "positive-definite-matrix-notation",
    "title": "Positive-Definite Matrix Notation",
    "description": "Compare positive definite, semidefinite, symmetric, and Hermitian conditions.",
    "topic": "Linear Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Compare positive definite, semidefinite, symmetric, and Hermitian conditions.\n\n## Core notation for Positive-Definite Matrix Notation\n\nIn linear algebra, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for positive-definite matrix notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Eigenpair | \u0060Av=\\lambda v\u0060 | v is an eigenvector with eigenvalue \u03BB |\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n| Norm | \u0060\\lVert x\\rVert_2\u0060 | Euclidean length of vector x |\n| Matrix product | \u0060C=AB\u0060 | composition with inner dimensions matched |\n\n## Practical workflow\n\nStart from \u0060Av=\\lambda v\u0060 and write one sentence that says it means \u201Cv is an eigenvector with eigenvalue \u03BB.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Failure checks\n\n- Multiplying matrices whose inner dimensions do not agree.\n- Treating elementwise multiplication as matrix multiplication.\n- Assuming an inverse exists without checking rank or determinant.\n\n## Accessibility and portability\n\nKeep the positive-definite matrix notation source selectable and editable. For an isolated character in positive-definite matrix notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of positive-definite matrix notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in positive-definite matrix notation has one defined meaning in the local context.\n- Reopen the exported file for **Positive-Definite Matrix Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "pca-notation-guide",
    "title": "Principal Component Analysis Notation",
    "description": "Track centered data, covariance matrices, eigenvectors, scores, and explained variance.",
    "topic": "Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Track centered data, covariance matrices, eigenvectors, scores, and explained variance.\n\n## Core notation for Principal Component Analysis Notation\n\nIn statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for principal component analysis notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n| Correlation | \u0060r=\\frac{\\operatorname{cov}(X,Y)}{s_Xs_Y}\u0060 | standardized linear association |\n| Observation | \u0060x_i\u0060 | the i-th measured or observed value |\n| Sample mean | \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 | the arithmetic mean of n observations |\n\n## Practical workflow\n\nStart from \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 and write one sentence that says it means \u201Can estimate with a stated confidence procedure.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Failure checks\n\n- Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate.\n- Reporting a standard deviation as though it were a standard error.\n- Rounding intermediate values so aggressively that the final result changes.\n\n## Accessibility and portability\n\nKeep the principal component analysis notation source selectable and editable. For an isolated character in principal component analysis notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of principal component analysis notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in principal component analysis notation has one defined meaning in the local context.\n- Reopen the exported file for **Principal Component Analysis Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "bayesian-prior-likelihood-posterior",
    "title": "Prior, Likelihood, and Posterior",
    "description": "Keep probability statements, proportionality, evidence, and conditioning explicit.",
    "topic": "Probability",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Keep probability statements, proportionality, evidence, and conditioning explicit.\n\n## Core notation for Prior, Likelihood, and Posterior\n\nIn probability, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for prior, likelihood, and posterior; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n| Expectation | \u0060\\mathbb{E}[X]\u0060 | mean of a random variable under its distribution |\n| Variance | \u0060\\operatorname{Var}(X)=\\mathbb{E}[(X-\\mathbb{E}X)^2]\u0060 | spread around the expectation |\n\n## Practical workflow\n\nStart from \u0060P(A)\u0060 and write one sentence that says it means \u201Cprobability assigned to event A.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Failure checks\n\n- Dropping the condition after applying a conditional identity.\n- Confusing a probability mass with a probability density.\n- Using the same distribution name with incompatible parameter orders.\n\n## Accessibility and portability\n\nKeep the prior, likelihood, and posterior source selectable and editable. For an isolated character in prior, likelihood, and posterior, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of prior, likelihood, and posterior is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in prior, likelihood, and posterior has one defined meaning in the local context.\n- Reopen the exported file for **Prior, Likelihood, and Posterior** and compare it with the editable source.\n"
  },
  {
    "slug": "probability-distribution-notation",
    "title": "Probability Distribution Notation",
    "description": "Read and write random variables, probability mass functions, density functions, parameters, and expectation notation.",
    "topic": "Probability",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Read and write random variables, probability mass functions, density functions, parameters, and expectation notation.\n\n## Core notation for Probability Distribution Notation\n\nIn probability, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for probability distribution notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n| Expectation | \u0060\\mathbb{E}[X]\u0060 | mean of a random variable under its distribution |\n\n## Practical workflow\n\nStart from \u0060X\\perp Y\u0060 and write one sentence that says it means \u201CX and Y are independent under the stated model.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Failure checks\n\n- Dropping the condition after applying a conditional identity.\n- Confusing a probability mass with a probability density.\n- Using the same distribution name with incompatible parameter orders.\n\n## Accessibility and portability\n\nKeep the probability distribution notation source selectable and editable. For an isolated character in probability distribution notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of probability distribution notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in probability distribution notation has one defined meaning in the local context.\n- Reopen the exported file for **Probability Distribution Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "probability-rules-common-errors",
    "title": "Probability Rules: Common Errors and Verification",
    "description": "Common Errors and Verification for probability rules: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Probability Rules",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Probability Rules: Common Errors and Verification explains events, complements, conditional probability, independence, and partitions.\n\n## Core notation for Probability Rules: Common Errors and Verification\n\nIn probability rules, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for probability rules: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Bayes rule | \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 | posterior proportional to likelihood times prior |\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n\n## Errors that change the meaning\n\n- **Problem:** Dropping the condition after applying a conditional identity. **Correction:** write the missing probability rules: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Confusing a probability mass with a probability density. **Correction:** write the missing probability rules: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using the same distribution name with incompatible parameter orders. **Correction:** write the missing probability rules: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the probability rules: common errors and verification expression. Then check the probability rules: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced probability rules: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n\n## Accessibility and portability\n\nKeep the probability rules: common errors and verification source selectable and editable. For an isolated character in probability rules: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of probability rules: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in probability rules: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Probability Rules: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "probability-rules-latex-formatting",
    "title": "Probability Rules: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for probability rules: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Probability Rules",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Probability Rules: LaTeX Formatting Guide explains events, complements, conditional probability, independence, and partitions.\n\n## Core notation for Probability Rules\n\nIn probability rules, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for probability rules; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Bayes rule | \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 | posterior proportional to likelihood times prior |\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n\n## LaTeX patterns that preserve the structure\n\nFor probability rules: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nP(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\nX\\perp Y\nP(A)\n\u0060\u0060\u0060\n\nFor probability rules, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In probability rules, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Renderer and export checks\n\nRender one demanding probability rules example in the actual destination. For probability rules, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the probability rules source selectable and editable. For an isolated character in probability rules, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of probability rules is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in probability rules has one defined meaning in the local context.\n- Reopen the exported file for **Probability Rules: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "probability-rules-notation-reference",
    "title": "Probability Rules: Notation Reference",
    "description": "Notation Reference for probability rules: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Probability Rules",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Probability Rules: Notation Reference explains events, complements, conditional probability, independence, and partitions.\n\n## Core notation for Probability Rules\n\nIn probability rules, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for probability rules; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n| Expectation | \u0060\\mathbb{E}[X]\u0060 | mean of a random variable under its distribution |\n\n## How to read a complete expression\n\nRead \u0060X\\perp Y\u0060 as \u201CX and Y are independent under the stated model.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in probability rules from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Cross-checks before reuse\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n\n## Accessibility and portability\n\nKeep the probability rules source selectable and editable. For an isolated character in probability rules, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of probability rules is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in probability rules has one defined meaning in the local context.\n- Reopen the exported file for **Probability Rules: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "quantum-notation-common-errors",
    "title": "Quantum Notation: Common Errors and Verification",
    "description": "Common Errors and Verification for quantum notation: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Quantum Notation",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Quantum Notation: Common Errors and Verification explains states, bras, kets, operators, inner products, and measurement probabilities.\n\n## Core notation for Quantum Notation: Common Errors and Verification\n\nIn quantum notation, the notation usually represents states, bras, kets, operators, observables, amplitudes, and Hilbert-space conventions. The table below gives a compact starting set for quantum notation: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Normalization | \u0060\\langle\\psi\\mid\\psi\\rangle=1\u0060 | unit norm state |\n| State | \u0060\\lvert\\psi\\rangle\u0060 | ket representing a quantum state |\n| Dual state | \u0060\\langle\\psi\\rvert\u0060 | bra dual to the ket |\n| Inner product | \u0060\\langle\\phi\\mid\\psi\\rangle\u0060 | complex amplitude between states |\n\n## Errors that change the meaning\n\n- **Problem:** Reversing bra and ket order in a complex inner product. **Correction:** write the missing quantum notation: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Treating noncommuting operators as ordinary scalars. **Correction:** write the missing quantum notation: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Omitting normalization before interpreting probabilities. **Correction:** write the missing quantum notation: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the quantum notation: common errors and verification expression. Then check the quantum notation: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced quantum notation: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Verify state normalization.\n- Check operator hermiticity when representing an observable.\n- Test the expression in a finite-dimensional basis.\n\n## Accessibility and portability\n\nKeep the quantum notation: common errors and verification source selectable and editable. For an isolated character in quantum notation: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of quantum notation: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify state normalization.\n- Check operator hermiticity when representing an observable.\n- Test the expression in a finite-dimensional basis.\n- Confirm every symbol used in quantum notation: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Quantum Notation: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "quantum-notation-latex-formatting",
    "title": "Quantum Notation: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for quantum notation: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Quantum Notation",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Quantum Notation: LaTeX Formatting Guide explains states, bras, kets, operators, inner products, and measurement probabilities.\n\n## Core notation for Quantum Notation\n\nIn quantum notation, the notation usually represents states, bras, kets, operators, observables, amplitudes, and Hilbert-space conventions. The table below gives a compact starting set for quantum notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Inner product | \u0060\\langle\\phi\\mid\\psi\\rangle\u0060 | complex amplitude between states |\n| Expectation | \u0060\\langle A\\rangle=\\langle\\psi\\rvert\\hat A\\lvert\\psi\\rangle\u0060 | expected value of observable A |\n| Commutator | \u0060[\\hat A,\\hat B]=\\hat A\\hat B-\\hat B\\hat A\u0060 | operator noncommutativity |\n| Normalization | \u0060\\langle\\psi\\mid\\psi\\rangle=1\u0060 | unit norm state |\n\n## LaTeX patterns that preserve the structure\n\nFor quantum notation: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\langle\\phi\\mid\\psi\\rangle\n\\langle A\\rangle=\\langle\\psi\\rvert\\hat A\\lvert\\psi\\rangle\n[\\hat A,\\hat B]=\\hat A\\hat B-\\hat B\\hat A\n\u0060\u0060\u0060\n\nFor quantum notation, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In quantum notation, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Distinguish operators from scalar eigenvalues typographically.\n- State normalization and basis conventions.\n- Keep complex conjugation and adjoints explicit.\n\n## Renderer and export checks\n\nRender one demanding quantum notation example in the actual destination. For quantum notation, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the quantum notation source selectable and editable. For an isolated character in quantum notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of quantum notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify state normalization.\n- Check operator hermiticity when representing an observable.\n- Test the expression in a finite-dimensional basis.\n- Confirm every symbol used in quantum notation has one defined meaning in the local context.\n- Reopen the exported file for **Quantum Notation: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "quantum-notation-notation-reference",
    "title": "Quantum Notation: Notation Reference",
    "description": "Notation Reference for quantum notation: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Quantum Notation",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Quantum Notation: Notation Reference explains states, bras, kets, operators, inner products, and measurement probabilities.\n\n## Core notation for Quantum Notation\n\nIn quantum notation, the notation usually represents states, bras, kets, operators, observables, amplitudes, and Hilbert-space conventions. The table below gives a compact starting set for quantum notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Dual state | \u0060\\langle\\psi\\rvert\u0060 | bra dual to the ket |\n| Inner product | \u0060\\langle\\phi\\mid\\psi\\rangle\u0060 | complex amplitude between states |\n| Expectation | \u0060\\langle A\\rangle=\\langle\\psi\\rvert\\hat A\\lvert\\psi\\rangle\u0060 | expected value of observable A |\n| Commutator | \u0060[\\hat A,\\hat B]=\\hat A\\hat B-\\hat B\\hat A\u0060 | operator noncommutativity |\n\n## How to read a complete expression\n\nRead \u0060\\langle\\psi\\rvert\u0060 as \u201Cbra dual to the ket.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in quantum notation from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- Distinguish operators from scalar eigenvalues typographically.\n- State normalization and basis conventions.\n- Keep complex conjugation and adjoints explicit.\n\n## Cross-checks before reuse\n\n- Verify state normalization.\n- Check operator hermiticity when representing an observable.\n- Test the expression in a finite-dimensional basis.\n\n## Accessibility and portability\n\nKeep the quantum notation source selectable and editable. For an isolated character in quantum notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of quantum notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify state normalization.\n- Check operator hermiticity when representing an observable.\n- Test the expression in a finite-dimensional basis.\n- Confirm every symbol used in quantum notation has one defined meaning in the local context.\n- Reopen the exported file for **Quantum Notation: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "quantum-operators-observables",
    "title": "Quantum Operators and Observables",
    "description": "Format Hermitian operators, eigenvalue equations, commutators, and expectation values.",
    "topic": "Quantum Mechanics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Format Hermitian operators, eigenvalue equations, commutators, and expectation values.\n\n## Core notation for Quantum Operators and Observables\n\nIn quantum mechanics, the notation usually represents states, bras, kets, operators, observables, amplitudes, and Hilbert-space conventions. The table below gives a compact starting set for quantum operators and observables; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Normalization | \u0060\\langle\\psi\\mid\\psi\\rangle=1\u0060 | unit norm state |\n| State | \u0060\\lvert\\psi\\rangle\u0060 | ket representing a quantum state |\n| Dual state | \u0060\\langle\\psi\\rvert\u0060 | bra dual to the ket |\n| Inner product | \u0060\\langle\\phi\\mid\\psi\\rangle\u0060 | complex amplitude between states |\n\n## Practical workflow\n\nStart from \u0060\\langle\\psi\\mid\\psi\\rangle=1\u0060 and write one sentence that says it means \u201Cunit norm state.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish operators from scalar eigenvalues typographically.\n- State normalization and basis conventions.\n- Keep complex conjugation and adjoints explicit.\n\n## Failure checks\n\n- Reversing bra and ket order in a complex inner product.\n- Treating noncommuting operators as ordinary scalars.\n- Omitting normalization before interpreting probabilities.\n\n## Accessibility and portability\n\nKeep the quantum operators and observables source selectable and editable. For an isolated character in quantum operators and observables, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of quantum operators and observables is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify state normalization.\n- Check operator hermiticity when representing an observable.\n- Test the expression in a finite-dimensional basis.\n- Confirm every symbol used in quantum operators and observables has one defined meaning in the local context.\n- Reopen the exported file for **Quantum Operators and Observables** and compare it with the editable source.\n"
  },
  {
    "slug": "quantum-state-normalization",
    "title": "Quantum State Normalization",
    "description": "Check normalization, probabilities, amplitudes, global phases, and basis expansions.",
    "topic": "Quantum Mechanics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Check normalization, probabilities, amplitudes, global phases, and basis expansions.\n\n## Core notation for Quantum State Normalization\n\nIn quantum mechanics, the notation usually represents states, bras, kets, operators, observables, amplitudes, and Hilbert-space conventions. The table below gives a compact starting set for quantum state normalization; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Commutator | \u0060[\\hat A,\\hat B]=\\hat A\\hat B-\\hat B\\hat A\u0060 | operator noncommutativity |\n| Normalization | \u0060\\langle\\psi\\mid\\psi\\rangle=1\u0060 | unit norm state |\n| State | \u0060\\lvert\\psi\\rangle\u0060 | ket representing a quantum state |\n| Dual state | \u0060\\langle\\psi\\rvert\u0060 | bra dual to the ket |\n\n## Practical workflow\n\nStart from \u0060[\\hat A,\\hat B]=\\hat A\\hat B-\\hat B\\hat A\u0060 and write one sentence that says it means \u201Coperator noncommutativity.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish operators from scalar eigenvalues typographically.\n- State normalization and basis conventions.\n- Keep complex conjugation and adjoints explicit.\n\n## Failure checks\n\n- Reversing bra and ket order in a complex inner product.\n- Treating noncommuting operators as ordinary scalars.\n- Omitting normalization before interpreting probabilities.\n\n## Accessibility and portability\n\nKeep the quantum state normalization source selectable and editable. For an isolated character in quantum state normalization, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of quantum state normalization is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify state normalization.\n- Check operator hermiticity when representing an observable.\n- Test the expression in a finite-dimensional basis.\n- Confirm every symbol used in quantum state normalization has one defined meaning in the local context.\n- Reopen the exported file for **Quantum State Normalization** and compare it with the editable source.\n"
  },
  {
    "slug": "random-variables-common-errors",
    "title": "Random Variables: Common Errors and Verification",
    "description": "Common Errors and Verification for random variables: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Random Variables",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Random Variables: Common Errors and Verification explains support, mass and density functions, expectation, variance, and transforms.\n\n## Core notation for Random Variables: Common Errors and Verification\n\nIn random variables, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for random variables: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Variance | \u0060\\operatorname{Var}(X)=\\mathbb{E}[(X-\\mathbb{E}X)^2]\u0060 | spread around the expectation |\n| Bayes rule | \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 | posterior proportional to likelihood times prior |\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n\n## Errors that change the meaning\n\n- **Problem:** Dropping the condition after applying a conditional identity. **Correction:** write the missing random variables: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Confusing a probability mass with a probability density. **Correction:** write the missing random variables: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using the same distribution name with incompatible parameter orders. **Correction:** write the missing random variables: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the random variables: common errors and verification expression. Then check the random variables: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced random variables: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n\n## Accessibility and portability\n\nKeep the random variables: common errors and verification source selectable and editable. For an isolated character in random variables: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of random variables: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in random variables: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Random Variables: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "random-variables-latex-formatting",
    "title": "Random Variables: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for random variables: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Random Variables",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Random Variables: LaTeX Formatting Guide explains support, mass and density functions, expectation, variance, and transforms.\n\n## Core notation for Random Variables\n\nIn random variables, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for random variables; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Variance | \u0060\\operatorname{Var}(X)=\\mathbb{E}[(X-\\mathbb{E}X)^2]\u0060 | spread around the expectation |\n| Bayes rule | \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 | posterior proportional to likelihood times prior |\n| Independence | \u0060X\\perp Y\u0060 | X and Y are independent under the stated model |\n| Event probability | \u0060P(A)\u0060 | probability assigned to event A |\n\n## LaTeX patterns that preserve the structure\n\nFor random variables: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\operatorname{Var}(X)=\\mathbb{E}[(X-\\mathbb{E}X)^2]\nP(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\nX\\perp Y\n\u0060\u0060\u0060\n\nFor random variables, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In random variables, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Renderer and export checks\n\nRender one demanding random variables example in the actual destination. For random variables, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the random variables source selectable and editable. For an isolated character in random variables, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of random variables is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in random variables has one defined meaning in the local context.\n- Reopen the exported file for **Random Variables: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "random-variables-notation-reference",
    "title": "Random Variables: Notation Reference",
    "description": "Notation Reference for random variables: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Random Variables",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Random Variables: Notation Reference explains support, mass and density functions, expectation, variance, and transforms.\n\n## Core notation for Random Variables\n\nIn random variables, the notation usually represents events, random variables, probability measures, parameters, and conditioning information. The table below gives a compact starting set for random variables; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Conditional probability | \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 | probability of A given B when P(B)\u003E0 |\n| Expectation | \u0060\\mathbb{E}[X]\u0060 | mean of a random variable under its distribution |\n| Variance | \u0060\\operatorname{Var}(X)=\\mathbb{E}[(X-\\mathbb{E}X)^2]\u0060 | spread around the expectation |\n| Bayes rule | \u0060P(\\theta\\mid x)\\propto P(x\\mid\\theta)P(\\theta)\u0060 | posterior proportional to likelihood times prior |\n\n## How to read a complete expression\n\nRead \u0060P(A\\mid B)=\\frac{P(A\\cap B)}{P(B)}\u0060 as \u201Cprobability of A given B when P(B)\u003E0.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in random variables from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State whether variables are discrete or continuous.\n- Write the conditioning event or sigma-algebra explicitly.\n- Name the parameterization of every distribution.\n\n## Cross-checks before reuse\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n\n## Accessibility and portability\n\nKeep the random variables source selectable and editable. For an isolated character in random variables, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of random variables is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify probabilities are nonnegative and normalize to one.\n- Test an extreme or degenerate case.\n- Confirm support and parameter constraints before substitution.\n- Confirm every symbol used in random variables has one defined meaning in the local context.\n- Reopen the exported file for **Random Variables: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "rational-functions-common-errors",
    "title": "Rational Functions: Common Errors and Verification",
    "description": "Common Errors and Verification for rational functions: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Rational Functions",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Rational Functions: Common Errors and Verification explains domains, poles, asymptotes, cancellation, and graph interpretation.\n\n## Core notation for Rational Functions: Common Errors and Verification\n\nIn rational functions, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for rational functions: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## Errors that change the meaning\n\n- **Problem:** Copying a rendered image when editable notation is required. **Correction:** write the missing rational functions: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using a look-alike unicode character with different semantics. **Correction:** write the missing rational functions: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Defining macros that hide arguments or conflict with package commands. **Correction:** write the missing rational functions: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the rational functions: common errors and verification expression. Then check the rational functions: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced rational functions: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the rational functions: common errors and verification example.\n\n## Accessibility and portability\n\nKeep the rational functions: common errors and verification source selectable and editable. For an isolated character in rational functions: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of rational functions: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the rational functions: common errors and verification example.\n- Confirm every symbol used in rational functions: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Rational Functions: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "rational-functions-latex-formatting",
    "title": "Rational Functions: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for rational functions: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Rational Functions",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Rational Functions: LaTeX Formatting Guide explains domains, poles, asymptotes, cancellation, and graph interpretation.\n\n## Core notation for Rational Functions\n\nIn rational functions, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for rational functions; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n\n## LaTeX patterns that preserve the structure\n\nFor rational functions: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\texttt{U\u002B2212}\n\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\n\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\n\u0060\u0060\u0060\n\nFor rational functions, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In rational functions, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Keep editable source with the rendered result.\n- Use semantic commands for rational functions rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the rational functions notation.\n\n## Renderer and export checks\n\nRender one demanding rational functions example in the actual destination. For rational functions, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the rational functions source selectable and editable. For an isolated character in rational functions, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of rational functions is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the rational functions example.\n- Confirm every symbol used in rational functions has one defined meaning in the local context.\n- Reopen the exported file for **Rational Functions: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "rational-functions-notation-reference",
    "title": "Rational Functions: Notation Reference",
    "description": "Notation Reference for rational functions: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Rational Functions",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Rational Functions: Notation Reference explains domains, poles, asymptotes, cancellation, and graph interpretation.\n\n## Core notation for Rational Functions\n\nIn rational functions, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for rational functions; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n\n## How to read a complete expression\n\nRead \u0060\\texttt{U\u002B2212}\u0060 as \u201Cidentifier for the mathematical minus sign.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in rational functions from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- Keep editable source with the rendered result.\n- Use semantic commands for rational functions rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the rational functions notation.\n\n## Cross-checks before reuse\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the rational functions example.\n\n## Accessibility and portability\n\nKeep the rational functions source selectable and editable. For an isolated character in rational functions, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of rational functions is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the rational functions example.\n- Confirm every symbol used in rational functions has one defined meaning in the local context.\n- Reopen the exported file for **Rational Functions: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "recurrence-relation-notation",
    "title": "Recurrence Relation Notation",
    "description": "Define initial conditions, indexes, characteristic equations, and asymptotic solutions.",
    "topic": "Discrete Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Define initial conditions, indexes, characteristic equations, and asymptotic solutions.\n\n## Core notation for Recurrence Relation Notation\n\nIn discrete mathematics, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for recurrence relation notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n| Graph | \u0060G=(V,E)\u0060 | vertices and edges |\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n\n## Practical workflow\n\nStart from \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 and write one sentence that says it means \u201Cterm defined from earlier terms.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Failure checks\n\n- Switching index origins halfway through a recurrence.\n- Counting permutations when combinations are required.\n- Using equality where modular congruence is intended.\n\n## Accessibility and portability\n\nKeep the recurrence relation notation source selectable and editable. For an isolated character in recurrence relation notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of recurrence relation notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in recurrence relation notation has one defined meaning in the local context.\n- Reopen the exported file for **Recurrence Relation Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "residue-theorem-notation",
    "title": "Residue Theorem Notation",
    "description": "Format contours, poles, residues, orientations, and enclosed singularities.",
    "topic": "Complex Analysis",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Format contours, poles, residues, orientations, and enclosed singularities.\n\n## Core notation for Residue Theorem Notation\n\nIn complex analysis, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for residue theorem notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Continuity | \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 | topological continuity criterion |\n| Complex logarithm | \u0060\\Log z=\\ln|z|\u002Bi\\Arg z\u0060 | a selected logarithm branch |\n| Residue theorem | \u0060\\oint_\\gamma f(z)\\,dz=2\\pi i\\sum_k\\operatorname{Res}(f,z_k)\u0060 | contour integral from enclosed residues |\n| Open ball | \u0060B_r(x)=\\{y:d(x,y)\u003Cr\\}\u0060 | points within radius r of x |\n\n## Practical workflow\n\nStart from \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 and write one sentence that says it means \u201Ctopological continuity criterion.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State the ambient space and topology.\n- Distinguish local from global properties.\n- Declare contour orientation and branch choices.\n\n## Failure checks\n\n- Using closed and bounded as a universal compactness criterion.\n- Crossing a branch cut without changing the selected argument.\n- Omitting hypotheses from a convergence or interchange theorem.\n\n## Accessibility and portability\n\nKeep the residue theorem notation source selectable and editable. For an isolated character in residue theorem notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of residue theorem notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in residue theorem notation has one defined meaning in the local context.\n- Reopen the exported file for **Residue Theorem Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "si-unit-typesetting",
    "title": "SI Unit Typesetting",
    "description": "Format values, spaces, prefixes, derived units, exponents, and uncertainty.",
    "topic": "Scientific Writing",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Format values, spaces, prefixes, derived units, exponents, and uncertainty.\n\n## Core notation for SI Unit Typesetting\n\nIn scientific writing, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for si unit typesetting; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## Practical workflow\n\nStart from \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 and write one sentence that says it means \u201Csemantic operator element.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for si unit typesetting rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the si unit typesetting notation.\n\n## Failure checks\n\n- Copying a rendered si unit typesetting image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in si unit typesetting.\n- Defining si unit typesetting macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the si unit typesetting source selectable and editable. For an isolated character in si unit typesetting, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of si unit typesetting is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the si unit typesetting example.\n- Confirm every symbol used in si unit typesetting has one defined meaning in the local context.\n- Reopen the exported file for **SI Unit Typesetting** and compare it with the editable source.\n"
  },
  {
    "slug": "scientific-unit-formatting-guide",
    "title": "Scientific Unit Formatting Guide",
    "description": "Format SI units, prefixes, spacing, exponents, temperature, and compound units consistently in reports, websites, and equations.",
    "topic": "Scientific writing",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Format SI units, prefixes, spacing, exponents, temperature, and compound units consistently in reports, websites, and equations. This guide focuses on reliable, editable output rather than visual shortcuts. The exact menu names can vary by application version, but the underlying choice remains the same: use Unicode for isolated characters and structured math for complete expressions.\n\n## Choose the right representation\n\nMathematical notation can be stored as ordinary Unicode text, structured equation markup, or an image. Unicode is convenient for isolated symbols and short labels. LaTeX and MathML preserve structure for fractions, matrices, scripts, and aligned equations. Images should be a last resort because they are harder to edit, search, resize, and make accessible.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Create the notation\n\nStart in the native equation editor when the destination application provides one. Native editors understand mathematical grouping, spacing, and baseline alignment better than manual character placement. When importing text, separate semantic content from presentation: identify operators, variables, units, subscripts, and conditions before deciding how they should look.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Check meaning and ambiguity\n\nThe same visible character can carry several meanings across algebra, statistics, physics, and chemistry. Define uncommon notation and review nearby variables before converting formats. Plain Unicode cannot always distinguish multiplication from a dot product, a hyphen from a minus sign, or a decorative letter from a mathematical constant.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Preserve accessibility\n\nUse real text or structured math whenever possible. Provide a concise spoken description for an image and include the surrounding purpose of the equation rather than reading every punctuation mark mechanically. Keyboard focus, selectable text, sufficient contrast, and responsive layout are also part of accessible mathematical communication.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Test the final output\n\nCopy the result into the actual destination, save and reopen the file, then inspect desktop, mobile, print, and exported PDF views. Confirm that fonts contain every symbol, line breaks do not split expressions incorrectly, and superscripts remain attached to the intended base. For web pages, test without JavaScript and with browser zoom.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Use a repeatable workflow\n\nKeep the source notation in a plain, version-controlled format when possible. Record the LaTeX command, Unicode code point, and intended meaning for symbols that appear frequently. A repeatable workflow reduces silent substitutions and makes later updates easier when the content moves between Word, HTML, Markdown, presentation software, and publishing systems.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Final checklist\n\n1. Confirm the mathematical meaning in context.\n2. Prefer native equation markup for structured expressions.\n3. Verify Unicode and LaTeX independently.\n4. Test copying, exporting, zooming, and screen-reader output.\n5. Keep an editable source version for future correction.\n"
  },
  {
    "slug": "mathml-scripts-limits",
    "title": "Scripts and Limits in MathML",
    "description": "Choose subscript, superscript, combined script, under, over, and limit structures that match mathematical meaning.",
    "topic": "MathML",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Choose subscript, superscript, combined script, under, over, and limit structures that match mathematical meaning.\n\n## Core notation for Scripts and Limits in MathML\n\nIn mathml, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for scripts and limits in mathml; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n\n## Practical workflow\n\nStart from \u0060\\frac{a}{b}\u0060 and write one sentence that says it means \u201Cstructured two-dimensional fraction.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for scripts and limits in mathml rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the scripts and limits in mathml notation.\n\n## Failure checks\n\n- Copying a rendered scripts and limits in mathml image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in scripts and limits in mathml.\n- Defining scripts and limits in mathml macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the scripts and limits in mathml source selectable and editable. For an isolated character in scripts and limits in mathml, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of scripts and limits in mathml is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the scripts and limits in mathml example.\n- Confirm every symbol used in scripts and limits in mathml has one defined meaning in the local context.\n- Reopen the exported file for **Scripts and Limits in MathML** and compare it with the editable source.\n"
  },
  {
    "slug": "unicode-math-search-normalization",
    "title": "Searching and Normalizing Unicode Math",
    "description": "Index aliases, code points, compatibility forms, confusables, and combining marks.",
    "topic": "Unicode",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Index aliases, code points, compatibility forms, confusables, and combining marks.\n\n## Core notation for Searching and Normalizing Unicode Math\n\nIn unicode, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for searching and normalizing unicode math; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n\n## Practical workflow\n\nStart from \u0060\\texttt{U\u002B2212}\u0060 and write one sentence that says it means \u201Cidentifier for the mathematical minus sign.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for searching and normalizing unicode math rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the searching and normalizing unicode math notation.\n\n## Failure checks\n\n- Copying a rendered searching and normalizing unicode math image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in searching and normalizing unicode math.\n- Defining searching and normalizing unicode math macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the searching and normalizing unicode math source selectable and editable. For an isolated character in searching and normalizing unicode math, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of searching and normalizing unicode math is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the searching and normalizing unicode math example.\n- Confirm every symbol used in searching and normalizing unicode math has one defined meaning in the local context.\n- Reopen the exported file for **Searching and Normalizing Unicode Math** and compare it with the editable source.\n"
  },
  {
    "slug": "sequences-series-common-errors",
    "title": "Sequences and Series: Common Errors and Verification",
    "description": "Common Errors and Verification for sequences and series: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Sequences and Series",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Sequences and Series: Common Errors and Verification explains indexing, arithmetic and geometric terms, partial sums, convergence, and notation.\n\n## Core notation for Sequences and Series: Common Errors and Verification\n\nIn sequences and series, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for sequences and series: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n\n## Errors that change the meaning\n\n- **Problem:** Switching index origins halfway through a recurrence. **Correction:** write the missing sequences and series: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Counting permutations when combinations are required. **Correction:** write the missing sequences and series: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using equality where modular congruence is intended. **Correction:** write the missing sequences and series: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the sequences and series: common errors and verification expression. Then check the sequences and series: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced sequences and series: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n\n## Accessibility and portability\n\nKeep the sequences and series: common errors and verification source selectable and editable. For an isolated character in sequences and series: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of sequences and series: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in sequences and series: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Sequences and Series: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "sequences-series-latex-formatting",
    "title": "Sequences and Series: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for sequences and series: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Sequences and Series",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Sequences and Series: LaTeX Formatting Guide explains indexing, arithmetic and geometric terms, partial sums, convergence, and notation.\n\n## Core notation for Sequences and Series\n\nIn sequences and series, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for sequences and series; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n\n## LaTeX patterns that preserve the structure\n\nFor sequences and series: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\np(x)=\\sum_{k=0}^{n}a_kx^k\n\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\n(a_n)_{n\\ge0}\n\u0060\u0060\u0060\n\nFor sequences and series, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In sequences and series, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Renderer and export checks\n\nRender one demanding sequences and series example in the actual destination. For sequences and series, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the sequences and series source selectable and editable. For an isolated character in sequences and series, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of sequences and series is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in sequences and series has one defined meaning in the local context.\n- Reopen the exported file for **Sequences and Series: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "sequences-series-notation-reference",
    "title": "Sequences and Series: Notation Reference",
    "description": "Notation Reference for sequences and series: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Sequences and Series",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Sequences and Series: Notation Reference explains indexing, arithmetic and geometric terms, partial sums, convergence, and notation.\n\n## Core notation for Sequences and Series\n\nIn sequences and series, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for sequences and series; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n\n## How to read a complete expression\n\nRead \u0060a\\equiv b\\pmod m\u0060 as \u201Ca and b have the same residue modulo m.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in sequences and series from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Cross-checks before reuse\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n\n## Accessibility and portability\n\nKeep the sequences and series source selectable and editable. For an isolated character in sequences and series, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of sequences and series is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in sequences and series has one defined meaning in the local context.\n- Reopen the exported file for **Sequences and Series: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "set-theory-symbols-explained",
    "title": "Set Theory Symbols Explained",
    "description": "Learn membership, subsets, unions, intersections, complements, and empty-set notation.",
    "topic": "Reference",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "# Set Theory Symbols Explained\n\nLearn membership, subsets, unions, intersections, complements, and empty-set notation. This guide focuses on reliable methods that preserve the intended character or mathematical structure when the text is copied, published, or shared.\n\n## Quick answer\n\nThe fastest option is to copy this character: **\u2208**. For a real mathematical equation, use the LaTeX form \u0060\\in\u0060 when your editor supports math rendering. Plain Unicode is ideal for short text, while LaTeX or an equation editor is better for structured notation.\n\n## Choose the right format\n\nUse **Unicode** when the symbol must remain a normal text character in an email, title, spreadsheet, or social post. Use **LaTeX** when the expression contains fractions, roots, limits, stacked scripts, or other two-dimensional notation. Use **HTML entities or numeric references** when the symbol is part of a web page and escaping or source-code clarity matters. Use **MathML** when semantic browser-accessible mathematics is required.\n\n| Format | Value | Best for |\n|---|---|---|\n| Character | \u0060\u2208\u0060 | Plain text and quick copy |\n| Unicode | \u0060U\u002B2208\u0060 | Character lookup and encoding |\n| LaTeX | \u0060\\in\u0060 | Equations and technical writing |\n| HTML | \u0060\u0026isin;\u0060 | Web pages |\n| MathML | \u0060\u0026lt;mo\u0026gt;\u2208\u0026lt;/mo\u0026gt;\u0060 | Semantic web mathematics |\n\n## Windows\n\nOpen **Character Map**, search for the symbol name, select the character, and copy it. In Microsoft Word and some Office applications, you can also type the hexadecimal Unicode value and press **Alt\u002BX**. Application support varies, so verify the result before relying on a shortcut in a different editor.\n\n## Mac\n\nPress **Control\u2013Command\u2013Space** to open Character Viewer. Search for the English symbol name, then double-click the result. Frequently used characters can be added to Favorites. In equation-capable applications, prefer the app\u2019s math editor when the character is part of a larger formula.\n\n## Microsoft Word\n\nPress **Alt\u002B=** to open an equation, type \u0060\\in\u0060, and press Space when Word recognizes the command. For plain text, use **Insert \u2192 Symbol \u2192 More Symbols**, or paste the Unicode character. The equation route is preferable when scripts, fractions, limits, or alignment are involved.\n\n## Google Docs\n\nChoose **Insert \u2192 Special characters**, search by name, or draw an approximate shape. For equations, choose **Insert \u2192 Equation** and use the available notation controls. Google Docs supports a useful subset of equation shortcuts, but it does not behave exactly like a full LaTeX system.\n\n## HTML and web pages\n\nA literal UTF-8 character is usually the clearest choice when the document declares UTF-8. Named entities can improve readability for common characters, while numeric references are a dependable fallback. Keep the symbol in meaningful text rather than using a background image, because text is selectable, searchable, and more accessible.\n\n\u0060\u0060\u0060html\n\u003Cspan aria-label=\u0022Element Of\u0022\u003E\u2208\u003C/span\u003E\n\u003Cspan\u003E\u0026isin;\u003C/span\u003E\n\u0060\u0060\u0060\n\n## LaTeX example\n\n\u0060\u0060\u0060latex\n\\in\n\u0060\u0060\u0060\n\nWhen the symbol is an operator or relation, place it in math mode and allow LaTeX to apply the correct spacing. Avoid forcing a mathematical expression into a sequence of unrelated Unicode characters when semantic structure matters.\n\n## Common mistakes\n\nDo not substitute a visually similar letter, punctuation mark, or image. Similar-looking characters may have different Unicode values and meanings. Also avoid copying from a decorative font that changes the glyph without changing the underlying character. Finally, check whether the surrounding context requires a specific convention; several mathematical symbols have meanings that vary by field or textbook.\n\n## Related resources\n\nUse the symbol page for definitions, examples, copy controls, and platform-specific input methods. Browse the relevant category for nearby notation, or open the LaTeX editor to test a complete formula before publishing it.\n"
  },
  {
    "slug": "set-builder-notation-guide",
    "title": "Set-Builder Notation Explained",
    "description": "Write sets by describing element conditions, choose a separator, and distinguish membership from subset relations.",
    "topic": "Set theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Write sets by describing element conditions, choose a separator, and distinguish membership from subset relations.\n\n## Core notation for Set-Builder Notation Explained\n\nIn set theory, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for set-builder notation explained; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n\n## Practical workflow\n\nStart from \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 and write one sentence that says it means \u201Cmulti-line alignment at relation signs.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for set-builder notation explained rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the set-builder notation explained notation.\n\n## Failure checks\n\n- Copying a rendered set-builder notation explained image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in set-builder notation explained.\n- Defining set-builder notation explained macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the set-builder notation explained source selectable and editable. For an isolated character in set-builder notation explained, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of set-builder notation explained is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the set-builder notation explained example.\n- Confirm every symbol used in set-builder notation explained has one defined meaning in the local context.\n- Reopen the exported file for **Set-Builder Notation Explained** and compare it with the editable source.\n"
  },
  {
    "slug": "shortest-path-notation",
    "title": "Shortest-Path and Distance Notation",
    "description": "Define path length, weighted distance, infinity for unreachable vertices, and predecessor information clearly.",
    "topic": "Graph Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Define path length, weighted distance, infinity for unreachable vertices, and predecessor information clearly.\n\n## Core notation for Shortest-Path and Distance Notation\n\nIn graph theory, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for shortest-path and distance notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Binomial coefficient | \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 | number of k-subsets of an n-set |\n| Sequence | \u0060(a_n)_{n\\ge0}\u0060 | indexed family of terms |\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n| Graph | \u0060G=(V,E)\u0060 | vertices and edges |\n\n## Practical workflow\n\nStart from \u0060\\binom{n}{k}=\\frac{n!}{k!(n-k)!}\u0060 and write one sentence that says it means \u201Cnumber of k-subsets of an n-set.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Failure checks\n\n- Switching index origins halfway through a recurrence.\n- Counting permutations when combinations are required.\n- Using equality where modular congruence is intended.\n\n## Accessibility and portability\n\nKeep the shortest-path and distance notation source selectable and editable. For an isolated character in shortest-path and distance notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of shortest-path and distance notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in shortest-path and distance notation has one defined meaning in the local context.\n- Reopen the exported file for **Shortest-Path and Distance Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "significant-figures-rounding-rules",
    "title": "Significant Figures and Rounding Rules",
    "description": "Count significant digits, handle leading and trailing zeros, and round measured values without implying false precision.",
    "topic": "Scientific writing",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Count significant digits, handle leading and trailing zeros, and round measured values without implying false precision.\n\n## Core notation for Significant Figures and Rounding Rules\n\nIn scientific writing, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for significant figures and rounding rules; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n\n## Practical workflow\n\nStart from \u0060\\frac{a}{b}\u0060 and write one sentence that says it means \u201Cstructured two-dimensional fraction.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for significant figures and rounding rules rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the significant figures and rounding rules notation.\n\n## Failure checks\n\n- Copying a rendered significant figures and rounding rules image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in significant figures and rounding rules.\n- Defining significant figures and rounding rules macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the significant figures and rounding rules source selectable and editable. For an isolated character in significant figures and rounding rules, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of significant figures and rounding rules is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the significant figures and rounding rules example.\n- Confirm every symbol used in significant figures and rounding rules has one defined meaning in the local context.\n- Reopen the exported file for **Significant Figures and Rounding Rules** and compare it with the editable source.\n"
  },
  {
    "slug": "svd-notation-guide",
    "title": "Singular Value Decomposition Notation",
    "description": "Track matrix shapes, singular vectors, singular values, rank, and truncation.",
    "topic": "Linear Algebra",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Track matrix shapes, singular vectors, singular values, rank, and truncation.\n\n## Core notation for Singular Value Decomposition Notation\n\nIn linear algebra, the notation usually represents scalars, vectors, matrices, linear maps, bases, and coordinate systems. The table below gives a compact starting set for singular value decomposition notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Transpose | \u0060A^{\\mathsf T}\u0060 | rows and columns exchanged |\n| Inverse | \u0060A^{-1}A=I\u0060 | inverse relation when A is nonsingular |\n| Eigenpair | \u0060Av=\\lambda v\u0060 | v is an eigenvector with eigenvalue \u03BB |\n| SVD | \u0060A=U\\Sigma V^{\\mathsf T}\u0060 | singular value decomposition |\n\n## Practical workflow\n\nStart from \u0060A^{\\mathsf T}\u0060 and write one sentence that says it means \u201Crows and columns exchanged.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State vector orientation and matrix dimensions.\n- Distinguish transpose, inverse, adjoint, and elementwise operations.\n- Name the basis whenever coordinates can change.\n\n## Failure checks\n\n- Multiplying matrices whose inner dimensions do not agree.\n- Treating elementwise multiplication as matrix multiplication.\n- Assuming an inverse exists without checking rank or determinant.\n\n## Accessibility and portability\n\nKeep the singular value decomposition notation source selectable and editable. For an isolated character in singular value decomposition notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of singular value decomposition notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Annotate dimensions beside a representative equation.\n- Verify identities on a small numeric matrix.\n- Check rank, symmetry, and definiteness assumptions.\n- Confirm every symbol used in singular value decomposition notation has one defined meaning in the local context.\n- Reopen the exported file for **Singular Value Decomposition Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "softmax-cross-entropy-guide",
    "title": "Softmax and Cross-Entropy",
    "description": "Use stable softmax computation and define target and prediction indexes.",
    "topic": "Statistics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Use stable softmax computation and define target and prediction indexes.\n\n## Core notation for Softmax and Cross-Entropy\n\nIn statistics, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for softmax and cross-entropy; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sample mean | \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 | the arithmetic mean of n observations |\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n\n## Practical workflow\n\nStart from \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 and write one sentence that says it means \u201Cthe arithmetic mean of n observations.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Failure checks\n\n- Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate.\n- Reporting a standard deviation as though it were a standard error.\n- Rounding intermediate values so aggressively that the final result changes.\n\n## Accessibility and portability\n\nKeep the softmax and cross-entropy source selectable and editable. For an isolated character in softmax and cross-entropy, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of softmax and cross-entropy is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in softmax and cross-entropy has one defined meaning in the local context.\n- Reopen the exported file for **Softmax and Cross-Entropy** and compare it with the editable source.\n"
  },
  {
    "slug": "solid-geometry-common-errors",
    "title": "Solid Geometry: Common Errors and Verification",
    "description": "Common Errors and Verification for solid geometry: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Solid Geometry",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Solid Geometry: Common Errors and Verification explains surface areas, volumes, cross-sections, units, and three-dimensional diagrams.\n\n## Core notation for Solid Geometry: Common Errors and Verification\n\nIn solid geometry, the notation usually represents points, lines, angles, lengths, coordinates, transformations, and orientation. The table below gives a compact starting set for solid geometry: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Line | \u0060y=mx\u002Bb\u0060 | slope-intercept form |\n| Pythagorean relation | \u0060a^2\u002Bb^2=c^2\u0060 | right-triangle side relation |\n| Sine rule | \u0060\\frac{a}{\\sin A}=\\frac{b}{\\sin B}=\\frac{c}{\\sin C}\u0060 | side-angle relation in a triangle |\n| Dot product | \u0060u\\cdot v=\\lVert u\\rVert\\lVert v\\rVert\\cos\\theta\u0060 | angle relation for vectors |\n\n## Errors that change the meaning\n\n- **Problem:** Feeding degree values into a radian-based function. **Correction:** write the missing solid geometry: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using slope formulas for vertical lines without a special case. **Correction:** write the missing solid geometry: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Discarding orientation when a signed area or angle is required. **Correction:** write the missing solid geometry: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the solid geometry: common errors and verification expression. Then check the solid geometry: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced solid geometry: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n\n## Accessibility and portability\n\nKeep the solid geometry: common errors and verification source selectable and editable. For an isolated character in solid geometry: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of solid geometry: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n- Confirm every symbol used in solid geometry: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Solid Geometry: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "solid-geometry-latex-formatting",
    "title": "Solid Geometry: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for solid geometry: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Solid Geometry",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Solid Geometry: LaTeX Formatting Guide explains surface areas, volumes, cross-sections, units, and three-dimensional diagrams.\n\n## Core notation for Solid Geometry\n\nIn solid geometry, the notation usually represents points, lines, angles, lengths, coordinates, transformations, and orientation. The table below gives a compact starting set for solid geometry; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Line | \u0060y=mx\u002Bb\u0060 | slope-intercept form |\n| Pythagorean relation | \u0060a^2\u002Bb^2=c^2\u0060 | right-triangle side relation |\n| Sine rule | \u0060\\frac{a}{\\sin A}=\\frac{b}{\\sin B}=\\frac{c}{\\sin C}\u0060 | side-angle relation in a triangle |\n| Dot product | \u0060u\\cdot v=\\lVert u\\rVert\\lVert v\\rVert\\cos\\theta\u0060 | angle relation for vectors |\n\n## LaTeX patterns that preserve the structure\n\nFor solid geometry: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\ny=mx\u002Bb\na^2\u002Bb^2=c^2\n\\frac{a}{\\sin A}=\\frac{b}{\\sin B}=\\frac{c}{\\sin C}\n\u0060\u0060\u0060\n\nFor solid geometry, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In solid geometry, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State degrees versus radians.\n- Name the coordinate system and orientation.\n- Distinguish directed angles, lengths, and vectors.\n\n## Renderer and export checks\n\nRender one demanding solid geometry example in the actual destination. For solid geometry, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the solid geometry source selectable and editable. For an isolated character in solid geometry, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of solid geometry is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n- Confirm every symbol used in solid geometry has one defined meaning in the local context.\n- Reopen the exported file for **Solid Geometry: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "solid-geometry-notation-reference",
    "title": "Solid Geometry: Notation Reference",
    "description": "Notation Reference for solid geometry: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Solid Geometry",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Solid Geometry: Notation Reference explains surface areas, volumes, cross-sections, units, and three-dimensional diagrams.\n\n## Core notation for Solid Geometry\n\nIn solid geometry, the notation usually represents points, lines, angles, lengths, coordinates, transformations, and orientation. The table below gives a compact starting set for solid geometry; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Area | \u0060A=\\frac12 ab\\sin C\u0060 | triangle area from two sides and included angle |\n| Distance | \u0060d=\\sqrt{(x_2-x_1)^2\u002B(y_2-y_1)^2}\u0060 | Euclidean distance in the plane |\n| Line | \u0060y=mx\u002Bb\u0060 | slope-intercept form |\n| Pythagorean relation | \u0060a^2\u002Bb^2=c^2\u0060 | right-triangle side relation |\n\n## How to read a complete expression\n\nRead \u0060A=\\frac12 ab\\sin C\u0060 as \u201Ctriangle area from two sides and included angle.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in solid geometry from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State degrees versus radians.\n- Name the coordinate system and orientation.\n- Distinguish directed angles, lengths, and vectors.\n\n## Cross-checks before reuse\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n\n## Accessibility and portability\n\nKeep the solid geometry source selectable and editable. For an isolated character in solid geometry, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of solid geometry is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n- Confirm every symbol used in solid geometry has one defined meaning in the local context.\n- Reopen the exported file for **Solid Geometry: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "latex-spacing-in-equations",
    "title": "Spacing Commands in LaTeX Mathematics",
    "description": "Use thin, medium, thick, negative, and text spacing intentionally rather than forcing layout with repeated spaces.",
    "topic": "LaTeX",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Use thin, medium, thick, negative, and text spacing intentionally rather than forcing layout with repeated spaces.\n\n## Core notation for Spacing Commands in LaTeX Mathematics\n\nIn latex, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for spacing commands in latex mathematics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## Practical workflow\n\nStart from \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 and write one sentence that says it means \u201Csemantic operator element.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for spacing commands in latex mathematics rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the spacing commands in latex mathematics notation.\n\n## Failure checks\n\n- Copying a rendered spacing commands in latex mathematics image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in spacing commands in latex mathematics.\n- Defining spacing commands in latex mathematics macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the spacing commands in latex mathematics source selectable and editable. For an isolated character in spacing commands in latex mathematics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of spacing commands in latex mathematics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the spacing commands in latex mathematics example.\n- Confirm every symbol used in spacing commands in latex mathematics has one defined meaning in the local context.\n- Reopen the exported file for **Spacing Commands in LaTeX Mathematics** and compare it with the editable source.\n"
  },
  {
    "slug": "statistical-inference-common-errors",
    "title": "Statistical Inference: Common Errors and Verification",
    "description": "Common Errors and Verification for statistical inference: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Statistical Inference",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Statistical Inference: Common Errors and Verification explains estimators, confidence intervals, hypotheses, p-values, and assumptions.\n\n## Core notation for Statistical Inference: Common Errors and Verification\n\nIn statistical inference, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for statistical inference: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n| Correlation | \u0060r=\\frac{\\operatorname{cov}(X,Y)}{s_Xs_Y}\u0060 | standardized linear association |\n\n## Errors that change the meaning\n\n- **Problem:** Using \u03BC and x\u0304 interchangeably without saying whether the value is a parameter or an estimate. **Correction:** write the missing statistical inference: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Reporting a standard deviation as though it were a standard error. **Correction:** write the missing statistical inference: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Rounding intermediate values so aggressively that the final result changes. **Correction:** write the missing statistical inference: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the statistical inference: common errors and verification expression. Then check the statistical inference: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced statistical inference: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n\n## Accessibility and portability\n\nKeep the statistical inference: common errors and verification source selectable and editable. For an isolated character in statistical inference: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of statistical inference: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in statistical inference: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Statistical Inference: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "statistical-inference-latex-formatting",
    "title": "Statistical Inference: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for statistical inference: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Statistical Inference",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Statistical Inference: LaTeX Formatting Guide explains estimators, confidence intervals, hypotheses, p-values, and assumptions.\n\n## Core notation for Statistical Inference\n\nIn statistical inference, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for statistical inference; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n| Correlation | \u0060r=\\frac{\\operatorname{cov}(X,Y)}{s_Xs_Y}\u0060 | standardized linear association |\n\n## LaTeX patterns that preserve the structure\n\nFor statistical inference: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\ns^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\n\\operatorname{SE}(\\hat{\\theta})\n\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\n\u0060\u0060\u0060\n\nFor statistical inference, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In statistical inference, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Renderer and export checks\n\nRender one demanding statistical inference example in the actual destination. For statistical inference, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the statistical inference source selectable and editable. For an isolated character in statistical inference, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of statistical inference is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in statistical inference has one defined meaning in the local context.\n- Reopen the exported file for **Statistical Inference: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "statistical-inference-notation-reference",
    "title": "Statistical Inference: Notation Reference",
    "description": "Notation Reference for statistical inference: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Statistical Inference",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Statistical Inference: Notation Reference explains estimators, confidence intervals, hypotheses, p-values, and assumptions.\n\n## Core notation for Statistical Inference\n\nIn statistical inference, the notation usually represents observations, samples, estimators, parameters, and uncertainty summaries. The table below gives a compact starting set for statistical inference; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Sample mean | \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 | the arithmetic mean of n observations |\n| Sample variance | \u0060s^2=\\frac{1}{n-1}\\sum_{i=1}^{n}(x_i-\\bar{x})^2\u0060 | an unbiased variance estimate under the usual assumptions |\n| Standard error | \u0060\\operatorname{SE}(\\hat{\\theta})\u0060 | estimated sampling variability of an estimator |\n| Confidence interval | \u0060\\hat{\\theta}\\pm z_{\\alpha/2}\\operatorname{SE}(\\hat{\\theta})\u0060 | an estimate with a stated confidence procedure |\n\n## How to read a complete expression\n\nRead \u0060\\bar{x}=\\frac{1}{n}\\sum_{i=1}^{n}x_i\u0060 as \u201Cthe arithmetic mean of n observations.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in statistical inference from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- Distinguish population parameters from sample estimates.\n- State whether variance uses n or n-1 in the denominator.\n- Define the confidence level, tail convention, and rounding rule.\n\n## Cross-checks before reuse\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n\n## Accessibility and portability\n\nKeep the statistical inference source selectable and editable. For an isolated character in statistical inference, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of statistical inference is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Recalculate one small sample by hand.\n- Confirm the denominator and degrees of freedom.\n- Report units for location and squared units for variance.\n- Confirm every symbol used in statistical inference has one defined meaning in the local context.\n- Reopen the exported file for **Statistical Inference: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "latex-project-structure",
    "title": "Structuring a LaTeX Math Project",
    "description": "Organize packages, macros, theorem environments, labels, references, and source files.",
    "topic": "LaTeX",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Organize packages, macros, theorem environments, labels, references, and source files.\n\n## Core notation for Structuring a LaTeX Math Project\n\nIn latex, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for structuring a latex math project; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n\n## Practical workflow\n\nStart from \u0060\\frac{a}{b}\u0060 and write one sentence that says it means \u201Cstructured two-dimensional fraction.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for structuring a latex math project rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the structuring a latex math project notation.\n\n## Failure checks\n\n- Copying a rendered structuring a latex math project image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in structuring a latex math project.\n- Defining structuring a latex math project macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the structuring a latex math project source selectable and editable. For an isolated character in structuring a latex math project, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of structuring a latex math project is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the structuring a latex math project example.\n- Confirm every symbol used in structuring a latex math project has one defined meaning in the local context.\n- Reopen the exported file for **Structuring a LaTeX Math Project** and compare it with the editable source.\n"
  },
  {
    "slug": "write-superscripts-subscripts-latex",
    "title": "Superscripts and Subscripts in LaTeX",
    "description": "Use braces, nested scripts, text labels, and limits without ambiguous formatting.",
    "topic": "LaTeX",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "# Superscripts and Subscripts in LaTeX\n\nUse braces, nested scripts, text labels, and limits without ambiguous formatting. This guide focuses on reliable methods that preserve the intended character or mathematical structure when the text is copied, published, or shared.\n\n## Quick answer\n\nThe fastest option is to copy this character: **\u00B2**. For a real mathematical equation, use the LaTeX form \u0060^2\u0060 when your editor supports math rendering. Plain Unicode is ideal for short text, while LaTeX or an equation editor is better for structured notation.\n\n## Choose the right format\n\nUse **Unicode** when the symbol must remain a normal text character in an email, title, spreadsheet, or social post. Use **LaTeX** when the expression contains fractions, roots, limits, stacked scripts, or other two-dimensional notation. Use **HTML entities or numeric references** when the symbol is part of a web page and escaping or source-code clarity matters. Use **MathML** when semantic browser-accessible mathematics is required.\n\n| Format | Value | Best for |\n|---|---|---|\n| Character | \u0060\u00B2\u0060 | Plain text and quick copy |\n| Unicode | \u0060U\u002B00B2\u0060 | Character lookup and encoding |\n| LaTeX | \u0060^2\u0060 | Equations and technical writing |\n| HTML | \u0060\u0026sup2;\u0060 | Web pages |\n| MathML | \u0060\u0026lt;mo\u0026gt;\u00B2\u0026lt;/mo\u0026gt;\u0060 | Semantic web mathematics |\n\n## Windows\n\nOpen **Character Map**, search for the symbol name, select the character, and copy it. In Microsoft Word and some Office applications, you can also type the hexadecimal Unicode value and press **Alt\u002BX**. Application support varies, so verify the result before relying on a shortcut in a different editor.\n\n## Mac\n\nPress **Control\u2013Command\u2013Space** to open Character Viewer. Search for the English symbol name, then double-click the result. Frequently used characters can be added to Favorites. In equation-capable applications, prefer the app\u2019s math editor when the character is part of a larger formula.\n\n## Microsoft Word\n\nPress **Alt\u002B=** to open an equation, type \u0060^2\u0060, and press Space when Word recognizes the command. For plain text, use **Insert \u2192 Symbol \u2192 More Symbols**, or paste the Unicode character. The equation route is preferable when scripts, fractions, limits, or alignment are involved.\n\n## Google Docs\n\nChoose **Insert \u2192 Special characters**, search by name, or draw an approximate shape. For equations, choose **Insert \u2192 Equation** and use the available notation controls. Google Docs supports a useful subset of equation shortcuts, but it does not behave exactly like a full LaTeX system.\n\n## HTML and web pages\n\nA literal UTF-8 character is usually the clearest choice when the document declares UTF-8. Named entities can improve readability for common characters, while numeric references are a dependable fallback. Keep the symbol in meaningful text rather than using a background image, because text is selectable, searchable, and more accessible.\n\n\u0060\u0060\u0060html\n\u003Cspan aria-label=\u0022Superscript Two\u0022\u003E\u00B2\u003C/span\u003E\n\u003Cspan\u003E\u0026sup2;\u003C/span\u003E\n\u0060\u0060\u0060\n\n## LaTeX example\n\n\u0060\u0060\u0060latex\n^2\n\u0060\u0060\u0060\n\nWhen the symbol is an operator or relation, place it in math mode and allow LaTeX to apply the correct spacing. Avoid forcing a mathematical expression into a sequence of unrelated Unicode characters when semantic structure matters.\n\n## Common mistakes\n\nDo not substitute a visually similar letter, punctuation mark, or image. Similar-looking characters may have different Unicode values and meanings. Also avoid copying from a decorative font that changes the glyph without changing the underlying character. Finally, check whether the surrounding context requires a specific convention; several mathematical symbols have meanings that vary by field or textbook.\n\n## Related resources\n\nUse the symbol page for definitions, examples, copy controls, and platform-specific input methods. Browse the relevant category for nearby notation, or open the LaTeX editor to test a complete formula before publishing it.\n"
  },
  {
    "slug": "taylor-approximations-common-errors",
    "title": "Taylor Approximations: Common Errors and Verification",
    "description": "Common Errors and Verification for taylor approximations: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Taylor Approximations",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Taylor Approximations: Common Errors and Verification explains expansion points, remainder terms, convergence, and truncation error.\n\n## Core notation for Taylor Approximations: Common Errors and Verification\n\nIn taylor approximations, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for taylor approximations: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n\n## Errors that change the meaning\n\n- **Problem:** Dropping an absolute value in a substitution jacobian. **Correction:** write the missing taylor approximations: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Interchanging a limit, sum, derivative, or integral without conditions. **Correction:** write the missing taylor approximations: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Omitting boundary terms after integration by parts. **Correction:** write the missing taylor approximations: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the taylor approximations: common errors and verification expression. Then check the taylor approximations: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced taylor approximations: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the taylor approximations: common errors and verification source selectable and editable. For an isolated character in taylor approximations: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of taylor approximations: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in taylor approximations: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Taylor Approximations: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "taylor-approximations-latex-formatting",
    "title": "Taylor Approximations: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for taylor approximations: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Taylor Approximations",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Taylor Approximations: LaTeX Formatting Guide explains expansion points, remainder terms, convergence, and truncation error.\n\n## Core notation for Taylor Approximations\n\nIn taylor approximations, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for taylor approximations; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n\n## LaTeX patterns that preserve the structure\n\nFor taylor approximations: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\nabla f\n\\int_a^b f(x)\\,dx\n\\nabla\\cdot F\n\u0060\u0060\u0060\n\nFor taylor approximations, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In taylor approximations, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Renderer and export checks\n\nRender one demanding taylor approximations example in the actual destination. For taylor approximations, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the taylor approximations source selectable and editable. For an isolated character in taylor approximations, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of taylor approximations is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in taylor approximations has one defined meaning in the local context.\n- Reopen the exported file for **Taylor Approximations: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "taylor-approximations-notation-reference",
    "title": "Taylor Approximations: Notation Reference",
    "description": "Notation Reference for taylor approximations: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Taylor Approximations",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Taylor Approximations: Notation Reference explains expansion points, remainder terms, convergence, and truncation error.\n\n## Core notation for Taylor Approximations\n\nIn taylor approximations, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for taylor approximations; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n\n## How to read a complete expression\n\nRead \u0060\\nabla\\cdot F\u0060 as \u201Clocal source strength of a vector field.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in taylor approximations from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Cross-checks before reuse\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the taylor approximations source selectable and editable. For an isolated character in taylor approximations, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of taylor approximations is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in taylor approximations has one defined meaning in the local context.\n- Reopen the exported file for **Taylor Approximations: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "tensor-index-notation",
    "title": "Tensor Index Notation",
    "description": "Use upper, lower, free, dummy, symmetric, and antisymmetric indexes correctly.",
    "topic": "Tensor Calculus",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Use upper, lower, free, dummy, symmetric, and antisymmetric indexes correctly.\n\n## Core notation for Tensor Index Notation\n\nIn tensor calculus, the notation usually represents tensor components, index positions, coordinate charts, bases, and contraction rules. The table below gives a compact starting set for tensor index notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Metric raising | \u0060v^i=g^{ij}v_j\u0060 | raising an index with the inverse metric |\n| Covariant derivative | \u0060\\nabla_i v^j\u0060 | coordinate-aware derivative of a vector field |\n| Einstein sum | \u0060a_i b^i\u0060 | implicit sum over the repeated index |\n| Tensor component | \u0060T^{i}{}_{jk}\u0060 | one contravariant and two covariant indices |\n\n## Practical workflow\n\nStart from \u0060v^i=g^{ij}v_j\u0060 and write one sentence that says it means \u201Craising an index with the inverse metric.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Declare the index range and summation convention.\n- Keep upper and lower index roles consistent.\n- State the metric signature and coordinate chart.\n\n## Failure checks\n\n- Repeating an index more than twice in one monomial.\n- Contracting two upper indices without a metric.\n- Moving an index without applying the metric tensor.\n\n## Accessibility and portability\n\nKeep the tensor index notation source selectable and editable. For an isolated character in tensor index notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of tensor index notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify each free index appears once on both sides.\n- Check that dummy indices may be renamed consistently.\n- Test the expression in a simple coordinate system.\n- Confirm every symbol used in tensor index notation has one defined meaning in the local context.\n- Reopen the exported file for **Tensor Index Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "mathml-browser-testing",
    "title": "Testing MathML Across Browsers",
    "description": "Validate markup, fallback behavior, accessibility, styling, and export pipelines.",
    "topic": "MathML",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Validate markup, fallback behavior, accessibility, styling, and export pipelines.\n\n## Core notation for Testing MathML Across Browsers\n\nIn mathml, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for testing mathml across browsers; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n\n## Practical workflow\n\nStart from \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 and write one sentence that says it means \u201Cmulti-line alignment at relation signs.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for testing mathml across browsers rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the testing mathml across browsers notation.\n\n## Failure checks\n\n- Copying a rendered testing mathml across browsers image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in testing mathml across browsers.\n- Defining testing mathml across browsers macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the testing mathml across browsers source selectable and editable. For an isolated character in testing mathml across browsers, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of testing mathml across browsers is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the testing mathml across browsers example.\n- Confirm every symbol used in testing mathml across browsers has one defined meaning in the local context.\n- Reopen the exported file for **Testing MathML Across Browsers** and compare it with the editable source.\n"
  },
  {
    "slug": "latex-theorem-proof-formatting",
    "title": "Theorem and Proof Formatting in LaTeX",
    "description": "Structure theorem-like environments, labels, references, proof endings, and mathematical statements consistently.",
    "topic": "LaTeX",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Structure theorem-like environments, labels, references, proof endings, and mathematical statements consistently.\n\n## Core notation for Theorem and Proof Formatting in LaTeX\n\nIn latex, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for theorem and proof formatting in latex; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n\n## Practical workflow\n\nStart from \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 and write one sentence that says it means \u201Csemantic operator element.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for theorem and proof formatting in latex rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the theorem and proof formatting in latex notation.\n\n## Failure checks\n\n- Copying a rendered theorem and proof formatting in latex image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in theorem and proof formatting in latex.\n- Defining theorem and proof formatting in latex macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the theorem and proof formatting in latex source selectable and editable. For an isolated character in theorem and proof formatting in latex, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of theorem and proof formatting in latex is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the theorem and proof formatting in latex example.\n- Confirm every symbol used in theorem and proof formatting in latex has one defined meaning in the local context.\n- Reopen the exported file for **Theorem and Proof Formatting in LaTeX** and compare it with the editable source.\n"
  },
  {
    "slug": "thermodynamics-common-errors",
    "title": "Thermodynamics: Common Errors and Verification",
    "description": "Common Errors and Verification for thermodynamics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Thermodynamics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Thermodynamics: Common Errors and Verification explains state variables, sign conventions, processes, energy, entropy, and units.\n\n## Core notation for Thermodynamics: Common Errors and Verification\n\nIn thermodynamics, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for thermodynamics: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Momentum | \u0060p=mv\u0060 | linear momentum in a nonrelativistic model |\n| Ohm law | \u0060V=IR\u0060 | voltage-current-resistance relation |\n| Wave relation | \u0060v=f\\lambda\u0060 | wave speed equals frequency times wavelength |\n| First law | \u0060\\Delta U=Q-W\u0060 | internal-energy change under the stated work sign convention |\n\n## Errors that change the meaning\n\n- **Problem:** Adding quantities with incompatible units. **Correction:** write the missing thermodynamics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Dropping vector direction when only magnitudes were given. **Correction:** write the missing thermodynamics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Mixing peak, rms, angular-frequency, and ordinary-frequency values. **Correction:** write the missing thermodynamics: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the thermodynamics: common errors and verification expression. Then check the thermodynamics: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced thermodynamics: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n\n## Accessibility and portability\n\nKeep the thermodynamics: common errors and verification source selectable and editable. For an isolated character in thermodynamics: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of thermodynamics: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in thermodynamics: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Thermodynamics: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "thermodynamics-latex-formatting",
    "title": "Thermodynamics: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for thermodynamics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Thermodynamics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Thermodynamics: LaTeX Formatting Guide explains state variables, sign conventions, processes, energy, entropy, and units.\n\n## Core notation for Thermodynamics\n\nIn thermodynamics, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for thermodynamics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Momentum | \u0060p=mv\u0060 | linear momentum in a nonrelativistic model |\n| Ohm law | \u0060V=IR\u0060 | voltage-current-resistance relation |\n| Wave relation | \u0060v=f\\lambda\u0060 | wave speed equals frequency times wavelength |\n| First law | \u0060\\Delta U=Q-W\u0060 | internal-energy change under the stated work sign convention |\n\n## LaTeX patterns that preserve the structure\n\nFor thermodynamics: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\np=mv\nV=IR\nv=f\\lambda\n\u0060\u0060\u0060\n\nFor thermodynamics, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In thermodynamics, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the coordinate axes and positive directions.\n- Attach si or other units to every measured quantity.\n- Declare the work, heat, voltage, and current sign conventions.\n\n## Renderer and export checks\n\nRender one demanding thermodynamics example in the actual destination. For thermodynamics, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the thermodynamics source selectable and editable. For an isolated character in thermodynamics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of thermodynamics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in thermodynamics has one defined meaning in the local context.\n- Reopen the exported file for **Thermodynamics: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "thermodynamics-notation-reference",
    "title": "Thermodynamics: Notation Reference",
    "description": "Notation Reference for thermodynamics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Thermodynamics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Thermodynamics: Notation Reference explains state variables, sign conventions, processes, energy, entropy, and units.\n\n## Core notation for Thermodynamics\n\nIn thermodynamics, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for thermodynamics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Energy | \u0060E=T\u002BV\u0060 | total mechanical energy as kinetic plus potential energy |\n| Momentum | \u0060p=mv\u0060 | linear momentum in a nonrelativistic model |\n| Ohm law | \u0060V=IR\u0060 | voltage-current-resistance relation |\n| Wave relation | \u0060v=f\\lambda\u0060 | wave speed equals frequency times wavelength |\n\n## How to read a complete expression\n\nRead \u0060E=T\u002BV\u0060 as \u201Ctotal mechanical energy as kinetic plus potential energy.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in thermodynamics from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the coordinate axes and positive directions.\n- Attach si or other units to every measured quantity.\n- Declare the work, heat, voltage, and current sign conventions.\n\n## Cross-checks before reuse\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n\n## Accessibility and portability\n\nKeep the thermodynamics source selectable and editable. For an isolated character in thermodynamics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of thermodynamics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in thermodynamics has one defined meaning in the local context.\n- Reopen the exported file for **Thermodynamics: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "topology-basics-common-errors",
    "title": "Topology Basics: Common Errors and Verification",
    "description": "Common Errors and Verification for topology basics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Topology Basics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Topology Basics: Common Errors and Verification explains open sets, closures, boundaries, continuity, compactness, and spaces.\n\n## Core notation for Topology Basics: Common Errors and Verification\n\nIn topology basics, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for topology basics: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Closure | \u0060\\overline{A}\u0060 | A together with its limit points |\n| Interior | \u0060A^\\circ\u0060 | largest open set contained in A |\n| Continuity | \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 | topological continuity criterion |\n| Complex logarithm | \u0060\\Log z=\\ln|z|\u002Bi\\Arg z\u0060 | a selected logarithm branch |\n\n## Errors that change the meaning\n\n- **Problem:** Using closed and bounded as a universal compactness criterion. **Correction:** write the missing topology basics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Crossing a branch cut without changing the selected argument. **Correction:** write the missing topology basics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Omitting hypotheses from a convergence or interchange theorem. **Correction:** write the missing topology basics: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the topology basics: common errors and verification expression. Then check the topology basics: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced topology basics: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n\n## Accessibility and portability\n\nKeep the topology basics: common errors and verification source selectable and editable. For an isolated character in topology basics: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of topology basics: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in topology basics: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Topology Basics: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "topology-basics-latex-formatting",
    "title": "Topology Basics: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for topology basics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Topology Basics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Topology Basics: LaTeX Formatting Guide explains open sets, closures, boundaries, continuity, compactness, and spaces.\n\n## Core notation for Topology Basics\n\nIn topology basics, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for topology basics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Open ball | \u0060B_r(x)=\\{y:d(x,y)\u003Cr\\}\u0060 | points within radius r of x |\n| Closure | \u0060\\overline{A}\u0060 | A together with its limit points |\n| Interior | \u0060A^\\circ\u0060 | largest open set contained in A |\n| Continuity | \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 | topological continuity criterion |\n\n## LaTeX patterns that preserve the structure\n\nFor topology basics: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nB_r(x)=\\{y:d(x,y)\u003Cr\\}\n\\overline{A}\nA^\\circ\n\u0060\u0060\u0060\n\nFor topology basics, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In topology basics, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the ambient space and topology.\n- Distinguish local from global properties.\n- Declare contour orientation and branch choices.\n\n## Renderer and export checks\n\nRender one demanding topology basics example in the actual destination. For topology basics, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the topology basics source selectable and editable. For an isolated character in topology basics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of topology basics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in topology basics has one defined meaning in the local context.\n- Reopen the exported file for **Topology Basics: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "topology-basics-notation-reference",
    "title": "Topology Basics: Notation Reference",
    "description": "Notation Reference for topology basics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Topology Basics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Topology Basics: Notation Reference explains open sets, closures, boundaries, continuity, compactness, and spaces.\n\n## Core notation for Topology Basics\n\nIn topology basics, the notation usually represents sets, neighborhoods, limits, continuity conditions, contours, and chosen branches. The table below gives a compact starting set for topology basics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Closure | \u0060\\overline{A}\u0060 | A together with its limit points |\n| Interior | \u0060A^\\circ\u0060 | largest open set contained in A |\n| Continuity | \u0060f^{-1}(U)\\text{ is open for every open }U\u0060 | topological continuity criterion |\n| Complex logarithm | \u0060\\Log z=\\ln|z|\u002Bi\\Arg z\u0060 | a selected logarithm branch |\n\n## How to read a complete expression\n\nRead \u0060\\overline{A}\u0060 as \u201CA together with its limit points.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in topology basics from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the ambient space and topology.\n- Distinguish local from global properties.\n- Declare contour orientation and branch choices.\n\n## Cross-checks before reuse\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n\n## Accessibility and portability\n\nKeep the topology basics source selectable and editable. For an isolated character in topology basics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of topology basics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test definitions directly on a simple set.\n- Draw the contour and singularities.\n- State the topology, metric, or norm in force.\n- Confirm every symbol used in topology basics has one defined meaning in the local context.\n- Reopen the exported file for **Topology Basics: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "tree-graph-notation",
    "title": "Tree and Forest Notation",
    "description": "Distinguish roots, parents, children, leaves, depth, height, subtrees, and components in tree-based arguments.",
    "topic": "Graph Theory",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Distinguish roots, parents, children, leaves, depth, height, subtrees, and components in tree-based arguments.\n\n## Core notation for Tree and Forest Notation\n\nIn graph theory, the notation usually represents finite sets, graphs, integers, indices, recurrences, coefficients, and counting conventions. The table below gives a compact starting set for tree and forest notation; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Recurrence | \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 | term defined from earlier terms |\n| Graph | \u0060G=(V,E)\u0060 | vertices and edges |\n| Congruence | \u0060a\\equiv b\\pmod m\u0060 | a and b have the same residue modulo m |\n| Polynomial | \u0060p(x)=\\sum_{k=0}^{n}a_kx^k\u0060 | polynomial with coefficients a_k |\n\n## Practical workflow\n\nStart from \u0060a_n=a_{n-1}\u002Ba_{n-2}\u0060 and write one sentence that says it means \u201Cterm defined from earlier terms.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- State whether indexing begins at zero or one.\n- Distinguish ordered from unordered selections.\n- Declare whether graphs are directed, simple, weighted, or allow loops.\n\n## Failure checks\n\n- Switching index origins halfway through a recurrence.\n- Counting permutations when combinations are required.\n- Using equality where modular congruence is intended.\n\n## Accessibility and portability\n\nKeep the tree and forest notation source selectable and editable. For an isolated character in tree and forest notation, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of tree and forest notation is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Enumerate a small case.\n- Verify boundary indices.\n- Compare a recurrence with its initial conditions.\n- Confirm every symbol used in tree and forest notation has one defined meaning in the local context.\n- Reopen the exported file for **Tree and Forest Notation** and compare it with the editable source.\n"
  },
  {
    "slug": "triangle-trigonometry-common-errors",
    "title": "Triangle Trigonometry: Common Errors and Verification",
    "description": "Common Errors and Verification for triangle trigonometry: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Triangle Trigonometry",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Triangle Trigonometry: Common Errors and Verification explains angles, side labels, sine and cosine laws, radians, and inverse functions.\n\n## Core notation for Triangle Trigonometry: Common Errors and Verification\n\nIn triangle trigonometry, the notation usually represents points, lines, angles, lengths, coordinates, transformations, and orientation. The table below gives a compact starting set for triangle trigonometry: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Area | \u0060A=\\frac12 ab\\sin C\u0060 | triangle area from two sides and included angle |\n| Distance | \u0060d=\\sqrt{(x_2-x_1)^2\u002B(y_2-y_1)^2}\u0060 | Euclidean distance in the plane |\n| Line | \u0060y=mx\u002Bb\u0060 | slope-intercept form |\n| Pythagorean relation | \u0060a^2\u002Bb^2=c^2\u0060 | right-triangle side relation |\n\n## Errors that change the meaning\n\n- **Problem:** Feeding degree values into a radian-based function. **Correction:** write the missing triangle trigonometry: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using slope formulas for vertical lines without a special case. **Correction:** write the missing triangle trigonometry: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Discarding orientation when a signed area or angle is required. **Correction:** write the missing triangle trigonometry: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the triangle trigonometry: common errors and verification expression. Then check the triangle trigonometry: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced triangle trigonometry: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n\n## Accessibility and portability\n\nKeep the triangle trigonometry: common errors and verification source selectable and editable. For an isolated character in triangle trigonometry: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of triangle trigonometry: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n- Confirm every symbol used in triangle trigonometry: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Triangle Trigonometry: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "triangle-trigonometry-latex-formatting",
    "title": "Triangle Trigonometry: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for triangle trigonometry: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Triangle Trigonometry",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Triangle Trigonometry: LaTeX Formatting Guide explains angles, side labels, sine and cosine laws, radians, and inverse functions.\n\n## Core notation for Triangle Trigonometry\n\nIn triangle trigonometry, the notation usually represents points, lines, angles, lengths, coordinates, transformations, and orientation. The table below gives a compact starting set for triangle trigonometry; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Pythagorean relation | \u0060a^2\u002Bb^2=c^2\u0060 | right-triangle side relation |\n| Sine rule | \u0060\\frac{a}{\\sin A}=\\frac{b}{\\sin B}=\\frac{c}{\\sin C}\u0060 | side-angle relation in a triangle |\n| Dot product | \u0060u\\cdot v=\\lVert u\\rVert\\lVert v\\rVert\\cos\\theta\u0060 | angle relation for vectors |\n| Area | \u0060A=\\frac12 ab\\sin C\u0060 | triangle area from two sides and included angle |\n\n## LaTeX patterns that preserve the structure\n\nFor triangle trigonometry: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\na^2\u002Bb^2=c^2\n\\frac{a}{\\sin A}=\\frac{b}{\\sin B}=\\frac{c}{\\sin C}\nu\\cdot v=\\lVert u\\rVert\\lVert v\\rVert\\cos\\theta\n\u0060\u0060\u0060\n\nFor triangle trigonometry, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In triangle trigonometry, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State degrees versus radians.\n- Name the coordinate system and orientation.\n- Distinguish directed angles, lengths, and vectors.\n\n## Renderer and export checks\n\nRender one demanding triangle trigonometry example in the actual destination. For triangle trigonometry, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the triangle trigonometry source selectable and editable. For an isolated character in triangle trigonometry, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of triangle trigonometry is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n- Confirm every symbol used in triangle trigonometry has one defined meaning in the local context.\n- Reopen the exported file for **Triangle Trigonometry: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "triangle-trigonometry-notation-reference",
    "title": "Triangle Trigonometry: Notation Reference",
    "description": "Notation Reference for triangle trigonometry: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Triangle Trigonometry",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Triangle Trigonometry: Notation Reference explains angles, side labels, sine and cosine laws, radians, and inverse functions.\n\n## Core notation for Triangle Trigonometry\n\nIn triangle trigonometry, the notation usually represents points, lines, angles, lengths, coordinates, transformations, and orientation. The table below gives a compact starting set for triangle trigonometry; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Line | \u0060y=mx\u002Bb\u0060 | slope-intercept form |\n| Pythagorean relation | \u0060a^2\u002Bb^2=c^2\u0060 | right-triangle side relation |\n| Sine rule | \u0060\\frac{a}{\\sin A}=\\frac{b}{\\sin B}=\\frac{c}{\\sin C}\u0060 | side-angle relation in a triangle |\n| Dot product | \u0060u\\cdot v=\\lVert u\\rVert\\lVert v\\rVert\\cos\\theta\u0060 | angle relation for vectors |\n\n## How to read a complete expression\n\nRead \u0060y=mx\u002Bb\u0060 as \u201Cslope-intercept form.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in triangle trigonometry from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State degrees versus radians.\n- Name the coordinate system and orientation.\n- Distinguish directed angles, lengths, and vectors.\n\n## Cross-checks before reuse\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n\n## Accessibility and portability\n\nKeep the triangle trigonometry source selectable and editable. For an isolated character in triangle trigonometry, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of triangle trigonometry is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Test a right triangle or axis-aligned example.\n- Verify angle units.\n- Check that lengths and areas have the expected dimensions.\n- Confirm every symbol used in triangle trigonometry has one defined meaning in the local context.\n- Reopen the exported file for **Triangle Trigonometry: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "trigonometric-identities-common-errors",
    "title": "Trigonometric Identities: Common Errors and Verification",
    "description": "Common Errors and Verification for trigonometric identities: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Trigonometric Identities",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Trigonometric Identities: Common Errors and Verification explains equivalent forms, domains, periodicity, double angles, and verification steps.\n\n## Core notation for Trigonometric Identities: Common Errors and Verification\n\nIn trigonometric identities, the notation usually represents tensor components, index positions, coordinate charts, bases, and contraction rules. The table below gives a compact starting set for trigonometric identities: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Metric lowering | \u0060v_i=g_{ij}v^j\u0060 | lowering an index with the metric |\n| Metric raising | \u0060v^i=g^{ij}v_j\u0060 | raising an index with the inverse metric |\n| Covariant derivative | \u0060\\nabla_i v^j\u0060 | coordinate-aware derivative of a vector field |\n| Einstein sum | \u0060a_i b^i\u0060 | implicit sum over the repeated index |\n\n## Errors that change the meaning\n\n- **Problem:** Repeating an index more than twice in one monomial. **Correction:** write the missing trigonometric identities: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Contracting two upper indices without a metric. **Correction:** write the missing trigonometric identities: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Moving an index without applying the metric tensor. **Correction:** write the missing trigonometric identities: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the trigonometric identities: common errors and verification expression. Then check the trigonometric identities: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced trigonometric identities: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Verify each free index appears once on both sides.\n- Check that dummy indices may be renamed consistently.\n- Test the expression in a simple coordinate system.\n\n## Accessibility and portability\n\nKeep the trigonometric identities: common errors and verification source selectable and editable. For an isolated character in trigonometric identities: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of trigonometric identities: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify each free index appears once on both sides.\n- Check that dummy indices may be renamed consistently.\n- Test the expression in a simple coordinate system.\n- Confirm every symbol used in trigonometric identities: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Trigonometric Identities: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "trigonometric-identities-latex-formatting",
    "title": "Trigonometric Identities: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for trigonometric identities: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Trigonometric Identities",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Trigonometric Identities: LaTeX Formatting Guide explains equivalent forms, domains, periodicity, double angles, and verification steps.\n\n## Core notation for Trigonometric Identities\n\nIn trigonometric identities, the notation usually represents tensor components, index positions, coordinate charts, bases, and contraction rules. The table below gives a compact starting set for trigonometric identities; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Tensor component | \u0060T^{i}{}_{jk}\u0060 | one contravariant and two covariant indices |\n| Contraction | \u0060T^{i}{}_{ik}\u0060 | summation over a repeated upper-lower index |\n| Metric lowering | \u0060v_i=g_{ij}v^j\u0060 | lowering an index with the metric |\n| Metric raising | \u0060v^i=g^{ij}v_j\u0060 | raising an index with the inverse metric |\n\n## LaTeX patterns that preserve the structure\n\nFor trigonometric identities: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\nT^{i}{}_{jk}\nT^{i}{}_{ik}\nv_i=g_{ij}v^j\n\u0060\u0060\u0060\n\nFor trigonometric identities, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In trigonometric identities, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Declare the index range and summation convention.\n- Keep upper and lower index roles consistent.\n- State the metric signature and coordinate chart.\n\n## Renderer and export checks\n\nRender one demanding trigonometric identities example in the actual destination. For trigonometric identities, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the trigonometric identities source selectable and editable. For an isolated character in trigonometric identities, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of trigonometric identities is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify each free index appears once on both sides.\n- Check that dummy indices may be renamed consistently.\n- Test the expression in a simple coordinate system.\n- Confirm every symbol used in trigonometric identities has one defined meaning in the local context.\n- Reopen the exported file for **Trigonometric Identities: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "trigonometric-identities-notation-reference",
    "title": "Trigonometric Identities: Notation Reference",
    "description": "Notation Reference for trigonometric identities: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Trigonometric Identities",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Trigonometric Identities: Notation Reference explains equivalent forms, domains, periodicity, double angles, and verification steps.\n\n## Core notation for Trigonometric Identities\n\nIn trigonometric identities, the notation usually represents tensor components, index positions, coordinate charts, bases, and contraction rules. The table below gives a compact starting set for trigonometric identities; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Tensor component | \u0060T^{i}{}_{jk}\u0060 | one contravariant and two covariant indices |\n| Contraction | \u0060T^{i}{}_{ik}\u0060 | summation over a repeated upper-lower index |\n| Metric lowering | \u0060v_i=g_{ij}v^j\u0060 | lowering an index with the metric |\n| Metric raising | \u0060v^i=g^{ij}v_j\u0060 | raising an index with the inverse metric |\n\n## How to read a complete expression\n\nRead \u0060T^{i}{}_{jk}\u0060 as \u201Cone contravariant and two covariant indices.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in trigonometric identities from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- Declare the index range and summation convention.\n- Keep upper and lower index roles consistent.\n- State the metric signature and coordinate chart.\n\n## Cross-checks before reuse\n\n- Verify each free index appears once on both sides.\n- Check that dummy indices may be renamed consistently.\n- Test the expression in a simple coordinate system.\n\n## Accessibility and portability\n\nKeep the trigonometric identities source selectable and editable. For an isolated character in trigonometric identities, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of trigonometric identities is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Verify each free index appears once on both sides.\n- Check that dummy indices may be renamed consistently.\n- Test the expression in a simple coordinate system.\n- Confirm every symbol used in trigonometric identities has one defined meaning in the local context.\n- Reopen the exported file for **Trigonometric Identities: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "unicode-code-point-html",
    "title": "Unicode Code Points and HTML Entities",
    "description": "Move safely between literal characters, U\u002B notation, decimal references, hexadecimal references, and named HTML entities.",
    "topic": "Unicode",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Move safely between literal characters, U\u002B notation, decimal references, hexadecimal references, and named HTML entities.\n\n## Core notation for Unicode Code Points and HTML Entities\n\nIn unicode, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for unicode code points and html entities; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n| Aligned equations | \u0060\\begin{aligned}a\u0026=b\u002Bc\\\\d\u0026=e\\end{aligned}\u0060 | multi-line alignment at relation signs |\n\n## Practical workflow\n\nStart from \u0060\\frac{a}{b}\u0060 and write one sentence that says it means \u201Cstructured two-dimensional fraction.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for unicode code points and html entities rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the unicode code points and html entities notation.\n\n## Failure checks\n\n- Copying a rendered unicode code points and html entities image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in unicode code points and html entities.\n- Defining unicode code points and html entities macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the unicode code points and html entities source selectable and editable. For an isolated character in unicode code points and html entities, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of unicode code points and html entities is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the unicode code points and html entities example.\n- Confirm every symbol used in unicode code points and html entities has one defined meaning in the local context.\n- Reopen the exported file for **Unicode Code Points and HTML Entities** and compare it with the editable source.\n"
  },
  {
    "slug": "unicode-math-to-latex-guide",
    "title": "Unicode Math to LaTeX Conversion Guide",
    "description": "Convert common Unicode mathematics into structured LaTeX while handling ambiguous operators, styled letters, superscripts, and plain-text limitations.",
    "topic": "Format conversion",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Convert common Unicode mathematics into structured LaTeX while handling ambiguous operators, styled letters, superscripts, and plain-text limitations. This guide focuses on reliable, editable output rather than visual shortcuts. The exact menu names can vary by application version, but the underlying choice remains the same: use Unicode for isolated characters and structured math for complete expressions.\n\n## Choose the right representation\n\nMathematical notation can be stored as ordinary Unicode text, structured equation markup, or an image. Unicode is convenient for isolated symbols and short labels. LaTeX and MathML preserve structure for fractions, matrices, scripts, and aligned equations. Images should be a last resort because they are harder to edit, search, resize, and make accessible.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Create the notation\n\nStart in the native equation editor when the destination application provides one. Native editors understand mathematical grouping, spacing, and baseline alignment better than manual character placement. When importing text, separate semantic content from presentation: identify operators, variables, units, subscripts, and conditions before deciding how they should look.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Check meaning and ambiguity\n\nThe same visible character can carry several meanings across algebra, statistics, physics, and chemistry. Define uncommon notation and review nearby variables before converting formats. Plain Unicode cannot always distinguish multiplication from a dot product, a hyphen from a minus sign, or a decorative letter from a mathematical constant.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Preserve accessibility\n\nUse real text or structured math whenever possible. Provide a concise spoken description for an image and include the surrounding purpose of the equation rather than reading every punctuation mark mechanically. Keyboard focus, selectable text, sufficient contrast, and responsive layout are also part of accessible mathematical communication.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Test the final output\n\nCopy the result into the actual destination, save and reopen the file, then inspect desktop, mobile, print, and exported PDF views. Confirm that fonts contain every symbol, line breaks do not split expressions incorrectly, and superscripts remain attached to the intended base. For web pages, test without JavaScript and with browser zoom.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Use a repeatable workflow\n\nKeep the source notation in a plain, version-controlled format when possible. Record the LaTeX command, Unicode code point, and intended meaning for symbols that appear frequently. A repeatable workflow reduces silent substitutions and makes later updates easier when the content moves between Word, HTML, Markdown, presentation software, and publishing systems.\n\nA practical check is to copy the notation into a second application and compare both the visible result and the underlying editable text. This catches font substitution, escaped backslashes, broken delimiters, and character normalization before publication.\n\n## Final checklist\n\n1. Confirm the mathematical meaning in context.\n2. Prefer native equation markup for structured expressions.\n3. Verify Unicode and LaTeX independently.\n4. Test copying, exporting, zooming, and screen-reader output.\n5. Keep an editable source version for future correction.\n"
  },
  {
    "slug": "unicode-mathematics-common-errors",
    "title": "Unicode Mathematics: Common Errors and Verification",
    "description": "Common Errors and Verification for unicode mathematics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Unicode Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Unicode Mathematics: Common Errors and Verification explains code points, normalization, styled alphabets, fonts, and copy portability.\n\n## Core notation for Unicode Mathematics: Common Errors and Verification\n\nIn unicode mathematics, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for unicode mathematics: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n\n## Errors that change the meaning\n\n- **Problem:** Copying a rendered image when editable notation is required. **Correction:** write the missing unicode mathematics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Using a look-alike unicode character with different semantics. **Correction:** write the missing unicode mathematics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Defining macros that hide arguments or conflict with package commands. **Correction:** write the missing unicode mathematics: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the unicode mathematics: common errors and verification expression. Then check the unicode mathematics: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced unicode mathematics: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the unicode mathematics: common errors and verification example.\n\n## Accessibility and portability\n\nKeep the unicode mathematics: common errors and verification source selectable and editable. For an isolated character in unicode mathematics: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of unicode mathematics: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the unicode mathematics: common errors and verification example.\n- Confirm every symbol used in unicode mathematics: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Unicode Mathematics: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "unicode-mathematics-latex-formatting",
    "title": "Unicode Mathematics: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for unicode mathematics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Unicode Mathematics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Unicode Mathematics: LaTeX Formatting Guide explains code points, normalization, styled alphabets, fonts, and copy portability.\n\n## Core notation for Unicode Mathematics\n\nIn unicode mathematics, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for unicode mathematics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n\n## LaTeX patterns that preserve the structure\n\nFor unicode mathematics: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\newcommand{\\vect}[1]{\\mathbf{#1}}\n\\frac{a}{b}\n\\texttt{U\u002B2212}\n\u0060\u0060\u0060\n\nFor unicode mathematics, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In unicode mathematics, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- Keep editable source with the rendered result.\n- Use semantic commands for unicode mathematics rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the unicode mathematics notation.\n\n## Renderer and export checks\n\nRender one demanding unicode mathematics example in the actual destination. For unicode mathematics, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the unicode mathematics source selectable and editable. For an isolated character in unicode mathematics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of unicode mathematics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the unicode mathematics example.\n- Confirm every symbol used in unicode mathematics has one defined meaning in the local context.\n- Reopen the exported file for **Unicode Mathematics: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "unicode-normalization-math",
    "title": "Unicode Normalization and Mathematical Text",
    "description": "Avoid accidental changes to combining marks, styled mathematical letters, and visually similar compatibility characters.",
    "topic": "Unicode",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Avoid accidental changes to combining marks, styled mathematical letters, and visually similar compatibility characters.\n\n## Core notation for Unicode Normalization and Mathematical Text\n\nIn unicode, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for unicode normalization and mathematical text; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n| MathML operator | \u0060\\texttt{\u003Cmo\u003E\u2212\u003C/mo\u003E}\u0060 | semantic operator element |\n\n## Practical workflow\n\nStart from \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 and write one sentence that says it means \u201Creusable semantic notation command.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for unicode normalization and mathematical text rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the unicode normalization and mathematical text notation.\n\n## Failure checks\n\n- Copying a rendered unicode normalization and mathematical text image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in unicode normalization and mathematical text.\n- Defining unicode normalization and mathematical text macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the unicode normalization and mathematical text source selectable and editable. For an isolated character in unicode normalization and mathematical text, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of unicode normalization and mathematical text is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the unicode normalization and mathematical text example.\n- Confirm every symbol used in unicode normalization and mathematical text has one defined meaning in the local context.\n- Reopen the exported file for **Unicode Normalization and Mathematical Text** and compare it with the editable source.\n"
  },
  {
    "slug": "unicode-superscript-limitations",
    "title": "Unicode Superscript and Subscript Limitations",
    "description": "Know which characters exist, where copyable scripts work, and when semantic math markup is necessary.",
    "topic": "Unicode",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "## Quick answer\n\nKnow which characters exist, where copyable scripts work, and when semantic math markup is necessary. The safest choice is to preserve semantic math whenever the destination supports equations, and use Unicode only for short standalone characters.\n\n## Recommended methods\n\n### LaTeX and equation editors\n\nUse an equation editor for structured notation. LaTeX keeps operators, limits, scripts, fractions, and spacing connected to the mathematical meaning. Copy the exact command from the symbol reference, preview it, and verify that the target platform uses a compatible math engine.\n\n### Unicode text\n\nUnicode is convenient for a single symbol in a message, heading, spreadsheet label, or plain-text note. Confirm that the selected font contains the glyph and that a visually similar character was not substituted. Unicode text does not automatically encode complex relationships such as a numerator over a denominator.\n\n### Word, Windows, and macOS\n\nIn Microsoft Word, insert an equation before entering LaTeX-like commands. On Windows, Character Map and the emoji/symbol panel can insert individual characters. On macOS, Character Viewer is useful for searching by the English Unicode name. Always test copy and paste in the final application.\n\n## Common mistakes\n\n1. Replacing a mathematical symbol with punctuation that only looks similar.\n2. Mixing Unicode characters with equation-editor markup without checking baseline and spacing.\n3. Copying hidden directional or formatting characters from a web page.\n4. Assuming the same shortcut works in normal text and in an equation field.\n\n## HTML and accessible publishing\n\nFor a single character, place the Unicode symbol directly in UTF-8 HTML and include surrounding words that explain its meaning. For a formula, prefer MathML or a renderer that exposes semantic MathML to assistive technology. Do not publish important equations only as unlabeled images.\n\n## Final check\n\nVerify the symbol, meaning, font, spacing, and spoken description in the final output. If the notation could be interpreted in more than one way, define it in the sentence before the equation.\n\n## Practical verification workflow\n\nBefore publishing, test the notation in the exact application and export format your readers will use. Copy the source into a clean document, save it, reopen it, and verify that the expression remains editable. Compare the original source with the exported PDF or HTML so that substituted fonts, missing glyphs, broken braces, and incorrect line breaks are caught early.\n\nFor web content, inspect the page at narrow mobile widths, at 200 percent browser zoom, and with keyboard-only navigation. Confirm that symbols can be selected and copied as text. When an equation is rendered by JavaScript, keep a meaningful text fallback and avoid placing essential explanation only inside the visual formula. For office documents, check both normal view and presentation or print view because equation spacing can change during export.\n\nFinally, ask a second reviewer to read the notation in context. The reviewer should confirm not only that the symbol looks correct, but also that its mathematical meaning, units, sign convention, and surrounding explanation are unambiguous. Store the editable source beside the published version so future corrections do not depend on reverse-engineering an image.\n"
  },
  {
    "slug": "vector-calculus-common-errors",
    "title": "Vector Calculus: Common Errors and Verification",
    "description": "Common Errors and Verification for vector calculus: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Vector Calculus",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Vector Calculus: Common Errors and Verification explains gradients, divergence, curl, line integrals, and coordinate systems.\n\n## Core notation for Vector Calculus: Common Errors and Verification\n\nIn vector calculus, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for vector calculus: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n| Derivative | \u0060f\\\u0027(x)=\\frac{df}{dx}\u0060 | instantaneous rate of change |\n| Gradient | \u0060\\nabla f\u0060 | vector of first partial derivatives |\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n\n## Errors that change the meaning\n\n- **Problem:** Dropping an absolute value in a substitution jacobian. **Correction:** write the missing vector calculus: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Interchanging a limit, sum, derivative, or integral without conditions. **Correction:** write the missing vector calculus: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Omitting boundary terms after integration by parts. **Correction:** write the missing vector calculus: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the vector calculus: common errors and verification expression. Then check the vector calculus: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced vector calculus: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the vector calculus: common errors and verification source selectable and editable. For an isolated character in vector calculus: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of vector calculus: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in vector calculus: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Vector Calculus: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "vector-calculus-latex-formatting",
    "title": "Vector Calculus: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for vector calculus: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Vector Calculus",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Vector Calculus: LaTeX Formatting Guide explains gradients, divergence, curl, line integrals, and coordinate systems.\n\n## Core notation for Vector Calculus\n\nIn vector calculus, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for vector calculus; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n\n## LaTeX patterns that preserve the structure\n\nFor vector calculus: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\int_a^b f(x)\\,dx\n\\nabla\\cdot F\nf(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\n\u0060\u0060\u0060\n\nFor vector calculus, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In vector calculus, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Renderer and export checks\n\nRender one demanding vector calculus example in the actual destination. For vector calculus, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the vector calculus source selectable and editable. For an isolated character in vector calculus, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of vector calculus is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in vector calculus has one defined meaning in the local context.\n- Reopen the exported file for **Vector Calculus: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "vector-calculus-notation-reference",
    "title": "Vector Calculus: Notation Reference",
    "description": "Notation Reference for vector calculus: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Vector Calculus",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Vector Calculus: Notation Reference explains gradients, divergence, curl, line integrals, and coordinate systems.\n\n## Core notation for Vector Calculus\n\nIn vector calculus, the notation usually represents functions, domains, derivatives, integrals, limits, fields, and boundary data. The table below gives a compact starting set for vector calculus; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Definite integral | \u0060\\int_a^b f(x)\\,dx\u0060 | accumulated quantity over an interval |\n| Divergence | \u0060\\nabla\\cdot F\u0060 | local source strength of a vector field |\n| Taylor expansion | \u0060f(x\u002Bh)=\\sum_{k=0}^{m}\\frac{f^{(k)}(x)}{k!}h^k\u002BR_m\u0060 | local polynomial approximation with remainder |\n| Limit | \u0060\\lim_{x\\to a}f(x)=L\u0060 | value approached near a |\n\n## How to read a complete expression\n\nRead \u0060\\int_a^b f(x)\\,dx\u0060 as \u201Caccumulated quantity over an interval.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in vector calculus from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the domain, orientation, and regularity assumptions.\n- Distinguish total, partial, directional, and material derivatives.\n- Include differential elements and integration bounds.\n\n## Cross-checks before reuse\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n\n## Accessibility and portability\n\nKeep the vector calculus source selectable and editable. For an isolated character in vector calculus, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of vector calculus is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Differentiate or integrate a simple test function.\n- Inspect endpoint and singular cases.\n- Compare numerical output with a known analytic case.\n- Confirm every symbol used in vector calculus has one defined meaning in the local context.\n- Reopen the exported file for **Vector Calculus: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "waves-optics-common-errors",
    "title": "Waves and Optics: Common Errors and Verification",
    "description": "Common Errors and Verification for waves and optics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Waves and Optics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Waves and Optics: Common Errors and Verification explains frequency, wavelength, phase, amplitude, interference, and units.\n\n## Core notation for Waves and Optics: Common Errors and Verification\n\nIn waves and optics, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for waves and optics: common errors and verification; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Energy | \u0060E=T\u002BV\u0060 | total mechanical energy as kinetic plus potential energy |\n| Momentum | \u0060p=mv\u0060 | linear momentum in a nonrelativistic model |\n| Ohm law | \u0060V=IR\u0060 | voltage-current-resistance relation |\n| Wave relation | \u0060v=f\\lambda\u0060 | wave speed equals frequency times wavelength |\n\n## Errors that change the meaning\n\n- **Problem:** Adding quantities with incompatible units. **Correction:** write the missing waves and optics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Dropping vector direction when only magnitudes were given. **Correction:** write the missing waves and optics: common errors and verification convention or condition next to the first affected expression.\n- **Problem:** Mixing peak, rms, angular-frequency, and ordinary-frequency values. **Correction:** write the missing waves and optics: common errors and verification convention or condition next to the first affected expression.\n\n## A safer correction workflow\n\nFirst identify the object type in each term of the waves and optics: common errors and verification expression. Then check the waves and optics: common errors and verification notation, dimensions or support, and only then simplify or evaluate it. A visually balanced waves and optics: common errors and verification formula is not evidence that its underlying assumptions are valid.\n\n## Minimal test cases\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n\n## Accessibility and portability\n\nKeep the waves and optics: common errors and verification source selectable and editable. For an isolated character in waves and optics: common errors and verification, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of waves and optics: common errors and verification is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in waves and optics: common errors and verification has one defined meaning in the local context.\n- Reopen the exported file for **Waves and Optics: Common Errors and Verification** and compare it with the editable source.\n"
  },
  {
    "slug": "waves-optics-latex-formatting",
    "title": "Waves and Optics: LaTeX Formatting Guide",
    "description": "LaTeX Formatting Guide for waves and optics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Waves and Optics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Waves and Optics: LaTeX Formatting Guide explains frequency, wavelength, phase, amplitude, interference, and units.\n\n## Core notation for Waves and Optics\n\nIn waves and optics, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for waves and optics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Newton law | \u0060\\sum F=ma\u0060 | net force equals mass times acceleration |\n| Energy | \u0060E=T\u002BV\u0060 | total mechanical energy as kinetic plus potential energy |\n| Momentum | \u0060p=mv\u0060 | linear momentum in a nonrelativistic model |\n| Ohm law | \u0060V=IR\u0060 | voltage-current-resistance relation |\n\n## LaTeX patterns that preserve the structure\n\nFor waves and optics: guide, group arguments explicitly, use named operators, scale delimiters to the enclosed expression, and align rows at the mathematical relation being compared.\n\n\u0060\u0060\u0060latex\n\\sum F=ma\nE=T\u002BV\np=mv\n\u0060\u0060\u0060\n\nFor waves and optics, keep multi-character labels inside \u0060\\text{...}\u0060 or an appropriate operator command. In waves and optics, use braces whenever a subscript, superscript, numerator, denominator, or radical contains more than one token.\n\n## Conventions to state beside the formula\n\n- State the coordinate axes and positive directions.\n- Attach si or other units to every measured quantity.\n- Declare the work, heat, voltage, and current sign conventions.\n\n## Renderer and export checks\n\nRender one demanding waves and optics example in the actual destination. For waves and optics, compare the source, browser output, office-equation output, and exported PDF so grouping, indices, minus signs, and line breaks remain unchanged.\n\n## Accessibility and portability\n\nKeep the waves and optics source selectable and editable. For an isolated character in waves and optics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of waves and optics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in waves and optics has one defined meaning in the local context.\n- Reopen the exported file for **Waves and Optics: LaTeX Formatting Guide** and compare it with the editable source.\n"
  },
  {
    "slug": "waves-optics-notation-reference",
    "title": "Waves and Optics: Notation Reference",
    "description": "Notation Reference for waves and optics: write, format, verify, and publish clear definitions, assumptions, examples, accessible markup, and portable notation.",
    "topic": "Waves and Optics",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Waves and Optics: Notation Reference explains frequency, wavelength, phase, amplitude, interference, and units.\n\n## Core notation for Waves and Optics\n\nIn waves and optics, the notation usually represents physical quantities, vectors, coordinate systems, units, constitutive parameters, and sign conventions. The table below gives a compact starting set for waves and optics; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Ohm law | \u0060V=IR\u0060 | voltage-current-resistance relation |\n| Wave relation | \u0060v=f\\lambda\u0060 | wave speed equals frequency times wavelength |\n| First law | \u0060\\Delta U=Q-W\u0060 | internal-energy change under the stated work sign convention |\n| Newton law | \u0060\\sum F=ma\u0060 | net force equals mass times acceleration |\n\n## How to read a complete expression\n\nRead \u0060V=IR\u0060 as \u201Cvoltage-current-resistance relation.\u201D Identify the outer operation first, then its inputs, index set, conditions, and result type. This prevents a superscript, bar, vertical line, or styled letter in waves and optics from being interpreted by appearance alone.\n\n## Conventions that belong in the notation table\n\n- State the coordinate axes and positive directions.\n- Attach si or other units to every measured quantity.\n- Declare the work, heat, voltage, and current sign conventions.\n\n## Cross-checks before reuse\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n\n## Accessibility and portability\n\nKeep the waves and optics source selectable and editable. For an isolated character in waves and optics, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of waves and optics is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Perform dimensional analysis.\n- Test a zero-force, zero-current, or equilibrium limit.\n- Draw the chosen directions before assigning signs.\n- Confirm every symbol used in waves and optics has one defined meaning in the local context.\n- Reopen the exported file for **Waves and Optics: Notation Reference** and compare it with the editable source.\n"
  },
  {
    "slug": "accessible-spoken-math",
    "title": "Writing Helpful Spoken Descriptions for Equations",
    "description": "Create concise spoken descriptions for equation images and structured math without reading every punctuation mark mechanically.",
    "topic": "Accessibility",
    "updated": "2026-07-26",
    "indexable": false,
    "markdown": "Create concise spoken descriptions for equation images and structured math without reading every punctuation mark mechanically.\n\n## Core notation for Writing Helpful Spoken Descriptions for Equations\n\nIn accessibility, the notation usually represents source notation, rendered output, semantic structure, code points, macros, and destination formats. The table below gives a compact starting set for writing helpful spoken descriptions for equations; define any local variation before the first calculation.\n\n| Concept | Notation | How to read it |\n|---|---|---|\n| Accessible label | \u0060\\text{\u201Cx squared plus one\u201D}\u0060 | plain-language reading when a text alternative is needed |\n| Macro | \u0060\\newcommand{\\vect}[1]{\\mathbf{#1}}\u0060 | reusable semantic notation command |\n| LaTeX fraction | \u0060\\frac{a}{b}\u0060 | structured two-dimensional fraction |\n| Unicode code point | \u0060\\texttt{U\u002B2212}\u0060 | identifier for the mathematical minus sign |\n\n## Practical workflow\n\nStart from \u0060\\text{\u201Cx squared plus one\u201D}\u0060 and write one sentence that says it means \u201Cplain-language reading when a text alternative is needed.\u201D List the objects and assumptions, evaluate a small example, and then move the verified source into the target document or codebase.\n\n## Decisions that must be explicit\n\n- Keep editable source with the rendered result.\n- Use semantic commands for writing helpful spoken descriptions for equations rather than visual spacing tricks.\n- Test the final destination, export path, and assistive-technology reading of the writing helpful spoken descriptions for equations notation.\n\n## Failure checks\n\n- Copying a rendered writing helpful spoken descriptions for equations image when editable notation is required.\n- Using a look-alike Unicode character with different semantics in writing helpful spoken descriptions for equations.\n- Defining writing helpful spoken descriptions for equations macros that hide arguments or conflict with package commands.\n\n## Accessibility and portability\n\nKeep the writing helpful spoken descriptions for equations source selectable and editable. For an isolated character in writing helpful spoken descriptions for equations, Unicode text may be sufficient; for structured expressions, preserve LaTeX, MathML, or a native equation object. When an image of writing helpful spoken descriptions for equations is unavoidable, describe the operation, inputs, conditions, and conclusion rather than listing glyph names.\n\n## Verification checklist\n\n- Copy and paste into plain text.\n- Validate with a second renderer or browser.\n- Inspect keyboard, zoom, PDF, and screen-reader behavior for the writing helpful spoken descriptions for equations example.\n- Confirm every symbol used in writing helpful spoken descriptions for equations has one defined meaning in the local context.\n- Reopen the exported file for **Writing Helpful Spoken Descriptions for Equations** and compare it with the editable source.\n"
  }
]