Fix grammar

odinserj · odinserj · commit 0bb340b02717 · 2016-08-11T12:11:20.000+03:00
diff --git a/README.md b/README.md
@@ -1,7 +1,7 @@
 Hangfire Official Site
 ====================
 
-This repository hosts the Hangfire project organization pages. [Jekyll](https://github.com/mojombo/jekyll) is being used to manage page transformation in accordance with GitHub Pages usage.
+This repository hosts the Hangfire project organization pages. [Jekyll](https://github.com/mojombo/jekyll) is used to manage page transformation in accordance with GitHub Pages usage.
 
 [Visit Hangfire on GitHub.](https://github.com/HangfireIO/Hangfire)
 
diff --git a/_posts/2014-05-02-hangfire-0.8-released.md b/_posts/2014-05-02-hangfire-0.8-released.md
@@ -56,7 +56,7 @@ Elmah library author and contributors conducted a deep investigation on a topic
 2. The location element's path attribute carries the same value as the path attribute of the handler registrations. Unfortunately, it has to be repeated so if you change one, the others must be updated to match.
 3. The authorization element is where the authorization rules go and where you will want to selectively grant access.
 
-So, starting from this version, Hangfire Monitor HTTP handler is being registered under the `location` tag:
+So, starting from this version, Hangfire Monitor HTTP handler is registered under the `location` tag:
 
 {% highlight xml %}
 <location path="hangfire.axd" inheritInChildApplications="false">
diff --git a/_posts/2014-05-17-hangfire-0.8.1-released.md b/_posts/2014-05-17-hangfire-0.8.1-released.md
@@ -25,7 +25,7 @@ As always, the new version of [Hangfire](http://hangfire.io) can be installed vi
 
 ### Deleting jobs
 
-There is a new state – `DeletedState`, and some methods to perform the deletion – `BackgroundJob.Delete` and `IBackgroundJobClient.Delete`. When you are using these methods, a job is not being actually deleted, there is only state transition. Jobs in the deleted state expire after some delay (as succeeded jobs).
+There is a new state – `DeletedState`, and some methods to perform the deletion – `BackgroundJob.Delete` and `IBackgroundJobClient.Delete`. When you are using these methods, a job is not actually deleted, there is only state transition. Jobs in the deleted state expire after some delay (as succeeded jobs).
 
 The operation does not provides guarantee that the job will not be performed. If you deleting a job that is performing right now, it will be performed anyway, despite of calls to delete methods.
 
diff --git a/_posts/2014-05-21-hangfire-0.8.2-released.md b/_posts/2014-05-21-hangfire-0.8.2-released.md
@@ -19,7 +19,7 @@ You are also able to select all jobs in one click. Many thanks to GitHub Issues
 
 ### Additional metrics
 
-When you write the code, it is important to have an instrument to measure the performance time. ASP.NET has different diagnostic tools for this task – [Glimpse](http://getglimpse.com), [MiniProfiler](http://miniprofiler.com) and other useful ones. But they are aimed to provide information about requests only, and almost useless for background jobs – they are being executed outside of a request.
+When you write the code, it is important to have an instrument to measure the performance time. ASP.NET has different diagnostic tools for this task – [Glimpse](http://getglimpse.com), [MiniProfiler](http://miniprofiler.com) and other useful ones. But they are aimed to provide information about requests only, and almost useless for background jobs – they are executed outside of a request.
 
 I've implemented simple diagnostic feature (and not the replacement to full-stack performance profilers, such as [dotTrace](http://www.jetbrains.com/profiler/)) for Hangfire Monitor, and now you are able to see the following timings in Hangfire Monitor:
 
@@ -34,7 +34,7 @@ These metrics are added to the `SucceededState`, so they are also available to s
 
 ### DisableConcurrentExecution filter
 
-This filter places a distributed lock in the beginning of a method performance and releases it after it was completed using the `IServerFilter` interface. The type and method name are being used as a locking resource. Each storage uses its own distributed lock implementation:
+This filter places a distributed lock in the beginning of a method performance and releases it after it was completed using the `IServerFilter` interface. The type and method name are used as a locking resource. Each storage uses its own distributed lock implementation:
 
 * SQL Server uses `sp_getapplock` stored procedure;
 * Redis implementation uses the technique described in its [documentation](http://redis.io/commands/setnx).
diff --git a/_posts/2014-06-07-hangfire-0.9-released.md b/_posts/2014-06-07-hangfire-0.9-released.md
@@ -15,7 +15,7 @@ This version brings incredibly easy method of scheduling and running recurring j
 RecurringJob.AddOrUpdate(() => Console.Write("Easy!"), Cron.Daily);
 {% endhighlight %}
 
-The `Cron` class provides different easy to use methods and overloads to set up recurring jobs on a minutely, hourly, weekly, monthly and yearly basis. It is also possible to use more complex [CRON expressions](http://en.wikipedia.org/wiki/Cron#CRON_expression), since the [`NCrontab`](https://code.google.com/p/ncrontab/) library is being used to perform scheduling logic.
+The `Cron` class provides different easy to use methods and overloads to set up recurring jobs on a minutely, hourly, weekly, monthly and yearly basis. It is also possible to use more complex [CRON expressions](http://en.wikipedia.org/wiki/Cron#CRON_expression), since the [`NCrontab`](https://code.google.com/p/ncrontab/) library is used to perform scheduling logic.
 
 {% highlight csharp %}
 RecurringJob.AddOrUpdate(
diff --git a/_posts/2014-11-15-hangfire-pro.md b/_posts/2014-11-15-hangfire-pro.md
@@ -16,7 +16,7 @@ As an ASP.NET developer, I always wanted to have something simple to handle scen
 
 But every time I faced Windows Services, message queues and other difficult-to-understand problems and hard-to-maintain solutions, my head exploded into a billion pieces. At the same time I looked at Rails' [Sidekiq](http://sidekiq.org) and wished to have a simple .NET alternative for background job processing. That is why I began to develop [Hangfire](http://hangfire.io) (yep, just for the loader).
 
-Slightly more than a year passed from the [first commit](https://github.com/HangfireIO/Hangfire/tree/d58a619ebc487ef28bef8c6e7f4df8e1d51ee8c5) and [first version](https://www.nuget.org/packages/Hangfire/0.1.0) of Hangfire. This was my first open-source project that is being used more than in one organization, and it was an amazing experience for me to grow a project from scratch. I'm glad to see more and more people coming to the project and giving positive ratings and unvaluable feedback.
+Slightly more than a year passed from the [first commit](https://github.com/HangfireIO/Hangfire/tree/d58a619ebc487ef28bef8c6e7f4df8e1d51ee8c5) and [first version](https://www.nuget.org/packages/Hangfire/0.1.0) of Hangfire. This was my first open-source project that is used more than in one organization, and it was an amazing experience for me to grow a project from scratch. I'm glad to see more and more people coming to the project and giving positive ratings and unvaluable feedback.
 
 I want to keep Hangfire project as free as possible, but eliminate the most dangerous risk – the absence of time. There are many things to be done, including problems, new features, documentation, and I want to do them in a reasonable time.
 
@@ -36,7 +36,7 @@ I understand that this step breaks your expectations, and I'm sorry for this. Th
 
 [Most](https://github.com/HangfireIO/Hangfire/issues/122) [wanted](https://github.com/HangfireIO/Hangfire/issues/195) features were implemented in the next version of Hangfire.Redis package. It now includes:
 
-* **Compatibility with ServiceStack 4.0** libraries. It still uses ServiceStack v3 libraries, but `ILMerge /internalize` utility is being used to merge them into Hangfire.Redis assembly. So, you can use either Service v3 or v4 in your projects.
+* **Compatibility with ServiceStack 4.0** libraries. It still uses ServiceStack v3 libraries, but `ILMerge /internalize` utility is used to merge them into Hangfire.Redis assembly. So, you can use either Service v3 or v4 in your projects.
 * **Configurable prefix for keys**. You can use now the same database for different environments by setting corresponding prefix for keys in the `RedisStorageOptions.Prefix` property.
 
 ### Hangfire Pro Today
diff --git a/_posts/2015-01-29-hangfire-1.3.3-released.md b/_posts/2015-01-29-hangfire-1.3.3-released.md
@@ -7,11 +7,11 @@ redirect_from:
 - /2015/01/29/hangfire-1.3.3-released.html
 ---
 
-This is a correcting release. Fixed a bug related to MSMQ or RabbitMQ extensions, when enqueued job is not being processed and "stucked" in the *Enqueued* state indefinitely until we retry it manually.
+This is a correcting release. Fixed a bug related to MSMQ or RabbitMQ extensions, when enqueued job is not processed and "stucked" in the *Enqueued* state indefinitely until we retry it manually.
 
 ### Release Notes
 
-* **Fixed** – Enqueued job is not being processed with MSMQ or RabbitMQ.
+* **Fixed** – Enqueued job is not processed with MSMQ or RabbitMQ.
 
 Please see the corresponding [GitHub Release](https://github.com/HangfireIO/Hangfire/releases/tag/v1.3.3) for the details.
 
diff --git a/_posts/2015-04-13-hangfire-1.4.0.md b/_posts/2015-04-13-hangfire-1.4.0.md
@@ -40,7 +40,7 @@ Time zone support has been added for recurring jobs. It is based on BCL's `TimeZ
     <span class="string">"15 08 * * *"</span>, 
     <span class="type">TimeZoneInfo</span>.FindSystemTimeZoneById(<span class="string">"Hawaiian Standard Time"</span>));</pre>
 
-By default, UTC is being used to schedule recurring jobs, but this will be changed in 2.0 release to correspond other default values of other schedulers. Please note that time zone identifiers don't match between Windows and non-Windows machines.
+By default, UTC is used to schedule recurring jobs, but this will be changed in 2.0 release to correspond other default values of other schedulers. Please note that time zone identifiers don't match between Windows and non-Windows machines.
 
 ### Continuations
 
diff --git a/_posts/2016-08-05-hangfire-1.6.2.md b/_posts/2016-08-05-hangfire-1.6.2.md
@@ -4,7 +4,7 @@ author: odinserj
 category: release
 ---
 
-This correcting release contains important fixes for SQL Server and MSMQ integrations, as well as some cosmetic changes to the Dashboard UI. Major blocking problem was resolved, when using Hangfire with SQL Server, that may cause a lot of blocking records in the `State` table, preventing background processing from working flawlessly, when expired records are being removed from a database – Database Engine didn't use the right index during the query performance.
+This correcting release contains important fixes for SQL Server and MSMQ integrations, as well as some cosmetic changes to the Dashboard UI. Major blocking problem was resolved, when using Hangfire with SQL Server, that may cause a lot of blocking records in the `State` table, preventing background processing from working flawlessly, when expired records are removed from a database – Database Engine didn't use the right index during the query performance.
 
 #### Hangfire.Core
 
diff --git a/downloads.md b/downloads.md
@@ -36,7 +36,7 @@ The Package Manage Console can be opened in Visual Studio through `Tools` &rarr;
 
 ## Continuous Integration Feed
 
-Can't wait for a new release? Not a problem as there is a continuous integration feed for Hangfire packages hosted in [AppVeyor](http://www.appveyor.com/). After each successful commit to the `master` or `dev` branches or any open pull request based on these branches, pre-release packages are being pushed to the feed automatically. Here is its url:
+Can't wait for a new release? Not a problem as there is a continuous integration feed for Hangfire packages hosted in [AppVeyor](http://www.appveyor.com/). After each successful commit to the `master` or `dev` branches or any open pull request based on these branches, pre-release packages are pushed to the feed automatically. Here is its url:
 
     https://ci.appveyor.com/nuget/hangfire
 
diff --git a/features.md b/features.md
@@ -78,17 +78,17 @@ public class EmailService
 BackgroundJob.Enqueue<EmailService>(x => x.Send());
 {% endhighlight %}
 
-When a worker sees that the given method is an instance-method, it will activate its class first. By default, the Activator.CreateInstace method is being used, so only classes with default constructors are supported by default. But you can plug in your IoC container and pass the dependencies through the constructor.
+When a worker sees that the given method is an instance-method, it will activate its class first. By default, the `Activator.CreateInstace` method is used, so only classes with default constructors are supported by default. But you can plug in your IoC container and pass the dependencies through the constructor.
 
 ### Culture capturing
 
-When you marshal your method invocation into another execution context, you should be able to preserve some environment settings. Some of them – Thread.CurrentCulture and Thread.CurrentUICulture are automatically being captured for you.
+When you marshal your method invocation into another execution context, you should be able to preserve some environment settings. Some of them – `Thread.CurrentCulture` and `Thread.CurrentUICulture` are automatically captured for you.
 
-It is done by the PreserveCultureAttribute class that is applied to all of your methods by default.
+It is done by the `PreserveCultureAttribute` class that is applied to all of your methods by default.
 
 ### Cancellation tokens
 
-Hangfire can tell your methods were aborted or canceled due to shutdown event, so you can stop them gracefully using job cancellation tokens that are similar to the regular CancellationToken class.
+Hangfire can tell your methods were aborted or canceled due to shutdown event, so you can stop them gracefully using job cancellation tokens that are similar to the regular `CancellationToken` class.
 
 {% highlight csharp %}
 public void Method(IJobCancellationToken token)
diff --git a/overview.md b/overview.md
@@ -42,15 +42,15 @@ Hangfire supports all kind of background tasks – short-running and long-runnin
     <div class="col-md-6">
         <h4>Fire-and-forget</h4>
         <p>
-            These jobs are being executed <strong>only once</strong> and almost <strong>immediately</strong> after they fired.
+            These jobs are executed <strong>only once</strong> and almost <strong>immediately</strong> after they fired.
         </p>
 <pre><span class="keywd">var</span> jobId = <span class="type">BackgroundJob</span>.Enqueue(
     () => <span class="type">Console</span>.WriteLine(<span class="string">"Fire-and-forget!"</span>));</pre>
     </div>
     <div class="col-md-6">
         <h4>Delayed</h4>
         <p>
-            Delayed jobs are being executed <strong>only once</strong> too, but not immediately – only after the <strong>specified time interval</strong>.
+            Delayed jobs are executed <strong>only once</strong> too, but not immediately – only after the <strong>specified time interval</strong>.
         </p>
 <pre><span class="keywd">var</span> jobId = <span class="type">BackgroundJob</span>.Schedule(
     () => <span class="type">Console</span>.WriteLine(<span class="string">"Delayed!"</span>),
@@ -130,7 +130,7 @@ Hangfire supports all kind of background tasks – short-running and long-runnin
 
 ### Backed by Persistent Storage
 
-Background jobs are very important part of an application and Hangfire ensures that any job is being performed **at least once**. To persist background job information between application restarts, all the information is being saved in your favorite persistent storage. Currently the following storages are supported:
+Background jobs are very important part of an application and Hangfire ensures that any job is performed **at least once**. To persist background job information between application restarts, all the information is saved in your favorite persistent storage. Currently the following storages are supported:
 
 <table class="text-center supported-storages">
     <tr>
@@ -196,7 +196,7 @@ You are also able to retry any background job manually through the programming c
 
 ### Scale as You Grow
 
-You are not required to make any architecture decisions to start using Hangfire. You can begin with simple setup, where background processing is being implemented on the web application side.
+You are not required to make any architecture decisions to start using Hangfire. You can begin with simple setup, where background processing is implemented on the web application side.
 
 Later, when you face with performance problems, you can separate the processing among different processes or servers – Hangfire uses distributed locks to handle synchronization issues.
 
diff --git a/pricing/index.md b/pricing/index.md
@@ -174,7 +174,7 @@ redirect_from: /subscriptions/
 
             <h3>How many licenses do I need to buy?</h3>
             <p>
-                Each license allows you to embed Hangfire Pro within software that is being developed by one company/organization.
+                Each license allows you to embed Hangfire Pro within software that is developed by one company/organization.
             </p>
         </div>
         <div class="col-md-6">
