LanguageTool Community

<< return to list of rules

Rule "SV agreement, subjects containing clauses - sing."

This is one of many errors that LanguageTool can detect.

Description: SV agreement, subjects containing clauses - sing.
By default, this rule is not active in LanguageTool
Message: Possible agreement error detected: the verb form '\18' does not seem to match the subject.
Category: Grammar (ID: GRAMMAR)
Incorrect sentences
that this rule can detect:
  • The code that throws the error seem to actually test for both UrlReadingCondition as well as Condition, but the error message is always the same.
    Correction suggestion: seems, seemed
  • Any reason that calling this built-in method always give debug messages?
    Correction suggestion: gives, gave
  • The drunk driver who ran the light fatally injure the pedestrian in the crosswalk.
    Correction suggestion: injures, injured
  • The tall woman that I met yesterday manage the department.
    Correction suggestion: manages, managed
  • The tall woman that I actually met yesterday manage the department.
    Correction suggestion: manages, managed
  • The tall woman that I didn't meet yesterday manage the department.
    Correction suggestion: manages, managed
  • The magician who performed at my previous birthdays ask my mom out on a date.
    Correction suggestion: asks, asked
  • The note that was given to the girls have weird stuff written on it.
    Correction suggestion: has, had
  • The note that she hurriedly gave to the girls have weird stuff written on it.
    Correction suggestion: has, had
Correct sentences
for comparison:
  • (That third item makes me think alternative diasporafoundation.org “front pages”, for different audiences, might be valuable.)
  • @goob Before doing anything like that we should implement easy steps for podmins to remove a user which signed up on that specific pod including all posts and comments and all posts and comments already send to other pods.
  • The fact that people are worried things break because changes in diaspora, probably means that there's an issue with API stability in the diaspora project itself.
  • One thing that might help you figure out what that call tree looks like after `SoapMessageDispatcher` is if you mark the Transaction in question as a Key Transaction (link) and then run an X-Ray session on it.
  • The last piece which is what I suspect might be hitting you is: does your proxy allow unauthenticated connections or does it require all sessions to be authenticated.
  • One thing that made me stop looking into it is that the api key is exposed in the tool.
  • * POWERFUL PLUG: The only Z-Wave Plug that lets you safely control and monitor heavy-duty 110V appliances from your Z-Wave smart home system.
  • I do have two virtual switches in ST so I can do things like “Turn on Goodnight,” which runs a routine and shuts off all the lights.
  • My choices at first was Atom… feature rich, extendable with plugins, the same environment for all employees, no matter which platform they choose to work on.
  • One other thing that helps in a case like this is to notice the cogwheel.
  • The sensor that is not working I have to wake up everyday.
  • A troop that appears like its gonna randomly scramble your team.
  • Anyone that does not believe me come to Alaska and see for yourself!
  • A spell that has its main effects trigger on death has no place for ab empowered troop unless the damage is extremely high, has a bonus multiplier, or other secondary effect.
  • Wonder which much needed arcane colors will we get this week.
  • Even if they dev never talk about it, the fact that the troops exist will always imply a possible plan of future kingdoms for those troops.
  • I did the challenges of 4 kingdoms when I just started, as in low level and low cards, cuz that was easier then explore with the cards I had.
  • For reference, you can use our nifty tool: go.atlassian.com/ac1 which scaffolds a static connect app that you can use to play around.
ID: SV_AGREEMENT_CLAUSES_SINGULAR [3]
Version: 6.6-SNAPSHOT (2024-11-21 22:33:10 +0100)