Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Minor spelling and grammar corrections in README

Aperta
  • Qualcosa non va?
#34 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
38/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
powershell
Ambito
documentation

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
PowerShell
Stelle
37
Fork
22
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PowerShell/ThreadJob

Tutte le issue di PowerShell/ThreadJob

Issue simili

Altre issue su Documentation

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.