---
title: Check class names for wording issues
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > Code Security > Static Code Analysis (SAST) > SAST
  Rules > Check class names for wording issues
---

# Check class names for wording issues

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site). ().
{% /alert %}

{% /callout %}

## Metadata{% #metadata %}

**ID:** `ruby-inclusive/class-definition`

**Language:** Ruby

**Severity:** Notice

**Category:** Best Practices

## Description{% #description %}

In Ruby, class names should be meaningful and concise, and follow the naming conventions. Avoid using terms that might be considered offensive, derogatory, or otherwise inappropriate. Instead, use terminology that accurately represents the functionality or role of the class.

For instance, instead of using `MasterClass`, consider using `PrimaryClass`, `MainClass`, or another appropriate term that doesn't have potentially negative connotations.

## Non-Compliant Code Examples{% #non-compliant-code-examples %}

```ruby
class MasterClass
    def my_method
    end
end
```

## Compliant Code Examples{% #compliant-code-examples %}

```ruby
class PrimaryClass
    def my_method
    end
end
```
  Seamless integrations. Try Datadog Code SecurityDatadog Code Security 
{% icon name="icon-external-link" /%}