Skip to content

Commit a1db0ce

Browse files
cfergeaupraveenkumar
authored andcommitted
Remove more "CodeReady Container" occurrences
1 parent f9ae5eb commit a1db0ce

File tree

3 files changed

+8
-8
lines changed

3 files changed

+8
-8
lines changed

developing.adoc

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11

22

3-
= Developing CodeReady Containers
3+
= Developing CRC
44

55
[[developing-overview]]
66
== Overview
@@ -39,7 +39,7 @@ Do not keep the source code in your `$GOPATH`, as link:https://github.com/golang
3939
[[dependency-management]]
4040
== Dependency management
4141

42-
CodeReady Containers uses link:https://github.com/golang/go/wiki/Modules[Go modules] for dependency management.
42+
CRC uses link:https://github.com/golang/go/wiki/Modules[Go modules] for dependency management.
4343

4444
For more information, see the following:
4545

@@ -96,11 +96,11 @@ $ make generate_mocks
9696
[[running-e2e-tests]]
9797
== Running e2e tests
9898

99-
We have automated e2e tests which keep CodeReady Containers in shape.
99+
We have automated e2e tests which keep CRC in shape.
100100

101101
[[intro-to-e2e-testing]]
102102
=== Introduction
103-
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.
103+
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.
104104

105105
[[how-to-run-e2e-tests]]
106106
=== How to run

packaging/rpm/crc.spec.in

+2-2
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Version: __VERSION__
1313
%global __os_install_post /usr/lib/rpm/brp-compress %{nil}
1414

1515
%global common_description %{expand:
16-
CodeReady Container's executable}
16+
CRC's main executable}
1717

1818

1919
%global golicenses LICENSE
@@ -22,7 +22,7 @@ CodeReady Container's executable}
2222

2323
Name: %{goname}
2424
Release: 1%{?dist}
25-
Summary: CodeReady Container's executable
25+
Summary: CRC's main executable
2626
License: APL 2.0
2727
ExcludeArch: armv7hl i686
2828
URL: %{gourl}

usage-data.adoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
= Usage data
22

3-
The following table describes the opt-in usage data collected by CodeReady Containers.
3+
The following table describes the opt-in usage data collected by CRC.
44

55
.Data points
66
|===
77
|Occasion | Data | Type
88

99
|*Install* | Host OS |
1010
| | Host OS version |
11-
| | CodeReady Containers version |
11+
| | CRC version |
1212
| | Installed using installers | true/false
1313

1414
|*Setup* | Error message |

0 commit comments

Comments
 (0)