Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Minor spelling and grammar corrections in README

Offen
  • Stimmt etwas nicht?
#34 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
1/5
Geschätzter Aufwand
Unter einer Stunde
Anfängerfreundlichkeit
38/100
Issue-Typ
Dokumentation
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
powershell
Bereich
documentation

Rechercherichtung

The requested edits are in README.md at lines 5 and 9. Read the surrounding README text, make the two spelling and wording corrections described in the issue, and check that both passages match the proposed versions.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.
Steps to reproduce

This fixes minor spelling/grammar mistakes in the README and has no effect on the functionality.

Line 5
Current

There is no throttling mechanism and so all jobs are started immediately and are all run currently.

The intended word here is 'concurrently'. The distinction is important because concurrent operations is the purpose of this module.

Proposed

There is no throttling mechanism and so all jobs are started immediately and are all run concurrently.

Line 9
Current

ThreadJob jobs will tend to run much faster because there is lower overhead and they do not use the remoting serialization system as BackgroundJob jobs do. And they will use up fewer system resources.

This snippet can be reworded for clarity and to fix a minor issue with parallel structure.

Proposed

ThreadJob jobs will tend to run much faster because there is lower overhead and they do not use the remoting serialization system as BackgroundJob jobs do. Additionally, they consume fewer system resources.

Expected behavior
Line 5:
> There is no throttling mechanism and so all jobs are started immediately and are all run concurrently.

Line 9:
> ThreadJob jobs will tend to run much faster because there is lower overhead and they do not use the remoting serialization system as BackgroundJob jobs do. Additionally, they consume fewer system resources.
Actual behavior
Line 5:
> There is no throttling mechanism and so all jobs are started immediately and are all run currently.

The intended word here is 'concurrently'. The distinction is important because _concurrent_ operations is the purpose of this module.

Line 9:
> ThreadJob jobs will tend to run much faster because there is lower overhead and they do not use the remoting serialization system as BackgroundJob jobs do. And they will use up fewer system resources.

This snippet can be reworded for clarity and to fix a minor issue with parallel structure.
Error details
N/A
Environment data
N/A
Version

2.0.3

Visuals

No response

Vorherrschende Sprache
PowerShell
Sterne
37
Forks
22
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus PowerShell/ThreadJob

Alle Issues in PowerShell/ThreadJob

Ähnliche Issues

Weitere Issues zu Documentation

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.