Merge lp:~dannf/pyjuju/docs-other-providers-than-ec2 into lp:~charm-contributors/pyjuju/docs

[dann frazier]

fix some language that apparently predates the MAAS/openstack providers

[Clint Byrum (clint-fewbar)]

LGTM, thanks!

review: Approve

[Clint Byrum (clint-fewbar)]

Wrong target, already merged to the right one though.

Unmerged revisions

73. By dann frazier on 2012-10-29

Remove out-of-date text referring to EC2 is as the only juju provider

=== modified file 'source/expose-services.rst'
--- source/expose-services.rst	2011-12-09 13:32:33 +0000
+++ source/expose-services.rst	2012-10-29 12:57:41 +0000
@@ -9,8 +9,8 @@
 Service exposing works by opening appropriate ports in the firewall of
 the cloud provider. Because service exposing is necessarily tied to
 the underlying provider, juju manages all aspects of
-exposing. Such management ensures that a charm can work with other
-cloud providers besides EC2, once support for them is implemented.
+exposing. Such management ensures that a charm can work with any of the
+supported cloud providers.
 
 juju provides the ``juju expose`` command to expose a service.
 For example, you might have deployed a ``my-wordpress`` service, which