Remove more "CodeReady Container" occurrences

praveenkumar · Mar 23, 2023 · a1db0ce · a1db0ce
1 parent f9ae5eb
commit a1db0ce
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 8 deletions.
diff --git a/developing.adoc b/developing.adoc
@@ -1,6 +1,6 @@
 
 
-= Developing CodeReady Containers
+= Developing CRC
 
 [[developing-overview]]
 == Overview
@@ -39,7 +39,7 @@ Do not keep the source code in your `$GOPATH`, as link:https://github.com/golang
 [[dependency-management]]
 == Dependency management
 
-CodeReady Containers uses link:https://github.com/golang/go/wiki/Modules[Go modules] for dependency management.
+CRC uses link:https://github.com/golang/go/wiki/Modules[Go modules] for dependency management.
 
 For more information, see the following:
 
@@ -96,11 +96,11 @@ $ make generate_mocks
 [[running-e2e-tests]]
 == Running e2e tests
 
-We have automated e2e tests which keep CodeReady Containers in shape.
+We have automated e2e tests which keep CRC in shape.
 
 [[intro-to-e2e-testing]]
 === Introduction
-End-to-end (e2e) tests borrow code from link:http://github.com/crc-org/clicumber[Clicumber] package to provide basic functionality for testing CLI binaries. This facilitates running commands in a persistent shell instance (`bash`, `tcsh`, `zsh`, Command Prompt, or PowerShell), assert its outputs (standard output, standard error, or exit code), check configuration files, and so on. The general functionality of Clicumber is then extended by CodeReady Containers specific test code to cover the whole functionality of CodeReady Containers.
+End-to-end (e2e) tests borrow code from link:http://github.com/crc-org/clicumber[Clicumber] package to provide basic functionality for testing CLI binaries. This facilitates running commands in a persistent shell instance (`bash`, `tcsh`, `zsh`, Command Prompt, or PowerShell), assert its outputs (standard output, standard error, or exit code), check configuration files, and so on. The general functionality of Clicumber is then extended by CRC specific test code to cover the whole functionality of CRC.
 
 [[how-to-run-e2e-tests]]
 === How to run

diff --git a/packaging/rpm/crc.spec.in b/packaging/rpm/crc.spec.in
@@ -13,7 +13,7 @@ Version:                __VERSION__
 %global __os_install_post /usr/lib/rpm/brp-compress %{nil}
 
 %global common_description %{expand:
-CodeReady Container's executable}
+CRC's main executable}
 
 
 %global golicenses    LICENSE
@@ -22,7 +22,7 @@ CodeReady Container's executable}
 
 Name:           %{goname}
 Release:        1%{?dist}
-Summary:        CodeReady Container's executable
+Summary:        CRC's main executable
 License:        APL 2.0
 ExcludeArch:    armv7hl i686
 URL:            %{gourl}

diff --git a/usage-data.adoc b/usage-data.adoc
@@ -1,14 +1,14 @@
 = Usage data
 
-The following table describes the opt-in usage data collected by CodeReady Containers.
+The following table describes the opt-in usage data collected by CRC.
 
 .Data points
 |===
 |Occasion          | Data                         | Type 
 
 |*Install*         | Host OS                      |
 |                  | Host OS version              |
-|                  | CodeReady Containers version |
+|                  | CRC version                  |
 |                  | Installed using installers   | true/false
 
 |*Setup*           | Error message                |