vmware
diff --git a/‎content/en/docs-v3/Overview/Flavours.md‎
Lines changed: 2 additions & 2 deletions b/‎content/en/docs-v3/Overview/Flavours.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎content/en/docs-v3/Overview/Introduction.md‎
Lines changed: 1 addition & 1 deletion b/‎content/en/docs-v3/Overview/Introduction.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎content/en/docs-v3/administration-guide/changing-the-locale.md‎
Lines changed: 1 addition & 1 deletion b/‎content/en/docs-v3/administration-guide/changing-the-locale.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎content/en/docs-v3/administration-guide/cloud-init-on-photon-os/customizing-a-photon-os-machine-on-ec2.md‎
Lines changed: 3 additions & 3 deletions b/‎content/en/docs-v3/administration-guide/cloud-init-on-photon-os/customizing-a-photon-os-machine-on-ec2.md‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎content/en/docs-v3/administration-guide/cloud-init-on-photon-os/deploy-photon-os-with-cloud-init.md‎
Lines changed: 1 addition & 1 deletion b/‎content/en/docs-v3/administration-guide/cloud-init-on-photon-os/deploy-photon-os-with-cloud-init.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎content/en/docs-v3/administration-guide/cloud-init-on-photon-os/running-a-photon-os-machine-on-gce.md‎
Lines changed: 2 additions & 2 deletions b/‎content/en/docs-v3/administration-guide/cloud-init-on-photon-os/running-a-photon-os-machine-on-gce.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎content/en/docs-v3/administration-guide/managing-network-configuration/netmgr.c.md‎
Lines changed: 1 addition & 1 deletion b/‎content/en/docs-v3/administration-guide/managing-network-configuration/netmgr.c.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎content/en/docs-v3/administration-guide/managing-packages-with-tdnf/adding-a-new-repository.md‎
Lines changed: 2 additions & 2 deletions b/‎content/en/docs-v3/administration-guide/managing-packages-with-tdnf/adding-a-new-repository.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎content/en/docs-v3/administration-guide/managing-packages-with-tdnf/configuration-files-and-repositories.md‎
Lines changed: 2 additions & 2 deletions b/‎content/en/docs-v3/administration-guide/managing-packages-with-tdnf/configuration-files-and-repositories.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎content/en/docs-v3/administration-guide/managing-packages-with-tdnf/standard-syntax-for-tndf/commands.md‎
Lines changed: 1 addition & 1 deletion b/‎content/en/docs-v3/administration-guide/managing-packages-with-tdnf/standard-syntax-for-tndf/commands.md‎
Lines changed: 1 addition & 1 deletion
@@ -5,6 +5,6 @@ weight: 2
 
 Photon OS consists of a minimal version and a full version. 
 
-The minimal version of Photon OS is lightweight container host runtime environment that is suited to managing and hosting containers. The minimal version contains just enough packaging and functionality to manage and modify containers while remaining a fast runtime environment. The minimal version is ready to work with appliances. 
+The minimal version of Photon OS is a lightweight container host runtime environment that is suited to managing and hosting containers. The minimal version contains just enough packaging and functionality to manage and modify containers while remaining a fast runtime environment. The minimal version is ready to work with appliances. 
 
-The Developer version of Photon OS includes additional packages to help you customize the system and create containerized applications. For running containers, the developer version is excessive. The devloper version helps you create, develop, test, and package an application that runs a container. 
+The Developer version of Photon OS includes additional packages to help you customize the system and create containerized applications. For running containers, the developer version is excessive. The developer version helps you create, develop, test, and package an application that runs a container. 
@@ -3,7 +3,7 @@ title: Introduction to Photon OS
 weight: 1
 ---
 
-Photon OS, is an open-source minimalist Linux operating system from VMware that is optimized for cloud computing platforms, VMware vSphere deployments, and applications native to the cloud. 
+Photon OS is an open-source minimalist Linux operating system from VMware that is optimized for cloud computing platforms, VMware vSphere deployments, and applications native to the cloud. 
 
 Photon OS is a Linux container host optimized for vSphere and cloud-computing platforms such as Amazon Elastic Compute and Google Compute Engine. As a lightweight and extensible operating system, Photon OS works with the most common container formats, including Docker, Rocket, and Garden. Photon OS includes a yum-compatible, package-based lifecycle management system called tdnf.
 
 
@@ -5,7 +5,7 @@ weight: 8
 
 You can change the locale if the default locale does not meet your requirements. 
 
-To find the locale, run the the `localectl` command:  
+To find the locale, run the `localectl` command:  
 
     localectl
     System Locale: LANG=en_US.UTF-8
 
@@ -3,7 +3,7 @@ title:  Customizing a Photon OS Machine on EC2
 weight: 5
 ---
 
-You can upload an `ami` image of Photon OS to Amazon Elastic Compute Cloud (EC2) and customize the Photon OS machine by using `cloud-init` with an EC2 data source. The Amazon machine image version of Photon OS is available as a free download on Packages URL at the location `https://packages.vmware.com/photon/`.
+You can upload an `ami` image of Photon OS to Amazon Elastic Compute Cloud (EC2) and customize the Photon OS machine by using `cloud-init` with an EC2 data source. The Amazon machine image version of Photon OS is available as a free download on Packages URL at the location `https://packages.broadcom.com/photon/`.
 
 The `cloud-init` service is commonly used on EC2 to configure the cloud instance of a Linux image. On EC2, `cloud-init` sets the `.ssh/authorized_keys` file to let you log in with a private key from another computer, that is, a computer besides the workstation that you are already using to connect with the Amazon cloud. 
 
@@ -15,7 +15,7 @@ The cloud-config user-data file that appears in the following example contains a
 
 - To work with EC2, obtain Amazon accounts for both AWS and EC2 with valid payment information. If you execute the below examples, you will be charged by Amazon. You must replace the `<placeholders>` for access keys and other account information in the examples with your account information. 
 - Install and set up the Amazon AWS CLI and the EC2 CLI tools, including `ec2-ami-tools`. 
-    For more information, see [Installing the AWS Command Line Interface](http://docs.aws.amazon.com/cli/latest/userguide/installing.html), [Setting Up the Amazon EC2 Command Line Interface Tools on Linux](http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/set-up-ec2-cli-linux.html) and [Setting Up the AMI Tools](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-up-ami-tools.html). 
+    For more information, see [Installing the AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/userguide/installing.html), [Installing the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html) and [Setting Up the AMI Tools](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-up-ami-tools.html). 
 - Create  SSH keys and an RSA user signing certificate and its corresponding private RSA key file.  
 
 ### Procedure 
@@ -91,7 +91,7 @@ The following are the contents of the `user-data.txt` file that `cloud-init` app
 
 You can view the cloud-init output log file on EC2 at `/var/log/cloud-init-output.log`. 
 
-For more information on using cloud-init user data on EC2, see [Running Commands on Your Linux Instance at Launch](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html).
+For more information on using cloud-init user data on EC2, see [Running Commands on Your Linux Instance at Launch](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html).
 
 For more information on how to get Photon OS up and running on EC2 and run a containerized application in the Docker engine, see [Running Photon OS on Amazon Elastic Cloud Compute](../../../installation-guide/run-photon-aws-ec2/).
 
 
@@ -17,7 +17,7 @@ When a cloud instance of Photon OS starts, `cloud-init` requires a data source.
 
 The metadata gives the cloud service provider instructions on how to implement the Photon OS machine in the cloud infrastructure. Metadata typically includes the instance ID and the local host name. 
 
-The user data contains the commands and scripts that Photon OS executes when it starts in the cloud. The user data commonly takes the form of a shell script or a YAML file containing a cloud configuration. The [cloud-init overview](https://launchpad.net/cloud-init) and [cloud-init documentation](https://cloudinit.readthedocs.org/en/latest/) contains information about the types of data sources and the formats for metadata and user data. 
+The user data contains the commands and scripts that Photon OS executes when it starts in the cloud. The user data commonly takes the form of a shell script or a YAML file containing a cloud configuration. The [cloud-init overview](https://launchpad.net/cloud-init) and [cloud-init documentation](https://cloudinit.readthedocs.org/en/latest/) contain information about the types of data sources and the formats for metadata and user data. 
 
 On Photon OS, `cloud-init` is enabled and running by default. You can use the following command to check the status: 
 
 
@@ -11,9 +11,9 @@ The example in this section shows how to create a Photon OS instance on Google C
 
 ### Prerequisites 
 
-- You must have set up a GCE account and are ready to pay Google for its cloud services. The GCE-ready version of Photon OS is licensed as described in the Photon OS [LICENSE guide](https://github.com/vmware/photon/blob/master/LICENSE.md). GCE and other environment-specific Packages are stored in the open using the following URL pattern: `https://packages.vmware.com/photon/<release>/<revision>/gce`
+- You must have set up a GCE account and are ready to pay Google for its cloud services. The GCE-ready version of Photon OS is licensed as described in the Photon OS [LICENSE guide](https://github.com/vmware/photon/blob/master/LICENSE.md). GCE and other environment-specific Packages are stored in the open using the following URL pattern: `https://packages.broadcom.com/photon/<release>/<revision>/gce`
 
-For example, the current GA revision of the 4.0 release would be located at the following URL: [https://packages.vmware.com/photon/4.0/GA/gce/](https://packages.vmware.com/photon/4.0/GA/gce/), and the 3.0 GA version would be located at: [https://packages.vmware.com/photon/3.0/GA/gce/](https://packages.vmware.com/photon/3.0/GA/gce/).
+For example, the current GA revision of the 4.0 release would be located at the following URL: [https://packages.broadcom.com/photon/4.0/GA/gce/](https://packages.broadcom.com/photon/4.0/GA/gce/), and the 3.0 GA version would be located at: [https://packages.broadcom.com/photon/3.0/GA/gce/](https://packages.broadcom.com/photon/3.0/GA/gce/).
 
     The GCE-ready image of Photon OS contains packages and scripts that prepare it for the Google cloud to save you time as you implement a compute cluster or develop cloud applications. The GCE-ready version of Photon OS adds the following packages to the [packages installed with the minimal version](https://github.com/vmware/photon/blob/master/common/data/packages_minimal.json): 
 
 
@@ -1008,7 +1008,7 @@ Delete a server from the DNS servers list associated with an interface.
 
 **Description**
 
-Get the the DNS servers list for the interface.
+Get the DNS servers list for the interface.
 
 **Declaration**
 ~~~~
 
@@ -16,12 +16,12 @@ On Photon OS, the existing repositories appear in the `/etc/yum.repos.d` directo
 	photon-updates.repo
 	photon.repo 
 
-To view the the format and information that a new repository configuration file should contain, see one of the `.repo` files. The following is an example:
+To view the format and information that a new repository configuration file should contain, see one of the `.repo` files. The following is an example:
 
 	cat /etc/yum.repos.d/lightwave.repo
 	[lightwave]
 	name=VMware Lightwave 1.0(x86_64)
-	baseurl=https://packages.vmware.com/photon/1.0/lightwave
+	baseurl=https://packages.broadcom.com/photon/1.0/lightwave
 	gpgkey=file:///etc/pki/rpm-gpg/VMWARE-RPM-GPG-KEY
 	gpgcheck=1
 	enabled=1
 
@@ -25,7 +25,7 @@ The following repositories appear in /etc/yum.repos.d/ with `.repo` file extensi
 	photon.repo 
 
 
-You can list the the repositories by using the `tdnf repolist` command. Tdnf filters the results with `enabled`, `disabled`, and `all`. Running the command without specifying an argument returns the enabled repositories:  
+You can list the repositories by using the `tdnf repolist` command. Tdnf filters the results with `enabled`, `disabled`, and `all`. Running the command without specifying an argument returns the enabled repositories:  
 
 	tdnf repolist
 	repo id             repo name                               status
@@ -38,7 +38,7 @@ The `photon-iso.repo`, however, does not appear in the list of repositories beca
 
 	cat /etc/yum.repos.d/photon-iso.repo
 	[photon-iso]
-	name=VMWare Photon Linux 2.0(x86_64)
+	name=VMware Photon Linux 2.0(x86_64)
 	baseurl=file:///mnt/cdrom/RPMS
 	gpgkey=file:///etc/pki/rpm-gpg/VMWARE-RPM-GPG-KEY
 	gpgcheck=1
 
@@ -144,7 +144,7 @@ To list enabled repositories, run the following command:
 
 	Total installed size: 210.15 M
 
-**remove**: This command removes a package. When removing a package, tdnf by default also removes dependencies that are no longer used if they were was installed by tdnf as a dependency without being explicitly requested by a user. You can modify the dependency removal by changing the `clean_requirements_on_remove` option in /etc/tdnf/tdnf.conf to `false`. 
+**remove**: This command removes a package. When removing a package, tdnf by default also removes dependencies that are no longer used if they were installed by tdnf as a dependency without being explicitly requested by a user. You can modify the dependency removal by changing the `clean_requirements_on_remove` option in /etc/tdnf/tdnf.conf to `false`. 
 
 	tdnf remove packagename