A page can look almost right while its source contains a mismatched tag. Linting helps locate that source problem; the rendered page still needs a separate check after the repair.
Turn on linting and reveal its results
On Windows, open Edit > Preferences. On macOS, use Dreamweaver > Preferences. Choose Linting, select Enable Linting, and apply the setting. Check the On edit linting preference if you want feedback while typing. Dreamweaver supports linting for HTML, CSS, Dreamweaver templates, and JavaScript.
If the result panel is hidden, use Window > Results > Output or Shift+F6. Read both the message and the indicated source line. A message can identify where the parser became confused rather than where you first made the mistake.
Repair a small section before changing the rule set
Consider this original broken practice fragment:
<section>
<h2>Equipment return</h2>
<p>Leave the key at reception.</div>
</section>
The paragraph opens with <p> and closes with </div>. Its intended replacement is:
<section>
<h2>Equipment return</h2>
<p>Leave the key at reception.</p>
</section>
Keep a copy of the original file, make that one repair, and save. Recheck Output instead of editing every highlighted line at once. Later messages may describe consequences of the same broken structure. The exact wording and number of messages depend on the installed rule set; this example does not require one particular diagnostic string.
In the browser, confirm that the instruction remains inside the equipment-return section. Follow any affected link and check neighboring content. A clean lint result alone does not establish that the page says or does the right thing.
When an intentional pattern triggers a warning
Adobe documents separate configuration files: DW.htmlhintrc for HTML, DW.csslintrc for CSS, and .eslintrc for JavaScript. Open the relevant rule set through Preferences > Linting > Edit Rule Set. Older Dreamweaver versions use different JavaScript configuration, so preserve the file your installation actually opens.
Before changing a rule, record its name and the code it flags. Confirm whether the code is valid for your project's target environment. Avoid disabling a broad check merely to clear the status indicator. A formatting preference and an unpaired HTML tag call for different decisions.
Separate syntax, loading, and behavior
If linting reports no relevant error but an image is missing, inspect the requested image path. If a button does nothing, inspect its event handler and the browser Console. These failures need evidence from the running page. HTML DevTools checks help trace what the browser received.
Finish with the saved source, a fresh lint result, and the affected page open together. Verify the repaired instruction in its surrounding section before handing the file back.