Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Minor spelling and grammar corrections in README

Abierto
  • ¿Algo no está bien?
#34 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
38/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
powershell
Área
documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
PowerShell
Estrellas
37
Forks
22
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de PowerShell/ThreadJob

Todos los issues de PowerShell/ThreadJob

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.