---
title: Check method and parameters 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 method and parameters names for wording issues
---

# Check method and parameters 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.md). ().
{% /alert %}

{% /callout %}

## Metadata{% #metadata %}

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

**Language:** Ruby

**Severity:** Notice

**Category:** Best Practices

## Description{% #description %}

This rule helps ensure that you adhere to naming conventions that are inclusive, clear, and unambiguous. Instead of using terms like `master` and `slave`, which have offensive connotations, use neutral and descriptive terms like `primary` and `secondary`. Names you choose should be clear, descriptive, and considerate of the diverse backgrounds of those who might read or work with your code.

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

```ruby
def master(slave)
end
```

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

```ruby
def primary(secondary)
end
```
  Seamless integrations. Try Datadog Code SecurityDatadog Code Security 
{% icon name="icon-external-link" /%}