GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Minor spelling and grammar corrections in README · Issue #34 · PowerShell/ThreadJob

Minor spelling and grammar corrections in README #34

New issue
Copy link
New issue
Copy link
Open
Open
Minor spelling and grammar corrections in README#34
Copy link

Description

@DevOpsJeremy
DevOps Jeremy (DevOpsJeremy)
opened on Jan 30, 2024
Issue body actions

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

Activity

  1. krzydoug commented on Apr 13, 2024

    @krzydoug
    Doug Maurer (krzydoug)
    on Apr 13, 2024
    More actions

    they do not use the remoting serialization system as BackgroundJob jobs do.

    Still needs a slight adjustment. Either add 'same'

    they do not use the same remoting serialization system as BackgroundJob jobs do.

    or

    they do not use the remoting serialization system that BackgroundJob jobs do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.