Fix typo in FiddlerCore startup configuration documentation

Open Beginner friendly
#37 0 comments 0 reactions 0 assignees View on GitHub

@CatFortman is already working on this.

Since Sep 21, 2026.

  • #36 by @CatFortman — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
95/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
documentation

Research direction

Open basic-usage/configuration.md and read the “Startup configuration” section. Correct the misspelled type name to FiddlerCoreStartupSetting and check that the example text remains consistent with FiddlerCoreStartupSettingsBuilder; the issue identifies no test to run.

Written by the indexing model from the issue text.

Description

Summary

The startup configuration documentation for FiddlerCore contains a typo in the class name used in the example text.

Affected area

  • File: basic-usage/configuration.md
  • Section: ## Startup configuration

Problem

The docs currently describe the configuration object as FiddlerCoreStartupSettting instead of FiddlerCoreStartupSetting.

This appears in the text explaining how to configure FiddlerCore via FiddlerCoreStartupSettingsBuilder and is inconsistent with the actual type name used by the API.

Expected behavior

The documentation should refer to the correct type name:

FiddlerCoreStartupSetting

Suggested fix

Update the documentation wording to match the actual API surface and keep the startup configuration example accurate.

Dominant language
CSS
Stars
17
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.