wording

docs/getting-started/brokers/couchdb.rst

@@ -7,7 +7,7 @@
 .. admonition:: Experimental Status
 
     The CouchDB transport is in need of improvements in many areas and there
-    are several open bugs.  Sadly we don't have the resources or funds
+    are several open bugs.  Unfortunately we don't have the resources or funds
     required to improve the situation, so we're looking for contributors
     and partners willing to help.
 

docs/getting-started/brokers/django.rst

@@ -7,7 +7,7 @@
 .. admonition:: Experimental Status
 
     The Django database transport is in need of improvements in many areas
-    and there are several open bugs.  Sadly we don't have the resources or funds
+    and there are several open bugs.  Unfortunately we don't have the resources or funds
     required to improve the situation, so we're looking for contributors
     and partners willing to help.
 

docs/getting-started/brokers/mongodb.rst

@@ -7,7 +7,7 @@
 .. admonition:: Experimental Status
 
     The MongoDB transport is in need of improvements in many areas and there
-    are several open bugs.  Sadly we don't have the resources or funds
+    are several open bugs.  Unfortunately we don't have the resources or funds
     required to improve the situation, so we're looking for contributors
     and partners willing to help.
 

docs/getting-started/brokers/sqlalchemy.rst

@@ -7,7 +7,7 @@
 .. admonition:: Experimental Status
 
     The SQLAlchemy transport is unstable in many areas and there are
-    several issues open.  Sadly we don't have the resources or funds
+    several issues open.  Unfortunately we don't have the resources or funds
     required to improve the situation, so we're looking for contributors
     and partners willing to help.
 

docs/getting-started/brokers/sqs.rst

@@ -7,7 +7,7 @@
 .. admonition:: Experimental Status
 
     The SQS transport is in need of improvements in many areas and there
-    are several open bugs.  Sadly we don't have the resources or funds
+    are several open bugs.  Unfortunately we don't have the resources or funds
     required to improve the situation, so we're looking for contributors
     and partners willing to help.
 

docs/history/changelog-3.0.rst

@@ -558,7 +558,7 @@ If you're looking for versions prior to 3.0.x you should go to :ref:`history`.
 
     execv was only enabled when transports other than amqp/redis was used,
     and it's there to prevent deadlocks caused by mutexes not being released
-    before the process forks.  Sadly it also changes the environment
+    before the process forks.  Unfortunately it also changes the environment
     introducing many corner case bugs that is hard to fix without adding
     horrible hacks.  Deadlock issues are reported far less often than the
     bugs that execv are causing, so we now disable it by default.

docs/internals/guide.rst

@@ -179,8 +179,8 @@ can't co-exist in the same process space, this later posed a problem
 for using Celery with frameworks that doesn't have this limitation.
 
 Therefore the app concept was introduced.  When using apps you use 'celery'
-objects instead of importing things from celery submodules, this sadly
-also means that Celery essentially has two API's.
+objects instead of importing things from celery submodules, this
+(unfortunately) also means that Celery essentially has two API's.
 
 Here's an example using Celery in single-mode:
 

docs/userguide/extending.rst

@@ -698,8 +698,8 @@ and then after installation, read from the system using the :mod:`pkg_resources`
 
 Celery recognizes ``celery.commands`` entry-points to install additional
 subcommands, where the value of the entry-point must point to a valid subclass
-of :class:`celery.bin.base.Command`.  Sadly there is limited documentation,
-but you can find inspiration from the various commands in the
+of :class:`celery.bin.base.Command`.  There is limited documentation,
+unfortunately, but you can find inspiration from the various commands in the
 :mod:`celery.bin` package.
 
 This is how the Flower_ monitoring extension adds the :program:`celery flower` command,

docs/whatsnew-3.1.rst

@@ -270,7 +270,7 @@ Caveats
 Django supported out of the box
 -------------------------------
 
-Celery 3.0 introduced a shiny new API, but sadly did not
+Celery 3.0 introduced a shiny new API, but unfortunately did not
 have a solution for Django users.
 
 The situation changes with this version as Django is now supported